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
- Encrypted file content and encrypted filenames required to deliver a transfer.
- Transfer metadata such as encrypted size, creation time, expiry time, file count and status.
- Temporary anti-abuse identifiers derived from network information. Raw IP addresses are not intended to be stored in D1; the service uses keyed hashes for quota and abuse controls.
- Security and usage events needed for rate limits, quota enforcement, cost protection and operational troubleshooting.
- If you use transfer password protection, PsiDrive stores only a salted password verifier, not the plaintext password.
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.
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.
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.