Privacy & Data Safety
Chronicle is built as a private personal archive. This page explains what is stored, when AI transcription is used, and which controls you have over your data.
Your Chronicle is account-scoped
Chronicle data is private by default and protected by account-scoped access controls so your cycles, images, and transcriptions are tied to your signed-in account.
Chronicle is not a social feed
Public sharing is not enabled by default.
Email code sign-in
Chronicle uses one-time email codes for account access.
Row-level access rules
Database access is scoped so users can only read and write rows tied to their own account.
You decide when AI is used
Transcription is optional per entry. If transcription is not requested, that page is not sent to OpenAI.
What is sent when requested
The selected page image(s) and formatting instructions are sent through Chronicle's server route. Visible handwriting and details on the page may be included.
Server-side API handling
The OpenAI API key is not exposed in your browser.
No content review by default
Phoenix Planner does not read the contents of Chronicle records except when you explicitly request content-processing features, such as AI transcription, or when limited access is required by law or to protect the security and integrity of the service.
Encrypted transport and storage
Chronicle relies on managed infrastructure that provides encrypted transport and encrypted storage at rest.
Layered controls
Protection comes from multiple layers: authentication, database policies, private object storage, and server-side processing.
Review and edit transcriptions
You can revise transcription text inside your cycle document.
Export and delete
You can export account data and delete cycles from Account.
What we claim
Chronicle is designed to reduce risk with private-by-default architecture and layered technical controls.
What we won't claim
No online system has zero risk. We choose clear disclosures over false certainty.