Data Processing Addendum

Effective Date: October 10, 2026

This Data Processing Addendum (“DPA”) describes how Revive Sales processes personal data on behalf of its customers. It forms part of the Terms of Service and applies automatically to customers who accept them.

1. Definitions

“Customer Data” means the personal data contained in the sales pipeline information the customer uploads, connects or generates in the Service. “Data Protection Law” means the laws that apply to the processing, including the GDPR, the UK GDPR and US state privacy laws such as the California Consumer Privacy Act. Terms such as controller, processor, business, service provider, personal data, processing and subprocessor have the meanings in that law.

2. Scope and Roles

For Customer Data, the customer is the controller (or business) and Revive Sales is the processor (or service provider). The subject matter, duration, nature and purpose of the processing, the types of personal data and the categories of data subjects are described in Annex I.

3. Instructions

We process Customer Data only to provide the Service and on the customer’s documented instructions, which are the Terms, the customer’s use of the Service’s features, and written requests to support@revivesales.app. We will tell the customer if we believe an instruction breaches Data Protection Law. The customer confirms it has a lawful basis to have us process Customer Data and has given any notices required.

4. Confidentiality

Everyone at Revive Sales with access to Customer Data is bound by confidentiality obligations. Access is limited to what is needed to run, support and secure the Service.

5. Security

We maintain the technical and organisational measures described in Annex II and on our Security page. We may update these measures but will not materially reduce the overall level of protection.

6. Subprocessors

The customer authorises the subprocessors listed on our Security page (Annex III). We bind each to data protection obligations no less protective than this DPA and remain responsible for their performance. We will notify customers by email before adding or replacing a subprocessor that handles Customer Data. A customer may object on reasonable data protection grounds by contacting support@revivesales.app; if we cannot resolve the objection, the customer may close their account.

7. International Transfers

The Service is operated in the United States. Where Data Protection Law requires a transfer mechanism for personal data moving from the EEA, UK or Switzerland, the parties will rely on the European Commission’s Standard Contractual Clauses (and the UK addendum where applicable), which are incorporated by reference and which we will sign on request, with Annexes I to III of this DPA as their annexes.

8. Data Subject Requests

Taking into account the nature of the Service, we will help the customer respond to requests from individuals exercising their data protection rights. If we receive such a request about Customer Data directly, we will refer the individual to the customer unless the law requires otherwise.

9. Security Incidents

We will notify the customer without undue delay after becoming aware of a breach of security leading to the accidental or unlawful destruction, loss, alteration or unauthorised disclosure of, or access to, Customer Data. The notice will describe what we know of the nature of the incident, the data affected, and the measures taken, and we will provide further information as it becomes available to help the customer meet its own obligations.

10. Assistance

Taking into account the nature of the processing and the information available to us, we will reasonably assist the customer with data protection impact assessments and consultations with regulators that relate to the Service.

11. US State Law (CCPA)

Where the CCPA or a similar US state law applies, we act as the customer’s service provider. We will not sell or share Customer Data; retain, use or disclose it outside the direct business relationship or for any purpose other than the business purposes in the Terms and this DPA; or combine it with personal information from other sources except as the law permits. We will give the same level of privacy protection as the law requires, and will tell the customer if we can no longer meet our obligations. The customer may take reasonable steps to stop and remediate unauthorised use.

12. Deletion and Return

Closing the account in the Service deletes the customer’s workspace and Customer Data and asks HubSpot to revoke our access to a connected HubSpot account. The customer can export their data through the Service’s export features before closing. Copies in backups are removed when the backups expire. We may keep data where the law requires it.

13. Audits and Information

On reasonable request we will provide information needed to show compliance with this DPA, such as completing a security questionnaire. We are not currently SOC 2 certified. Any on-site audit must be agreed in advance, be limited in scope and duration, and not expose other customers’ data.

14. Liability and Order of Precedence

This DPA is subject to the limitations of liability in the Terms of Service. If it conflicts with the Terms on the processing of personal data, this DPA prevails.

15. Signed Copy and Contact

This DPA applies automatically to customers who accept the Terms. For a countersigned copy or Standard Contractual Clauses, contact support@revivesales.app.

Annex I: Details of Processing

ItemDescription
Subject matterProviding the Revive Sales Service to the customer
DurationWhile the customer has an account, until deletion as described in section 12
Nature and purposeStoring and analysing sales pipeline data to produce re-engagement signals, briefings and suggested messages; syncing with and writing deal outcomes back to the customer’s HubSpot account at the customer’s direction
Types of personal dataContact names, company names, deal details and sales notes, deal owner names, and other fields the customer uploads or syncs; users’ names and email addresses
Data subjectsThe customer’s prospects, customers and contacts, and the customer’s employees and users
Sensitive dataNone intended. The customer should not upload special-category or other sensitive data
FrequencyContinuous while the customer uses the Service

Annex II: Security Measures

  • Encryption in transit (TLS) and at rest; additional application-level encryption of CRM tokens with a separately held key.
  • Per-workspace data isolation using row-level security and server-side checks.
  • Server-only handling of secrets; billing and plan fields protected from browser edits.
  • Hashed passwords; signed, time-limited state in OAuth flows; rate limiting of sign-in, sign-up and account-lookup endpoints.
  • Security headers including a content security policy; patched web framework.
  • Internal audit log of key account and billing actions.
  • Access to production systems limited to authorised personnel; confidentiality obligations.
  • Account deletion process that removes data and asks the CRM provider to revoke access.

Annex III: Subprocessors

The current list, with what each provider receives, is on our Security page: Supabase, Vercel, Stripe, Resend, Anthropic, Tavily, Google (optional sign-in) and HubSpot (when the customer connects it).