Privacy and security notes
This page explains the technical boundaries and security model of CleanDoc. It is a product guide explaining our data isolation principles, not a substitute for our Privacy Policy.
Authenticated file access
CleanDoc isolates user data strictly at the account boundary. Dashboard and document API routes require a verified authenticated session token. Database queries for folders, sections, and documents are explicitly scoped to the authenticated user's ID.
Uploaded documents are never exposed through a public web root. When you request a document preview, the server issues a time-limited signed URL or streams the file only after confirming document ownership in the database.
What you should do
- Use a strong, unique password: Never reuse email passwords, and keep your login credentials private.
- Maintain independent backups: Always keep a local copy of important coursework or lab manuals on your device or university cloud drive.
- Avoid uploading sensitive credentials: Do not upload documents containing unencrypted API keys, database credentials, passwords, or personal financial information.
- Sign out on public computers: When accessing CleanDoc in campus computer labs or shared library terminals, remember to sign out of your session completely.
Platform boundaries & commitments
CleanDoc does not sell your uploaded files or training data. Our storage and cloud infrastructure providers operate under strict data protection standards. Previews, in-browser rendering, and file types are optimized for modern academic documents.
Questions or support
If you notice suspicious activity or have questions about data handling, please reach out to our team at [email protected]. For legal terms governing service usage, refer to our Terms of Use.