Cognitiva Systems Inc.
INTRODUCTION#
This document lists the sub-processors Cognitiva Systems Inc. ("Cognitiva") uses to process personal data on behalf of our customers.
What is a Sub-processor?
A sub-processor is a third-party service provider that processes personal data on behalf of Cognitiva to help us provide our Services.
Why We Disclose This:
- GDPR Article 28(3)(d) requires data processors to inform customers of sub-processors
- Transparency and trust
- Customer due diligence
CURRENT SUB-PROCESSORS#
Payment, verification and integration partners today: Stripe is the only one under a signed contract and active. Didit, Surepass, Rapyd, Zapier and Voyage AI are in development and testing: they process test data only, and are listed in advance so customers can review them. Each goes live only after a signed contract and the 30-day notice under Change Management.
1. CLOUD AND WEB HOSTING#
Amazon Web Services (AWS)
Entity: Amazon Web Services, Inc.
Purpose: Cloud hosting, compute, storage and database services
Data Processed: Customer data stored on the platform (campaign data, user accounts, files)
Location: United States and European Union regions
Data Transfer Mechanism: EU Standard Contractual Clauses (SCCs)
Certifications: ISO 27001, SOC 2 Type II, ISO 27017, ISO 27018
Privacy Policy: https://aws.amazon.com/privacy/
Website: https://aws.amazon.com
Google Cloud
Entity: Google LLC
Purpose: Document storage
Data Processed: Uploaded documents and files
Location: United States and European Union regions
Data Transfer Mechanism: EU Standard Contractual Clauses (SCCs)
Certifications: ISO 27001, SOC 2 Type II, ISO 27017, ISO 27018
Privacy Policy: https://cloud.google.com/terms/cloud-privacy-notice
Website: https://cloud.google.com
Vercel
Entity: Vercel Inc.
Purpose: Web hosting for the website and web application
Data Processed: HTTP request data (IP addresses, headers), pages and forms served to visitors
Location: United States
Data Transfer Mechanism: EU Standard Contractual Clauses (SCCs)
Certifications: As published in the provider's own trust documentation
Privacy Policy: https://vercel.com/legal/privacy-policy
Website: https://vercel.com
Supabase
Entity: Supabase Inc.
Purpose: Databases and authentication for the shareholder portal and for Cognitiva ID creator verification (cognitiva-id.me), and private file storage for verification evidence
Data Processed: Portal and creator accounts, login credentials (hashed), session data, verification outcomes and references, connected-profile data, uploaded evidence files
Location: United States
Data Transfer Mechanism: EU Standard Contractual Clauses (SCCs)
Certifications: As published in the provider's own trust documentation
Privacy Policy: https://supabase.com/privacy
Website: https://supabase.com
Cloudflare
Entity: Cloudflare, Inc.
Purpose: DNS, content delivery network, bot protection (Turnstile) and cookieless web analytics for our domains, including the CognitivaOS console
Data Processed: HTTP request data (IP addresses, headers, user agent), Turnstile challenge signals, aggregated page-view data
Location: Global edge network; United States
Data Transfer Mechanism: EU-U.S. Data Privacy Framework, EU SCCs
Certifications: ISO 27001, SOC 2 Type II, PCI DSS
Privacy Policy: https://www.cloudflare.com/privacypolicy/
Website: https://www.cloudflare.com
Upstash
Entity: Upstash, Inc.
Purpose: Rate limiting and anti-scraping counters for cognitiva-id.me
Data Processed: Hashed IP addresses and request counters (short-lived)
Location: United States and European Union regions
Data Transfer Mechanism: EU Standard Contractual Clauses (SCCs)
Certifications: SOC 2 Type II
Privacy Policy: https://upstash.com/trust/privacy.pdf
Website: https://upstash.com
2. COMMUNICATION#
Resend
Entity: Resend
Purpose: Transactional email delivery (account notices, workflow notifications, receipts)
Data Processed: Email addresses, email content (transactional only), delivery logs
Location: United States
Data Transfer Mechanism: EU Standard Contractual Clauses (SCCs)
Data Retention: Email logs retained for 30 days
Certifications: As published in the provider's own trust documentation
Privacy Policy: https://resend.com/legal/privacy-policy
Website: https://resend.com
Anthropic
Entity: Anthropic, PBC
Purpose: AI model for the website chat assistant, for customer-support tickets about CognitivaOS, for drafting replies in our internal workspace (a person reviews every draft before it is sent), and for reading profile screenshots a creator uploads as evidence on cognitiva-id.me (when that feature is switched on)
Data Processed: Chat messages (not the name or email a visitor enters), support-ticket and email content, names and business contact details in that content
Data Use: Not used to train Anthropic's models under its commercial terms
Location: United States
Data Transfer Mechanism: EU Standard Contractual Clauses (SCCs)
Certifications: As published in the provider's own trust documentation
Privacy Policy: https://www.anthropic.com/legal/privacy
Website: https://www.anthropic.com
Google Workspace
Entity: Google LLC
Purpose: Business email, documents, chat and calendar for our staff, including appointment booking for demos and tours
Data Processed: Correspondence with customers, creators and prospects; names, business contact details and booking details; documents shared with us
Location: United States and European Union regions
Data Transfer Mechanism: EU-U.S. Data Privacy Framework, EU SCCs
Certifications: ISO 27001, ISO 27017, ISO 27018, SOC 2 Type II
Privacy Policy: https://policies.google.com/privacy
Website: https://workspace.google.com
3. INTEGRATIONS#
Zapier
Status: In development and testing. No contract signed yet; processes test data only, never live customer or creator data. Goes live only after a signed contract and the 30-day notice below
Entity: Zapier, Inc.
Purpose: Integration platform (white-label) that connects CognitivaOS to the tools a customer already uses, at the customer's instruction
Data Processed: The records a customer chooses to sync (for example campaign, contract-status and contact data) and connection credentials
Location: United States
Data Transfer Mechanism: EU-U.S. Data Privacy Framework, EU SCCs
Certifications: SOC 2 Type II, SOC 3
Privacy Policy: https://zapier.com/privacy
Website: https://zapier.com
Voyage AI
Status: In development and testing. No contract signed yet; processes test data only, never live customer or creator data. Goes live only after a signed contract and the 30-day notice below
Entity: Voyage AI
Purpose: Text embeddings so brands can search the descriptions creators write about themselves on cognitiva-id.me (only creators who switched discovery on)
Data Processed: The creator's own self-description and audience description; no names, contact details or documents
Location: United States
Data Transfer Mechanism: EU Standard Contractual Clauses (SCCs)
Privacy Policy: https://www.voyageai.com/privacy
Website: https://www.voyageai.com
OpenStreetMap Nominatim
Entity: OpenStreetMap Foundation
Purpose: Address look-up when our staff enter a shareholder's postal address in the shareholder portal
Data Processed: The address text typed into the search field and the requesting IP address; no name or account data is sent
Location: European Union and United Kingdom
Data Transfer Mechanism: Not required (EU/UK adequacy)
Privacy Policy: https://osmfoundation.org/wiki/Privacy_Policy
Website: https://nominatim.org
4. ANALYTICS#
Google Analytics
Entity: Google LLC
Purpose: Website analytics (consent-based; loaded only after the visitor allows analytics cookies)
Data Processed: IP addresses (anonymized), browser information, page views, user interactions
Location: United States
Data Transfer Mechanism: EU-U.S. Data Privacy Framework, EU SCCs
IP Anonymization: Enabled (last octet removed before storage)
Data Retention: 14 months
Privacy Policy: https://policies.google.com/privacy
Opt-Out: https://tools.google.com/dlpage/gaoptout
5. IDENTITY VERIFICATION#
Didit
Status: In development and testing. No contract signed yet; processes test data only, never live customer or creator data. Goes live only after a signed contract and the 30-day notice below
Entity: Didit (regulated identity-verification provider)
Purpose: Identity, document, liveness and face-match checks for creator verification and for shareholder (KYC) verification
Data Processed: Government-issued identity documents, selfie and liveness (biometric) data, address documents, verification result. Didit holds the documents and biometric data; Cognitiva stores only the verification outcome, a reference and the expiry
Location: European Union; other locations as set out in Didit's data processing terms
Data Transfer Mechanism: EU Standard Contractual Clauses (SCCs) where data leaves the EEA
Fees to creators or shareholders: None; Cognitiva pays for each check
Privacy Policy: https://didit.me/privacy-policy
Website: https://didit.me
Surepass
Status: In development and testing. No contract signed yet; processes test data only, never live customer or creator data. Goes live only after a signed contract and the 30-day notice below
Entity: Surepass Technologies
Purpose: Confirming a UAE Emirates ID or trade licence with the issuing authority for creator verification (India later)
Data Processed: Emirates ID or licence number, the names on the licence, the result
Location: India
Data Transfer Mechanism: EU Standard Contractual Clauses (SCCs) where EEA data is involved; UAE PDPL transfer basis to be confirmed by counsel
Fees to creators: None; Cognitiva pays for each check
Website: https://surepass.io
6. PAYMENTS#
Stripe
Status: Active (contract signed)
Entity: Stripe, Inc. and its licensed affiliates (Stripe Payments and Stripe Connect)
Purpose: Reserving and charging the USD 10 creator verification fee, and collecting customer payments
Data Processed: Card and bank details, billing information, identity data Stripe requires for its own checks, transaction records
Location: United States, European Union and the local markets Stripe serves
Data Transfer Mechanism: Stripe acts as an independent data controller for payment data; EU-U.S. Data Privacy Framework and EU SCCs where it processes on our behalf
Certifications: PCI DSS Level 1, SOC 1 and SOC 2 Type II
Fees: Card-processing fees on the USD 10 are paid by Cognitiva. Fees on customer payments are passed through at cost, with no Cognitiva markup
Privacy Policy: https://stripe.com/privacy
Website: https://stripe.com
Rapyd
Status: In development and testing. No contract signed yet; processes test data only, never live customer or creator data. Goes live only after a signed contract and the 30-day notice below
Entity: Rapyd Financial Network and its licensed affiliates
Purpose: Payout wallets held in the name of each creator, brand or agency; setting deal funds aside on signing and releasing them on approval; creator payouts
Data Processed: Wallet holder name and identity data, bank details, transaction records
Location: European Union, United Kingdom, United States and the local markets Rapyd serves
Data Transfer Mechanism: Rapyd acts as an independent data controller for payment data; EU SCCs where it processes on our behalf
Certifications: PCI DSS Level 1
Fees: Payout, cross-border and currency-conversion fees on creator payouts are passed through at cost, with no Cognitiva markup. Wallet fees are paid by Cognitiva. Cognitiva charges creators nothing (see the Creator Terms, Section 4)
Privacy Policy: https://www.rapyd.net/legal/privacy-policy/
Website: https://www.rapyd.net
Local Licensed Payment Partners
Status: None selected yet
Entity: Named to customers and creators in the affected market before they handle any money
Purpose: The same as Rapyd, in markets Rapyd does not serve
Data Processed: Payment and bank details, billing information, transaction records
Location: The local market concerned
Data Transfer Mechanism: Independent data controller for payment data; EU SCCs where it processes on our behalf
Fees: Their published fees, passed through at cost, with no Cognitiva markup
Important Note:
Our licensed payment partners are independent data controllers for payment processing. Cognitiva does not store card or bank details and is not responsible for the partner's own data processing. Refer to the partner's privacy policy for details.
CHANGE MANAGEMENT#
Notification of Changes#
30-Day Advance Notice:
We will notify customers at least 30 days in advance before:
- Adding a new sub-processor
- Changing an existing sub-processor's purpose or data processing scope
- Replacing a sub-processor with a different entity
Notification Method:
- Email to account administrator
- In-app notification
- Update to this page (check "Last Updated" date)
Customer Objection Rights#
You have the right to object to new sub-processors or changes.
How to Object:
- Email: dpa@cognitiva.systems
- Subject: "Sub-Processor Objection - [Company Name]"
- Within: 15 days of notification
- Include: Specific objection reasons (data protection grounds)
If We Cannot Accommodate Objection:
- Good faith discussion to resolve concerns
- If unresolved, you may terminate Services Agreement with 30 days notice
- Pro-rated refund of prepaid fees
If No Objection:
Failure to object within 15 days constitutes acceptance.
DATA PROTECTION SAFEGUARDS#
Contractual Protections#
All sub-processors are contractually obligated to:
✓ Process data only on Cognitiva's instructions
✓ Maintain confidentiality
✓ Implement appropriate technical and organizational security measures
✓ Assist with data subject rights requests
✓ Notify Cognitiva of personal data breaches
✓ Delete or return data upon termination
✓ Provide independent audit reports (such as SOC 2 or ISO 27001), and allow audits or inspections as their data processing agreement with Cognitiva provides
International Data Transfers#
For sub-processors located outside the European Economic Area:
✓ EU Standard Contractual Clauses (SCCs) or the EU-U.S. Data Privacy Framework: In place with every non-EU sub-processor, through its data processing agreement with Cognitiva
✓ UK International Data Transfer Addendum (IDTA): For UK personal data
✓ Transfer Impact Assessments (TIAs): Conducted per Schrems II requirements
✓ Supplementary Measures: Encryption in transit (TLS 1.3) and at rest (AES-256)
Security Measures#
All sub-processors must implement:
✓ Encryption in transit and at rest
✓ Access controls and authentication
✓ Regular security assessments
✓ Incident response procedures
✓ Employee training on data protection
✓ Industry-standard certifications (ISO 27001, SOC 2, etc.)
SUB-PROCESSOR CATEGORIES#
Processing Activities#
| Sub-Processor | Hosting | Communication | Integrations | Analytics | Identity | Payment |
|---|---|---|---|---|---|---|
| AWS | ✅ | |||||
| Google Cloud | ✅ | |||||
| Vercel | ✅ | |||||
| Supabase | ✅ | |||||
| Upstash | ✅ | |||||
| Cloudflare | ✅ | ✅ | ||||
| Resend | ✅ | |||||
| Anthropic | ✅ | |||||
| Google Workspace | ✅ | |||||
| Zapier (testing) | ✅ | |||||
| Voyage AI (testing) | ✅ | |||||
| OpenStreetMap Nominatim | ✅ | |||||
| Google Analytics | ✅ | |||||
| Didit (testing) | ✅ | |||||
| Surepass (testing) | ✅ | |||||
| Stripe | ✅ | |||||
| Rapyd (testing) | ✅ | |||||
| Local licensed payment partners | ✅ |
DATA LOCATIONS#
Where Your Data May Be Processed#
United States:
- AWS (US regions)
- Google Cloud (US regions)
- Google Workspace (US regions)
- Vercel
- Supabase
- Upstash (US regions)
- Cloudflare (and its global edge network)
- Resend
- Anthropic
- Zapier
- Voyage AI
- Google Analytics
- Stripe
- Rapyd (US)
European Union and United Kingdom:
- AWS (EU regions)
- Google Cloud (EU regions)
- Google Workspace (EU regions)
- Stripe (EU)
- Rapyd (EU and UK)
- Upstash (EU regions)
- Didit
- OpenStreetMap Nominatim
India:
- Surepass
Local markets:
- Local licensed payment partners
Customer Control:
Enterprise customers can specify data residency preferences (US-only, EU-only, or multi-region).
FREQUENTLY ASKED QUESTIONS#
Q1: Can I request that my data only be processed in the EU?#
A: Yes. Enterprise customers can request EU-only data residency. Platform data is then stored only in AWS (EU regions) and Google Cloud (EU regions). Edge delivery (Cloudflare), identity checks (Didit, EU; Surepass, India, for UAE documents) and payments (Stripe and Rapyd, EU entities) continue as listed above. Some features may have limited availability.
Contact: sales@cognitiva.systems for EU data residency options
Q2: What happens if a sub-processor has a data breach?#
A: Sub-processors are contractually required to notify us within 24-48 hours. We then:
- Assess impact on customer data
- Notify affected customers without undue delay, so that a controller can meet its 72-hour duty to the supervisory authority under GDPR Article 33
- Cooperate with investigation and remediation
- Evaluate continued relationship with sub-processor
Q3: Can I audit sub-processors?#
A: Customers can audit Cognitiva's compliance (including sub-processor management). Direct sub-processor audits typically require:
- Reasonable advance notice
- Confidentiality agreements
- Coordination with Cognitiva
- Or: Review of sub-processor's SOC 2 / ISO 27001 reports (substitute for on-site audit)
Contact: dpa@cognitiva.systems to arrange audit
Q4: Does Cognitiva use any sub-processors in China, Russia, or other high-risk countries?#
A: No. We do not use sub-processors located in or subject to laws of countries deemed high-risk for data protection. All sub-processors are in US, EU, or equivalent jurisdictions with strong data protection frameworks.
Q5: What if I object to a sub-processor on GDPR Article 28 grounds?#
A: You have the right to object. We will:
- Discuss your concerns in good faith
- Seek alternative sub-processor if feasible
- If we cannot accommodate, you may terminate agreement with 30 days notice and receive pro-rated refund
This is a legal right under GDPR Article 28(2).
Q6: Are sub-processors in the US subject to CLOUD Act or FISA 702?#
A: Yes, US-based sub-processors may be subject to US government access requests under:
- CLOUD Act (cross-border lawful access)
- FISA Section 702 (foreign intelligence surveillance)
Our Safeguards:
- Encryption prevents government access to plaintext data
- Transfer Impact Assessments conducted
- Contractual commitments to challenge overbroad requests
- Transparency reporting of government requests (annual)
Read More: Privacy Policy Section 12.3 (Schrems II Compliance)
CONTACT INFORMATION#
For Sub-Processor Questions:#
Email: dpa@cognitiva.systems
Subject: "Sub-Processor Inquiry - [Company Name]"
Response Time: 5 business days
To Object to Sub-Processor:#
Email: dpa@cognitiva.systems
Subject: "Sub-Processor Objection - [Company Name]"
Deadline: Within 15 days of notification
For Data Processing Agreement:#
Email: dpa@cognitiva.systems
Request: Full Data Processing Agreement (DPA) template
LEGAL REFERENCES#
This sub-processor list is maintained pursuant to:
- GDPR Article 28(3)(d): Processor must inform controller of sub-processors
- GDPR Article 28(2): Prior written authorization required for sub-processors
- GDPR Article 28(4): Processor remains liable for sub-processor performance
DOCUMENT HISTORY#
| Version | Date | Changes |
|---|---|---|
| 1.0 | 15 April 2026 | Initial publication |
| 2.0 | 8 October 2026 | Vendor list aligned with the live stack |
| 3.1 | 27 October 2026 | Status added: Stripe active; Didit, Surepass, Rapyd, Zapier and Voyage AI in development and testing |
| 3.0 | 27 October 2026 | All third parties named: Cloudflare, Upstash, Google Workspace, Zapier, Voyage AI, OpenStreetMap Nominatim, Didit, Surepass, Stripe and Rapyd added; Supabase widened to Cognitiva ID; Anthropic's purpose widened; pass-through of third-party payment fees stated; audit and transfer wording aligned with provider terms |
Next Review: April 2027
TRANSPARENCY COMMITMENT#
We are committed to transparency about our data processing practices. This sub-processor list is updated promptly when changes occur.
Subscribe to Updates:
Email dpa@cognitiva.systems with subject "Subscribe to Sub-Processor Updates" to receive automatic notifications.
END OF SUB-PROCESSOR LIST
Published: 27 October 2026 (version 3.1)
Maintained by: Legal & Compliance Team
Contact: dpa@cognitiva.systems