RepCabin

RepCabin legal

Data Processing Addendum

Version 1.4. Effective November 10, 2026.

The version and effective date at the top of https://repcabin.com/legal/dpa are the ones in force.

This Data Processing Addendum ("DPA") is part of the RepCabin Terms of Service (the "Agreement") between WhichAI LLC ("WhichAI") and the Customer. It applies whenever WhichAI processes Personal Data in Customer Data. It is accepted with the Agreement by the same click, and it is binding under the federal Electronic Signatures in Global and National Commerce Act; a Customer that needs a signed copy can email ibrahim@repcabin.com and we will countersign this text without changes. If this DPA conflicts with the Agreement, this DPA controls for the processing of Personal Data. For everything else, including fees, refunds, liability and disputes, the Agreement controls.

1. Definitions

"Personal Data" means information in Customer Data that identifies or is reasonably linkable to a person, including a User's name, work email, voice during a call, transcripts, scores and reviews.

"Process" means any operation on Personal Data, including collecting, storing, transmitting, analyzing, disclosing and deleting.

"Data Protection Laws" means the laws that apply to the processing of Personal Data under the Agreement, including the California Consumer Privacy Act as amended by the California Privacy Rights Act and its regulations ("CCPA"), and the consumer privacy laws of Colorado, Connecticut, Delaware, Indiana, Iowa, Kentucky, Maryland, Minnesota, Montana, Nebraska, New Hampshire, New Jersey, Oregon, Rhode Island, Tennessee, Texas, Utah, Virginia and any other United States state law that applies.

"Security Incident" means a confirmed unauthorized access to, or acquisition, disclosure, loss or alteration of, Personal Data in WhichAI's possession or in a Subprocessor's possession on WhichAI's behalf. Unsuccessful attempts (blocked requests, port scans, failed sign-ins) are not Security Incidents.

"Subprocessor" means a third party WhichAI engages to process Personal Data on its behalf.

"Business", "Service Provider", "Controller", "Processor", "Consumer", "Sell", "Share" and "Business Purpose" have the meanings in the Data Protection Laws.

2. Roles and scope

2.1 Customer is the Business or Controller. WhichAI is the Service Provider or Processor. Where Customer itself acts as a processor for another party, Customer warrants it has that party's authority to appoint WhichAI as a subprocessor on these terms.

2.2 Annex 1 describes the processing: subject matter, duration, nature, purposes, categories of data subjects and Personal Data.

2.3 This DPA covers United States Data Protection Laws. RepCabin is not offered in the European Economic Area, the United Kingdom or Switzerland, and Customer agrees not to add Users located there. If that changes, the parties will sign transfer terms first.

3. Customer instructions

3.1 WhichAI processes Personal Data only on Customer's documented instructions. The instructions are: the Agreement, this DPA, Customer's and its Users' use of the product features (for example inviting Users, starting calls, assigning drills, sharing a call with managers or stopping that sharing, exporting or deleting records, setting retention), and any further written instruction Customer gives that is consistent with the Agreement. Customer's standing instructions include the visibility rules in section 8.10 of the Agreement: call content a User has not shared is not displayed, returned or exported to Customer's owners or managers; no User's scores, levels, growth lines, ranks or readiness judgments are displayed, returned, exported or emailed to them; skill, score and growth figures reach them only as whole-team figures when at least 5 Users contributed; and at the end of the term call content a User has not shared is deleted rather than returned.

3.2 WhichAI will tell Customer without delay if it thinks an instruction breaks Data Protection Laws or if it can no longer meet its obligations under this DPA, in either case within 5 business days of learning it.

3.3 Customer is responsible for the lawfulness of the Personal Data it and its Users put into the Service, for the notices and consents described in section 8.6 of the Agreement, for its own privacy notices to its Users, for any data protection assessment its own law requires of it as the Business or Controller, and for the accuracy of its instructions. Customer will not instruct WhichAI to process Personal Data in a way that breaks Data Protection Laws, and will indemnify WhichAI under section 14.2 of the Agreement for claims arising from Customer's failure to give a required notice or obtain a required consent.

