Data Processing Addendum – Demaai AB
Version: 2026-10-19
This Data Processing Addendum (this "DPA"), including its Annexes, forms part of the agreement between Demaai AB ("Demaai") and the customer identified in the Order ("Customer") under which Demaai provides the Services (the "Agreement"). It applies where Demaai processes Customer Personal Data on Customer's behalf in providing the Services.
If this DPA conflicts with the Agreement, this DPA controls with respect to the processing of Customer Personal Data.
1. Definitions
Words defined in the Agreement have the same meaning in this DPA. In addition:
- "Applicable Data Protection Laws" means all laws relating to the processing of personal data that apply to a party's processing of Customer Personal Data under the Agreement, including, as applicable: (a) Regulation (EU) 2016/679 (the "EU GDPR") and the laws of EU and EEA member states implementing or supplementing it; (b) the EU GDPR as it forms part of the law of the United Kingdom (the "UK GDPR") and the UK Data Protection Act 2018; and (c) US State Privacy Laws.
- "US State Privacy Laws" means the California Consumer Privacy Act of 2018, as amended by the California Privacy Rights Act of 2020, and its implementing regulations (the "CCPA"), and any other comprehensive US state consumer privacy law to the extent it applies to the processing of Customer Personal Data.
- "Customer Personal Data" means personal data contained in Customer Data that Demaai processes on behalf of Customer in providing the Services, as further described in Annex 1.
- "Customer-Directed Integration" means a third-party product or service that Customer, or a User on Customer's behalf, selects, contracts with directly and connects to the Services, so that Demaai retrieves Customer Data from it or transmits Customer Data to it on Customer's instruction. Annex 3 describes the categories of Customer-Directed Integrations.
- "Personal Data Breach" means a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, Customer Personal Data transmitted, stored or otherwise processed by Demaai or its Subprocessors.
- "Subprocessor" means a processor engaged by Demaai that processes Customer Personal Data on Demaai's behalf.
The terms "controller", "processor", "data subject", "personal data", "processing", "special categories of personal data" and "supervisory authority" have the meanings given in the EU GDPR, or the equivalent terms in other Applicable Data Protection Laws. The terms "business", "service provider", "consumer", "sell", "share", "business purpose" and "sensitive personal information" have the meanings given in the CCPA.
2. Scope and roles
2.1. Scope. This DPA applies to Demaai's processing of Customer Personal Data in providing the Services. The subject matter, nature, purpose and duration of the processing, the types of personal data and the categories of data subjects are set out in Annex 1.
2.2. Roles. Customer may act as a controller or business of Customer Personal Data, in which case Demaai acts as its processor or service provider. Where Customer acts as a processor on behalf of another controller, Demaai acts as Customer's subprocessor. Customer warrants that its instructions, including the appointment of Demaai as a subprocessor, have been authorised by the relevant controller. Customer remains Demaai's sole point of contact for that controller.
2.3. Demaai as independent controller. Demaai processes the following personal data for its own purposes as an independent controller, and this DPA does not apply to that processing:
- business contact details of Customer's personnel, used to manage the commercial relationship, invoicing and communications;
- Users' account, authentication and security data, and product usage and diagnostic data relating to Users' interaction with the Services, such as feature usage, page views, error reports and support conversations, used to operate, secure, support and develop the Services; and
- personal data of visitors to Demaai's websites, prospects, event attendees and job applicants.
The controller processing described in this section does not include Demaai's processing of personal data about Customer's end customers or other individuals contained in Customer Data, which remains governed by this DPA when Demaai processes it on Customer's behalf.
Where the same personal data is also Customer Personal Data (for example, the names and email addresses of Users that Customer provides when inviting them), Demaai processes it as Customer's processor when providing the Services and as a controller only for the purposes described in its Privacy Policy.
2.4. Compliance with law. Both parties will comply with all applicable requirements of Applicable Data Protection Laws. The terms of this DPA are in addition to, and do not relieve, remove or replace, a party's obligations or rights under Applicable Data Protection Laws.
3. Customer's obligations
3.1. Lawfulness. Customer is responsible for:
- the lawfulness of its instructions and of the collection of Customer Personal Data, including having a lawful basis for each purpose of processing;
- giving data subjects all notices, and obtaining all consents, that Applicable Data Protection Laws require. This includes any consent required under Directive 2002/58/EC and national implementing laws for the Demaai tracking script and other technologies Customer deploys on its websites and apps;
- the accuracy and quality of Customer Personal Data; and
- informing Demaai without undue delay of Customer Personal Data that is inaccurate, rectified or deleted, where Customer cannot make the change itself through the Services.
Customer's lawfulness obligations apply equally to Customer Personal Data obtained from Customer-Directed Integrations, including historical data.
3.2. Sensitive data. Customer will not submit special categories of personal data, personal data relating to criminal convictions and offences, or other sensitive personal data unless Demaai has separately agreed in writing to that processing.
3.3. Agreed mechanisms. Customer will not include Customer Personal Data in features, fields, support channels or other mechanisms that the Agreement, applicable documentation or Demaai's written instructions identify as not intended to process Customer Personal Data.
3.4. Customer-determined content. Customer and its Users determine the content they submit through prompts, files, free-text fields, search requests, code-execution requests and other interactive inputs. Customer is responsible for ensuring that its instructions and submitted content are lawful, that it has provided required notices and obtained required rights or consents, and that the content complies with sections 3.2 and 3.3. Demaai will process Customer-determined content only to provide the Services on Customer's instructions, including by transmitting it to the applicable Subprocessors in Annex 2 or Customer-Directed Integrations in Annex 3. Customer's responsibility for submitted content does not reduce Demaai's obligations under this DPA or Applicable Data Protection Laws.
4. Demaai's obligations
4.1. Instructions. Demaai processes Customer Personal Data only on Customer's documented instructions, including with regard to transfers, unless required to do otherwise by applicable EU, EU member state or UK law. In that case, Demaai will inform Customer of the legal requirement before processing, unless that law prohibits it on important grounds of public interest. Customer's instructions are:
- the Agreement and this DPA;
- Customer's configuration and use of the Services, including enabling features, connecting Customer-Directed Integrations and configuring exports; and
- other reasonable written instructions that are consistent with the Agreement.
Demaai will inform Customer without delay if, in its opinion, an instruction infringes Applicable Data Protection Laws, and may suspend the affected processing until Customer confirms or modifies the instruction. Instructions outside the scope of the Agreement require the parties' prior written agreement, including on any additional fees.
4.2. Confidentiality. Demaai ensures that persons it authorises to process Customer Personal Data are bound by appropriate confidentiality obligations and access Customer Personal Data only as needed to provide the Services.
4.3. Security. Demaai will implement appropriate technical and organisational measures to protect Customer Personal Data against unauthorised or unlawful processing and against accidental loss, destruction or damage, taking into account the state of technological development, implementation costs, the nature of the data and the risks presented by the processing, in accordance with Article 32 of the EU GDPR or UK GDPR, as applicable.
4.4. Data subject requests. Taking into account the nature of the processing, Demaai assists Customer through appropriate technical and organisational measures in responding to requests from data subjects to exercise their rights. If Demaai receives such a request directly and can identify Customer as the relevant controller, Demaai will forward it to Customer and will not respond itself unless Customer instructs otherwise or the law requires.
4.5. Assistance. Taking into account the nature of the processing and the information available to it, Demaai provides reasonable assistance to Customer in meeting its obligations concerning security, breach notification, data protection impact assessments and prior consultation under Articles 32 to 36 of the EU GDPR or UK GDPR, as applicable, and equivalent provisions of other Applicable Data Protection Laws. Demaai may charge reasonable fees for assistance that goes beyond what is available through the Services or Demaai's standard documentation.
4.6. Records. Demaai maintains records of the processing it carries out on behalf of Customer as required by Article 30(2) of the EU GDPR or UK GDPR, as applicable.
4.7. Data protection officer. Demaai has appointed a data protection officer, who can be contacted at dpo@dema.ai.
5. Subprocessors
5.1. General authorisation. Customer gives Demaai general authorisation to engage Subprocessors. The Subprocessors engaged at the date of this DPA are listed in Annex 2.
5.2. Subprocessor obligations. Demaai will:
- impose on each Subprocessor, by written contract, data protection obligations no less protective than those in this DPA, to the extent applicable to the services it provides; and
- remain liable to Customer for each Subprocessor's performance of those obligations.
5.3. Changes to Subprocessors. Demaai will notify Customer at least fourteen (14) days before it authorises a new or replacement Subprocessor to process Customer Personal Data. Notice may be given by email, through the Platform or through the Services and will state the Subprocessor's name, the services it provides and the location of processing.
5.4. Objections. Customer may object to a new or replacement Subprocessor by notifying Demaai in writing at dpo@dema.ai within the notice period. If Customer objects and cannot demonstrate, to Demaai's reasonable satisfaction, that the objection is due to an actual or likely breach of Applicable Data Protection Laws, Customer shall indemnify Demaai for any losses, damages, costs (including reasonable legal fees) and expenses suffered by Demaai in accommodating the objection.
5.5. What is not a Subprocessor. The following are not Subprocessors, and changes to them do not require notice under section 5.3:
- providers of Customer-Directed Integrations (section 6);
- service providers that Demaai uses only for its own processing as a controller under section 2.3 and that do not process Customer Personal Data, such as the tools behind its marketing website, customer relationship management, sales, events and recruitment;
- service providers used only with information that is not Customer Personal Data, where Demaai configures and operates the relevant service so that Customer Personal Data is not sent to or made available to the provider; and
- providers of datasets or software that Demaai licenses and runs within its own environment without sending them Customer Personal Data, such as the IP geolocation database used to enrich tracking data.
6. Customer-Directed Integrations
6.1. Customer's instruction. The Services let Customer connect Customer-Directed Integrations, such as commerce platforms, advertising accounts, analytics tools, email and CRM platforms, data warehouses and collaboration tools. By connecting a Customer-Directed Integration, or by configuring an export, audience sync or automated action that sends data to one, Customer instructs Demaai to retrieve Customer Data from it, or transmit Customer Data to it, as configured.
6.2. Status of the provider. The provider of a Customer-Directed Integration is not engaged by Demaai and is not a Subprocessor. Its processing of Customer Personal Data is governed by Customer's own agreement with it. Customer is solely responsible for:
- having that agreement in place;
- having a lawful basis for the disclosure to the provider and for the provider's processing;
- handling data subject requests concerning data held by the provider.
6.3. Demaai's responsibility. Demaai remains responsible for its processing of Customer Personal Data when providing the integration and for transfer obligations that Applicable Data Protection Laws impose on Demaai. Demaai is not responsible for the provider's independent processing after Customer Personal Data has been delivered to it on Customer's instruction.
6.4. Disconnection. Customer may disconnect a Customer-Directed Integration at any time. Disconnection stops future access through that connection but does not itself delete Customer Personal Data previously imported into the Services. That data remains subject to this DPA.
6.5. Platform terms. Some Customer-Directed Integrations impose terms on how Demaai may use data received through them, such as the Google API Services User Data Policy, the Meta Platform Terms and the Slack API Terms of Service. Demaai complies with applicable provider terms and describes its handling in its Google API Disclosure, Meta API Disclosure and Slack App Disclosure.
6.6. Providers in two roles. A provider may be both a Subprocessor and a Customer-Directed Integration. Each role is governed by the relevant section of this DPA.
7. International transfers
7.1. Demaai may transfer Customer Personal Data outside the country in which it was collected as required to provide the Services, provided that Demaai ensures that transfers for which it is responsible comply with Applicable Data Protection Laws.
7.2. Where Demaai transfers Customer Personal Data to a Subprocessor in a country for which Applicable Data Protection Laws require a transfer mechanism, Demaai will ensure that the transfer is covered by an applicable lawful mechanism. This may include an adequacy decision, the European Commission's Standard Contractual Clauses using the module applicable to the parties' roles, supplemented by the UK International Data Transfer Addendum where applicable, the UK International Data Transfer Agreement, or another lawful mechanism.
7.3. On request, Demaai will provide Customer with information reasonably necessary to understand the transfer mechanism used for a Subprocessor, subject to appropriate redactions and confidentiality restrictions.
7.4. If Applicable Data Protection Laws require a transfer mechanism for a transfer between Customer and Demaai, the parties will cooperate in good faith to enter into the documentation applicable to that transfer. This DPA does not automatically incorporate a particular Standard Contractual Clauses module where that module is not required for the transfer.
8. Personal Data Breaches
8.1. Notification. Demaai will notify Customer without undue delay after becoming aware of a Personal Data Breach.
8.2. Content. The notification will be sent to Customer's designated contact and will describe, to the extent then known: the nature of the Personal Data Breach, including the categories and approximate number of data subjects and records concerned; the likely consequences; the measures taken or proposed to address it and mitigate its effects; and a contact point for more information. Where not all information is available at once, Demaai will provide it in phases without undue further delay.
8.3. Response. Demaai will promptly take reasonable steps to contain, investigate and mitigate the Personal Data Breach, and will keep Customer informed of material developments.
8.4. Customer notifications. Customer is responsible for deciding whether to notify supervisory authorities and data subjects. Demaai will not notify Customer's data subjects or supervisory authorities about a Personal Data Breach concerning Customer Personal Data on Customer's behalf, unless Customer instructs it to or the law requires it.
9. Audits
9.1. Customer may audit Demaai's processing of Customer Personal Data, including processing by its Subprocessors, to verify compliance with this DPA and Applicable Data Protection Laws. Demaai will make available the information reasonably necessary to demonstrate that compliance.
9.2. During normal business hours and upon reasonable notice, with twenty (20) Business Days always deemed reasonable, Demaai will provide an independent auditor appointed by Customer and approved by Demaai, with approval not to be unreasonably withheld, with reasonable access to the relevant facilities, personnel and information relating to the processing of Customer Personal Data. The auditor must comply with Demaai's work rules, security requirements and standards when conducting site visits.
9.3. A competent supervisory authority will have access to Demaai's premises, data processing equipment and documentation as required by Applicable Data Protection Laws.
9.4. Customer is responsible for all costs associated with an audit unless it concludes that Demaai materially breached this DPA. In that case, Demaai will reimburse Customer's reasonable and verified audit costs.
10. Retention, return and deletion
10.1. On termination or expiry of the Agreement, Demaai will cease processing Customer Personal Data and, at Customer's choice and expense, return it to Customer or delete it, including copies, unless applicable EU, EU member state or UK law requires its continued storage. Customer must communicate its choice within one (1) month after Demaai asks Customer to choose. If Customer does not do so, Demaai may delete the Customer Personal Data. Customer Personal Data is considered deleted when it is put beyond further use by Demaai.
10.2. Where applicable law requires Demaai to retain Customer Personal Data, Demaai will isolate and protect it from further processing except to the extent required by law.
11. US State Privacy Laws
11.1. Role and purposes. For Customer Personal Data subject to US State Privacy Laws, Demaai acts as Customer's service provider or processor. Customer discloses Customer Personal Data to Demaai only for the limited and specified business purposes and processing operations described in Annex 1.
11.2. Restrictions. Demaai will not:
- sell or share Customer Personal Data;
- retain, use or disclose Customer Personal Data for any purpose, including any commercial purpose, other than the business purposes specified in section 11.1 or as otherwise permitted by US State Privacy Laws;
- retain, use or disclose Customer Personal Data outside the direct business relationship between Demaai and Customer; or
- combine Customer Personal Data with personal information that Demaai receives from or on behalf of another person, or collects from its own interactions with consumers, except as permitted by US State Privacy Laws.
Nothing in this section prevents Demaai from using information that no longer constitutes personal data under Applicable Data Protection Laws. Demaai may use aggregated, de-identified statistics from finalised incrementality experiments solely to produce cross-customer causal-factor-attribution benchmark distributions as part of the Services. Demaai will take reasonable measures to ensure that the information cannot be associated with a consumer, household, Customer or User; maintain and use it solely in de-identified form; not attempt to re-identify it; and, if Demaai discloses it to a recipient, contractually require the recipient to comply with the same restrictions.
11.3. Compliance. Demaai will comply with the obligations that US State Privacy Laws impose on service providers and processors, and will provide the level of privacy protection those laws require. Demaai will notify Customer if it determines that it can no longer meet those obligations. On notice of unauthorised processing, Customer may take reasonable and appropriate steps to stop and remediate it. Customer may take reasonable steps to ensure that Demaai uses Customer Personal Data in a manner consistent with Customer's obligations, using the audit rights in section 9.
11.4. Requests. Taking into account the nature of the processing and the information available to Demaai, Demaai will provide reasonable assistance to enable Customer to comply with consumer requests relating to Customer Personal Data, including requests to access, correct, delete or opt out where applicable. Some requests involving analytics and data-warehouse systems may require Customer's instruction and coordinated processing by Demaai. When Customer forwards a request, Demaai will comply with Customer's lawful instructions and provide the information reasonably necessary for Customer to respond.
11.5. Subcontractors. Demaai will require any subcontractor that processes Customer Personal Data subject to US State Privacy Laws to comply with corresponding restrictions and obligations.
12. Liability
12.1. Administrative fines. Administrative fines under Article 83 of the EU GDPR or UK GDPR, or equivalent provisions of other Applicable Data Protection Laws, are borne by the party on which they are imposed.
12.2. Compensation to data subjects. Compensation payable to a data subject for damage caused by processing of Customer Personal Data in breach of this DPA, Customer's instructions or Applicable Data Protection Laws is allocated in accordance with Article 82 of the EU GDPR or UK GDPR, as applicable.
12.3. Other claims. For all other claims arising out of or in connection with this DPA, the liability provisions and limitations in the Agreement apply.
13. Term, changes and general provisions
13.1. Term. This version of the DPA takes effect for Customer when it is duly executed by the parties, or on another effective date stated in the applicable signed instrument, and remains in force for as long as Demaai processes Customer Personal Data.
13.2. Remuneration. Demaai's obligations under this DPA are included in the fees payable under the Agreement. If Customer changes its instructions, or requires additional technical or organisational measures, and this increases Demaai's costs, Demaai may request an equitable adjustment of the fees.
The payment terms for adjusted or other remuneration under this DPA are governed by the payment provisions in the Agreement.
13.3. Changes to this DPA. No amendment, modification, release or discharge of this DPA is binding unless in writing and duly executed by authorised representatives of both parties, except that Demaai may add or replace Subprocessors in accordance with section 5.
13.4. Assignment. Neither party may assign its rights or obligations under this DPA without the prior written consent of the other party.
13.5. Entire agreement. This DPA sets forth and constitutes the entire agreement and understanding between the parties with respect to its subject matter, and all prior agreements, understandings or promises with respect to it are superseded by this DPA.
13.6. Governing law and disputes. The governing law and dispute resolution provisions of the Agreement apply to this DPA.
Annex 1 – Details of processing
A. Parties
Customer: Customer, as identified in the Order. Contact details: as set out in the Order or designated by Customer in the Services. Activities: use of the Services. Role: controller or processor on behalf of another controller (section 2.2).
Demaai: Demaai AB, org. no. 559376-0118, Birger Jarlsgatan 7, 111 43 Stockholm, Sweden. Contact: Data Protection Officer, dpo@dema.ai. Activities: provision of the Services. Role: processor, service provider or subprocessor as described in section 2.2.
B. Description of processing
Categories of data subjects
- Customer's end customers and prospective customers, including shoppers and visitors to Customer's websites and apps where Customer has installed the Demaai tracking script.
- Customer's Users, to the extent their personal data is contained in Customer Data (for example, content they create in the Services).
- Any other individuals whose personal data Customer or its Users choose to include in Customer Data, for example in uploaded files or in prompts to AI features.
Categories of personal data
- Order and customer data: order and customer identifiers (a customer ID is often an email address), name, email address, phone number, shipping and billing address, postal code, purchased products, prices, discounts, returns and order timestamps, and customer tags imported from Customer's commerce platform.
- Online tracking and device data: IP address, pseudonymous visitor identifier stored in a cookie, user agent, device and browser details, page URLs, referrers, campaign parameters and click identifiers, and events such as page views, clicks, add-to-cart actions and purchases, with timestamps.
- Derived location data: country, region, city, postal code and coordinates derived from IP addresses.
- Derived analytical data: sessions, attribution results, new or returning customer status, customer segments and labels, and predicted customer lifetime value.
- Data from Customer-Directed Integrations: data Customer instructs Demaai to retrieve, such as advertising and campaign performance data (generally aggregated), and historical web analytics event data including pseudonymous identifiers and IP addresses.
- Customer-defined data: custom attributes Customer configures on tracking events, items and sessions.
- AI feature content: prompts, files and other content Users submit to AI features, and the outputs generated.
Special categories of data: special categories of personal data are not intended or authorised unless Demaai separately agrees in writing to their processing.
Frequency of the transfer: continuous, for the duration of the Agreement.
Nature of the processing
- Collection of events through the Demaai tracking script and server-side integrations that Customer installs, and retrieval of data from Customer-Directed Integrations.
- Storage and hosting.
- Cleansing, structuring, deduplication and bot-traffic filtering.
- Enrichment: approximate location is derived from IP addresses using a licensed geolocation database that runs within Demaai's environment, so no Customer Personal Data is sent to its provider; events are grouped into sessions and orders are attributed to marketing activity.
- Machine learning: Customer-specific models trained on Customer Data scoped to Customer's account produce predictions and forecasts for Customer, such as customer lifetime value. Aggregated and anonymised statistics from finalised incrementality experiments may be used solely for causal-factor-attribution benchmark distributions as part of the Services where authorised by the Agreement, provided that they do not identify Customer or contain Confidential Information or personal data. For information subject to US State Privacy Laws, the de-identification requirements in section 11.2 also apply.
- Segmentation and labelling as Customer configures.
- AI-assisted analysis: when Users ask questions, Demaai's AI agents query Customer Data and send relevant context to the AI Subprocessors in Annex 2. Content that Users paste or attach is sent as provided.
- Display to Users: Customer's Users can view end-customer identifiers (such as email-based customer IDs) and export reports containing them.
- Transmission to Customer-Directed Integrations on Customer's instruction (section 6).
- Customer support, troubleshooting, security monitoring and deletion.
Purpose of the processing: providing the Services as described in the Agreement (including Exhibit 1), including e-commerce analytics, attribution, forecasting, AI-assisted analysis and content generation, and the related support, maintenance and security.
Retention: as set out in section 10.
Transfers to Subprocessors: the subject matter, nature and duration of the processing by each Subprocessor are set out in Annex 2, for the duration of the Agreement.
Annex 2 – Subprocessors
Demaai engages the following Subprocessors to process Customer Personal Data. Changes are notified in accordance with section 5.3. Service providers described in section 5.5 are not listed because they do not process Customer Personal Data on Demaai's behalf.
An entry marked Optional applies only when Customer enables or uses the feature described in its comment.
Service infrastructure and features
Amazon Web Services
- Provider: Amazon Web Services EMEA SARL
- Website: https://aws.amazon.com
- Address: 38 Avenue John F. Kennedy, L-1855 Luxembourg
- Contact: https://aws.amazon.com/contact-us/compliance-support/
- Purpose: Cloud hosting, storage, compute and networking
- Personal data processed: Customer data, order data, tracking data, User data and other Customer Personal Data hosted in the Services
- Data subjects: Users of the Dema platform and individuals whose data Customer submits to the Services
- Processing location: EU (Ireland) for primary hosting; other locations may apply to support and onward Subprocessors
Anthropic (Optional)
- Provider: Anthropic Ireland, Limited
- Website: https://www.anthropic.com
- Address: Dogpatch Labs, The CHQ Building, Custom House Quay, Dublin 1, D01 Y6H7, Ireland
- Contact: privacy@anthropic.com
- Purpose: AI model inference
- Personal data processed: Prompts, responses and content submitted to AI features
- Data subjects: Users of the Dema platform and individuals whose data Users include in submitted content
- Processing location: US / global
- Comment: Optional; used only when Customer uses Agent features configured to use Anthropic
Clerk
- Provider: Clerk, Inc.
- Website: https://clerk.com
- Address: 660 King Street, Unit 345, San Francisco, CA 94107, USA
- Contact: privacy@clerk.dev
- Purpose: Identity and access management when Customer invites and provisions Users
- Personal data processed: User names, email addresses and profile information that Customer provides to create or manage access to the Services
- Data subjects: Users of the Dema platform
- Processing location: US / global
Google Cloud (Optional)
- Provider: Google Cloud EMEA Limited
- Website: https://cloud.google.com
- Address: 70 Sir John Rogerson's Quay, Dublin 2, Ireland
- Contact: https://support.google.com/cloud/contact/dpo
- Purpose: Cloud-based image and video generation
- Personal data processed: Generation prompts, reference creative assets and generated outputs
- Data subjects: Users of the Dema platform and individuals whose data Users include in submitted content
- Processing location: EU / US / global, depending on model availability
- Comment: Optional; used only when Customer uses creative-generation features
Modal (Optional)
- Provider: Modal Labs, Inc.
- Website: https://modal.com
- Address: 233 Spring Street, Floor 11, New York, NY 10013, USA
- Contact: privacy@modal.com
- Purpose: Sandboxed code execution
- Personal data processed: Code, files and other content provided for processing, execution outputs and request metadata
- Data subjects: Users of the Dema platform and individuals whose data Users include in submitted content
- Processing location: US routing by default, with execution containers potentially running in Modal's global fleet unless Demaai pins them. EU execution is used where Demaai explicitly pins it for Customer requirements. Sandbox lifecycle and control-plane processing, application logs, snapshots and Modal durable-storage products are processed in the US.
- Comment: Optional; used only when Customer uses Agent features that execute code. Customer-determined code, files, inputs and outputs may contain personal data.
OpenAI (Optional)
- Provider: OpenAI Ireland Limited
- Website: https://openai.com
- Address: 1st Floor, The Liffey Trust Centre, 117-126 Sheriff Street Upper, Dublin 1, D01 YC43, Ireland
- Contact: privacy@openai.com
- Purpose: AI model inference
- Personal data processed: Prompts, responses and content submitted to AI features
- Data subjects: Users of the Dema platform and individuals whose data Users include in submitted content
- Processing location: US by default; EU where configured and supported; other locations may apply to support and onward Subprocessors
- Comment: Optional; used only when Customer uses Agent features configured to use OpenAI
Opper (Optional)
- Provider: Opper Technology AB
- Website: https://opper.ai
- Address: Västerängsvägen 51 A, 182 47 Enebyberg, Sweden
- Contact: privacy@opper.ai
- Purpose: AI model gateway and related Agent processing
- Personal data processed: Customer-determined prompts, files, tool context and other inputs; model outputs; and request and usage metadata
- Data subjects: Users of the Dema platform and individuals whose data Users include in submitted content
- Processing location: EU for the shared platform and control plane; model inference and provider storage are route-dependent and are not restricted to the EEA by default
- Comment: Optional; used only when Customer uses Agent features routed through Opper
Pydantic (Optional)
- Provider: Pydantic Services Inc.
- Website: https://pydantic.dev
- Address: 1207 Delaware Avenue #1225, Wilmington, DE 19806, USA
- Contact: privacy@pydantic.dev
- Purpose: Observability and logging for AI features
- Personal data processed: AI traces, prompts, responses, submitted content, User identifiers and request metadata
- Data subjects: Users of the Dema platform and individuals whose data Users include in submitted content
- Processing location: EU for primary hosting; US and other locations may apply to support and onward Subprocessors
- Comment: Optional; used only when Customer uses Agent features
Sentry
- Provider: Functional Software, Inc. d/b/a Sentry
- Website: https://sentry.io
- Address: 45 Fremont Street, 8th Floor, San Francisco, CA 94105, USA
- Contact: privacy@sentry.io
- Purpose: Error tracking and performance monitoring where diagnostic records contain Customer Personal Data
- Personal data processed: Customer Personal Data incidentally included in GraphQL variables, application logs, stack traces, error context or interaction breadcrumbs
- Data subjects: Individuals whose data is included in Customer Data that appears in diagnostic records
- Processing location: EU for Dema App and Dema API event ingest; US for Integrations API, Bifrost, Shopify App and Google Ads Connector event ingest. US and other locations may also apply to account and organisation metadata, support and onward Subprocessors.
Support and operations
These Subprocessors support Demaai's operation of the Services and receive Customer Personal Data only incidentally, for example when it is needed to handle a support request or investigate an issue.
Google Workspace
- Provider: Google Ireland Limited
- Website: https://workspace.google.com
- Address: 70 Sir John Rogerson's Quay, Dublin 2, Ireland
- Contact: https://support.google.com/a/contact/googlecloud_dpr
- Purpose: Email, documents and file storage used for support and service operations
- Personal data processed: Customer correspondence, support content, attachments and related metadata
- Data subjects: Customer personnel and Users who communicate with Demaai
- Processing location: EU for configured primary data regions, with global support processing
Linear
- Provider: Linear Orbit, Inc.
- Website: https://linear.app
- Address: 2261 Market Street, Suite 10632, San Francisco, CA 94114, USA
- Contact: privacy@linear.app
- Purpose: Issue tracking for support and product issues
- Personal data processed: Support and engineering ticket content, attachments and User contact details where included
- Data subjects: Customer personnel and Users whose information is included in support or product issues
- Processing location: US
Slack
- Provider: Slack Technologies Limited
- Website: https://slack.com
- Address: Salesforce Tower, 60 R801, North Dock, Dublin, Ireland
- Contact: privacy@slack.com
- Purpose: Internal communication, incident handling and customer collaboration
- Personal data processed: Customer support messages, operational alerts, file attachments and User contact details where included
- Data subjects: Customer personnel and Users whose information is included in support or incident communications
- Processing location: US / global
- Comment: Shared Slack Connect channels are used only where Customer chooses to communicate with Demaai through Slack
Annex 3 – Customer-Directed Integrations
The Services can connect to the categories of third-party services below. Each is a Customer-Directed Integration under section 6: it processes data only when Customer connects it, and its provider is not a Subprocessor. The current catalogue is published at dema.ai/integrations.
| Category | Examples | Data flow |
|---|---|---|
| Commerce platforms and order sources | Shopify, Centra, commercetools, Salesforce Commerce Cloud, Sitoo | Retrieval of orders, customers, products, inventory and returns, including through file-transfer methods such as CSV or SFTP |
| Advertising and social platforms | Google Ads, Meta Ads, Meta Pages and Instagram, TikTok Ads, Pinterest Ads, Snapchat Ads, Google Display & Video 360, Awin, Google Merchant Center | Retrieval of campaign, spend and performance data and, for connected Meta Pages and Instagram accounts, content and insights. Google Ads and Meta Ads may also create, update or manage campaigns, budgets, targeting or creatives on Customer's or a User's instruction and approval |
| Web analytics | Google Analytics 4, Google Search Console | Retrieval of analytics data, including historical event data on request |
| Email, CRM and customer engagement | Klaviyo, Voyado, Ometria, Attentive, Rule, Intercom, Gorgias | Retrieval of engagement data. Where Customer configures an audience or segment export, transmission of customer identifiers and segment membership |
| Data warehouses | BigQuery, Snowflake, Databricks, Azure SQL | Retrieval or transmission of data, as Customer configures |
| Collaboration and productivity | Slack, Microsoft Teams, Gmail, Microsoft Outlook, Google Sheets, Figma | Gmail is send-only. Other integrations may read, create or update messages, documents and files on a User's instruction |
| Customer's own tools and AI clients | Customer's applications and AI assistants connected through Demaai's API or MCP server | Transmission of Customer Data that a User requests through the connection |
Turn data into decisions.