RocketVerifier Data Processing Addendum
Effective November 1, 2026. Latest version: https://app.rocketverifier.com/trust/dpa
This Data Processing Addendum ("DPA") forms part of the RocketVerifier Terms of Service (the "Terms") between RocketVerifier ("RocketVerifier" or "Processor") and the customer that accepted the Terms ("Customer" or "Controller").
This DPA is incorporated into the Terms when Customer accepts them. No signature is required for it to take effect. Customers who want a countersigned copy for their records can complete the optional block at the end and send it to legal@rocketverifier.com.
1. Definitions
- "Data Protection Laws" means all laws that apply to the processing of Customer Personal Data under the Terms, including Regulation (EU) 2016/679 (the "GDPR"), the GDPR as retained in UK law with the UK Data Protection Act 2018, the Swiss Federal Act on Data Protection, and United States state privacy laws such as the California Consumer Privacy Act as amended.
- "Customer Personal Data" means personal data that Customer submits to the Service, or that RocketVerifier otherwise processes on Customer's behalf in providing the Service.
- "Service" means the RocketVerifier email verification platform, including the dashboard, REST API, bulk verification, real time verification widget and integrations.
- "Subprocessor" means any third party that RocketVerifier engages to process Customer Personal Data.
- "Personal Data Breach" means a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to, Customer Personal Data.
- "SCCs" means the standard contractual clauses approved by European Commission Implementing Decision (EU) 2021/914. "UK Addendum" means the International Data Transfer Addendum to the SCCs issued by the UK Information Commissioner.
- "Controller", "processor", "data subject", "personal data" and "processing" have the meanings given in the GDPR.
2. Roles and Scope
Customer is the controller of Customer Personal Data and RocketVerifier is its processor. Where Customer acts as a processor for its own clients, RocketVerifier acts as Customer's subprocessor and this DPA applies in the same way.
Customer is responsible for having a lawful basis for the Customer Personal Data it submits and for giving any notices that Data Protection Laws require. RocketVerifier processes account data about Customer's own users as an independent controller under its Privacy Policy, and applies the security measures in Annex 1 to that data as well.
3. Details of Processing
- Subject matter: providing the Service, including syntax, domain, DNS and mailbox checks on email addresses, risk classification, list cleaning, result storage and export.
- Duration: the term of the Terms, plus the deletion period in section 10.
- Nature and purpose: receiving, storing, analyzing and returning email addresses and their verification results so that Customer can decide which addresses to keep. Mailbox checks query the mail server responsible for the address. No email is ever sent to the address itself.
- Categories of data subjects: individuals whose email addresses Customer submits (for example customers, subscribers, prospects and form users) and Customer's authorized users of the Service.
- Categories of personal data: email addresses submitted for verification, any other columns Customer includes in an uploaded file, the verification results for those addresses, and account data (names, email addresses, login and session metadata such as IP address and browser, and billing contact details). Full payment card numbers are handled by Stripe and never stored by RocketVerifier.
- Special categories of data: none. Customer will not submit special categories of personal data to the Service.
- Frequency of processing: continuous, for as long as Customer uses the Service.
4. Processor Obligations
RocketVerifier will:
- Process Customer Personal Data only on Customer's documented instructions. The Terms, this DPA and Customer's configuration and use of the Service are Customer's complete instructions. RocketVerifier will tell Customer promptly if it believes an instruction infringes Data Protection Laws.
- Never sell or share Customer Personal Data and never use it for its own marketing. RocketVerifier uses only aggregated, anonymized metrics derived from processing to improve verification accuracy and reliability.
- Ensure that every person authorized to process Customer Personal Data is bound by an obligation of confidentiality.
- Implement and maintain the technical and organizational measures in Annex 1.
- Assist Customer, taking into account the nature of the processing, in responding to data subject requests, in carrying out data protection impact assessments and in prior consultations with supervisory authorities.
- Notify Customer without undue delay, and in any case within 72 hours, after becoming aware of a Personal Data Breach, and provide the information Customer reasonably needs to meet its own obligations, updating it as the investigation progresses.
- Make available the information necessary to demonstrate compliance with this DPA, as described in section 8.
5. Subprocessors
Customer gives RocketVerifier general authorization to engage Subprocessors. The current list is published at https://app.rocketverifier.com/trust#subprocessors and reproduced in Annex 2.
RocketVerifier will update the published list and email the account owner at least 30 days before a new Subprocessor begins processing Customer Personal Data. Customer can object on reasonable data protection grounds within that period. The parties will work in good faith to resolve the objection, and if they cannot, Customer can terminate the affected part of the Service.
RocketVerifier imposes data protection obligations on each Subprocessor that are no less protective than this DPA and remains responsible to Customer for each Subprocessor's performance.
6. International Transfers
RocketVerifier and its Subprocessors process and store Customer Personal Data in the United States. Transfers of Customer Personal Data from the European Economic Area, the United Kingdom and Switzerland are made under the following safeguards, which the parties incorporate into this DPA by reference:
- EEA: the SCCs, Module Two (controller to processor) and, where Customer is a processor, Module Three (processor to processor). Clause 7 (docking) applies. Under Clause 9, Option 2 (general authorization) applies with the notice period in section 5. The optional language in Clause 11 does not apply. Under Clauses 17 and 18, the SCCs are governed by the laws of Ireland and disputes are resolved by the courts of Ireland. Annex I of the SCCs is completed by sections 2 and 3 and Annex 2 of this DPA, and Annex II by Annex 1 of this DPA.
- United Kingdom: the SCCs as amended by the UK Addendum. Tables 1 to 3 of the UK Addendum are completed with the information in this DPA, and either party can end the UK Addendum as set out in its Section 19.
- Switzerland: the SCCs, with references to the GDPR read as references to the Swiss Federal Act on Data Protection and the Swiss Federal Data Protection and Information Commissioner acting as the competent supervisory authority.
If the SCCs or the UK Addendum conflict with this DPA or the Terms, the SCCs or the UK Addendum prevail.
7. Security
RocketVerifier protects Customer Personal Data with the measures in Annex 1, which provide a level of security appropriate to the risk. RocketVerifier can update these measures over time, provided the overall level of protection never decreases.
8. Audits
RocketVerifier will answer Customer's reasonable written security and privacy questionnaires once in any 12 month period. Where Data Protection Laws or a supervisory authority require more, or after a Personal Data Breach, Customer can have an independent auditor bound by confidentiality inspect RocketVerifier's relevant processing, on at least 30 days' written notice, during business hours, without access to other customers' data, and at Customer's expense.
9. Data Subject Requests
The Service gives Customer self-serve tools to find, export and delete Customer Personal Data, including job and result deletion, configurable retention, and full data export and account deletion in Settings, Privacy. If RocketVerifier receives a request from a data subject about Customer Personal Data, it will forward the request to Customer and will not respond to it except on Customer's instructions.
10. Return and Deletion
Customer can export or delete Customer Personal Data at any time from the dashboard. Verification data is deleted automatically after the retention period Customer selects (90 days by default, configurable from 30 to 365 days or kept until Customer deletes it). Within 30 days after the Terms end, RocketVerifier deletes all remaining Customer Personal Data, unless the law requires RocketVerifier to keep it, in which case RocketVerifier keeps it confidential and processes it only for that legal purpose.
11. Liability
Each party's liability arising out of or relating to this DPA, including under the SCCs to the extent permitted by them, is subject to the limitations and exclusions of liability in the Terms.
12. General
If this DPA conflicts with the Terms on the processing of Customer Personal Data, this DPA prevails. This DPA is governed by the law that governs the Terms, except where the SCCs require otherwise. RocketVerifier can update this DPA to reflect changes in Data Protection Laws or in the Service by publishing a new version with a new effective date at https://app.rocketverifier.com/trust/dpa. An update never reduces the protection this DPA gives Customer Personal Data.
Annex 1: Technical and Organizational Measures
- Encryption in transit: TLS on all dashboard and API traffic.
- Encryption at rest: database storage is encrypted at rest by the database provider. Integration credentials and OAuth tokens are additionally encrypted at the application layer with AES-256-GCM.
- Credential protection: passwords are hashed with bcrypt. API keys are stored only as SHA-256 hashes and shown in full once, at creation.
- Access control: two-factor authentication (TOTP) is available on every account, and team workspaces use role based permissions. Production access is limited to authorized staff.
- Accountability: administrative actions are recorded in an audit log, and every staff view and every export of customer personal data is recorded in a dedicated data access log.
- Session security: signed session tokens, per device session tracking and remote revocation of any session.
- Abuse prevention: bot protection on signup and login, and rate limiting on the API.
- Data minimization and retention: automatic deletion of verification data on a customer configurable schedule enforced by a daily retention job, plus self-serve export and account deletion.
- Monitoring: application error monitoring configured not to collect personal data by default, and a public status page with 90 day uptime history.
- Resilience: the verification API runs on redundant instances, and bulk jobs are processed by dedicated workers from a persistent queue.
- Vendor management: every Subprocessor is bound by data protection terms no less protective than this DPA.
Annex 2: Subprocessors
Current as of November 1, 2026. The live list is published at https://app.rocketverifier.com/trust#subprocessors.
| Subprocessor | Purpose | Data location |
|---|
| Vercel | Web app and dashboard hosting | United States |
| Railway | Verification API, verification workers and job queue | United States |
| Supabase | PostgreSQL database | United States |
| Stripe | Payment processing and billing | United States |
| Resend | Transactional email (receipts, alerts, account notices) | United States |
| SendGrid (Twilio) | Transactional email fallback | United States |
| Cloudflare | DNS, edge network and bot protection (Turnstile) | United States |
| Sentry | Error monitoring, with personal data collection disabled by default | United States |
| Clicky | Product analytics for the web app | United States |
Optional Countersignature
This DPA is already binding through Customer's acceptance of the Terms. Complete this block only if your organization wants a countersigned copy for its records.
Customer
Company
Name
Title
Date
Signature
RocketVerifier
Company
Name
Title
Date
Signature