Legal

Data Processing Agreement

GDPR Article 28 agreement governing how we process personal data on your behalf.

Last updated: 2026-10-08

By accepting the Terms of Service, you execute this DPA on the terms stated herein as of the date of your acceptance.

.Parties

Between:

IKARUSHOLDS LLC ("Data Processor"), a limited liability company incorporated in Florida, USA, operating the Texterz.ai platform

And:

The Customer ("Data Controller") who has accepted the Terms of Service.

1.Definitions

TermDefinition
Personal DataAny information relating to an identified or identifiable natural person
ProcessingAny operation on Personal Data (collection, storage, use, disclosure, deletion)
Data SubjectThe natural person to whom Personal Data relates
Sub-ProcessorAny third party engaged by the Processor to process Personal Data on behalf of the Controller. Customer-Directed Recipients (Section 4.6) are not Sub-Processors
GDPREU General Data Protection Regulation 2016/679
PIPEDAPersonal Information Protection and Electronic Documents Act (Canada)

2.Scope and Purpose

This DPA governs the processing of Personal Data by IKARUSHOLDS LLC on behalf of the Customer in connection with the Texterz.ai platform ("Services").

The subject matter, nature, purpose, and duration of processing are described in Annex I below.

The Processor shall process Personal Data only:

  • On documented instructions from the Controller, including with regard to transfers of Personal Data to a third country or an international organisation
  • As necessary to provide the Services
  • Where required by Union or Member State law to which the Processor is subject; in that case the Processor shall inform the Controller of that legal requirement before processing, unless that law prohibits such information on important grounds of public interest

The Processor shall immediately inform the Controller if, in its opinion, an instruction infringes the GDPR or other applicable data protection provisions (Art. 28(3) GDPR).

2.5Customer Acting as Processor (White-Label)

Where the Customer resells or provides the Services to its own clients, including under the White-Label Partner Policy, the Customer acts as processor on behalf of those clients and the Processor acts as the Customer's sub-processor. In that case:

  • The Customer warrants that it has obtained from each of its clients the general written authorisation required by Art. 28(2) GDPR to engage the Processor and the Sub-Processors listed in Annex II, and that its agreements with its clients impose on the Processor no data protection obligations beyond those set out in this DPA (Art. 28(4) GDPR)
  • The Customer shall pass on each notice received under Section 4.4 to its clients without undue delay and within the notice period agreed with them, and shall relay any objection of a client to the Processor
  • Instructions, requests, audits and objections of the Customer's clients are made through the Customer; the Processor notifies Personal Data breaches to the Customer, which notifies its clients
  • Module Three of the SCCs applies as set out in Section 4.2

3.Obligations of the Processor

3.1Confidentiality

The Processor ensures that persons authorized to process Personal Data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality.

3.2Security

The Processor implements appropriate technical and organizational measures including:

  • Encryption of all data in transit (TLS 1.3, mutual TLS between services) and at rest (AES-256)
  • Per-tenant database isolation
  • Access controls with least-privilege principles
  • Audit logging for all write operations
  • Regular security assessments

3.3Sub-Processors

The Controller provides general written authorization for the Processor to engage the Sub-Processors listed in Annex II by executing this DPA. The Processor shall notify the Controller of any changes to Sub-Processors in accordance with Section 4.4.

The Processor shall impose equivalent data protection obligations on Sub-Processors and remain liable for their compliance.

3.4Data Subject Rights

Upon request, the Processor shall assist the Controller in responding to Data Subject requests including:

  • Right of Access (Art. 15 GDPR)
  • Right to Erasure (Art. 17 GDPR)
  • Right to Rectification (Art. 16 GDPR)
  • Right to Restriction (Art. 18 GDPR)
  • Right to Portability (Art. 20 GDPR)
  • Right to Object (Art. 21 GDPR)

3.5Data Breach Notification

