Data processing

Data processing agreement.

The short answer

Version 1.1, effective October 29, 2026. It forms part of the Kaypo terms, so a customer accepts it by accepting them. Questions to hello@sapwood.io.

This Data Processing Agreement ("DPA") forms part of the Kaypo Terms of Service at kaypo.io/terms, or any other written agreement for Kaypo (the "Agreement"), between Sapwood LLC and the organization subscribing to Kaypo.

1. Parties and roles

1.1 Sapwood LLC ("Sapwood") is a Colorado limited liability company based in Denver, Colorado, United States. Sapwood operates Kaypo. "Customer" is the organization subscribing to Kaypo.

1.2 For the CRM records and other data Customer connects to Kaypo, and the people in them ("Customer Personal Data"), Customer is the controller or business and Sapwood is the processor or service provider. Customer decides what is connected and why.

1.3 For Customer's account information, such as the signup name, email, and billing details ("Account Data"), Sapwood is an independent controller. Sapwood's privacy policy, not this DPA, governs it.

2. Definitions

Terms not defined here have the meaning given in the Agreement or Data Protection Law.

  • Data Protection Law: laws that apply to processing Customer Personal Data, including where applicable the GDPR (Regulation (EU) 2016/679), the UK GDPR, the Swiss Federal Act on Data Protection, and US State Privacy Laws.
  • US State Privacy Laws: the California Consumer Privacy Act as amended by the California Privacy Rights Act ("CCPA"), the Colorado Privacy Act, and comparable US state laws.
  • Personal Data Breach: a breach of security leading to accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to, Customer Personal Data.
  • Subprocessor: a third party Sapwood engages to process Customer Personal Data.
  • Customer-Directed Service: a service Customer chooses to connect under its own agreement with that provider, such as HubSpot, Salesforce, Attio, Gong, Google Calendar, Slack, or Claude through the Kaypo connector. These are not Subprocessors.
  • SCCs: the standard contractual clauses in European Commission Implementing Decision (EU) 2021/914.

3. Scope, nature, and purpose

3.1 Sapwood processes Customer Personal Data only to provide Kaypo. Kaypo reads the systems Customer connects, derives signals, scores open deals, shows each score with its inputs, and sends digests and alerts where Customer configures. Annex 1 gives details.

3.2 Kaypo keeps derived signals rather than source material. It does not store calls, recordings, or transcripts.

3.3 Kaypo is read-only by default. Sapwood writes to Customer's CRM only when Customer chooses: a user's edit in Kaypo, the score once write-back is on, or agent-prepared work after a user approves it. Every write is recorded and an approval can be undone for seven days.

3.4 Scores are advisory. Kaypo does not make decisions about people, evaluate individuals, or produce legal or similarly significant effects about anyone.

3.5 Sapwood will not sell Customer Personal Data, share it with other customers, use it to score another customer's deals, or use it to train models.

3.6 Sapwood may create aggregated, de-identified statistics from use of the service that do not identify Customer, its deals, or any individual, and use them to improve Kaypo.

4. Customer instructions

4.1 Sapwood will process Customer Personal Data only on Customer's documented instructions. The Agreement, this DPA, and Customer's configuration of the service (sources connected, fields tracked, write-back, retention setting) are Customer's complete instructions at signature.

4.2 Sapwood will tell Customer if it believes an instruction infringes Data Protection Law, and may suspend that processing until the instruction is resolved.

4.3 If law requires other processing, Sapwood will inform Customer first unless the law prohibits it.

4.4 Customer is responsible for the lawful basis, notices, and consents needed to connect Customer Personal Data, and must not connect data it has no right to process.

5. Confidentiality of personnel

Sapwood limits access to Customer Personal Data to what is needed to operate the service. Personnel with access will be bound by written confidentiality obligations or a statutory duty of confidentiality.

6. Security

Sapwood will maintain the measures in Annex 2. Sapwood may update them if the overall level of protection does not decrease.

7. Subprocessors

7.1 Customer gives general authorization for Sapwood to engage Subprocessors. Those in use on the effective date are listed in Annex 3.

7.2 Sapwood will bind each Subprocessor in writing to data protection obligations no less protective than this DPA, as applicable to its service. Sapwood remains responsible for each Subprocessor's performance.

7.3 Sapwood will give notice of a new or replacement Subprocessor at least 30 days before it processes Customer Personal Data, by email to the workspace owner and by updating the list at kaypo.io/security.

7.4 Customer may object on reasonable data protection grounds within 15 days of notice. If the parties cannot resolve the objection in good faith, Customer may terminate the affected service by written notice.

7.5 Customer-Directed Services process data under Customer's own agreements with them. Consistent with Section 7 of the Agreement, Sapwood is not responsible for them. Customer can revoke Kaypo's access at any time.

