Privacy at Postern.
We built Postern because the security tools we'd want as founders don't exist. That includes the privacy posture.
What we store.
- Your email address. We don't store your password at all; authentication is handled by Clerk, our authentication provider, which we don't control and never sees your assessment data.
- Your company name, if you give us one.
- Your assessment responses.
- Which recommendations you've marked done, in progress, or skipped.
What we don't store.
- Any analytics. No Google Analytics, no Mixpanel, no Segment.
- Any third-party JavaScript that loads from outside trypostern.com, with two exceptions: Tailwind CSS loads from a CDN, and Clerk's authentication SDK. We'll host Tailwind ourselves before we leave preview.
- Any tracking cookies. The only cookie we set is your login session, managed by Clerk.
- Your responses are never used to train any AI model. We don't have one. We don't plan to.
Third-party dependencies.
We use Clerk (clerk.com) to handle authentication. Clerk holds your email address and the password you set with them; we never see your password. Clerk's privacy policy is at clerk.com/privacy. We use Clerk because rolling our own authentication is one of the easiest things to do badly. The trade-off is one external dependency for substantially better security.
When you delete your Postern account, we also delete your Clerk account so neither system retains your data.
We use Neon (neon.com) to host our production database, provisioned through Replit. Neon stores your assessment responses, account data, and roadmap progress; it does not access or use this data beyond running the queries our application sends it. Neon's privacy policy is at neon.com/privacy-policy.
Where it lives.
A managed PostgreSQL database, provisioned through Replit and run on Neon's infrastructure. We moved off a single local file because it didn't reliably survive our own deployment process — a file that can silently disappear is a worse privacy outcome than a database that reliably keeps what it promises. One production database. Authentication identity lives with Clerk, not in our database.
How to delete everything.
Account, then Delete account. Hard delete, no soft-delete, no recovery, no waiting period. The only record we keep afterward is an audit-log entry confirming the deletion happened. Your user ID is removed from it.