3.4 WhichAI may preserve or disclose Personal Data, including call content a User has not shared with managers, where a law, court order, subpoena, litigation hold or government demand requires it. Where the law allows, WhichAI will tell Customer before disclosing so Customer can seek protection, and will disclose only the minimum required.

3.5 Purpose and prohibited uses. Customer instructs WhichAI to process Personal Data only so that Users can practice sales conversations and receive coaching, and so that Customer can coach its team. Customer will not use the Service or its output, and will not instruct WhichAI to process Personal Data, for any of these:

  • any hiring, pay, promotion, discipline or termination decision about a person;
  • deciding which leads a person receives (lead routing);
  • building a score, rank or rating of a named User from the Service's output;
  • working out a named User's score, level or growth from team figures;
  • monitoring anything other than practice calls;
  • inferring emotion, health, personality or any protected characteristic;
  • identifying a person by voice.

Customer will not require, pressure or reward a User to share a call. Section 9 of the Agreement sets out these limits in full.

4. CCPA Service Provider terms

To the extent the CCPA applies, and in accordance with 11 CCR section 7051(a), WhichAI agrees that:

(a) Customer discloses Personal Data to WhichAI only for the limited and specified Business Purposes in Annex 1, which are: providing the sales-practice service to Customer (running AI practice calls, transcription, scoring and review for the User's own practice, manager reporting of each User's practice activity and of whole-team figures, display of calls a User shares, drills and exports), maintaining and securing the Service, providing customer support, billing and defending payment disputes, complying with law, and internal use to build or improve the Service as permitted by section 7050(a)(3) of the regulations without using the Personal Data to build or modify profiles for use with other businesses, to correct or augment data from another source, or to train or improve any machine learning model.

(b) WhichAI will not Sell or Share Personal Data.

(c) WhichAI will not retain, use or disclose Personal Data for any purpose other than the Business Purposes in (a), including any commercial purpose, or outside the direct business relationship between WhichAI and Customer.

(d) WhichAI will not combine Personal Data received from Customer with Personal Data received from another person or collected from its own interaction with a Consumer, except as the CCPA regulations permit for the Business Purposes.

(e) WhichAI will comply with the CCPA and provide the same level of privacy protection the CCPA requires of Businesses.

(f) Customer has the right to take reasonable and appropriate steps to ensure WhichAI uses Personal Data consistently with Customer's CCPA obligations, including the assessment and audit rights in section 10, and to receive on request WhichAI's completed answers to a reasonable security and privacy questionnaire once every 12 months.

(g) WhichAI will notify Customer within 5 business days if it determines it can no longer meet its obligations under the CCPA.

(h) Customer has the right, on notice, to require WhichAI to stop and remediate any unauthorized use of Personal Data.

(i) WhichAI will notify Customer of any Subprocessor engaged to process Personal Data as set out in section 7 and will bind each Subprocessor in writing to terms at least as protective as this DPA.

(j) WhichAI will cooperate with Customer to respond to verifiable Consumer requests as set out in section 8.

(k) WhichAI certifies that it understands the restrictions in this section and will comply with them.

(l) Customer confirms that it has given its Consumers the notice at collection the CCPA requires, or will do so before their first call, and that it does not rely on WhichAI to give that notice.

5. Multi-state Processor terms

For every other Data Protection Law that applies, WhichAI, as Processor, will:

(a) process Personal Data only on Customer's documented instructions and for the purposes in Annex 1;

(b) ensure that every person authorized to process Personal Data is bound by a duty of confidentiality;

(c) implement the technical and organizational security measures in Annex 2 and keep them under review;

(d) engage Subprocessors only under a written contract that imposes the same obligations as this DPA, and remain responsible for them;

(e) at Customer's choice, delete or return Personal Data at the end of the Service as set out in section 11, unless the law requires retention, and subject to Customer's standing instruction in section 3.1 that call content a User has not shared is deleted, not returned;

(f) make available to Customer all information reasonably needed to demonstrate compliance with this DPA, and allow and contribute to reasonable assessments as set out in section 10;

(g) help Customer meet its obligations to respond to Consumer requests, to provide security, to notify breaches and to conduct data protection assessments, taking into account the nature of the processing and the information available to WhichAI;

(h) not Sell Personal Data or process it for targeted advertising or profiling that produces legal or similarly significant effects.

6. Confidentiality and personnel

