Privacy Policy
Who this covers. This policy describes how OrgHQ handles personal information across orghq.org and the websites, member hubs, and admin 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 — 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 and its demo (not on
organizations' own sites) we measure our own traffic first-party — no Google Analytics, no
advertising pixels, no third-party trackers. A 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, and nothing else:
no IP address, user agent, name, or anything else that identifies you goes with it, and the
id is never linked to your account or shared. When the link that first brought you here carried a
campaign tag such as ref or utm_source in its address, a second cookie named
oh_ref keeps that first tag alone and drops any that looks like an email address so we can tell which of our
emails and posts bring people; we store it with the same random id and with any workspace you create.
Events older than 180 days are deleted automatically, and
clearing your cookies resets the id and the tag. Because it is strictly first-party measurement with no
personal data and no ad tracking, there is no consent banner.
The demo tour and the board one-pager. The interactive demo opens without an email address. If you choose to leave one (to have the link sent to you), we keep the demo pages you visit and the campaign tag of the link that first brought you, 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. If you make a board one-pager, we keep your email address, your organization's name, and any current costs you enter, with the same browser, device, and location details. We use this to follow up personally and to fix the demo when it misbehaves in a particular browser. Either way, you'll receive a short series of emails about OrgHQ over the next two weeks, and after that an occasional note when something new ships. Each one has a one-click unsubscribe link, replying to any of them reaches a person, not a system, and we never share your address.
Retention & deletion. Data is kept while the organization's workspace is active. Deleting a workspace removes its records, its uploaded files, and its connected-service credentials. Ask an organization to remove your record, or contact us and we'll help. If you have ever been a workspace admin, we keep your email address on a do-not-market list, even after the workspace is deleted, so our sales email never reaches you.
Private messages between members. Deleting a conversation removes it from your view only; the other member keeps their copy. Conversations in Trash are deleted for good after 30 days. A message is erased from our database once both people have deleted it (or the other person's account is gone), except while an admin is reviewing a report about that conversation.
Questions to Ask OrgHQ. When a workspace admin asks Ask OrgHQ (the help assistant in the admin) a question, we keep the question, its answer and whether it helped for one year, so we can improve OrgHQ’s help. Email addresses, phone numbers and anything that looks like a password or key are removed before it is stored, and nothing about the association’s members is sent with it.
AI features. Some tools draft text with AI: the pages, events and news copied in from an association’s current website, a news post, welcome email or translation an admin asks for, Ask OrgHQ’s answers, and replies to messages sent to OrgHQ support. To write a draft, we send the text it needs (the association’s own pages, events and posts, or what the admin typed) to Anthropic, the AI company listed among the companies that process data on our Security page. Email addresses and phone numbers are taken out first, and no member records are sent. AI only drafts: nothing it writes is saved, published or sent until an admin (or, for a support reply, a person at OrgHQ) has read it and chosen to.
AI agents and the API. An AI assistant can set a workspace up through our API for the person it works for. The person proves their email with a code we send them, and pays through Stripe themselves. The assistant receives a key that acts as that admin; an admin can also create keys in Settings. We store only a fingerprint of each key (a hash), never the key itself, and record when it was made and last used. An admin can revoke a key at any time, and it stops working when the admin it acts as is removed or the workspace closes. When an assistant reports a problem to us, we keep its report, with keys, codes and passwords removed, so we can fix the problem.
Messages to OrgHQ support. When you write to OrgHQ support, we keep your message and our reply so we can help you and follow up. We may have AI draft a reply from your message and from facts about your workspace’s setup (never your members’ records); a person at OrgHQ reads every reply, edits it as needed and sends it.
Reading a website you name. When you ask orghq.org for a preview of a website, or an admin gives a website’s address to import, we read only the public pages of that website: what anyone can see without signing in. A preview is drawn for you and not kept. An import copies the pages, events and news it finds into that workspace as drafts, which stay there until the admin publishes or deletes them.
Stories. OrgHQ publishes interviews with association leaders on orghq.org. A story is published only after the person interviewed has approved its text, and with a photo only if they gave one. Ask us and we will take a story, or its photo, down.
Our sales email. To tell associations about OrgHQ, we keep business contact details that associations publish on their own public websites (an officer’s name and role, and the association’s published email address) and write to them personally. We send at most two emails to an address, each with our postal address. Reply “no thanks” and we will never write to that address again.
Backups. We keep encrypted backups so that a mistake or an outage is survivable, and a deletion therefore takes a little while to reach every copy. Daily backups are kept for 30 days and weekly ones for 180. A monthly archive is kept long-term, because continuing-education records are the kind of thing a member may need proof of years later. Files deleted from storage are held for 90 days before being removed from the backup copy as well. Backups are never used to bring a deleted workspace back, and are not searched or read except to recover from a failure.
Security. Traffic is encrypted in transit (TLS 1.2+), credentials are stored encrypted, and each organization's data is isolated.
Abuse protection. To keep sign-in and public forms from being abused, we count recent requests from each network (IP) address — sign-in codes asked for and tried, and messages, registrations, and sign-ups sent — and refuse more past a limit. The same counters let a job posting's view count include each connection once a day. A counter holds the address and a number, is not linked to your account or to what you sent, is used for nothing else, and is deleted within two days. Messages sent through an organization's contact form, and to us through the support form, are checked automatically for spam. One that looks like spam, or comes from an address the recipient has marked as spam, is still kept in the inbox but is not emailed on. Marking a sender as spam keeps that email address on that inbox's blocked list until someone unblocks it.
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; postal mail reaches us at JJ Fisher & Co., LLC, PO Box 14, Bellbrook, OH 45305.