The Processor shall notify the Controller without undue delay, and in any event no later than 48 hours after becoming aware, of a Personal Data breach, providing:

  • Nature of the breach
  • Categories and approximate number of Data Subjects and records affected
  • Likely consequences
  • Measures taken or proposed

3.6Data Protection Impact Assessments

The Processor shall assist the Controller with DPIAs where required by applicable law, and with prior consultation of supervisory authorities under Art. 36 GDPR where applicable.

3.7Audit Rights

Upon reasonable written request with at least 30 days advance notice and no more than once per calendar year, the Controller may request an audit or inspection of the Processor's data handling practices. The Processor may satisfy this obligation by providing a written summary of security measures, recent penetration test results (if available) or a third-party audit report. On-site inspections require mutual agreement on scope, timing and confidentiality. The Controller shall bear its own costs for any audit.

3.8Deletion / Return of Data

Upon termination of the Services, the Processor shall, at the Controller's choice:

  • Delete all Personal Data and certify deletion, or
  • Return all Personal Data in machine-readable format (JSON)

Deletion shall be completed within 30 days of termination. Backup systems may retain encrypted copies for up to a further 30 days, matching the configured backup retention cycle, after which they are permanently purged.

4.International Transfers

The Processor utilizes infrastructure providers with data center locations in the European Union and the United States. The Processor implements encryption in transit (TLS 1.3) and at rest (AES-256) for all Personal Data regardless of processing location.

4.2Standard Contractual Clauses

The Processor is established in the United States and is not certified under the EU-U.S. Data Privacy Framework. To the extent Personal Data subject to the GDPR is transferred to the Processor, the parties hereby enter into the standard contractual clauses annexed to Commission Implementing Decision (EU) 2021/914 ("SCCs"), which are incorporated into this DPA by reference: Module Two (controller to processor) where the Customer acts as controller, and Module Three (processor to processor) where the Customer acts as processor on behalf of its own clients (Section 2.5).

For the purposes of the SCCs: Clause 7 (docking clause) applies; under Clause 9(a), Option 2 (general written authorisation) applies, with notice given as set out in Section 4.4; the optional language in Clause 11(a) does not apply; the competent supervisory authority under Clause 13 is determined in accordance with Clause 13(a) by reference to the Customer as data exporter; under Clause 17, Option 1 applies and the SCCs are governed by the law of Ireland; under Clause 18, disputes are resolved by the courts of Ireland. The Parties section and Annex I of this DPA serve as Annex I of the SCCs, Annex III of this DPA as Annex II of the SCCs, and Annex II of this DPA as Annex III of the SCCs. In the event of a conflict between this DPA and the SCCs, the SCCs prevail.

Where the Processor engages a Sub-Processor outside the European Economic Area, it does so under a written contract that provides the same data protection obligations as this DPA and the SCCs (Clauses 8.8 and 9(b)), relying on the Sub-Processor's certification under the Data Privacy Framework or on the SCCs, as indicated in Annex II.

For transfers subject to the UK GDPR, the International Data Transfer Addendum to the EU Commission Standard Contractual Clauses issued by the UK Information Commissioner applies and is incorporated by reference. For transfers subject to the Swiss Federal Act on Data Protection (FADP), the SCCs apply with the adaptations required by the Swiss Federal Data Protection and Information Commissioner (FDPIC): references to the GDPR are read as references to the FADP, the FDPIC is the competent supervisory authority, and the term "Member State" does not exclude Data Subjects in Switzerland from bringing claims at their place of habitual residence.

The Processor has assessed the laws and practices of the United States applicable to it as data importer (transfer impact assessment) and will provide a summary of that assessment to the Controller on request.

Canadian Data Subjects (PIPEDA): The Controller acknowledges that data may be processed outside of Canada. The Processor will disclose the purpose, nature, and location of such transfers upon request.

