Privacy Policy
Who this covers. This policy describes how OrgHQ handles personal information across orghq.org and the websites, member hubs, and admin consoles we host for organizations. One relationship note up front: the information members submit to an organization (registrations, memberships, messages) belongs to that relationship — the organization is responsible for its member data and we process it on the organization's behalf to provide the service. Requests about a specific member record go first to the organization that holds it; we help either of you at any time.
What we collect. Account emails, the content organizations publish, and the details members submit when they register, join, or send a message (name, email, organization). Payment card details go directly to Stripe — we never see or store them.
How it's used. To run the service: signing you in, processing registrations, sending the emails you'd expect (confirmations, reminders, receipts, newsletters with unsubscribe links). We don't sell personal data or use it for third-party advertising.
Who sees it. Each organization sees only its own members' data. Our infrastructure providers (hosting, database, email delivery, payments) process data on our behalf under their own security commitments. A small number of named OrgHQ operators can also sign in to an organization's admin console — to provide support, and so an organization is never locked out if the person who set it up becomes unreachable. That access uses the same emailed sign-in code every admin uses, is recorded in our logs, and is stated on the organization's own Admin Team page; ask us any time who holds it.
Connected services (including Zoom). Organizations may connect their own accounts with services like Zoom, Stripe, and Resend. When an organization connects Zoom, we store its OAuth credentials encrypted (AES-256-GCM) and the details of meetings we create for its events (meeting ID, join link, passcode, dial-in numbers). After a meeting ends, we read Zoom's participant report (names and email addresses) once, solely to mark attendance against the event's own registration list — the report itself is not retained. Meetings we create are configured with cloud recording enabled, so the organization has a recording available in its own Zoom account for its members' on-demand library; the recording never leaves that Zoom account and is governed by the organization's own Zoom retention settings. We never access, download, or store recordings, transcripts, chat, or meeting content, and we never join meetings. Disconnecting Zoom in the organization's admin, or uninstalling the app from Zoom's side, deletes the stored credentials immediately.
Facebook Pages. An organization may connect its own Facebook Page so that events and news it publishes on its OrgHQ site are announced on that Page. When the organization's admin connects, we receive from Meta: their user id, the list of Pages they manage (name and id — shown once so they can choose one), and an access token, which we store encrypted (AES-256-GCM) together with the chosen Page's id and name. We use that access solely to publish the organization's own announcements to the organization's own Page. We do not receive or store Facebook profile information beyond the user id, and we never access friends, followers, messages, comments, insights, advertising data, or other Business Manager assets. Disconnecting in the organization's admin deletes the stored credentials immediately; removing the app from Facebook's settings does the same through Meta's deauthorization callback, and we honor Meta's data-deletion requests with a confirmation page.
Financial records. When an organization connects its Stripe account, we process its payment records (payer name and email, amounts, dates, and payment descriptions) to power its bookkeeping tools — recording dues and event revenue and, when the organization runs an import, summarizing its own Stripe payment history into its ledger. These records stay inside that organization's workspace, are used only for its own bookkeeping and reports, and are never sold or used for advertising. We do not collect bank account credentials or bank transaction data; if we ever add an optional bank feed, this policy will be updated first and the feature will be strictly opt-in.
This marketing site's analytics. On orghq.org itself (not on
organizations' own sites) we measure our own traffic first-party — no Google Analytics, no
advertising pixels, no third-party trackers. One cookie, oh_a, holds a random
identifier so a visit that starts on a marketing page and ends at signup counts once
instead of three times; when we occasionally compare two versions of a page, it also decides
which one you see. We store that random id with the page path and time. We do not store IP
addresses, user agents, names, or anything else that identifies you, and the id is never
linked to your account or shared. Events older than 180 days are deleted automatically, and
clearing your cookies resets the id. Because it is strictly first-party measurement with no
personal data and no ad tracking, there is no consent banner.
The demo tour. Opening the interactive demo asks for an email address. With it we keep the demo pages you visit, your browser type, whether you were on a phone or a computer, and your approximate location (city and state) — never your IP address or anything more precise. We use this to follow up personally and to fix the demo when it misbehaves in a particular browser. You may receive a handful of emails about OrgHQ afterward; each one has a one-click stop link, and replying to any of them reaches a person, not a system.
Retention & deletion. Data is kept while the organization's workspace is active; deleting a workspace removes all of its data, including connected-service credentials. Ask an organization to remove your record, or contact us and we'll help.
Security. Traffic is encrypted in transit (TLS 1.2+), credentials are stored encrypted, and each organization's data is isolated.
Your privacy rights (state privacy laws). Several states — including California (CCPA/CPRA), Colorado, Connecticut, and Virginia — give their residents rights over personal information. Where those laws apply to us, you can ask us: what categories of personal information we have collected about you and why (information); for a copy of it (access); to correct it (correction); to delete it (deletion); and to reconsider if we decline a request (appeal). We honor these rights without discriminating against you for exercising them. Three things those laws ask us to say plainly: we do not sell personal information, we do not share it for targeted advertising (we do no targeted advertising at all), and we do not use it for profiling or automated decisions with legal or similarly significant effects — so there is nothing to opt out of on those fronts, and browser signals like Global Privacy Control have nothing to switch off here. To exercise any right, use the support form at orghq.org/support, giving the email address associated with your record; we verify requests by confirming control of that email (a code, the same way sign-in works) and never ask for more information than verification needs. An authorized agent may submit a request on your behalf with proof of authority. Remember the relationship note above: if your record lives in an organization's workspace, the fastest path is often the organization itself, and we support them in responding.
Children. OrgHQ accounts and member hubs are for adults; the service is not directed to children under 13, and we do not knowingly collect their personal information. If you believe a child's information has reached us, contact us and we will delete it as the law requires.
Where data lives. We are a U.S. company and the service is hosted in the United States; if you use it from elsewhere, your information is processed in the U.S., where privacy laws may differ from your jurisdiction's.
Changes to this policy. If we make material changes, we will update the effective date above and post a prominent notice here (and, for changes that matter to workspace owners, email them). We keep prior versions available on request.
Contact. The support form at orghq.org/support reaches a person (or email support@orghq.org); postal mail reaches us at JJ Fisher & Co., LLC, PO Box 14, Bellbrook, OH 45305.