Privacy notice
Plain English, and specific. Every statement here was checked against how the product actually works, not against how we would like it to work. If anything is unclear, write to hello@farband.co.
Last updated 17 October 2026
Farband is a supporter CRM for organizations: one record per supporter, holding their donations, event signups, form answers, advocacy actions and an activity timeline. Farband is made by OrgKit, a software studio for mission-driven organizations.
In this notice, “we” means the people who build and run Farband. An “organization” is a group that uses Farband to run its work. A “supporter” is a person in an organization’s database: a donor, volunteer, member, event guest or petition signer.
For supporter data, we act for the organization. When an organization keeps its supporters in Farband, the organization decides what to collect and why, so it is responsible for that data (the “controller”). We store and process it on the organization’s behalf and on its instructions (the “processor”). If you are a supporter, the organization you gave your details to is the first place to ask about them. We help it answer.
For our own accounts and our own website, we decide. That covers staff accounts (the people at an organization who sign in to Farband), people who book a demo or write to us, and visitors to farband.co.
Only to provide Farband to the organization: keeping its records, sending the email it chooses to send, running its events, forms and reports, and keeping the system secure and working. We do not sell supporter data. We do not use it to market our own services to supporters. We never combine one organization’s supporters with another’s: the same person in two organizations is two unrelated records, and the database itself keeps them apart. We do not train AI models on it, or on anything else.
A short list of service providers help run Farband: Neon (the database), Vercel (hosting and file storage), Resend (email), Anthropic (the AI features), PostHog (usage analytics), Cloudflare Turnstile (the spam check on public forms), Google (staff sign-in) and Slack (our own operations alerts). The US Census Bureau’s geocoder receives a supporter’s street address, city, state and ZIP code, and nothing else, to find their congressional and state legislative districts. The sub-processor list says exactly what each one receives, and AI and your data covers the AI features in detail. An organization can turn AI off with one switch (its owners and admins, under Admin, Branding & naming); while it is off, nothing about that organization or its supporters is sent to Anthropic.
Automations never post to our operations Slack. The old supporter-journey Slack step is retired and sends nothing. A project workflow rule can post to the organization’s own Slack channel, and only once its owners or admins have connected that channel.
Some flows happen only because the organization switched them on and connected its own account, so the data goes to its vendor under its own contract: its EveryAction account, its Cal.com account, its own Google Analytics, Google Ads or Meta pixel, its own Slack channel, or a webhook address a staff member typed in.
In the United States. The database is Neon Postgres on Amazon Web Services in us-east-1 (Northern Virginia), and the app runs on Vercel in the United States. Uploaded files (images and attachments) are stored in Vercel Blob and delivered through Vercel’s global network.
Supporter records are kept for as long as the organization keeps them, or until it leaves Farband. A few things have their own rules:
If you are a supporter, contact the organization that holds your details. Its staff can see, correct, export and delete your record in Farband. You can also do some of this yourself: emails from the organization carry a link to your own preferences page, where you can update your contact details, unsubscribe, change how often you hear from it, and manage event registrations. If you cannot reach the organization, write to hello@farband.co and we will pass your request on and help it answer.
If you are an organization, your staff can view, edit, export and delete supporter records directly. For anything the product cannot do, write to us.
The organization can ask us to delete its whole workspace. We export its data first, then hold a grace period (1 to 90 days, 30 by default) during which the deletion can be cancelled. Then, in one step, every row carrying that organization’s id is removed from the live database, including its audit log, and its uploaded files are deleted from file storage. The 7-day backup history still holds it for 7 more days. If we gave the organization an export file, we destroy our copy once it confirms it has it. We keep one permanent line saying the workspace existed, its name, when and why it was deleted, by whom, and how many rows were removed from each table. That line holds no personal data about any individual.
When an organization adds a staff member, we hold their name, email address, role and permissions, sign-in method (a password hash, a passkey, or Google sign-in), two-factor settings, and a record of their sign-ins and of what they change. We use this to let them sign in, to keep accounts secure (for example locking an account after repeated failed sign-ins, and alerting us to a sign-in from an unexpected country), and to keep the audit trail.
Alerts and bug reports that reach our Slack can name a staff account and include what the staff member wrote in the report. Staff account data is kept while the account exists; sign-in and change history is part of the audit log, which is kept forever. When an organization leaves, its staff accounts go with it.
If you book a demo on farband.co, the booking calendar is run by Cal.com, which receives your name, email address and anything else you type into the booking form. The booking is then saved as a contact in our own Farband workspace so we can follow up, and is kept until we delete it. If you email us, we keep the email so we can reply.
We use PostHog to count anonymous page views in Farband and on farband.co, and for nothing else. What PostHog receives:
That is all. We never use PostHog’s “identify” feature and no person profile is ever created. Automatic click capture, session recording, heatmaps and surveys are all switched off in the product’s code, so PostHog never sees the text on a page.
On an organization’s public pages (forms, petitions, event pages and chapter pages), PostHog only starts after the visitor chooses “Accept all”. On farband.co and inside the staff app there is no banner, and PostHog counts every visit.
Separately, the staff app keeps its own first-party usage counts, in Farband’s database and nowhere else: how many times each page, profile section and control was used per day and per role, with no person, no record and no typed text, visible only to the Farband operator, who uses them to decide what to improve.
Farband uses cookies the service needs to work: keeping a staff member signed in, the spam check on public forms (Cloudflare Turnstile, which looks at browser signals to tell people from bots), and remembering a visitor’s cookie choice. Where PostHog runs, it keeps its anonymous ID in a cookie and in the browser’s local storage.
On an organization’s public pages, a banner asks visitors to choose “Accept only necessary” or “Accept all”. Only “Accept all” turns on analytics (our PostHog, and the organization’s own Google Analytics, Google Ads or Meta pixel if it set them up) and the cookie that remembers where a visitor first came from.
Fonts: every font is served by Farband itself, including the ones an organization picks for a themed public page, so loading a page does not contact Google Fonts or any other font service.
We do not claim any certification. Farband is designed with SOC 2 readiness in mind.
Farband is a tool for organizations, not a service for children, and we do not collect children’s data for our own purposes. If an organization records information about young people, for example in a youth program, it is responsible for doing so lawfully, and everything in this notice applies to that data too.
When what we do changes, we update this page and the date at the top. Questions, requests and complaints go to hello@farband.co.
Questions
Privacy questions are welcome, including the awkward ones. Write to hello@farband.co.