8. Data subject requests

8.1 Sapwood will not answer a data subject request about Customer Personal Data except to identify Customer as controller, and will forward it to Customer within 5 business days.

8.2 Customer can export every table its workspace owns as JSON at any time from settings, and deals as CSV. Customer can delete connected data as described in Section 11. Sapwood will give further reasonable assistance where these tools are not enough.

9. Personal Data Breach

9.1 Sapwood will notify Customer without undue delay, and within 72 hours, after becoming aware of a Personal Data Breach.

9.2 The notice will describe, as far as known, the breach, the data subjects and records affected, likely consequences, and measures taken. Information may follow in phases.

9.3 Notice goes to the workspace owner's email address. Sapwood will take reasonable steps to contain and remediate the breach. Notice is not an admission of fault.

10. Impact assessments and consultation

Sapwood will reasonably assist with any required data protection impact assessment or prior consultation with a supervisory authority, to the extent the information relates to its processing.

11. Deletion or return

11.1 Sapwood retains Customer Personal Data while the workspace is active. Customer may set a shorter retention period in workspace settings.

11.2 When Customer disconnects a source, its stored credential is erased immediately and the data it produced is deleted 30 days later. Reconnecting inside that window cancels the deletion.

11.3 On cancellation, Customer Personal Data remains available for thirty days and is then deleted. Export during that window is Sapwood's method of return.

11.4 When the workspace owner deletes the workspace, every table referencing it is removed by database cascade, including deals, scores, history, signals, rules, keys, and credentials. There is no archived copy and it cannot be restored.

11.5 Audit records may be kept longer where needed for legal or security obligations, and used only for those purposes. Copies in backups are removed as those backups expire on their normal rotation.

11.6 Sapwood will confirm deletion in writing on request.

12. Audits and information

12.1 Sapwood will provide the information reasonably necessary to demonstrate compliance: its published security and privacy pages, this DPA, and written answers to reasonable security questionnaires, no more than once in any 12 months unless a Personal Data Breach has occurred.

12.2 Sapwood does not currently hold a SOC 2 report and has not had a third party penetration test.

12.3 Where Data Protection Law or a supervisory authority requires an audit that Section 12.1 cannot satisfy, Customer or an independent auditor under confidentiality may conduct one, at Customer's cost, on at least 30 days' notice, no more than once in any 12 months, during normal business hours, and limited to the processing under this DPA.

13. International transfers

13.1 Customer Personal Data is stored in the United States. Kaypo does not offer a choice of region.

13.2 The website tag does not run for visitors in the EEA, the UK, or Switzerland. That limit covers the tag only. CRM records may still describe people there.

13.3 Sections 13.4 to 13.6 apply only where Data Protection Law requires a transfer mechanism for Customer Personal Data.

13.4 EEA. For transfers subject to the GDPR to a country without an adequacy decision, the SCCs are incorporated by reference: Module 2 where Customer is a controller, Module 3 where Customer is a processor. Clause 7 applies. Clause 9 option 2 applies with the notice period in Section 7.3. The optional language in Clause 11 does not apply. Clauses 17 and 18: the law and courts of Ireland. Annexes 1 and 2 of this DPA complete SCC Annexes I and II.

13.5 UK. The UK International Data Transfer Addendum to the SCCs applies, and neither party may end it under Table 4.

13.6 Switzerland. The SCCs apply with GDPR references read as references to the Swiss Federal Act on Data Protection, and the Swiss Federal Data Protection and Information Commissioner as competent authority.

14. US State Privacy Laws

14.1 Sapwood acts as Customer's service provider or processor. The business purpose is providing Kaypo as described in Section 3 and Annex 1.

14.2 Sapwood will not sell or share Customer Personal Data. It will not retain, use, or disclose it for any purpose other than the business purpose, or outside the direct business relationship with Customer. It will not combine it with personal information from other sources, except as Data Protection Law permits.

14.3 Sapwood will comply with US State Privacy Laws and will notify Customer if it can no longer meet them. Customer may then take reasonable steps to stop and remediate unauthorized use.

14.4 Kaypo's website tag honors Global Privacy Control and Do Not Track. When a browser sends either, the tag stops before reading or writing anything.

14.5 Sapwood certifies that it understands and will comply with this Section 14.

15. Liability

Liability under this DPA, including the SCCs where permitted, is subject to the exclusions and limits in the Agreement. Under the current Terms, neither party is liable for indirect, incidental, or consequential loss, and Sapwood's total liability is capped at the fees Customer paid in the twelve months before the claim.

16. Term

This DPA lasts as long as Sapwood processes Customer Personal Data, including the period in Section 11.3.

17. Order of precedence