WhichAI restricts access to Personal Data to personnel who need it to perform the Service and who are bound by confidentiality. As of this version, WhichAI's only personnel with production access is its founder. WhichAI will keep that access limited and logged where the platform allows.

7. Subprocessors

7.1 Customer authorizes the Subprocessors listed at https://repcabin.com/legal/subprocessors as of the effective date of this DPA.

7.2 WhichAI will email the workspace owner at least 30 days before adding or replacing a Subprocessor that will process Personal Data. The notice names the Subprocessor, its role and location. Customer may object in writing within the 30 days on reasonable data-protection grounds. If the parties cannot resolve the objection within 30 days after that, Customer may terminate the affected Service and receive a pro-rated refund of prepaid unused fees. Continued use after the 30-day notice period without objection is acceptance.

7.3 An emergency replacement of a Subprocessor needed to keep the Service secure or available may be made with notice as soon as practical, and Customer keeps the same objection and termination right.

7.4 WhichAI binds each Subprocessor to written terms at least as protective of Personal Data as this DPA and remains liable to Customer for each Subprocessor's performance.

8. Consumer and data subject requests

8.1 If WhichAI receives a request from a Consumer about Personal Data in Customer's workspace, WhichAI will refer the Consumer to Customer and inform Customer within 5 business days, unless the law prohibits it. WhichAI will not respond to the request itself except to say it has been passed to Customer, or as the law requires.

8.2 The product provides self-service tools that let Customer meet most requests without WhichAI: owner and manager export of workspace records within the visibility rules in section 8.10 of the Agreement, per-User export, per-User deletion of practice records, call sharing controls for each User, User removal, retention settings and workspace closure. For anything else, WhichAI will help within 10 business days of Customer's written request.

9. Security Incidents

9.1 WhichAI will notify the workspace owner by email without undue delay and no later than 72 hours after becoming aware of a Security Incident affecting Customer's Personal Data.

9.2 The notice will state, to the extent known: what happened, when, which categories of Personal Data and roughly how many Users are affected, what WhichAI has done and plans to do, and a contact. WhichAI may give this information in stages as it learns more.

9.3 WhichAI will investigate, contain and remediate the incident, keep Customer reasonably informed, and give Customer the information it reasonably needs to meet its own notification duties. WhichAI will not name Customer in any public statement about the incident without Customer's consent, unless the law requires.

9.4 Notice of a Security Incident is not an admission of fault.

10. Assessments and audits

10.1 Once every 12 months, and after any Security Incident, Customer may ask WhichAI to complete a reasonable written security and privacy questionnaire (for example SIG Lite or CAIQ) and to provide supporting evidence such as the current security description, the subprocessor list, retention settings and deletion confirmations. WhichAI responds within 30 days.

10.2 If the written response does not reasonably resolve Customer's concern, or a regulator requires it, Customer may conduct or commission an assessment of WhichAI's relevant controls, on at least 30 days' written notice, during business hours, no more than once in 12 months (except after a Security Incident), at Customer's expense, by an assessor bound by confidentiality who is not a competitor of WhichAI. The assessment must not disrupt the Service or access other customers' data. WhichAI can satisfy an assessment request with a third-party audit report (for example SOC 2) once it has one.

10.3 Customer may use assessment results only to check compliance with this DPA and must treat them as WhichAI's Confidential Information.

11. Deletion and return

11.1 During the term: Customer and its Users can export and delete Personal Data through the product at any time, within the visibility rules in section 8.10 of the Agreement: each User can export and delete their own records, and owners and managers can export activity records for every call and the transcript and written review of calls a User is sharing, with no scores. A workspace owner can set transcript retention to 90, 180 or 365 days; WhichAI deletes older calls automatically.

11.2 At the end of the term: from the day the subscription ends, the owner keeps read-only access for 60 days to export the Customer Data that section 8.8 of the Agreement makes available to the owner; call content a User has not shared is deleted on day 60, not returned, under Customer's standing instruction in section 3.1. On day 60, WhichAI deletes all Personal Data in the workspace from its live systems and emails the owner a deletion confirmation. If the owner requests workspace closure in the product, WhichAI confirms the request within 2 business days and completes deletion within 30 days of confirmation, and emails confirmation.

