GDPR

1. Roles

• For customer account, billing, support, and website data, BillionVerify generally acts as the controller, depending on the processing context.
• For email lists and other verification inputs submitted by customers, the customer generally acts as the controller and BillionVerify acts as a processor.
• Customers are responsible for having a lawful basis and any required notices for the email addresses they submit for verification.

2. Data Usage

BillionVerify processes data as needed to provide email verification, bulk file processing, API verification, result delivery, account administration, billing, support, fraud prevention, abuse prevention, and service reliability.

3. Data Subject Rights

BillionVerify provides workflows to review and respond to privacy requests through account deletion and internal DSAR/GDPR processes. Request types may include, subject to identity verification and applicable law:

• Removal of the active customer account identity and access credentials.
• Access and portability exports through support or GDPR review workflows.
• Correction of account profile data where editable in the dashboard or support process.
• Restriction or objection requests handled by support on a case-by-case basis, subject to applicable law, controller instructions, and required security, audit, or legal retention.

4. Account Deletion Model

Account deletion removes the active BillionVerify account identity and revokes sessions, API keys, webhooks, OAuth access, and engagement contacts. Historical verification, billing, job, file storage, and audit records may remain under the former account identifier as restricted internal business records when we have a valid retention basis.

If the same email address registers again after deletion, the new account receives a new account identifier and does not inherit prior verification history, jobs, API keys, download access, billing records, or retained files from the deleted account.

5. Verification Data

Verification data can include submitted email addresses, job metadata, SMTP responses, technical delivery signals, uploaded file rows, result files, and storage paths. These records are personal data where they can identify a person or be linked back to a customer or data subject.

Customer-facing dashboard and API views are minimized by default. Detailed processor data is not included in default history exports and requires a separate support or legal review path.

6. International Transfers

BillionVerify uses infrastructure, payment, email, authentication, and verification-related providers that may process data in multiple regions. Where required, international transfers may be supported through appropriate contractual safeguards such as Standard Contractual Clauses.

7. Related Pages

• Data Processing Agreement
• Subprocessors
• Data Retention
• Privacy Policy

8. Contact

GDPR questions and privacy requests can be sent to support@billionverify.com.