Skip to content

Home/Data Processing Agreement

Exporb Data Processing Agreement

GDPR-compliant data processing terms for Exporb customers

Last updated: June 27, 2026 · Effective: June 27, 2026

DPA

Data Processing Agreement (DPA)

This Data Processing Agreement ("DPA") forms part of the Terms of Service between Aeon Kosmos, LLC ("Processor," "we," "us," "our") and the customer ("Controller," "you," "your") who has entered into the Terms of Service for the Exporb service ("Service"). This DPA governs the Processing of Personal Data by Processor on behalf of Controller in the course of providing the Service.

This DPA is incorporated by reference into the Terms of Service effective as of the date you accept the Terms (the "Effective Date"). By using the Service, you enter into this DPA on behalf of yourself and any organization you represent, and you represent that you have authority to bind that organization.

Why This DPA Matters

GDPR Article 28 requires a written contract between Controller and Processor. This DPA is that contract. It legally defines: what data we process, for how long, under what security measures, which sub-processors we use (named explicitly), how we handle breaches, and your audit rights. It also incorporates the EU Standard Contractual Clauses (SCCs) for international data transfers.

01

1. Definitions

Capitalized terms used but not defined in this DPA have the meanings given in the Terms of Service. In this DPA:

"Controller" means the natural or legal person who determines the purposes and means of Processing Personal Data — you, the Exporb customer.

"Processor" means Aeon Kosmos, LLC, which processes Personal Data on behalf of the Controller.

"Personal Data" means any information relating to an identified or identifiable natural person ("Data Subject") that is processed by Processor on behalf of Controller under the Terms and this DPA.

"Customer Data" means the Personal Data you upload to the Service: audio recordings, transcriptions, business card images, extracted contact details (names, emails, phone numbers, companies), notes, tags, and attachments.

"Processing" means any operation performed on Personal Data (collection, recording, organization, structuring, storage, adaptation, retrieval, use, disclosure by transmission, alignment, combination, restriction, erasure, or destruction).

"Sub-processor" means any third party engaged by Processor that processes Personal Data under this DPA.

"Standard Contractual Clauses" or "SCCs" means the European Commission's Standard Contractual Clauses for the transfer of personal data to third countries (Commission Implementing Decision (EU) 2021/914 of 4 June 2021), Module Two (Controller-to-Processor), as amended or replaced.

02

2. Processing of Personal Data

2.1 Subject Matter, Nature, and Purpose

Processor processes Personal Data to provide, maintain, and improve the Service as described in the Terms and Privacy Policy, acting on Controller's documented instructions.

2.2 Duration of Processing

For the duration of the Terms of Service plus the data retention periods specified in Section 8 of the Privacy Policy (active account → 30 days post-deletion → 90 days backup retention). Audio recordings deleted by Controller are permanently removed within 24 hours.

2.3 Categories of Data Subjects

The Personal Data processed concerns the following categories of Data Subjects:

  • Controller's employees, contractors, and authorized users of the Service
  • Trade show booth visitors, prospects, and business contacts whose conversations are recorded
  • Individuals whose business cards are scanned or contact details are captured
  • Any other natural person whose Personal Data Controller uploads to the Service

2.4 Types of Personal Data

The following types of Personal Data may be processed:

  • Account Data: Name, email address, company name, phone number, job title, billing information (Controller acts as Data Subject here)
  • Contact Data (Customer Data): Names, email addresses, phone numbers, job titles, company names of third-party contacts
  • Audio Data: Voice recordings of conversations, AI-generated transcriptions
  • Visual Data: Business card images, selfie photos (where used for contact profiles)
  • Derived Data: AI-generated summaries, sentiment analysis, topic extraction, key insights

Special Category Data

Audio recordings may incidentally capture special categories of Personal Data under GDPR Article 9 (e.g., health information, political opinions, religious beliefs, or biometric voice characteristics disclosed during conversations). Where such data is present, Controller warrants that it has obtained explicit consent under Article 9(2)(a) or another valid lawful basis. Processor processes such data strictly on Controller's instructions, without generating persistent voice biometrics, and recommends immediate deletion once the business purpose is fulfilled.

03

3. Sub-processors

Controller authorizes Processor to engage the following Sub-processors to process Personal Data. All Sub-processors are bound by written agreements that impose data protection obligations no less protective than those in this DPA, including confidentiality, security, and limited-use provisions.

Transparency commitment: Every Sub-processor with access to Customer Data is named below with their role, data processed, and processing location. No anonymous "cloud provider" references. We will never engage a new Sub-processor for Customer Data without the notice and objection procedure in Section 3.3.