11.3 Exceptions: deleted rows may persist in Cloudflare's point-in-time recovery for up to 30 days after deletion and are then gone; billing records are kept for 7 years as the law requires; acceptance records of these Terms and the AI-call notice (identifier, version, time, IP, browser) are kept for 3 years to evidence consent; Google's abuse-monitoring logs expire within 55 days under Google's policy. WhichAI will not use retained data for any other purpose.

12. Liability

Each party's liability under this DPA is subject to section 15 of the Agreement, including the higher cap in section 15.2 for WhichAI's breach of this DPA and the carve-outs in section 15.4. Nothing in this DPA increases WhichAI's liability beyond that section. Customer's indemnity in section 14.2 of the Agreement applies to claims arising from Customer's obligations under this DPA.

13. Term and changes

13.1 This DPA lasts as long as WhichAI processes Personal Data for Customer, including the deletion period in section 11.

13.2 WhichAI may update this DPA where a change in Data Protection Laws requires it, with 30 days' email notice to the workspace owner, or without notice where the change only adds protection for Customer. Any other change follows section 18.2 of the Agreement.

13.3 If a Data Protection Law that applies to Customer requires a term this DPA lacks, the parties will add that term in writing; until then, this DPA is read to include it to the extent the law requires.


Annex 1: Processing details

ItemDescription
Subject matterSales-practice calls between Customer's Users and an AI buyer, and the coaching records produced from them
DurationThe Agreement term plus the export and deletion period in section 11
NatureHosting, transmission to the AI provider, transcription, automated scoring and review, display to Users, and to owners and managers within the visibility rules in section 8.10 of the Agreement, export, deletion
PurposesSales practice and coaching through the RepCabin service as described in the Agreement; security; support; billing; legal compliance. Not the prohibited uses in section 3.5
Data subjectsCustomer's employees and contractors who are Users (reps, managers, owners)
Personal DataName, work email, role, account id; practice activity (sessions, minutes, objections practiced, last practice date); live voice during calls (not stored); transcripts of practice calls; scores, reviews, saved moments, hints, drills, certification status and whether a call is shared with managers; usage and timing data; IP address transiently for security
Sensitive dataNone intended. Users are told not to disclose sensitive information in practice calls. WhichAI does not create voiceprints or any other biometric identifier, does not identify people by voice and does not infer emotion
FrequencyContinuous during the term
RetentionAs in section 11 and the Privacy Policy section 5

Annex 2: Security measures

The current measures are described at https://repcabin.com/legal/security and are summarized here. WhichAI may improve them and will not materially reduce them during the term.

  • Hosting on Cloudflare Workers, Durable Objects and D1, with TLS 1.2 or higher in transit and provider-managed encryption at rest.
  • Tenant isolation: every record carries a workspace identifier and every query is scoped to the caller's workspace membership, covered by automated multi-tenant tests.
  • Role-based field restrictions: every response to an owner or manager, including exports, is built on the server from a list of fields that role may receive. Scores, levels, growth lines, trends and flags for a named User are not on that list. An automated test checks every manager route for those fields.
  • Aggregate threshold: skill, score and growth figures reach owners and managers only as whole-team figures from at least 5 Users, and a count that would show the result of fewer than 2 Users is not returned.
  • Audit records: sharing a call, stopping sharing and every workspace export are recorded with who did it and when.
  • Authentication by hashed one-time email links or Google sign-in; no passwords stored; signed HttpOnly, Secure, SameSite session cookies with a maximum life of 5 days; sign-out-everywhere; CSRF double-submit protection.
  • Rate limiting per workspace, per user and per IP on authentication and costly endpoints; per-workspace and global spend limits on AI usage.
  • Secrets held in Cloudflare secret storage, never in the database, code or browser.
  • Call audio never written to storage; transcripts stored only in the workspace's database rows.
  • Automatic retention jobs as listed in the Privacy Policy.
  • Production access limited to the founder.
  • Security contact: ibrahim@repcabin.com. Incident handling as in section 9.

Legal documents

  • Terms of Service
  • Privacy Policy
  • Data Processing Addendum
  • Acceptable Use
  • Subprocessors
  • Security
  • AI Disclosure
  • Team notice template