Verasio Data Processing Addendum
- Version
- 1.0
- Effective
- Nov 3, 2026
ClientConnect of Florida, Inc., d/b/a Verasio, 5201 West Kennedy Boulevard, Tampa, Florida 33609
Change log
- v1.0, Nov 3, 2026: First release.
This Data Processing Addendum ("DPA") is part of the Verasio Terms of Service between ClientConnect of Florida, Inc., doing business as Verasio, 5201 West Kennedy Boulevard, Tampa, Florida 33609 ("Verasio") and the Customer. It applies to Personal Data in Customer Data. Capitalized terms not defined here have the meaning in the Terms.
1. Roles
1.1 Definitions. "Personal Data" means information in Customer Data that identifies or could reasonably be linked to an individual. "Data Protection Laws" means the US federal and state laws that apply to the Parties' handling of Personal Data, including the Florida Information Protection Act (Fla. Stat. 501.171), the California Consumer Privacy Act as amended, and the comparable laws of other states. "Sub-processor" means a third party Verasio uses to process Personal Data on the Customer's behalf. "Security Incident" means a confirmed unauthorized access to, or acquisition, disclosure or loss of, Personal Data in Verasio's possession.
1.2 Customer is the controller. For Personal Data, the Customer is the controller, business or data owner, and decides why and how it is processed. Verasio is the processor, service provider or third-party agent, and processes Personal Data only for the Customer.
1.3 Verasio's own data. Verasio is the controller of account, billing, usage, log and performance data about the Customer's use of the service, and of data about the Customer's own users as account holders, as Section 15.5 of the Terms describes.
1.4 Customer's duties. The Customer will comply with Data Protection Laws as controller, including giving every notice and obtaining every consent the law requires for Verasio and its Sub-processors to process Personal Data as this DPA allows, and ensuring it has a lawful basis for the Personal Data it puts into Verasio.
2. Instructions
2.1 What counts as an instruction. Verasio processes Personal Data only on the Customer's documented instructions. The Customer's documented instructions are: the Terms, this DPA, the Order Form, and the Owner's settings and configuration in the Workspace, including Privileged mode, per-user AI grants, retention periods, integrations and automations. Any additional instruction must be in writing from an Owner and agreed by Verasio.
2.2 Unlawful instructions. If Verasio believes an instruction would breach Data Protection Laws, it will tell the Customer and may decline to follow it until the Customer confirms or changes it. Verasio is not liable for delay or non-performance caused by an unlawful instruction.
2.3 Required by law. Verasio may process Personal Data where law or legal process requires, and will tell the Customer first where the law allows.
3. Personnel
3.1 Verasio ensures that every person it authorizes to access Personal Data is bound by a written confidentiality obligation and has access only to the extent needed to do their job.
3.2 Operator support sessions in a Workspace are logged with the operator, time and reason. In a Workspace with Privileged mode on, no operator session happens without the Customer's consent. Verasio's in-app AI assistant is disabled for operators in every Workspace.
4. Security
4.1 Taking into account the nature of the processing, Verasio will maintain commercially reasonable technical and organizational measures designed to protect Personal Data against unauthorized or unlawful access, use, disclosure, alteration or loss while it is in Verasio's possession or control. Annex 2 summarizes those measures. Verasio may update them as technology and threats change, so long as the overall level of protection does not fall.
4.2 Security is shared. The Customer is responsible for its own users, passwords, two-factor settings, devices, networks, Connected Services, the roles and permissions it assigns, and what it chooses to put into Verasio.
5. Assurance
5.1 Verasio has no SOC report or equivalent certification of its own. On written request, no more than once a year, Verasio will provide (a) a written summary of its security program, and (b) where its providers make them available, the then-current SOC 2 or equivalent reports of its hosting and infrastructure Sub-processors. All of this is Verasio Confidential Information under the Terms.
5.2 Verasio will answer reasonable written security questionnaires from the Customer no more than once a year, within 30 days, at no charge for the first four hours and at $250 an hour after that.
6. Sub-processors
6.1 Consent. The Customer authorizes Verasio to use Sub-processors to provide the service. The current list, with each Sub-processor's role and location, is at [verasio.app/legal/sub-processors]. Sub-processors include hosting, networking, voice and messaging carriers, fax, email delivery, e-signature, AI model providers and payment processing.
6.2 Flow-down. Verasio has a written agreement with each Sub-processor that imposes data protection obligations no less protective than this DPA for the processing it performs, and Verasio remains responsible to the Customer for its Sub-processors' performance.
6.3 Changes. Verasio will update the list and notify Owners by email or in-app notice at least 30 days before a new Sub-processor begins processing Personal Data. Where a Sub-processor must be replaced urgently for security, legal or availability reasons, Verasio will give as much notice as it reasonably can and explain why.
6.4 Objection. If the Customer has a reasonable, documented data-protection objection to a new Sub-processor, it must tell Verasio in writing within the 30-day notice period. The Parties will discuss in good faith. If Verasio cannot accommodate the objection, the Customer's sole remedy is to terminate the node or service that depends on that Sub-processor, on written notice before the Sub-processor starts, with a pro-rata refund of prepaid node fees for that node and no Early Termination Fee for it. Silence is acceptance.
7. Security Incidents
7.1 When the clock starts. Verasio will notify the Owner of a Security Incident as expeditiously as practicable and in any case no later than 10 days after Verasio determines that a Security Incident has occurred or has reason to believe one has occurred, which is the deadline Florida Statute 501.171 sets for a third-party agent. Where another Data Protection Law that applies to the Customer sets a shorter deadline for a processor's notice, Verasio will meet that deadline. An alert, a scan or a failed attempt is not a determination.
7.2 What the notice says. The notice will describe, to the extent then known, the nature of the incident, the categories and approximate number of individuals and records affected, the likely consequences, the steps Verasio has taken or proposes to take, and a contact for more information. Verasio will update the notice as it learns more.
7.3 Who notifies whom. The Customer decides whether and how to notify individuals, regulators and others, and does so at its own expense. Verasio does not notify them on the Customer's behalf unless the Customer asks in writing and Verasio agrees. Verasio will give the Customer the information it reasonably needs to make those notices.
7.4 Not an admission. A notice under this Section is not an admission of fault or liability.
7.5 Unsuccessful attempts. Pings, port scans, failed log-in attempts, blocked attacks and similar events that do not result in unauthorized access to Personal Data are not Security Incidents and need no notice.
7.6 Customer-side incidents. An incident caused by the Customer's own users, credentials, devices, networks or Connected Services is the Customer's to handle; Verasio will give reasonable help at its hourly rate.
8. Requests from individuals
8.1 Verasio provides tools in the app that let the Customer search, export, correct and delete Personal Data about an individual, which is how the Customer answers access, deletion, correction and portability requests. If Verasio receives such a request directly, it will refer the individual to the Customer and will not respond on the merits unless the law requires.
8.2 Where the Customer needs help beyond the tools, Verasio will assist at $250 an hour.
9. Audits and records
9.1 Verasio keeps a record of the categories of processing it carries out for the Customer and will provide, on written request no more than once a year, the information reasonably necessary to show that it meets this DPA.
9.2 Verasio satisfies audit rights by providing the documents in Sections 5 and 9.1. An on-site or remote inspection is allowed only if a regulator with jurisdiction over the Customer requires it in writing, or a Security Incident affecting the Customer has occurred and the documents do not resolve the Customer's reasonable concerns. Any inspection is limited to once a year, on 30 days' written notice, during business hours, by the Customer or an independent auditor bound by confidentiality who is not a Verasio competitor, in a non-production environment where possible, and at the Customer's cost including Verasio's time at $250 an hour.
10. AI and de-identified data
10.1 No training. Verasio will not use Personal Data to train, fine-tune or improve any machine-learning or AI model, and will not permit a Sub-processor to do so, unless the Owner opts in through a Workspace setting that says so in plain words. Verasio's AI model providers process Personal Data under terms that prohibit training on it.
10.2 What the AI sees. Verasio's AI processes only the Personal Data the Owner's settings allow it to see, as described in the Documentation. Prompts, model inputs and outputs are retained for the periods the Documentation and the Owner's settings state, and no longer than needed to provide the feature, investigate abuse or meet the law.
10.3 De-identified data. Verasio may create de-identified or aggregated data from Customer Data that cannot reasonably be linked to the Customer or any individual, and use it for statistics, product improvement, benchmarking and similar purposes. Verasio will take reasonable measures to prevent re-identification, will not attempt to re-identify it, and will require anyone it shares it with to do the same.
11. Location and transfers
11.1 Verasio processes and stores Personal Data in the United States. Sub-processors may use infrastructure in other countries for delivery of messages, calls, faxes and email, as their nature requires.
11.2 Verasio does not offer EU, UK or Swiss transfer mechanisms (Standard Contractual Clauses, Data Privacy Framework certification) in this DPA. A Customer that needs them must say so on its Order Form, and Verasio may decline or price them separately.
12. Return and deletion
12.1 Export window. For 30 days after termination or expiry of the Terms, the Customer may export its Personal Data using the self-service export tools in the app.
12.2 Deletion. After the 30-day window, Verasio deletes Personal Data from active systems within 30 days and from backups as they age out under Verasio's standard backup retention, which does not exceed 35 days, except where law requires retention or where Verasio reasonably needs it to resolve a dispute, in which case it is kept only for that purpose and then deleted. Files received by fax are deleted with the rest of the Workspace's storage.
12.3 During the term. The Customer can delete Personal Data at any time through the app; deleted records follow the same backup aging. Verasio keeps audit logs of deletions without the content.
12.4 Certification. On written request within 60 days after deletion, Verasio will confirm in writing that deletion is complete.
13. US state privacy laws
13.1 Where a state privacy law applies to Personal Data (for example the California Consumer Privacy Act as amended by the CPRA, and the comparable laws of Virginia, Colorado, Connecticut, Texas, Oregon, Montana and others), Verasio acts as a service provider, processor or contractor, and the Customer as the business or controller.
13.2 Verasio will: (a) process Personal Data only for the business purpose of providing the service under the Terms, this DPA and the Customer's instructions; (b) not sell or share Personal Data, and not use it for cross-context behavioral or targeted advertising; (c) not retain, use or disclose Personal Data for any purpose other than the business purpose, or outside the direct business relationship with the Customer, except as the law allows; (d) not combine Personal Data with personal data it holds for other customers or collects on its own, except as the law allows; (e) notify the Customer if it determines it can no longer meet its obligations under the applicable law; (f) give the Customer the information and cooperation needed to show compliance; and (g) allow the Customer to take reasonable steps to stop and remediate unauthorized use of Personal Data on written notice.
13.3 The Customer certifies that it understands these restrictions and will comply with them and with its own obligations as a business or controller.
14. Health data and other excluded data
14.1 Verasio is not a HIPAA business associate and does not sign Business Associate Agreements. The Customer will not put protected health information into Verasio, and Verasio has no obligations under HIPAA. If the Customer does so in breach of Section 5.3 of the Terms, Verasio has no liability for it and may delete it.
14.2 The same applies to payment card data, bank account numbers, and biometric or genetic data, which must not be put into Verasio at all, and to government identifiers and background-check data, which may be stored only in fields designated for sensitive data.
Annex 1. Details of processing
Subject matter and purpose. Providing the Verasio service to the Customer: a CRM and communications platform with AI assistance, as described in the Terms and the Order Form, and support for it.
Duration. The term of the Terms plus the export and deletion periods in Section 12.
Data subjects. The Customer's customers, clients, prospects, leads, candidates, applicants, vendors, business contacts and their staff; the Customer's own users, employees and contractors; and callers, texters, faxers and email senders who contact the Customer through Verasio.
| Category | Examples |
|---|---|
| Identity and contact | Name, email, phone, address, company, title, social handles |
| Communications | Texts, call summaries and transcripts, voicemail, faxes, captured emails, notes on the timeline |
| Relationship records | Deals, matters, cases, tasks, dates, documents, signing status, custom fields the Customer defines |
| Employment and recruiting (staffing customers) | Resumes, skills, work history, placement details |
| Financial (where connected) | Accounting records read from the Customer's own accounting system, invoices and payment status, never card or bank numbers |
| Technical | IP address, device and browser, login history, audit logs |
| Sensitive (designated fields only) | Government ID numbers, background-check results, where the Customer stores them in designated protected fields |
Not permitted. Protected health information, payment card numbers, bank account and routing numbers, biometric and genetic data.
Annex 2. Security measures
- Tenant isolation. Each Workspace's data is separated by row-level security in the database; every query is scoped to the Workspace. A Dedicated Workspace runs on its own database project.
- Encryption. Data is encrypted in transit (TLS) and at rest by the hosting provider. Credentials, API keys and secrets are kept in a vault, never in code or logs.
- Access control. Roles (Owner, Admin, User) with least privilege; two-factor authentication available and enforceable by the Owner; single sign-on with Google and Microsoft; agent users get their own scoped tokens.
- AI boundaries. The AI reads only what the Owner's settings allow; Privileged mode blocks AI access to confidential content; AI proposals apply only after human approval; AI model providers are contractually barred from training on Customer Data.
- Logging and audit. Logins, permission changes, operator sessions, AI actions, data exports and deletions are logged; the Owner can review the Workspace timeline and audit trail.
- Operator access. Operator support sessions are logged with reason; disabled in Privileged Workspaces without consent.
- Secure development. Code review and automated tests before release; dependency and security review on changes touching authentication, permissions or data access; secrets scanned out of the repository.
- Backups and recovery. Automated backups by the hosting provider with point-in-time recovery; retention not exceeding 35 days.
- Vendor management. Sub-processors chosen for security posture and bound by written terms; list published and change-notified.
- Incident response. Documented process for detection, containment, investigation and Customer notice under Section 7.