3.1 Current Sub-processors

Sub-processorService ProvidedData ProcessedLocation
SupabaseCloud database, authentication, file storageAll Customer Data (contacts, audio, images, transcripts), Account DataEU (eu-central-1)
VercelWeb hosting, serverless API functions, CDNHTTP request logs (IP, URL, response time), serverless function data in transitEU (iad1)
Google (Gemini API)AI transcription, contact extraction, conversation analysisAudio recordings, transcript text, business card images, contact detailsUS
StripePayment processing, subscription billingEmail, billing address, payment card data (PCI DSS Level 1)US
RevenueCatIn-app purchase receipt validation, entitlement managementPseudonymous user identifier, purchase metadata, subscription tierUS
ResendEmail delivery (transactional, campaigns, follow-up)Recipient email addresses, email contentUS
SentryError tracking, application performance monitoringError messages, stack traces, browser/device info, pseudonymized user ID (PII-scrubbed)EU (de)
PostHogProduct analytics (consent-gated)Page views, feature usage, session duration, pseudonymized user ID (reverse-proxied)EU
TelegramOAuth authentication, bot notificationsTelegram user ID, first name, last name, username, phone number; contact capture summaries (bot messages)Global (Telegram servers)
LemlistEmail marketing (consent-gated)Email address (marketing opt-in only)EU

Data Minimization by Sub-processor Tier

Not all Sub-processors access all data. Access is scoped to what each provider needs to perform its function:

  • Full Customer Data access: Supabase (primary data store)
  • Audio/contact data for AI processing: Google Gemini API (zero-retention, paid tier — no training)
  • Payment data only: Stripe (we never see full card numbers), RevenueCat (receipt metadata only)
  • Authentication/notification data only: Telegram (OAuth profile fields, bot notification content)
  • Email/communication data only: Resend (email addresses, email content for delivery), Lemlist (marketing email only, consent-gated)
  • Anonymized/technical data only: Vercel (request logs), Sentry (PII-scrubbed errors), PostHog (reverse-proxied analytics, consent-gated)

3.2 DPA/SCC Status per Sub-processor

Sub-processorDPA SignedSCCs in PlaceTransfer Safeguard
SupabaseYesN/A (EU-hosted)Data stays in EU; SOC 2 Type II
VercelYesYesSCCs; EU region hosting (iad1)
Google (Gemini API)YesYesSCCs; paid API tier (no training); DPF certified
StripeYesYesSCCs; PCI DSS Level 1; DPF certified
RevenueCatYesYesSCCs; DPF certified
ResendYesYesSCCs; DPF certified
SentryYesYesSCCs; EU region hosting; DPF certified
PostHogYesYesSCCs; EU region hosting; reverse-proxied
TelegramYesN/A (controller-processor, not processor-processor)Telegram Login Widget; data minimization
LemlistYesN/A (EU-hosted)Data stays in EU

3.3 Sub-processor Changes — Notice & Objection

We will notify Controller at least 30 days before engaging any new Sub-processor that will have access to Customer Data, by email to the account administrator and by updating this DPA. Controller may object to a new Sub-processor on legitimate data protection grounds within 10 business days of notice. If the objection cannot be resolved, Controller may terminate the affected Service without penalty for the unused portion of the subscription term. Continued use after the 30-day notice period constitutes acceptance of the new Sub-processor.

3.4 Sub-processor Liability

Processor remains fully liable to Controller for the performance of each Sub-processor's data protection obligations. If a Sub-processor fails to fulfill its obligations, Processor shall be liable to Controller for the performance of that Sub-processor's obligations.

04

4. Controller Obligations

Controller represents and warrants that:

  • It has a lawful basis for Processing Personal Data under GDPR Article 6 (and, where applicable, explicit consent under Article 9 for special-category data).
  • It has provided all necessary notices to Data Subjects, including a privacy notice that discloses the use of a third-party processor (Exporb/Aeon Kosmos).
  • It has obtained all consents required by applicable law before recording conversations or scanning business cards.
  • Its instructions to Processor comply with applicable data protection laws.
  • It will not instruct Processor to Process Personal Data in violation of applicable law.

Controller Instructions

Controller's complete instructions to Processor are: (a) Process Personal Data as necessary to provide the Service as described in the Terms and Privacy Policy; (b) Process Personal Data in accordance with controller-initiated actions within the Service (e.g., record, transcribe, delete); and (c) comply with other reasonable written instructions agreed by the parties. All other processing is outside the scope of these instructions.

05

5. Data Subject Rights

Processor shall, taking into account the nature of the Processing, assist Controller by appropriate technical and organizational measures, insofar as possible, to fulfill Controller's obligation to respond to Data Subject requests.

