Known Quantity

Privacy Policy

Effective October 20, 2026

Who we are

Known Quantity is a private relationship-management tool for independent coaches and fractional operators. It is a single-tenant application: each customer runs their own isolated instance, and one customer’s data is never commingled with another’s. This policy explains what data the application accesses, why, and how it is handled.

Google Workspace data we access, and why

When you connect your Google account, Known Quantity requests only the scopes it needs to do its job. We access:
  • Gmail (read):to detect replies to outreach you’ve sent, to show you the history of your past conversations with a specific contact so you have context before you follow up, and to read your signature so it can be appended to messages you send.
  • Gmail (send): to send an email on your behalf — only when you explicitly click to send a message you have reviewed. Known Quantity never sends mail on its own.
  • Google Calendar (read events):to see your meeting schedule, so the app can track relationship cadence and surface who you’re meeting and when.
  • Google Drive (only a file you pick): when you import a spreadsheet, Google’s file picker lets you choose one file, and Known Quantity can read only that file. It can’t see anything else in your Drive.
We request read-only access wherever reading is sufficient, and we never request permission to delete or modify your email, calendar, or contacts.

Chrome extension (Known Quantity LinkedIn Agent)

Known Quantity offers an optional Chrome browser extension that works alongside your Known Quantity instance while you browse LinkedIn.
  • What it collects: publicly visible LinkedIn profile information (such as name, headline, company, and profile URL) for people you explicitly choose to save or scan, and outreach videos you choose to record with your camera and microphone. The extension does not collect your browsing history, and it does not read pages on any site other than LinkedIn.
  • How it is used:solely to provide the extension’s features — saving people to your CRM, showing you your own CRM context while you browse, and attaching videos to outreach you send. It is never used for advertising or sold to anyone.
  • Where it goes and how it is stored: data captured by the extension is sent over encrypted connections (TLS) only to your own private Known Quantity instance and stored in your dedicated, per-customer database described below. Extension settings are stored locally in your browser. We do not transmit extension data to any third party beyond the infrastructure providers listed in this policy.
  • Sharing: we do not sell, rent, or share data collected by the extension with third parties, except the service providers listed below who host the service on our behalf.
  • Retention and deletion:extension data follows the same retention and deletion terms as the rest of your instance (see “Data retention and deletion”). You can remove locally stored settings at any time by uninstalling the extension.

Meeting recordings you connect

If you connect a call recorder (Fireflies, Zoom, Otter, Granola, Read.ai, Fathom, Avoma or Krisp), Known Quantity reads the transcripts of your meetings from your account with that service, so it can keep context on each person you meet with. We only read from these services; we don’t send them your data.

How we use your data

Google Workspace data is used solely to provide the features above — detecting replies, surfacing conversation history and meeting context, and sending messages you approve. We do not sell your data, use it for advertising, or build advertising profiles. Known Quantity support staff see your data only when you approve a request to view it, to investigate a bug, or where required for security or to comply with the law. Every such access is logged.

What we keep from your email

To show you your history with a contact — and to recognise a message from someone whose address you had not recorded — Known Quantity reads the messages in your mailbox and keeps a record of each one. What it keeps depends on whether the message involves one of your contacts:
  • Messages involving one of your contacts: sender, recipients, date, subject, and the message text, so the conversation appears on that person’s page when you need context before following up.
  • Every other message: only the sender, the recipients, the date, and which conversation it belongs to. We do not keep the subject line and we do not keep the message text.
We keep that second, minimal record so that someone you add to your contacts later can be matched against mail that already arrived, without re-reading your mailbox every time you add a person. It is also why a new contact’s history appears immediately rather than after a fresh scan of your inbox.

How your data is stored and secured

Your data is stored in a dedicated, per-customer database (Supabase Postgres) that is isolated from every other customer. Data is encrypted in transit (TLS). Access tokens are stored only for as long as needed to operate your instance and are used only to make the requests described above on your behalf.

Service providers (subprocessors)

We rely on a small set of infrastructure providers to run the service. They process data only to provide their service to us, under their own terms, and never to train generalized AI/ML models on your data:
  • Vercel — application hosting.
  • Supabase — database and storage.
  • Anthropic — processes email text, via its API, to draft messages and classify them. Anthropic deletes what it receives within 30 days and never trains its models on it.
  • OpenAI — indexes meeting transcripts, LinkedIn posts and contact summaries so they can be searched, via its API (which does not train on data submitted through it). No email text is sent.
  • Apify — looks up public LinkedIn profiles for people in your contacts, using only their name and company, so Known Quantity can match each person to the right profile. No email content is sent.
  • Resend— delivers the system emails Known Quantity sends you and our team, such as alerts and sign-in links, which can include a contact’s name or meeting details.
  • GitHub — stores the bug reports and ideas you send through the feedback button, including any files you attach, so our team can work on them.
  • Stripe — processes your subscription payments. Known Quantity never sees your full card number.

Google API Services — Limited Use disclosure

Known Quantity’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In particular, we do not use Google user data for advertising, we do not sell it, we do not transfer it except as necessary to provide or improve the app’s features (with your consent), for security, or to comply with the law, and we do not use it to train generalized AI/ML models.

Data retention and deletion

We keep your data while your subscription is active, and delete it within 30 days after your instance closes. You can revoke Known Quantity’s access to your Google account at any time from your Google Account permissions page. You can also request deletion of your data by emailing us; we will delete it promptly, except where retention is required by law.

Changes to this policy

We may update this policy from time to time. Material changes will be reflected by an updated effective date at the top of this page.

Contact

Questions about this policy or your data? Email privacy@knownquantity.com.

Send feedback

Goes straight to the team, with the page and technical details attached automatically.