Privacy
Corpus is a private notes app. This page describes the data stored to make it work.
Account data
Signing in creates an app user tied to your Clerk account id. Clerk handles authentication and may store the account details needed for sign-in, such as email addresses and session metadata.
Notes and folders
Notes, folder names, paths, document ids, timestamps, and version history are stored in PostgreSQL and associated with your account. Version history is used for note recovery.
Attachments
Uploaded images and files are stored in S3-compatible object storage under an account-specific prefix. Markdown stores the attachment links; the object storage keeps the file bytes, key, size, and content type.
API and MCP access
Personal access tokens are shown once, then stored only as hashes. Token names, prefixes, scopes, creation dates, last-used dates, revocation dates, and PAT/MCP write audit entries are stored for account security.
Browser storage
The browser stores small preferences such as language, sidebar state, and collapsed folders. Note content and personal access token plaintext are not intentionally stored in localStorage.
Sharing
Notes are not sold, used for advertising, or shared for marketing. Data is processed by the infrastructure providers needed to run the app, including hosting, authentication, database, and object storage providers.
Retention
Data stays until you delete it in the app or request account/data removal. Deleted notes try to remove unreferenced owned attachments; operational backups and logs may persist for ordinary service periods.
Data removal
To request account or data deletion, send a message to the contact address below.