5.1 Requests Received by Processor

If Processor receives a request from a Data Subject to exercise their rights (access, rectification, erasure, restriction, portability, objection), Processor will:

  • Verify the request concerns Customer Data (not Account Data)
  • Forward the request to Controller within 48 hours
  • Assist Controller in responding (e.g., providing data exports)
  • Not respond directly to the Data Subject except to acknowledge and redirect

5.2 Controller Requests to Processor

When Controller receives a Data Subject request that requires Processor's assistance, Controller shall submit a detailed request to support@exporb.com with "Data Subject Request — [Type]" in the subject line. Processor will respond within 5 business days and complete the requested action within 30 days (or provide a detailed explanation of any delay).

06

6. Technical & Organizational Measures

Processor implements and maintains the following technical and organizational measures to protect Personal Data against accidental or unlawful destruction, loss, alteration, unauthorized disclosure, or access:

Encryption

AES-256 encryption at rest (Supabase); TLS 1.2+ in transit for all communications; encrypted database backups.

Access Control

Row-Level Security (RLS) in Supabase enforces multi-tenant data isolation — users can only access their own data. Server-side API endpoints use admin-level service keys for privileged operations. No production data access for development or testing.

Pseudonymization

Error monitoring (Sentry) receives PII-scrubbed data (emails, phone numbers, IP addresses removed before transmission). Product analytics (PostHog) uses pseudonymized user IDs with no contact data. Session replay and autocapture disabled on both services.

System Security

Regular dependency updates, automated vulnerability scanning, pre-commit secret detection (gitleaks), infrastructure-as-code deployments, and continuous monitoring.

Resilience

Automated daily backups with point-in-time recovery (Supabase), 30-day server log retention (Vercel), geographic redundancy within EU region.

Regular Testing

Periodic penetration testing, security audits, and governance reviews under the LifeBacklog governance framework. Measures are assessed and updated at least annually.

Personnel

All personnel with access to Personal Data are bound by confidentiality obligations. Access is granted on a need-to-know basis and revoked upon role change or departure.

07

7. Personal Data Breach

Processor shall notify Controller without undue delay and in any event within 48 hoursof becoming aware of a Personal Data Breach involving Customer Data.

Breach Notification Content

The notification shall at minimum:

  • Describe the nature of the breach, including the categories and approximate number of Data Subjects and records affected
  • Communicate the name and contact details of the data protection contact point
  • Describe the likely consequences of the breach
  • Describe the measures taken or proposed to address the breach, including mitigation measures

Processor shall also cooperate with Controller, at Controller's expense, in any investigation, notification to supervisory authorities, or communication to Data Subjects required under GDPR Articles 33 and 34.

Incident Log: Processor maintains a confidential log of all Personal Data Breaches and near-miss events involving Customer Data, including the facts, effects, and remedial actions. This log is available to Controller's auditor upon request under Section 9.

08

8. International Data Transfers

8.1 Data Storage Location

All Customer Data is stored and processed primarily in the European Union(Supabase eu-central-1, Vercel iad1). The following transfers outside the EU/EEA occur:

  • Google Gemini API: Audio and text data processed in the United States for AI transcription and analysis. Zero-retention — data is not stored by Google after processing.
  • Stripe: Payment data processed in the United States for billing.
  • RevenueCat: Purchase receipt metadata processed in the United States.

8.2 Transfer Safeguards — Standard Contractual Clauses

For transfers of Personal Data from the EEA, UK, or Switzerland to a third country not subject to an adequacy decision, the parties agree that the EU Standard Contractual Clauses (Commission Implementing Decision (EU) 2021/914), Module Two (Controller-to-Processor), are incorporated by reference into this DPA and shall apply as follows:

  • Clause 7 — Docking Clause: Not applicable (only Controller and Processor are parties).
  • Clause 9(a) — Sub-processor Authorization: Option 2 (General Written Authorization) applies, with the specific notice period of 30 days as stated in Section 3.3 of this DPA.
  • Clause 11(a) — Redress: The optional language shall not apply. Data Subjects may not lodge complaints with an independent dispute resolution body at no cost.
  • Clause 17 — Governing Law: The laws of Ireland (for EEA transfers) or the laws of England and Wales (for UK transfers) shall govern the SCCs.
  • Clause 18 — Choice of Forum: Disputes shall be resolved by the courts of Ireland (for EEA) or England and Wales (for UK).
  • Annex I.A — Data Exporter: Controller (as identified by account registration data).
  • Annex I.B — Data Importer: Aeon Kosmos, LLC, 9169 W State St, Ste 3694, Garden City, ID 83714, USA. Contact: support@exporb.com.
  • Annex II — Technical & Organisational Measures: As described in Section 6 of this DPA.
  • Annex III — Sub-processors: As listed in Section 3.1 of this DPA.