In a conflict, the SCCs and UK Addendum (where they apply) prevail, then this DPA, then the Agreement. The Agreement's Colorado governing law clause otherwise applies.

Notices: Sapwood LLC, Denver, Colorado, hello@sapwood.io.


Annex 1. Details of processing

Data exporter (controller): Customer, which accepts this DPA by accepting the Agreement.

Data importer (processor): Sapwood LLC, Denver, Colorado, United States.

Data subjects

  • Buyers and prospects in Customer's CRM.
  • Customer's users, deal owners, and sales staff named in CRM records.
  • Visitors to Customer's website, where Customer installs the tag and the visitor is outside the EEA, UK, and Switzerland.

Personal data

  • From the CRM: deals, companies, people, owners, stages, values, close dates, recorded activity, and custom fields Customer chooses to track. Contact names and emails. Text of emails, calls, meetings, and notes on deals, read to derive signals. Scoring uses the buyer side, and text by Customer's own people is discarded before matching. Short excerpts that matched a signal are kept.
  • From conversation and intent sources: derived facts only, such as whether a meeting happened, attendee count, whether a topic came up, and whether a commitment was made.
  • From a Google Calendar a user connects for themselves: meetings with a contact on one of Customer's open deals (title, start time, whether it was moved or canceled, and those contacts' email addresses and responses). Every other event is read and discarded, and descriptions, locations, and meeting links are never kept.
  • From the website tag: pages viewed, a random id in a first party cookie (kaypo_v, two years), and the company a visit appears to come from. The network address is sent for resolution and stored only as a one-way hash.
  • From licensed data providers, when a user asks about a named person: current work details for that person.
  • From use of Kaypo: sign-in records, an audit log, diagnostics, and a record of each Claude connector request (question type, inputs, result count, outcome, duration, requester, app), never the answers.

Special categories: none intended. Customer should not connect special category or sensitive personal data.

Processing: collection, storage, signal derivation, scoring, display, digests, alerts, optional write-back, export, deletion.

Frequency: continuous. Scores recalculate nightly and digests go out each morning.

Duration: the term of the Agreement plus the deletion periods in Section 11.

Annex 2. Technical and organizational measures

From kaypo.io/security, which states its figures are read from the running code.

Tenant separation. Row level security with an explicit policy on every table carrying workspace data, so Postgres refuses cross-workspace queries. Views set security_invoker. Elevated routines verify the workspace id belongs to the session. No endpoint accepts a workspace id from user input.

Encryption. CRM, Slack, Gong, and calendar tokens sealed with AES-256-GCM before storage: a fresh 96 bit IV per credential, a 128 bit authentication tag checked on every read, a version byte, and key rotation without downtime. Supabase encrypts the database volumes. TLS on every connection, including to Customer's CRM.

Access. Sign-in by signed link to a verified address, with no passwords. Session cookies are HTTP-only, secure, SameSite=Lax, with a server-checked signed issue time. Owner, admin, and member roles. Connecting a CRM, inviting, importing, and issuing API keys require an admin. Only the owner can delete the workspace. OAuth state is HMAC-signed and bound to the starting browser by a single-use nonce, and the person completing it must be an admin, except a calendar, which each user connects only for themselves and which the completing session must match. Sapwood access is limited to what is needed to run the service.

Accountability. An audit log of 46 actions with actor, target, timestamp, and address. API keys shown once, stored as a hash, scoped to one workspace, revocable, and limited to 600 requests an hour per key. Separate rate limits on sign-in links, imports, exports, invitations, and connections.

Minimization. Read-only by default. No stored calls, recordings, or transcripts. The tag records only on domains Customer lists, skips the EEA, UK, and Switzerland, and does not fingerprint devices or name visitors who have not identified themselves. The Claude connector is read-only and never returns contact emails, full email bodies, recordings, or transcripts.

Vulnerability reports go to hello@sapwood.io, with confirmation within one business day.

Not in place: SOC 2 report, third party penetration test, contractual uptime commitment, public status page, SSO, SCIM, customer-managed keys, choice of region.

Resilience and response. The database provider keeps automated backups. Sapwood monitors the service for errors and abuse, limits production access to the people who run it, and handles suspected incidents under Section 9.

Annex 3. Subprocessors

Subprocessor Purpose Location
Supabase Database and authentication United States
Vercel Application hosting and scheduled work United States
Google Workspace Email: digests, alerts, sign-in links and reports United States
Anthropic Writing follow-up drafts when a user asks for one United States

Not Subprocessors. Stripe processes subscription payments as Account Data and never receives pipeline data. Customer-Directed Services (HubSpot, Salesforce, Attio, Gong, Google Calendar, Slack, and Claude through the Kaypo connector) process data under Customer's own agreements with them.