OrgHQ

Association Platform

Create Your SiteGet started

Security and Your Data

Draft. This page is being reviewed and may change.

What a board or a treasurer usually asks before choosing OrgHQ, answered plainly. If a question isn’t here, contact us.

Where your data lives

The application runs on Cloudflare Workers. Each association’s records are kept in a Neon Postgres database, and its uploaded files (board files, receipts, logos, form attachments) in Cloudflare R2 storage.

Encryption

Every page and every request is served over HTTPS (TLS 1.2 or later), and browsers are told to use HTTPS only, for a year at a time (HSTS). The keys an association connects (Stripe, email, Zoom, Facebook) are stored encrypted with AES-256-GCM, so the database alone never reveals them. Database backups are encrypted before they are stored.

Each association’s data is kept apart

Every record an association keeps carries the workspace it belongs to, and every query the application makes is limited to one workspace. The database adds a second layer of the same rule: row-level security policies on the tables that hold associations’ records.

Signing in

There are no passwords to steal, reuse or reset. Admins and members sign in with a 6-digit code emailed to them, or a link that works once; codes and links expire, and repeated wrong guesses are refused. An admin’s session lasts a day, and Sign Out signs that person out on every device. A board member tagged in People can reach the website and the directory, but not money or setup.

Backups

The database can be restored to any moment in the last 7 days (Neon’s point-in-time restore). Every night it is also copied, checked, encrypted and stored in two places, Cloudflare R2 and GitHub, and uploaded files are copied to a separate backup bucket. Daily backups are kept for 30 days and weekly ones for 180, and a monthly archive is kept long-term. The database backups are encrypted to a key that is kept offline: the services that store them cannot read them.

Exporting and deleting your data

One button under Setup downloads everything: people, events, registrations, dues history, board files, forms and the books with their receipts, as ordinary files (CSV and PDF) any product can read. It keeps working even after a plan ends. To delete a workspace, contact us with an address on its Admin Team as yours: we reply to that address before anything is deleted. Deleting it removes its records, its uploaded files and its connected-service keys, and the backups age out on the schedule above. Our privacy policy has the details.

Who processes your data

These companies process data for OrgHQ, each only for the job named here:

  • Cloudflare: Runs the application (Cloudflare Workers), serves every page over HTTPS, stores uploaded files (R2), and holds the encrypted nightly backups. Always.
  • Neon: The Postgres database that holds every workspace’s records. Always.
  • Stripe: Takes payments: the OrgHQ plan, and members’ payments to the association, which go to the association’s own Stripe account. Card and bank details go straight to Stripe; OrgHQ never sees or stores them. For the OrgHQ plan; for member payments once the association connects Stripe.
  • Resend: Delivers email: sign-in codes, receipts and reminders, and the association’s member email. Always.
  • GitHub: Holds an encrypted copy of the nightly database backup for 90 days. It cannot read it: only the private key, kept offline, can. Always.
  • Zoom: Creates meetings for the association’s events and reports who attended, in the association’s own Zoom account. Only if the association connects Zoom.
  • Meta (Facebook): Posts the association’s events and news to its own Facebook Page. Only if the association connects a Facebook Page.
  • Anthropic: Writes drafts that a person reads before anything is saved, published or sent: the pages of an association’s current website brought in as drafts, a news post, welcome email or translation an admin asks for, Ask OrgHQ’s answers, and replies to messages sent to OrgHQ support. It receives only the text the draft needs, with people’s email addresses and phone numbers taken out first, and never member records. Only when one of these is used: a website import, a draft or translation an admin asks for, Ask OrgHQ, or a support reply.

Certifications

OrgHQ does not hold a SOC 2 report, an ISO 27001 certificate or any other security certification, and does not claim to. The practices on this page are what we can show you.

For your treasurer

Request OrgHQ’s W-9 and we’ll email it. Questions about security, or a form your board needs filled in: contact us.