Security

How your workspace's data is kept apart from everyone else's, what is encrypted, what cannot be rewritten, and what is not in place yet.

Last updated 17 November 2026

Every workspace is isolated by the database

Each workspace's records carry its id, and PostgreSQL row-level security is enabled and forced on every one of those tables. The application connects as a database role that owns nothing, is not a superuser and cannot bypass those policies.

So isolation does not depend on every query remembering a filter. A query that forgets returns nothing, not someone else's data. A test discovers every table from the database catalog and fails if one is ever added without a policy, and the application refuses to serve if the role it connects as could bypass them.

History cannot be edited or deleted

The application has no permission to delete any customer record; removing something archives it. Activities, deal stage and date changes, and the audit log are append-only at the database level. The deal-change log and the audit log are written only by database triggers, so the application can read its own history but cannot author or alter it. “Who moved this close date, and when” has one answer.

Encryption and credentials

  • All traffic is served over HTTPS; the database is encrypted at rest by the provider.
  • Connected mailbox credentials and queued outgoing email are additionally encrypted with AES-GCM under a key held only in the deployment's secret store.
  • API keys and invitation links are stored as hashes, never as the key itself.
  • Passwords are handled by Clerk, the identity provider. This product has no password column.
  • Card details go to Stripe's hosted checkout and never reach this application.

Access inside a workspace

  • Roles — owner, admin, member and viewer — are enforced on the server for every action, not only hidden in the interface.
  • A connected mailbox is private to the person who connected it; nothing from it enters shared history unless they choose to share it.
  • API keys are scoped (read, read/write, or lead intake only), expire after 90 days, are rate-limited, and stop working when the person who created them leaves or loses admin rights.
  • Changes to roles, pipelines, fields and billing are recorded in an audit log owners can read.
  • Invitations, mailbox actions, exports and billing changes are rate-limited per person.

Backups and recovery

The database is copied daily in two ways: a point-in-time branch kept for seven days, and an encrypted export stored outside the database provider (on GitHub) for thirty days. Restores from both have been rehearsed and checked table by table against the source.

Your data stays yours

An owner or admin can export the whole workspace — accounts, people, deals, tasks, activity and history — at any time, including after a trial or subscription ends. Closing a workspace erases it; see the privacy notice for exactly what that does and does not reach.

What is not in place yet

  • No SOC 2, ISO 27001 or similar certification.
  • No independent penetration test has been carried out.
  • No single sign-on (SAML) or directory provisioning.
  • Data is hosted in the EU (Frankfurt) only; there is no choice of region.

Reporting a security issue

Write to the contact form at mindforgetech.net with “Security” in the subject. Please do not test against other customers' workspaces.