Privacy

What Kaypo does with your data.

The short answer

Last updated November 4, 2026.

The short version

Kaypo reads the systems you connect, derives signals from them, and shows you scores built from those signals. It keeps the signal rather than the source material. It does not sell your data, share it with other customers, or use it to train models.

Who is responsible for what

Sapwood LLC operates Kaypo and is based in Denver, Colorado, United States.

For the data you connect, such as your CRM records and the people in them, you are the controller and Kaypo is the processor. You decide what is connected and why. We process it to run the service for you and for nothing else.

For your own account, such as the name and email of the person who signed up and billing details, we are the controller.

What Kaypo processes

From a connected CRM: deals, companies, people, owners, stages, values, close dates, the activity recorded against them, and whichever custom fields you choose to track.

From connected conversation or intent sources: derived facts only. Whether a meeting happened, how many people attended, whether a topic came up, whether a commitment was made. Kaypo does not store calls, recordings, or transcripts.

From a Google Calendar, if a person connects their own: meetings with a contact on one of the workspace’s open deals, as described below. Nothing else on the calendar is kept.

From the website tag, if you install it on your own site: the pages a visitor viewed and the company those visits appear to come from. The tag uses a first-party cookie on your domain. Kaypo does not build identity graphs, fingerprint devices, or attempt to name individual visitors who have not identified themselves.

From your use of Kaypo: sign-in records, an audit log of changes made in the workspace, and basic diagnostics needed to keep the service running.

Why we process it

To provide the service you asked for, to bill you, to keep the service secure, and to meet legal obligations. Where the law requires a legal basis, ours is the performance of our contract with you and our legitimate interest in operating and securing the service.

Scoring and automated decisions

Kaypo produces a score for each open deal. That score is a reading of recorded activity and is presented alongside every input that produced it. It is advisory. Kaypo does not make decisions about people, does not evaluate individuals, and does not produce legal or similarly significant effects about anyone.

Who else sees it

Named, because "our infrastructure providers" is not an answer to the question. Vercel hosts the application and serves it. Supabase runs the Postgres database your pipeline sits in, and the authentication behind signing in. Google Workspace sends Kaypo’s email. Anthropic writes the follow-up drafts a rep asks for, from that deal’s name, company, first names and recent activity, and does not train on it. Stripe processes subscription payments and never sees your pipeline. Each processes data on our instructions and nothing else, and the full list is on the security page alongside what each one touches.

Company details and buyer intent come from data providers Kaypo licenses. They receive only what is needed to answer the question asked of them, such as a company domain. We do not sell data and we do not share it with other customers.

Data is stored in the United States.

If you connect Kaypo to Claude

Kaypo can be added to Claude as a connector. Nothing is shared until a person signs in with their own Kaypo account and approves the connection, and it can be removed at any time from Settings, Connected apps, or from Claude.

What Claude receives. Only answers to questions asked in that person’s own Claude account, and only from deals that person can already see in Kaypo: deal and company names, amounts, stages, owner names, scores, the reasons behind them, and the signals behind those reasons: a meeting attended, a page a named contact viewed, or the few words in a CRM note that matched a signal. It never receives contact email addresses, full email bodies, call recordings or transcripts. The connection is read-only and cannot change anything in Kaypo or in your CRM.

Who processes it. Anthropic, under the Claude account and terms of the person who connected it. The connector answers only what a signed-in person asks. Separately from the connector, Kaypo uses Anthropic to write follow-up drafts when a rep asks for one, as described above.

What Kaypo keeps. A record of each request: which question type was asked, the inputs to it, how many results came back, whether it succeeded, how long it took, who asked and from which app. Never the answers. These records are kept while your workspace exists and are deleted with it.

If you connect your Google Calendar

Each person can connect their own Google Calendar, read only. Kaypo reads it each night and keeps only meetings with a contact on one of the workspace’s open deals: the title, the time, whether it was moved or canceled, and whether those contacts accepted. Every other event is read and discarded. Descriptions, locations and meeting links are never kept, and Kaypo cannot create, change or delete anything on a calendar. Disconnecting from Your calendar in Kaypo, or from your Google account, stops the reading at once.

Kaypo’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Calendar data is used only to score and explain the deals in your own workspace. It is never sold and never used for advertising.

