PRIVACY

Privacy by design, with minimal server-side knowledge.

This summary explains what PsiDrive processes in the current V1 service and what it intentionally avoids storing.

What PsiDrive processes

Encryption keys

The AES transfer key is generated in the browser. The production share link places that key after the # fragment. URL fragments are handled by the browser and are not sent as part of the normal HTTP request to the server.

Retention

Guest transfers are designed for 24-hour retention. A transfer configured for delete-after-first-download is deleted after the first successful completed download. Automated cleanup also handles expired transfers and abandoned multipart uploads.

Account deletion

Signed-in users can permanently delete their account from the PsiDrive iOS app after confirming their current password. Deletion cancels any future subscription renewal, removes stored encrypted files and transfer links, and erases the account email, credentials, sessions and active entitlements. Limited billing and transaction records may be retained only where required for tax, fraud-prevention or other legal obligations.

Infrastructure

PsiDrive is built on Cloudflare services including Workers, R2, D1, Pages and Turnstile. Cloudflare may process traffic and operational data as part of providing those services under its own terms and privacy commitments.

Aggregate product analytics

PsiDrive counts a small set of product events in daily aggregates, grouped by public page, broad device category and broad referrer category. These growth events do not include filenames, file contents, complete share links, URL fragments, encryption keys, transfer identifiers, recipient identities, email addresses or IP addresses. A local boolean may remember that this browser completed a prior upload so a later upload can be counted as returning; it is not an account or cross-site identifier.

What you should not upload

PsiDrive V1 should not be used for regulated or specially protected data where a specific contractual or compliance framework is required. In particular, do not use V1 for payment-card authentication data or protected health information unless the required agreements and controls have been formally implemented.

This page describes the current product design and is not a legal certification of GDPR, India DPDP, HIPAA, PCI DSS or any other regulatory regime.