1.Our approach
Communities trust GTHRS with their members' names, emails, conversations, and payments. We keep that data to what's needed, protect it at every layer, and make it easy for you to take it with you.
2.Encryption and hosting
- Every connection to GTHRS uses HTTPS, and browsers are told to always use it (HSTS).
- GTHRS runs on Vercel, and data is stored in a Postgres database run by Neon in the United States, encrypted at rest.
- Uploaded files are stored with the same protections and reached through long, random links that can't be guessed.
3.Each community is kept separate
Every request runs inside one community. The database enforces this with row-level security, so even a mistake in our code can't show one community's data to another.
4.Accounts and sign-in
- Passwords are hashed with scrypt and a unique salt. We never store or see your password.
- Sign-in cookies are secure and HTTP-only, so scripts on a page can't read them. Sessions end after 30 days.
- Sign-in attempts are rate limited to stop password guessing.
- Password reset links expire after 2 hours, and invitation links after 14 days. Both are stored only as hashes.
5.Protections in the app
- Every action is protected against cross-site request forgery.
- Posts and other rich text are cleaned before they're saved, so they can't carry harmful code.
- Pages are sent with security headers that block framing, content sniffing, and unwanted access to the camera, microphone, and location.
- Roles (owner, admin, moderator, member, guest) decide who can see and do what, and important admin actions are recorded in an audit log.
6.Payments
Payments are processed by Stripe, a PCI DSS Level 1 certified payment provider. Card numbers go straight to Stripe and never touch GTHRS. Payment updates from Stripe are checked against Stripe's signature before we act on them.
7.AI
- AI features run on Anthropic's API, which does not train models on your data.
- The assistant only uses what the person asking is allowed to see.
- The assistant can only take an action, like posting or sending a message, after a person approves it.
- Members choose whether to connect their own AI assistant, and can disconnect it at any time.
8.API keys and integrations
- API keys are stored only as hashes and shown once. You can revoke a key at any time.
- AI connections use OAuth, so members sign in to GTHRS themselves and never share a password.
- Webhooks are signed, so your systems can confirm each message came from GTHRS.
9.Your data stays yours
- Owners can download their members and all of their community's content from admin settings at any time.
- Members can download their own data, or delete their account, from their profile.
- We never sell personal information or use it for advertising.
Our Privacy Policy explains what we collect, the companies that help us run GTHRS, and the rights you have under laws like the GDPR and California's privacy law. Community owners who need a data processing agreement (DPA) can request one from hello@gthrs.com.
10.Reporting a security issue
If you think you've found a vulnerability, email hello@gthrs.com with the details and steps to reproduce it. Please give us a reasonable chance to fix it before sharing it, and don't access or change other people's data while testing. We'll confirm we've received your report and keep you updated.