Privacy Policy

Effective 2026-07-19. Applies to obsideo.io, the Obsideo storage service (signup.obsideo.io, s3.obsideo.io), the obsideo-cli package, and the Obsideo MCP server / desktop extension.

The short version: Obsideo is built so we hold as little as possible. Encryption keys are generated and kept on your machine; we never receive them. Content you encrypt before upload is unreadable to us and to storage providers. We collect what a storage account needs to function (your email, usage totals, operational metadata) and we do not sell or share it for advertising.

1. What we collect

Account identity: your email address. It is the account identifier and recovery anchor. Routing-equivalent aliases (dots, plus-tags) are collapsed to one identity.
Signup metadata: IP address, user agent, and the optional self-reported "source" field at signup. Kept for abuse prevention and to understand how people find us.
Stored data: the object bytes you upload (as sent: encrypted if you encrypt them), object keys (names), sizes, and content hashes. Object keys are stored in the clear, so avoid putting sensitive information in file names.
Operational data: storage usage totals, replication and proof-verification records, and service logs (requests, errors) needed to run and secure the network.
What we do NOT collect: your encryption keys or your account signing key (only its public half is sent to us); plaintext of content you encrypted client-side; payment card data for the free tier (there is no card).

2. The local extension and CLI

The Obsideo MCP server and CLI run entirely on your machine. Your S3 credentials, your Ed25519 account signing key, and any client-side encryption key live in local configuration files (for the MCP server, ~/.obsideo/mcp.json). They are transmitted only as required to use the service (credentials authenticate S3 requests to s3.obsideo.io) and are never sent to any other party. We do not operate, host, or have access to your local extension. Conversation content from your AI assistant is not collected by Obsideo; only the specific tool calls it makes (for example, an upload) reach our service.

3. How we use data

Operating the service: storing, replicating, verifying, and serving your objects.
Abuse prevention: velocity limits and anomaly detection on signup metadata.
Service communication: verification codes and, if enabled, operational notices to your email.
Understanding growth: aggregate signup and traffic statistics. The optional "source" field is used only for this.

We do not sell personal data. We do not share personal data with third parties for their marketing. We do not train AI models on your data or content.

4. Where data lives, and third parties

Storage providers: object bytes are replicated to independent storage providers on the Obsideo network. Providers hold bytes as sent; if you use the encrypt-first pattern, they hold ciphertext they cannot read. Providers never receive your email or account identity.
Subprocessors: email delivery (Resend, for verification codes and notices), network and DDoS protection (Cloudflare), coordination infrastructure (DigitalOcean), and site hosting (Netlify). Each receives only what its function requires.

5. Retention and deletion

Objects you delete are removed from the active network by signed delete instruction; provider copies of uncontracted data are pruned by the network's economic model and garbage collection.
Account records are kept while the account is active. Contact us to close an account and remove its records.
Signup and operational logs are kept only as long as needed for security and debugging.
Important: if you lose your client-side encryption key, your encrypted content is unrecoverable by design. We cannot decrypt it, reset it, or recover it for you.

6. Security posture

End-to-end encryption is architectural, not a policy promise: keys never enter Obsideo's systems, so no operator access to our infrastructure can decrypt client-side-encrypted content. Deletes require your cryptographic signature; the platform cannot destroy your data unilaterally. Stored objects are challenge-verified with cryptographic proofs every 4 hours.

7. Your choices and rights

Use the encrypt-first pattern for anything private: then even Obsideo cannot read it.
Request a copy or deletion of your account data by emailing us from your account address.
Depending on your jurisdiction (for example GDPR or CCPA), you may have additional rights of access, correction, deletion, and portability. Email us and we will honor them.

8. Changes and contact

We will update this page when practices change and adjust the effective date above. Questions, requests, or concerns: [email protected].