Privacy

How we handle your data, in plain language.

What we store

Account info: Name, email, and session data so you can sign in and link calendars.
Saved event fields: Title, date, time, and duration for events you create so you can review, edit, export, or import them.
Parse history: If you turn it on, we keep previous parse results so you can clone or re-parse later. You can turn it off anytime.
Activity log: A timeline of actions (parse, export, import, link, unlink). Entries may include event titles, but never your raw text input.
Imported event ledger: When you import an event, we keep status, provider, and destination so you can track what happened.

Raw text input: Text you type or paste is used for parsing and not stored after parsing finishes. Only the structured output is kept.
Model context: The parser uses your text to extract scheduling details and returns structured data. Context is not kept between parses.
Calendar API calls: During import or conflict checks, we call your calendar provider API. We do not keep full request logs beyond the ledger status.

Parse history toggle: Turn parse history on or off in your profile.
Delete history entries: Remove individual entries with a 10-second undo window. After that, sensitive payload data is redacted.
Unlink calendars: Disconnect Google or Apple Calendar from your profile at any time.
Activity title visibility: Hide event titles in your activity log from privacy settings.

We do not sell, share, or use your data for advertising.
We do not train AI models on your input or output data.
We only access calendar data needed for the import, conflict check, and ledger features you run.
Calendar provider access tokens are stored encrypted and scoped to the minimum permissions required.