Supplementary Measures (Schrems II)

For US-based Sub-processors (Google, Stripe, RevenueCat), Processor has conducted transfer-impact assessments and applies supplementary measures: (a) AES-256 encryption at rest; (b) TLS 1.2+ in transit; (c) pseudonymization of extracts where feasible; (d) reliance on EU-US Data Privacy Framework certification where the Sub-processor holds it (Google, Stripe, RevenueCat, Sentry are DPF-certified); (e) zero-retention inference mode for Google AI processing. Where Sub-processors are subject to FISA 702 or EO 12333, Processor has assessed that the data categories transferred and the encryption in transit make bulk surveillance disproportionate and practically infeasible.

8.3 UK Addendum

For transfers subject to UK GDPR, the International Data Transfer Addendum to the EU SCCs (issued by the UK ICO, version B1.0, in force 21 March 2022) is incorporated by reference. Tables 1-3 are completed per the SCC selections above. Table 4: Either party may end this Addendum per Section 19 of the Mandatory Clauses.

09

9. Audit Rights

Controller may, no more than once per twelve-month period and at Controller's expense, audit Processor's compliance with this DPA, subject to the following:

  • Audit requests must be submitted in writing at least 30 days in advance.
  • Audits are scoped to Processor's Processing of Controller's Personal Data.
  • Audits shall not unreasonably disrupt Processor's business operations.
  • Controller's auditor must sign a confidentiality agreement acceptable to Processor.
  • Controller bears all costs of the audit (including Processor's reasonable time spent supporting it).
  • Findings shall be shared with Processor and treated as confidential.

Alternative: Third-Party Certifications

In lieu of an on-site audit, Controller may request Processor's most recent security documentation, including Sub-processor SOC 2 reports (Supabase), penetration test summaries, and the incident log maintained under Section 7. Processor will provide these within 30 days of a written request to support@exporb.com.

10

10. Term & Termination

10.1 Duration

This DPA takes effect on the Effective Date and continues until the later of: (a) termination of Controller's account; or (b) the completion of all data deletion obligations in Section 10.2.

10.2 Deletion or Return of Data

Upon termination of the Service, Processor shall, at Controller's choice, delete or return all Customer Data. The deletion timeline follows the Privacy Policy Section 8:

  • Days 0-30: Data retained for recovery (Controller can request return during this period).
  • Day 30: All Customer Data permanently deleted from live systems.
  • Day 90: Customer Data purged from backups.
  • Exception: Legal/financial records retained as required by applicable law (tax compliance, max 7 years).

Processor will provide written confirmation of deletion within 30 days of completion.

11

11. Governing Law & Liability

11.1 Governing Law

This DPA is governed by the laws specified in Section 16 of the Terms of Service (Delaware, USA), provided that where the GDPR, UK GDPR, or Swiss FADP applies, the relevant provisions of those laws shall govern to the extent required by such laws. The SCCs incorporated under Section 8 shall be governed per Clauses 17-18 of the SCCs.

11.2 Order of Precedence

In the event of any conflict between this DPA and the Terms of Service, this DPA shall prevail with respect to data protection and privacy obligations. The SCCs shall prevail over this DPA with respect to the subject matter of the SCCs.

11.3 Liability

Processor's liability under this DPA is subject to the limitations in Section 14 of the Terms of Service (Limitation of Liability), except that nothing in this DPA limits either party's liability for: (a) violations of Data Subject rights under GDPR; (b) data breaches caused by Processor's failure to implement the security measures in Section 6; or (c) fines imposed by supervisory authorities to the extent caused by Processor's breach of this DPA.

12

12. Contact & Updates

For questions about this DPA, to exercise audit rights, or to request a signed copy:

Email

support@exporb.com

Subject: "DPA Request"

Mailing Address

Aeon Kosmos, LLC

9169 W State St, Ste 3694

Garden City, ID 83714

USA

12.1 DPA Updates

This DPA may be updated to reflect new Sub-processors, updated security measures, or changes in applicable law. Updates follow the same notice procedure as the Terms of Service:

  • Minor updates: posted here, effective on posting
  • Material changes: 30 days' email notice to account administrator
  • New Sub-processors: per Section 3.3 (30 days' notice + objection right)

Version: DPA v1.0 — Effective June 19, 2026. This DPA is incorporated by reference into the Exporb Terms of Service. By using Exporb, you enter into this DPA.