Where you are changes what we do

The website tag resolves a visitor’s network address to a company. In the United States that is business information about an employer, and we treat it that way: we identify companies, not people, and we never work out which individual you are from an address alone.

Under European and UK rules a network address is personal data whether or not we use it to name anybody, which is a stricter test than the American one. So the tag does not run for visitors in the EEA, the UK or Switzerland. No identifier is stored, no address is sent, and nothing about the visit is recorded. We would rather lose the data than collect it on a basis we cannot point to.

California residents have the right to opt out of the sale or sharing of personal information. We do not sell or share it, and we honor Global Privacy Control regardless, which is the signal that right is exercised through.

Cookies

Inside a workspace, everything is first party: no advertising cookie, no cross-site tracking and no third-party marketing tag. The public pages (this site and the public sandbox) also run one third-party visitor tag and the Meta Pixel, described below.

kaypo_trial keeps you signed in during a trial. It is signed, readable only by the server, and lasts fourteen days. A trial has no password, so this cookie is how your browser stays connected to your workspace. Clearing it signs you out, and the link in your welcome email is how you get back.

kaypo_sandbox signs you into the public sandbox at kaypo.io/sandbox, an example workspace with no account behind it. It is signed, readable only by the server, and lasts seven days.

kaypo_slack_state exists for a few minutes while you connect Slack. It carries a single random value that proves the request coming back is the one you started, and it is deleted as soon as the connection completes.

Vercel Analytics counts page views without a cookie and without an identifier that follows you between sites. It records the page, the country and the referrer, nothing else.

Our own tag is the thing this product sells, and we run it here. It stores a random id in your browser (the kaypo_v cookie, two years), records which pages you read and the kind of device, operating system and browser you use (the family and version, such as macOS and Chrome), and resolves your network address to the company you work for. The address itself is never stored, only a one-way hash of it, and we do not work out which individual you are unless you tell us by following a link we sent you.

kaypo_vid is a random id that joins one browser’s visits to this site, so a second visit is known as a second visit. It is first party, set by the page and by our server, and lasts about a year. It holds no name, email or address. A browser that asks not to be tracked, or that opts out at kaypo.io/no-track, is not recorded.

A third-party visitor tag runs on the public pages only, never inside a workspace. It works out which company a visit comes from. It follows the same choices below: a browser that asks not to be tracked never loads it.

The Meta Pixel runs on the same public pages, never inside a workspace. It tells Meta that a page was viewed and, when you leave your email in a form here, that a request came in, so our ads reach people like the ones who asked. It sets Meta's own cookies, and it follows the same choices below.

Telling us not to. If your browser sends Global Privacy Control, we stop before reading or writing anything. Brave, Firefox and DuckDuckGo send it, and so do the common privacy extensions. We honor Do Not Track the same way, for the browsers that still offer it. Neither needs you to visit a page or find a setting here. If you would rather switch it off by hand, use this page, which sets a single preference in this browser and nothing else.

When a page fails. If a page breaks in your browser, it sends us the error message and the page address so we can fix it. From a browser that asked not to be tracked, that is all it sends, with nothing that identifies the browser or you.

How long we keep it

For as long as your workspace is active. You can set a shorter retention period in workspace settings. On cancellation, your data remains available for thirty days and is then deleted. Deleting your workspace deletes the data synced into it.

Audit records are kept longer where needed to meet legal or security obligations.

Security

Each workspace is isolated at the database level rather than by application logic, so a query for one customer cannot reach another's records. Credentials for connected services are encrypted at rest. Access is limited to what is needed to operate the service.

Kaypo does not currently hold a SOC 2 report. If that matters to your organization, say so and we will tell you plainly where we are.

Your rights

Depending on where you are, you may have the right to access, correct, delete, or receive a copy of your personal data, to object to processing, and to complain to a regulator. We do not sell personal information or share it for cross-context behavioral advertising.

If you are a person whose details are in a customer's Kaypo workspace rather than a Kaypo customer yourself, that organization is the controller and your request should go to them. Contact us and we will help route it.

Contact

Sapwood LLC, Denver, Colorado, United States. daniel@sapwood.io

SecurityTermsDocumentationSapwood privacy