Privacy Policy
Last updated: 6 March 2026
deepcloud ("we", "us", "our") is committed to protecting your privacy. This Privacy Policy explains how we collect, use, and protect your personal information when you use our service at deepcloud.me.
1. Information We Collect
We collect information you provide directly: email address, full name, and account preferences. We also automatically collect usage data including IP address, browser type, device identifiers, pages visited, and actions taken within the platform. We do not use the contents of your files for advertising, analytics, or AI training. Files are encrypted at rest with AES-256-GCM. Because we provide previews, search, and sharing, our systems hold the key material needed to decrypt a file at the moment you request it, so we are technically capable of reading file contents; we do not do so. This is not a zero-knowledge system.
2. How We Use Your Information
Your information is used to: provide and improve the deepcloud service, authenticate your identity, send security alerts and product updates (with your consent), process payments via our payment processors, enforce our Terms of Service, and comply with legal obligations. We never sell your personal data to third parties.
3. Encryption Model
deepcloud encrypts your files at rest with AES-256-GCM, using a unique key derived for each file. Encryption and decryption take place on our servers, not on your device. We therefore hold the key material and are technically capable of decrypting your files, including where compelled by law. We do not read your file contents, and we do not build any product feature that requires doing so. This is server-side encryption at rest. It is not zero-knowledge encryption, and we do not describe it as such.
4. Connecting Third-Party File Providers
You may connect a third-party storage account to deepcloud so you can import files from it. When you do, we request read-only access to files you select, and we use that access solely to copy those files into your deepcloud vault. Specifically, connecting Google Drive requests the scope https://www.googleapis.com/auth/drive.readonly, which allows us to list and read the files in your Drive at the moment you ask us to. It does not allow us to modify or delete anything in your Drive, and we do not write to it. We also request your email address (https://www.googleapis.com/auth/userinfo.email) to label the connection so you can recognise it. Access is granted per-account under your control, can be revoked at any time by disconnecting the provider or removing the app from your Google account settings, and we delete the stored credentials when you disconnect. Connecting Dropbox requests three read-only scopes, and no others: files.metadata.read, to list the contents of the folder you open in the import picker; files.content.read, to download the specific files you choose to import; and account_info.read, solely to display which Dropbox account is linked so you can recognise it. We do not request any Dropbox permission to write, modify, move, rename, delete or share anything, and we make no such request at any point. We never write back to Dropbox, and we do not read whole folders recursively. Dropbox access can be revoked at any time by disconnecting the provider or by removing DeepCloud from your Dropbox account's connected apps, and we delete the stored credentials when you disconnect. Connecting Microsoft OneDrive requests three delegated permissions, and no others: Files.Read.All, to list folder contents and download the files you choose to import; User.Read, to display which Microsoft account is linked so you can recognise it; and offline_access, so the connection can be refreshed after your access token expires without asking you to sign in again. offline_access grants no additional ability to read your OneDrive and no ability to write to it. We request no Files.ReadWrite, Files.ReadWrite.All, or Share permission, so we cannot create, edit, move, rename or delete anything in your OneDrive. OneDrive access can be revoked at any time by disconnecting the provider or by removing DeepCloud from your Microsoft account's connected applications, and we delete the stored credentials when you disconnect. Our OneDrive connection works with personal Microsoft accounts as well as work and school accounts. For a work or school account, your organisation's administrator may need to approve the deepcloud connection before it can be used; we do not request administrator access to your organisation and cannot grant that approval ourselves. Connecting Box requests one scope: root_readwrite. This is wider than it sounds, and we want to be plain about why. Box requires the read/write scope merely to download a file: when only its read-only scope is enabled, Box lets an app list your folders, read file details and generate previews, but refuses every file download with an insufficient permission error. We asked for the narrower scope first and Box's own support confirmed that downloading requires the read/write scope, so we request it in order for importing to work at all. We use that access only to list the folders you open and to copy the specific files you select. We do not write, modify, move, rename or delete anything in your Box account, and we make no such request at any point, although the permission Box grants us would technically allow it. We request no write_app, delete_app, or admin permissions, so we cannot change the configuration of your Box account, create or delete applications, or administer your account. Box access can be revoked at any time by disconnecting the provider or by removing DeepCloud from your Box account's connected apps, and we delete the stored credentials when you disconnect. For every provider we use the access only to list folders you open and to copy the specific files you select, we never write back to the provider, and we do not read whole folders recursively. Importing from any provider requires a paid deepcloud plan; the free plan does not include provider import. We never access your provider account unless you choose to connect it. Once a file is imported it is encrypted by us and held by us; we do not retain a continuing connection to your provider in order to read it later, and we do not use provider contents for advertising, analytics, or AI training.
| Provider | Permissions requested | Write access |
|---|---|---|
| Google Drive | drive.readonly | None |
| Dropbox | files.metadata.read, files.content.read, account_info.read | None |
| OneDrive | Files.Read.All, User.Read, offline_access | None |
| Box | root_readwrite | Not exercised: Box requires its read/write scope to allow downloads at all. We only ever read. |
5. Data Sharing
We share data only with: (a) payment processors (Stripe, Paystack and Lemon Squeezy) to process payments, (b) Twilio for SMS authentication and notifications, (c) Resend for transactional email, (d) infrastructure providers bound by strict data processing agreements — Supabase for authentication and the database, Cloudflare for file storage and content delivery, and Vercel for application hosting — (d) the cloud storage provider you choose to connect (Dropbox, Google Drive, Microsoft OneDrive or Box), which receives your OAuth authorisation and the metadata of the files you choose to import so it can authenticate you and return those files to us, and (e) law enforcement when legally required. We require these providers to process data under written terms that limit them to the purpose we engage them for. Where a provider acts as a controller in its own right under data protection law, we identify them here rather than describing them as simply compliant.
6. Data Retention
Active account data is retained as long as your account exists. After account deletion, personal data is removed within 30 days. Encrypted file data is removed immediately upon deletion. Audit logs are retained for 12 months for security purposes, then permanently deleted.
7. Your Rights (GDPR / CCPA)
You have the right to: access your personal data, correct inaccurate data, delete your account and all associated data, export your data in a portable format, opt out of marketing communications, and restrict or object to processing. Exercise these rights at any time from your Profile settings or by emailing [email protected].
8. Cookies
We use essential cookies for authentication (session tokens) and preference storage. We do not use tracking cookies or third-party advertising cookies. You can manage cookie preferences in your browser settings. Our Cookie Policy at /cookies has the detail.
9. Security Measures
We implement: AES-256-GCM encryption of files at rest, TLS 1.3 for data in transit, bcrypt password hashing, malware and content scanning on upload, rate limiting, and row-level database security. Credentials for connected third-party providers are encrypted at rest in our database, separate from the keys used for your files. We are not yet SOC 2 certified. Despite these measures, no system is 100% secure.
10. Children's Privacy
deepcloud is not directed to children under 13. We do not knowingly collect personal information from children. If we become aware that a child under 13 has provided personal information, we will delete it immediately.
11. Changes to This Policy
We may update this Privacy Policy periodically. We will notify you of significant changes via email or in-app notification at least 30 days before changes take effect. Continued use of deepcloud after changes constitutes acceptance.
12. Contact Us
For privacy-related questions: email [email protected]. We do not publish a postal address on this site, because we would rather leave it out than print one we cannot stand behind. If a written response is required for your records, email us and we will provide what we are able to.
