Careful with your notes, from day one.

Where your data lives

Obscribe runs on Amazon Web Services in the United States (us-east-1). Notes, tasks and accounts are stored in a managed PostgreSQL database with storage encryption on, inside a private network that only the application can reach. Every connection to obscribe.com and app.obscribe.com uses TLS, and browsers are told to use it always.

A backup of the database is taken every night and kept with a second storage provider, so a problem at one provider does not take the copy with it. A restore check that rebuilds a database from a backup is part of the system, and restores are rehearsed on a schedule.

Uptime for the app and the website is checked every minute from inside AWS and every three minutes by an independent service outside it. The status page shows the current state and any incidents.

Who can read your notes

Members of your workspace. Workspace owners manage the team and can delete anything; members can remove only the notes they wrote. Invitations are sent to a named email address, work only for that address, and expire after seven days.

Inside the database, every note, task, comment, decision and question carries its workspace, and PostgreSQL row-level security policies refuse a row to anyone who is not a member of that workspace. These policies are enforced by the database itself, not only by the application, so a missing filter in our code cannot show one team's notes to another.

The application connects with a restricted database role that cannot change the schema or bypass those policies. The availability monitor uses a separate role that cannot read notes, tasks or accounts at all.

Notes are not end-to-end encrypted: the application itself, and the person who operates the AWS account, can technically reach the database. Operators at Obscribe see account and billing details on a launch dashboard, with every action recorded in an audit log that cannot be edited. The dashboard shows no note content, passwords, authenticator secrets or AI keys, and there is no way to sign in as a customer.

Sign-in and sessions

• Passwords are stored as scrypt hashes with a per-password salt. We cannot read them.
• Two-step sign-in is available to everyone: a six-digit code from an authenticator app, plus ten single-use recovery codes. Authenticator secrets are encrypted at rest. Turning it on or off signs out your other sessions.
• Sign-in, password reset and sign-up are rate-limited, and public sign-up includes a bot check.
• Sessions use HTTP-only, same-site cookies. You can see your active sessions and sign the others out from Settings.
• Security events such as sign-ins, two-step changes, exports and member changes are recorded in a log the application can only add to.

Payments

Cards, invoices and receipts are handled by Stripe on Stripe's own pages. Obscribe never sees or stores your card number. We keep only the subscription state needed to know whether a workspace is on a trial or a plan.

The optional AI assistant

Obscribe has an optional assistant that can rewrite selected text, find decisions, questions and tasks in a note, draft a follow-up recap, answer questions about your workspace, or set up a new workspace from a short chat.

• It is off by default. Workspace owners decide whether it is available at all.
• It runs on your own API key from Anthropic, OpenAI, Google or a compatible service, so what you send is handled by the provider you chose, under its terms. Obscribe has no AI provider account of its own and never sends your notes anywhere unless you ask it to.
• Your key is stored encrypted, tied to your account, and never shown again after you save it.
• A rewrite is shown to you first and replaces your text only when you accept it. Everything else the assistant does adds something new; it never deletes your existing work.
• No bot joins your calls and nothing is recorded. Obscribe works from what you write.

Keeping and leaving

• Note history keeps earlier versions of a note, and you can restore one.
• Deleted notes wait in Trash for 30 days before they are removed.
• Owners can export the whole workspace as JSON and Markdown, and tasks as CSV, whether or not a plan is active.
• When a trial or plan ends, the workspace becomes read-only. Nothing is deleted.
• You can delete your own account from Settings. A workspace where you are the only member goes with it; where others depend on you, make someone else an owner first.

What we do not claim

Obscribe is a small company. We do not hold SOC 2, ISO 27001 or similar certifications today, and we do not say otherwise. If your organisation needs a security questionnaire answered, write to accounts@obscribe.com and we will answer it honestly.

Reporting a problem

If you believe you have found a security issue, email accounts@obscribe.com with the details. Please give us a reasonable time to fix it before sharing it publicly, and do not access other people's data while testing.