Skip to content
← Back to Settings

Privacy Policy

Last updated: May 6, 2026

What Beckett Collects

When you use Beckett, we store the information you share in conversation: notes, entities (people, projects, places), categories, and your message history. If you connect third-party accounts or device services, we store the credentials needed to access those services on your behalf.

Where Your Data Lives

Your data is stored in a PostgreSQL database hosted on Railway (US-based infrastructure). Each user's data is isolated at the database level — your data is completely isolated and only accessible to your account.

AI Processing

Beckett uses OpenRouter to route conversation requests to zero-data-retention third-party AI model providers. Beckett also uses OpenAI for text embeddings that power semantic search. These providers process your data only to provide Beckett features and do not use it to train their models. Your conversations are not used for advertising or model training by any party.

Who Can See Your Data

Beckett operators may access account metadata (email, usage statistics) for debugging and support purposes. We do not read your notes, messages, or entity data unless you explicitly ask us to help with a support issue.

Your Rights

  • Export your data — Download everything Beckett knows about you as a JSON file from Settings.
  • Delete your account — Permanently remove your account and all associated data from Settings. This action is irreversible.
  • Request support — Contact us if you have questions about your data or need help exercising your rights.

Google Integration & Limited Use Disclosure

When you connect your Google account, Beckett requests access to the following scopes:

  • gmail.readonly — Read your emails so Beckett can summarize and triage your inbox.
  • gmail.send — Send emails on your behalf when you ask Beckett to draft and send a message.
  • calendar.readonly — Read your calendar events so Beckett can brief you on your schedule.
  • calendar.events — Create and update events when you ask Beckett to manage your calendar.
  • contacts.readonly — Read your contacts to auto-populate your knowledge graph with people you know.

How Google data is handled:

  • Google data (emails, calendar events, contacts) is accessed on-demand and processed in-memory. It is not stored in our database, except for the Google email address associated with your credential.
  • OAuth tokens are encrypted at rest using Fernet symmetric encryption.
  • Disconnecting your Google account or deleting your Beckett account revokes your tokens at Google.
  • Google data is used solely to populate your personal knowledge graph and respond to your requests. It is not used for AI model training.
  • Google data is not sold, shared, or transferred to any third party for advertising, analytics, or any other purpose.

Beckett's use and transfer of information received from Google APIs to any other app adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Colorado Privacy Act

We acknowledge the Colorado Privacy Act and respect your rights under it, including the right to access, correct, and delete your personal data, and to opt out of targeted advertising (which we do not engage in).

Changes

If we make meaningful changes to this policy, we'll notify you through the app. Continued use after changes constitutes acceptance.