The Processor shall notify the Controller of any intended addition or replacement of a Sub-Processor by email to the Customer's account owner address and by updating Annex II. Notice is given as soon as reasonably practicable and, where the Processor makes the change itself or its upstream provider gives the Processor advance notice, before the new Sub-Processor processes Personal Data. The Controller may object to the change on reasonable data protection grounds within 14 days of notice. If the parties cannot resolve the objection in good faith within a further 14 days, the Controller may terminate the affected Services without penalty, and the Processor shall refund any prepaid fees for the terminated Services covering the period after termination.

4.5Privacy Contact

Controllers and Data Subjects can reach the Processor directly at privacy@texterz.ai.

4.6Customer-Directed Transfers

The Services allow the Controller to connect tools, systems and recipients of its own choosing, including AI agents and clients connected through the Processor's MCP server or API, webhooks and HTTP actions, the Controller's own email (SMTP) server, connected calendar and scheduling accounts (such as Google Calendar, Microsoft 365, Cal.com and Calendly), and the Controller's own payment accounts (such as Stripe or PayPal) ("Customer-Directed Recipients"). When the Controller or its authorised users configure or trigger a transfer of Personal Data to a Customer-Directed Recipient, that transfer is a documented instruction of the Controller under Section 2.3.

Customer-Directed Recipients are not engaged by the Processor, are not Sub-Processors and are not listed in Annex II. The Controller is solely responsible for selecting each Customer-Directed Recipient, for having a lawful basis and, where required, a transfer mechanism for the transfer, and for its own agreement with that recipient. The Processor's obligations under this DPA apply to Personal Data while it is processed within the Services and end when the Personal Data is delivered to the Customer-Directed Recipient.

5.Term and Termination

This DPA is effective from the date of the Customer's acceptance of the Terms of Service and remains in force for the duration of the Services Agreement.

Either Party may terminate this DPA in case of material breach, upon 30 days written notice if the breach is not remedied.

6.Liability

Each Party shall be liable for damages caused to the other Party due to breach of this DPA, subject to the limitations set forth in the Terms of Service.

Where both Parties are responsible for damage to a Data Subject, liability shall be apportioned according to each Party's degree of fault.

7.Governing Law

The commercial Controller-Processor relationship under this DPA is governed by the laws of Florida, USA.

The Standard Contractual Clauses (Section 4.2) and all obligations arising under EU GDPR are governed by the laws of Ireland. This governing law applies to the interpretation, performance, and enforcement of the SCCs regardless of Section 7.1. Disputes arising from the SCCs are resolved by the courts of Ireland, without prejudice to the right of Data Subjects under Clause 18(c) of the SCCs to bring proceedings in the Member State of their habitual residence.

Obligations arising under Canadian PIPEDA are governed by the applicable Canadian federal and provincial privacy laws.

I.Annex I: Processing Details

Subject matterAI chatbot and communication automation services
DurationDuration of Services Agreement
NatureCollection, storage, use, transmission, and deletion of message content and user metadata
PurposeProviding AI-powered communication services (WhatsApp, Telegram, SMS, Voice, Web)
Categories of Personal DataNames, phone numbers, email addresses, conversation transcripts, voice call recordings and their transcripts, media files exchanged with End Users, documents uploaded to knowledge bases and data derived from them, appointment and calendar data, behavioral data
Categories of Data SubjectsEnd users of the Controller's communication channels
Health informationThe Processor does not enter into business associate agreements under HIPAA. The Controller shall not submit protected health information (PHI) to the Services

AI Model Processing

End User messages are routed through the Processor's infrastructure to third-party LLM providers (Sub-Processors listed in Annex II) for AI-generated responses, then delivered back to the End User via the originating channel.

What is sent to LLM providers:

  • End User message content
  • Controller's system prompt and bot configuration
  • Conversation history (for context, configurable retention)
  • Media sent by the End User, as a time-limited signed link, where the Controller's bot configuration provides for it

What is NOT sent to LLM providers:

  • Encrypted credentials
  • Billing or payment information
  • Data from other tenants

End User identifiers such as phone numbers and email addresses are not transmitted by default. The Controller may include them through its own bot configuration and is responsible for that decision.

