Data Processing Addendum
Last updated: November 2, 2026
This Data Processing Addendum (“DPA”) forms part of the agreement between Booked55 Inc., carrying on business as Booked55 (“Booked55,” “we”), and the customer that has accepted the Booked55 Terms of Service (“Customer,” “you”). That agreement (the “Agreement”) is the Terms of Service and any order form or other written agreement between us.
This DPA applies as Section 9.4 of the Terms says: to the extent Booked55 processes personal information on Customer’s behalf and an applicable privacy or data-protection law requires contractual processing terms. If this DPA conflicts with the Agreement on the processing of personal information, this DPA controls to the extent of the conflict.
- Customer
- The individual or entity that accepted the Terms of Service.
- Notices to Customer
- The email address of Customer’s account owner in the Service.
- Notices to Booked55
- Vikas Kumar, [email protected]
- Effective date
- The date Customer accepted the Terms, or the date above if that is later.
- Signature
- None is needed: accepting the Terms brings in this DPA. A Customer that needs a signed copy can ask us for one.
1. Definitions
- Customer Data: all data Customer or its Users submit to, import into or have the Service collect on their behalf, including CRM records (contacts, companies, deals, invoices, pipelines, tasks, notes, tags, files), synced email and calendar content, campaign and sequence content, meeting recordings, transcripts and summaries, call and text records, and AI chat transcripts.
- Personal Data: Customer Data relating to an identified or identifiable natural person. Where a law uses “personal information,” “nonpublic personal information,” “nonpublic information” or “customer information,” it is read as Personal Data for that law.
- Users: Customer’s employees, agents and contractors to whom Customer grants access.
- Subprocessor: a third party Booked55 engages to process Customer Data (Annex 3).
- Security Incident: a confirmed breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to, Customer Data in Booked55’s or a Subprocessor’s custody. Unsuccessful attempts (blocked logins, port scans, rate-limited requests) are not Security Incidents.
- Data Protection Laws: the laws applying to each party’s processing of Personal Data under the Agreement, which may include the Gramm-Leach-Bliley Act and the FTC Safeguards Rule (16 CFR Part 314); state insurance data-security laws based on the NAIC Insurance Data Security Model Law; 23 NYCRR Part 500; US state consumer-privacy laws, including the CCPA/CPRA; US state breach-notification laws; Canada’s PIPEDA and substantially similar provincial laws; and, where Annex 4 applies, the GDPR, the UK GDPR and the Swiss FADP.
- Controller and Processor: as defined in the applicable Data Protection Law, and read as “business” and “service provider” (CCPA) and as “licensee” and “third-party service provider” (NAIC, NY DFS) where those terms are used instead.
2. Scope and roles
2.1 Customer is the Controller of Customer Data and Booked55 is its Processor. Customer decides what Customer Data to collect, why and for how long; Booked55 stores and processes it on Customer’s documented instructions. Section 14 of our Privacy Policy states the same division.
2.2 Account data. Booked55 is the Controller of the account data of Users as such (name, email, login and billing details, product usage), which is governed by the Privacy Policy and not by this DPA.
2.3 Subject matter, duration, nature and purpose of the processing, and the categories of data and of data subjects, are in Annex 1.
2.4 Customer’s responsibilities. Customer warrants that it has a lawful basis for the Personal Data it places in the Service, gives any notices and obtains any consents the law requires from its contacts (including for meeting and call recording, and for the calls and texts its Users make, where it enables those features), and does not place in the Service data the Agreement prohibits. Section 10 of the Terms lists that data. Booked55 is not a HIPAA business associate unless it agrees to be in a separate written agreement.
3. Processing instructions
3.1 Booked55 processes Customer Data only:
- (a) to provide, secure, support and maintain the Service as described in the Agreement and the Service’s documentation;
- (b) as Customer and its Users instruct through the Service’s features;
- (c) as required by law, in which case Booked55 tells Customer before processing unless the law forbids it;
- (d) to create aggregated statistics that identify neither Customer nor any person, as Section 9.2(g) of the Terms allows; and
- (e) to record and review the inputs and outputs of AI features to find and fix errors in the Service, as Section 9.2(f) of the Terms allows and the Privacy Policy describes.
3.2 The following count as Customer’s instructions when a User performs them:
- connecting a mailbox or calendar (Google, Microsoft);
- invoking an AI feature, which sends the data needed for that request to the AI Subprocessor for it, and using the features whose AI work runs by itself, such as the summary of an email sent or of a reply received, as the Subprocessors page and the Privacy Policy describe;
- enabling meeting recording for the organization, which sends a notetaker into calendar meetings and records them;
- enabling or leaving enabled automatic contact enrichment;
- exporting data;
- connecting an external AI client through the MCP server;
- making or taking a call in the Service where calling is switched on for the organization, which carries the call through the telephony Subprocessor. Calls are recorded only where Customer’s owner turns call recording on, and a recording or voicemail is then kept by that Subprocessor until Booked55 deletes it with its call record; and
- texting from the Service where texts are switched on for the organization, which carries each text and its reply through the same Subprocessor and keeps them there until Booked55 deletes them with their records.
Customer can avoid any of these flows by not using the feature.
3.3 Booked55 does not sell Customer Data, use it to train AI models, use it for its own marketing, or combine it with data from other customers (other than the aggregated statistics in 3.1(d)). It discloses Customer Data only to Subprocessors under Annex 3 and as the law requires. Section 6.3 says what contact data enrichment providers may do with what they receive. Data received from Google APIs is used in accordance with the Google API Services User Data Policy, including its Limited Use requirements.
3.4 If Booked55 believes an instruction breaches Data Protection Law, it tells Customer and may suspend the processing concerned until the instruction is withdrawn or confirmed.
4. Confidentiality
4.1 Booked55 limits access to Customer Data to people who need it to provide, secure or support the Service and who are bound by written confidentiality obligations. Administrative access by Booked55 personnel to a Customer organization is restricted to super-user accounts and, for an event organizer’s account, to the Booked55 event partner manager assigned to it. Both must use an authenticator app, and their access is recorded in the request log like every other request, including who is behind a session opened as someone else.
4.2 Booked55 does not read Customer Data in the ordinary course, except where a User asks for support, where a security or legal issue requires it, where it reviews what an AI feature was sent and answered as 3.1(e) says, or where the Service’s safety review for the AI assistant flags a risk of harm. Section 9 of the Privacy Policy describes the last two, and what they never include.
5. Security
5.1 Booked55 implements and maintains the administrative, technical and physical safeguards described in Annex 2, appropriate to the sensitivity of Customer Data, and does not reduce their overall level during the term. Annex 2 also states the main limitations Booked55 is aware of, and its answers under Section 10 give the rest.
5.2 Regulated customers. Where Customer is a financial institution under the GLBA Safeguards Rule, a licensee under a state insurance data-security law, or a covered entity under 23 NYCRR Part 500, Booked55 additionally:
- (a) represents that it maintains the information-security program described in Annex 2 and the public security page, and that the representations there are accurate as of the date given;
- (b) encrypts Customer Data in transit and at rest as Annex 2 describes;
- (c) offers multi-factor authentication to every User and requires it of the roles listed in Annex 2, with the limitation noted there on organization-wide enforcement;
- (d) notifies Customer of Security Incidents under Section 7 so that Customer can meet its own notice duties, including 16 CFR 314.4(j), 23 NYCRR 500.17 and NAIC Model Law Section 6 equivalents;
- (e) cooperates, at Customer’s reasonable request, with inquiries from Customer’s regulator that concern Booked55’s processing of Customer Data, by providing the documents in Section 10; and
- (f) acknowledges that Customer remains responsible for its own regulatory filings and for assessing Booked55’s suitability as a service provider (16 CFR 314.4(f)).
6. Subprocessors
6.1 Customer authorizes the Subprocessors on Booked55’s Subprocessors page (Annex 3). That page is the authoritative list and is updated when a Subprocessor is added or removed. It describes contact data enrichment providers as one category, because those providers change over time; Booked55 gives Customer the current list on request.
6.2 Booked55 announces a new Subprocessor that will process Customer Data at least 14 days before it starts, by updating that page and by emailing everyone who has asked at [email protected] to be told. Customer may object on reasonable data-protection grounds within that period. If the parties cannot resolve the objection, Customer may terminate the affected part of the Service without penalty, with a pro-rated refund of prepaid fees for that part. Where a Subprocessor must be replaced urgently to keep the Service running or secure, Booked55 gives as much notice as it reasonably can. A change to a Subprocessor’s purpose or location, or among contact data enrichment providers, is not a new Subprocessor: the page shows the first when it takes effect, and the list under 6.1 shows the second.
6.3 Booked55 engages each Subprocessor under a written agreement, which may be the provider’s standard terms, that requires it to protect Customer Data for the processing it performs, and remains responsible to Customer for the Subprocessor’s performance. There is one exception to what that agreement covers. Contact data enrichment providers are business-data companies, and their standard terms can let them add the names, email addresses and companies Booked55 sends them to the business-contact databases they offer to their other customers. Customer can stop this for new contacts: an owner or manager can turn automatic enrichment off for the whole organization in Organization settings, and a contact is then sent only when a User asks to enrich it.
7. Security Incident notification
7.1 Booked55 notifies Customer of a Security Incident affecting Customer Data without undue delay and in any case within 72 hours after confirming it, even if the investigation is not complete.
7.2 The notice describes, to the extent known: the nature of the incident; the categories and approximate number of records and data subjects affected; the period of exposure; the likely consequences; the measures taken and proposed; and a contact. Booked55 updates the notice as facts change and provides a written summary when its review is complete.
7.3 Booked55 does not notify Customer’s contacts, Customer’s regulators or the public about an incident affecting Customer Data unless Customer instructs it to or the law requires it of Booked55 directly. Booked55 gives Customer reasonable assistance with Customer’s own notices.
7.4 Notice under this section is not an admission of fault or liability.
8. Help with people’s requests
8.1 The Service lets Customer handle most requests itself: Users can view, correct and export contact records (contacts as CSV), delete contacts and files, and delete the organization. A note cannot be deleted on its own; where someone has a right to have one removed, Booked55 helps under 8.2.
8.2 Booked55 assists Customer with requests from individuals (access, correction, deletion, portability, restriction, objection, opt-out) that Customer cannot complete through the Service, within 10 business days of a written request. It does not charge for this unless requests are excessive or repetitive, in which case it may charge a reasonable fee after telling Customer.
8.3 If an individual contacts Booked55 directly about data held in Customer’s organization, Booked55 does not respond on the substance, forwards the request to Customer without undue delay, and tells the individual it has done so.
8.4 Booked55 assists Customer, on reasonable request, with data-protection impact assessments and prior consultations with authorities that concern the Service.
9. Return and deletion
9.1 During the term, deletions by Users take effect in the Service at once. Deleted records are marked deleted and become inaccessible; deleted files are permanently erased from storage within 30 days; records stay in Booked55’s database backups until those expire in the ordinary course (up to 12 months; see Annex 2).
9.2 On termination or on Customer’s request, Customer may export its data using the Service’s export tools before the organization is deleted, and Booked55 will provide a reasonable export of other data on request within 30 days. When the organization is deleted:
- (a) all Customer Data is marked deleted at once and ceases to be accessible to Users;
- (b) CRM records (contacts, companies, deals, invoices, pipelines, tasks, notes, synced mail, transcripts and summaries, call and text records, recordings and voicemails, and the organization’s phone-number records) are permanently deleted within 90 days;
- (c) files are permanently erased from storage within 30 days;
- (d) meeting recordings held by the recording Subprocessor are deleted a week after the meeting, and in any case within the same 90 days;
- (e) Booked55 keeps, for legal, accounting, security or support reasons, only what Section 5 of the Privacy Policy lists: a record that the organization existed, who belonged to it and their sign-in history, the invitations and metered usage behind its invoices, billing history, request logs for the periods the Privacy Policy states, and any public profile username, so that a printed QR code never leads to someone else;
- (f) copies of the records in (b) stay in Booked55’s database backups until those expire in the ordinary course, the last of them up to 12 months later (Annex 2). Backups are used only to recover from a failure or a loss of data; and
- (g) where calling was switched on, the telephony Subprocessor’s own log of each call (the two numbers, the time and the length) stays in Booked55’s account with it, which deleting the organization does not remove.
9.3 Booked55 may retain Customer Data where a law requires it, for only as long as it requires, under this DPA’s protections.
10. Audits and information
10.1 Booked55 makes available to Customer, on request and no more than once in any 12 months (and additionally after a Security Incident affecting Customer Data): written answers to a reasonable security questionnaire within 30 days; its public security page and Subprocessors page; a summary of its incident response plan; any third-party assessment letter it holds; and reasonable supporting evidence for the measures in Annex 2.
10.2 On-site audits, penetration tests by or for Customer, and access to Booked55’s infrastructure or that of its Subprocessors are not offered. Booked55 operates on managed infrastructure whose providers do not admit customer auditors; the documents above are the audit.
10.3 Customer treats everything received under this section as Booked55’s confidential information and may share it with its regulator on request.
11. Data location
Booked55’s primary database and application servers are in Canada. Files are held in storage that is not tied to one country. Other Subprocessors process data in the locations the Subprocessors page gives, most of them in the United States. A move of the primary database or the application servers to another country is announced on that page at least 30 days before it happens.
12. Liability
Each party’s liability under this DPA is subject to the exclusions and limitations in the Agreement (Section 23 of the Terms, Limitation of Liability), which apply to this DPA as if set out here. Nothing in this DPA increases either party’s liability beyond the Agreement.
13. Term, governing law and changes
13.1 This DPA lasts as long as Booked55 processes Customer Data under the Agreement, and Section 9 survives until deletion is complete.
13.2 This DPA is governed by the law that governs the Terms, and disputes under it go to the courts Section 25 of the Terms names.
13.3 Annexes 1 to 3 form part of this DPA. Annex 4 applies as A4.1 says.
13.4 Booked55 may update this DPA. The version in force is the one on this page, and a material change is announced as Section 26 of the Terms says.
Annex 1: Description of processing
- Subject matter
- Provision of the Booked55 CRM: web application, mobile application, API and MCP server.
- Duration
- The term of the Agreement plus the deletion period in Section 9.
- Nature and purpose
- Hosting, storage, retrieval, display, search, synchronization (email, calendar, and connected social accounts where enabled), transmission (email sends on Customer’s instruction), making invoices and their PDFs where the organization turns it on, AI processing (drafting, enrichment, summarization, transcription, the AI assistant), meeting recording where enabled, calls and texts through the organization’s Booked55 phone numbers where enabled, and their recording where the owner turns it on, analytics about Users’ use of the Service, backup and deletion.
- Categories of data subjects
- Customer’s Users; Customer’s contacts, prospects, clients and their representatives; people who email, meet or message with Users through connected accounts, including participants in recorded meetings who are not Booked55 users; where calling or texting is enabled, people who call or text a User’s Booked55 phone number.
- Categories of Personal Data
- Names, email addresses, phone numbers, employer and job role, social-profile URLs, where and when met, free-text notes, tags and pipeline stage; email and calendar content from connected accounts; messages from connected social accounts where enabled; uploaded files and business-card images; meeting audio, video, chat and display names where recording is enabled, and the transcripts and summaries made from them; where calling is enabled, the organization’s phone numbers and who holds each, and for each call the two numbers, who called whom, when and for how long, with its audio only where call recording is on or the caller leaves a voicemail; where texts are enabled, each text; for invoices on deals, the amounts, tax, dates, status and a note on how each was paid, with a copy of the page and a PDF showing the contact’s name and email and their company where the organization has the Service make its invoices; AI chat transcripts; for Users, login identifiers, IP address, device and browser details.
- Sensitive data
- Not intended. Section 10 of the Terms prohibits health information, government identification numbers, financial account numbers and credentials, passwords for other services and biometric identifiers, except the few the Service itself asks for (a business’s own tax number to register for texting or to print on its invoices, a sign-in or key to connect another service). Free-text notes and synced email may incidentally contain any category of data, and are protected at the highest level the Service applies.
Annex 2: Technical and organizational measures
Each item below is what the Service does as of the date at the top of this page. The last part lists known limitations, which are part of this annex.
Encryption
- All traffic between clients and the Service, and between the Service and its database, object storage and third parties, is encrypted with TLS 1.2 or later.
- The database (MongoDB Atlas) encrypts all storage at rest with AES-256; object storage is encrypted at rest by the provider.
- Mailbox and calendar OAuth tokens, and MFA secrets, are additionally encrypted at the application layer with AES-256-GCM before storage, under keys held in the secrets manager.
- Passwords are stored as bcrypt hashes (work factor 12 for new hashes); API keys, reset tokens and refresh tokens are stored hashed.
Identity and access
- Multi-factor authentication is available to every User, by a code emailed to the account’s own address, an authenticator app (TOTP) or a code sent by text message, each with single-use backup codes. It is required for Booked55 super users, organization owners with team members, parent-account owners with teams, managers and operators; an event organizer’s account is exempt. A Booked55 super user must use an authenticator app.
- Accounts lock after 5 failed sign-in attempts; access tokens live 1 hour; refresh tokens are httpOnly, device-bound, single-use and rotated, with reuse detection that revokes the session; irreversible actions require re-authentication within the previous 10 minutes.
- Role-based access control (owner, manager, operator, sales-person) with a permission map each organization can configure.
- Records are kept apart by organization: every read and write a User makes is scoped to their organization. Within an organization, data isolation can restrict records to the User they are assigned to, per type of record.
- API keys and OAuth client registrations are created only by owners and managers and can be revoked at any time; a User’s own grant to an AI client can be revoked by that User; OAuth tokens are limited to the scopes consented to and to the organization they were granted in.
- Users can list and revoke their own sessions.
Logging and monitoring
- A request log records, for every API request, the route, method, status, timing, User, session, role, organization, IP address, the request body with secrets removed and, for error responses only, the response body. A row is kept 90 days, or 13 months when the request is security-relevant: sign-in, MFA, roles, API keys, OAuth, exports, bulk deletes, administration, and anything done under impersonation.
- Error monitoring through Sentry, with authorization headers, cookies, API keys, passwords and tokens stripped before sending.
- Rate limiting on API and authentication endpoints, applied both before and after authentication.
Secure development and operations
- Secrets are held in a secrets manager, never in the code repository, and a secret scanner runs on every pull request.
- Dependency vulnerability scanning (Node and Python) runs on every pull request and weekly, and blocks on high or critical advisories in production dependencies; DNS hygiene and cluster configuration drift are checked on the same schedule.
- Uploaded files pass a type allowlist, an extension blocklist and a content check, then a malware scan, before being written to storage.
- Public hosts sit behind Cloudflare (DDoS protection, bot mitigation) and a cloud firewall; the database accepts connections only from allow-listed addresses.
- Card data never reaches the Service; Stripe hosts all payment capture.
Backup and recovery
- Automated database snapshots every 6 hours, kept 7 days, with a weekly snapshot kept 4 weeks, a monthly one kept 12 months and a yearly one kept 1 year. Recovery point objective 6 hours; recovery time objective 2 hours for a database restore and 8 hours for a full rebuild. A restore was last rehearsed on August 7, 2026.
Incident response
- A written incident response plan with severity levels, containment steps and the 72-hour customer notice in Section 7.
- Responsible-disclosure reports are acknowledged within 48 hours.
Known limitations
- Booked55 holds no SOC 2 report or ISO 27001 certificate; its infrastructure providers publish their own.
- Customer cannot yet require MFA of every User in its organization; roles not listed above may use the Service without it.
- The database uses no customer-managed encryption key.
- The last restore rehearsal predates the database’s move to its current cluster on October 5, 2026; none has been run on that cluster yet.
- Apart from the API server, which runs two copies, every component runs as a single replica, so node maintenance can mean a brief outage.
Annex 3: Subprocessors
The Subprocessors are those on the Subprocessors page, which gives what each one does, the data it receives and where it processes it. That page is this annex; Section 6 says how it changes.
Annex 4: EU, UK, Swiss, Canadian and US state terms
A4.1 A4.2 and A4.3 apply only where Customer is established in, or Customer Data concerns data subjects in, the European Economic Area, the United Kingdom or Switzerland. A4.4 applies to Personal Data of people in Canada. A4.5 applies where a US state privacy law applies.
A4.2 Article 28(3) GDPR terms. This DPA holds each term in the places below.
- Processing only on documented instructions, including transfers
- Sections 3.1 and 3.3, A4.3
- Confidentiality of persons authorized to process
- Section 4
- Security measures (Art. 32)
- Section 5, Annex 2
- Conditions for engaging sub-processors (Art. 28(2), (4))
- Section 6
- Assistance with data-subject rights (Chapter III)
- Section 8
- Assistance with Art. 32 to 36 obligations
- Sections 5, 7 and 8.4
- Deletion or return at end of services
- Section 9
- Information to demonstrate compliance; audits
- Section 10
- Processor informs controller of an infringing instruction
- Section 3.4
A4.3 Transfers. Customer Data is processed outside the European Economic Area, the United Kingdom and Switzerland (Section 11 and Annex 3). This page does not contain transfer terms. A Customer that needs the EU Standard Contractual Clauses (Commission Decision 2021/914, Module Two), the UK International Data Transfer Addendum or the Swiss amendments asks at [email protected] before placing such data in the Service, and the parties sign them separately, with Annexes 1 to 3 of this DPA serving as their annexes.
A4.4 PIPEDA (Canada). Customer remains accountable for Canadian Personal Data while it is in Booked55’s custody; Booked55 provides a comparable level of protection by contract through this DPA; Customer is responsible for telling individuals that their data may be processed by service providers outside Canada where PIPEDA or provincial law requires it (Annex 3 states the locations); and Booked55 cooperates with Customer’s breach record-keeping and notification duties under Section 7.
A4.5 US state privacy laws (CCPA/CPRA and similar). Booked55 acts as a service provider. It does not sell or share Customer Data, does not retain, use or disclose it outside the direct business relationship or for any purpose other than the business purposes in Section 3, does not combine it with personal information from other sources except as the law permits a service provider to, complies with the obligations those laws place on service providers, notifies Customer if it can no longer meet them, and permits Customer to take reasonable steps under Section 10 to stop and remediate unauthorized use. Section 6.3 applies to contact data enrichment providers.
See also: Terms of Service · Privacy Policy · Subprocessors · Security