II.Annex II: Approved Sub-Processors

EntityRolePurposeLocationTransfer basis
Hetzner Cloud GmbHSub-ProcessorInfrastructure, compute, databases, object storageEUNot applicable (EU)
OpenRouter, Inc.Sub-ProcessorAI model routing (chat, embeddings); forwards requests to the inference hosts marked "via OpenRouter", with providers that use data for training excludedUSASCCs
OpenAIInference host via OpenRouterAI model inferenceUSAOpenRouter's sub-processor terms
AnthropicInference host via OpenRouterAI model inferenceUSAOpenRouter's sub-processor terms
Google LLCInference host via OpenRouterAI model inference (Gemini API, Vertex AI)USA/globalOpenRouter's sub-processor terms
Microsoft Corporation (Azure)Inference host via OpenRouterAI model inferenceUSA/EUOpenRouter's sub-processor terms
Amazon Web Services, Inc.Inference host via OpenRouterAI model inference (Amazon Bedrock)USA/EUOpenRouter's sub-processor terms
xAI Corp.Inference host via OpenRouterAI model inference (Grok)USAOpenRouter's sub-processor terms
Mistral AI SASInference host via OpenRouterAI model inference (Mistral)EUOpenRouter's sub-processor terms
Deep Infra Inc.Inference host via OpenRouterAI model inference (Meta Llama models), including conversation summariesUSAOpenRouter's sub-processor terms; not certified under the Data Privacy Framework
Meta Platforms Ireland Limited; Meta Platforms, Inc. for Controllers in the USA, Canada or BrazilSub-ProcessorWhatsApp Business Platform (Cloud API)Ireland/USAMeta's processor terms
Twilio Inc.Sub-Processor (see note)SMS/MMS, voice calls and call recordings, phone-number regulatory complianceUSAData Privacy Framework
Plus Five Five, Inc. d/b/a ResendSub-ProcessorTransactional email and inbound email for the email channelUSAData Privacy Framework; SCCs
Telegram Messenger Inc.Sub-ProcessorTelegram Bot APIOutside the EEATelegram's terms
Deepgram, Inc.Sub-ProcessorSpeech-to-text and text-to-speechUSASCCs
ElevenLabs Inc.Sub-ProcessorText-to-speechUSA/EUData Privacy Framework
Apple Inc.Sub-ProcessorPush notifications to the Controller's users (Apple Push Notification service)USAData Privacy Framework
Google LLCSub-ProcessorPush notifications to the Controller's users (Firebase Cloud Messaging)USAData Privacy Framework
Stripe, Inc.Sub-ProcessorPayment processingUSAData Privacy Framework

OpenRouter routes each AI request only to the inference hosts marked "via OpenRouter", and only to their endpoints that OpenRouter designates as zero-data-retention; which host processes a given request depends on the model the Controller selects and on availability. Twilio acts as an independent controller of message content for its own purposes, including abuse prevention (with related model training) and product improvement, as set out in Section 3.4 of the Twilio Data Protection Addendum. Changes to this list are notified as set out in Section 4.4.

III.Annex III: Technical and Organisational Measures

In addition to the measures in Section 3.2, the Processor maintains:

  • Tenant isolation: a separate database for each Customer tenant
  • Encryption in transit: TLS for external connections and mutual TLS between internal services
  • Encryption at rest for databases, object storage and backups
  • Role-based access control for the Controller's users within the Services, and least-privilege access for the Processor's personnel
  • Audit logs of write operations
  • Regular backups on a 30-day retention cycle (Section 3.8)

8.Contact

Data Protection Contact

IKARUSHOLDS LLC

1242 SW Pine Island Rd, Ste 42-348

Cape Coral, FL 33991, USA

The commercial relationship is governed by Florida law. EU GDPR obligations and Standard Contractual Clauses are governed by the laws of Ireland and subject to the jurisdiction of the courts of Ireland.