Data Processing and Confidentiality Agreement

Version dated 30 October 2026

This Data Processing and Confidentiality Agreement (the “Agreement”) is between Ronja Technologies AB (“Ronja”) and the legal entity identified in the applicable order or agreement (the “Customer”).

At a glance

This summary is for convenience; the numbered Sections and Annexes govern. In it, “your data” means Customer Data, “your content” means Customer Content, and capitalised terms have the meanings given in the preamble and Sections 1 and 2.

No training on your data. Neither Ronja nor any of its providers uses your data, including prompts, outputs and embeddings, to train, fine-tune or improve AI models. The only exception is a model for you alone that you ask for in writing. Your content never appears in another customer’s results or solutions (Section 10.1).

Your data stays yours, and stays confidential. Ronja does not sell it, disclose it to other customers or use it for advertising. Trade secrets and technical material are protected whether marked confidential or not (Sections 3.4 and 4).

EU by default. Your content is stored and processed in the EU/EEA, including AI inference, document extraction, embeddings, code execution, logs and backups. Two functions send your content to the United States: web search, which is on by default, and email sent to Ronja’s inbound address. Both are yours to control: switch web search off, or use your own mailbox instead of ours. Remote support access by providers is limited to what Annex 3 discloses, and Annex 3 names every provider and where it processes data (Section 7).

Product analytics never sees your content. Ronja measures how the Services are used through Usage Data: which functions are used, when, under which user and organisation identifiers, and with which browser type and approximate location. Documents, tables, prompts, outputs and files are never sent to an analytics provider (Sections 2.6 and 3.5).

New AI providers only with your consent. A new AI, web search or other provider for a function you choose is never used for your organisation until an administrator enables it in the Services, where the provider, its country and the data sent are shown. Other providers, for infrastructure and operations, are listed in Annex 3 with their country, agreement and retention; Ronja emails you about a change, in advance where practicable, and you may object; if your objection is not resolved within 30 days, you may terminate the affected Services (Section 6).

Your own systems stay yours. An ERP, CRM, database, file store, mailbox or messaging platform you connect is your system, not a Ronja provider. Ronja moves data to and from it only on your instruction (Section 6.6).

Deletion on request and at the end. What you delete leaves the trash after 30 days and is gone from active systems within 30 days after that, and a deletion request is completed in active systems within 30 days. At the end of the Services your data is deleted from active systems within 30 days; error diagnostics and logs expire within 90 days and provider copies follow the retention in Annex 3. Backups expire on the disclosed rotation and are used only for disaster recovery and ransomware resilience (Section 13).

Incidents within 48 hours. Ronja notifies you within 48 hours of becoming aware of a security incident affecting your data (Section 9).

You can verify. Ronja provides the information needed to demonstrate compliance and allows audits (Section 11).

Updates cannot remove the core guarantees. No update may permit training on your data, move your content outside the EU/EEA without your instruction, or reduce the overall protection of Personal Data. Any other change that reduces your protection, unless required by law or a supervisory authority, gets 30 days’ notice, and you may object and terminate the affected Services before it takes effect (Section 19).

1 Application and service coverage

1.1 This Agreement forms part of the agreement under which Ronja provides services to the Customer, including Ronja’s Terms of Service where applicable (the “Service Agreement”). It governs processing of Personal Data under Article 28 of Regulation (EU) 2016/679 (the “GDPR”) and separately imposes contractual protection for all Customer Data, including information that is not personal data.

1.2 It applies to all services Ronja supplies under the Service Agreement that receive, access, create, store or otherwise process Customer Data (the “Services”), as described in Annex 1, and only to functions actually supplied or enabled.

1.3 Mandatory law and the standard contractual clauses adopted by the European Commission under Article 46(2)(c) GDPR (“Standard Contractual Clauses”), where applicable, prevail over this Agreement. Special Terms (Section 2.3), and any other individually agreed and signed addendum, prevail over this Agreement to the extent they expressly and lawfully vary it; stricter agreed safeguards remain effective. This Agreement prevails over conflicting general terms on its subject matter.

2 Definitions and roles

2.1 “Customer Data” means all data or material supplied by or for the Customer, or processed or generated on its behalf through the Services: documents, technical specifications, drawings, source data, code, credentials, prompts, outputs, derived tables, indexes, embeddings, business rules and logs containing that material. It includes the Customer’s own information and material entrusted to it by customers, suppliers or other third parties.

2.2 “Personal Data” means personal data within Customer Data, and “Personal Data Breach” has its GDPR meaning. GDPR terms retain their statutory meanings. The Customer is a controller or a processor acting on a controller’s instructions; Ronja acts respectively as processor or sub-processor. The actual processing determines the legal roles.

2.3 “Special Terms” means any terms specific to the Customer that restrict or specify the Services or supplement this Agreement, agreed in writing and signed by both parties. Special Terms prevail over broader options in the Services and in Annex 3; Ronja enforces Special Terms at every processing step, including fallback, and stops a task that cannot comply.

2.4 A “Model” is the AI model and version used for a task; its “Model developer” is the entity that develops it, and an “Inference Provider” operates the service that executes it. The Model developer and Inference Provider may be different entities. A Model developer is included in the processing chain only where it actually processes Customer Data, directly or through the relevant service.

2.5 Each party shall comply with the data protection law applicable to its own role and processing. “business days” means Monday to Friday, excluding public holidays in Sweden.

2.6 “Customer Content” means the content within Customer Data: documents, files, tables, prompts, outputs, query results, credentials and material derived from them. “Usage Data” means pseudonymous information about how the Services are used: which functions are used, when, under which user and organisation identifiers, and with which browser type and approximate location. Usage Data never contains Customer Content and is not Customer Data; Ronja processes it under Section 3.5.

2.7 A “Provider” is a third party Ronja engages to process Customer Data for the Services; a Provider processing Personal Data is a sub-processor. “Customer-managed Services” are defined in Section 6.6.

3 Instructions and permitted use

3.1 Ronja shall process Customer Data only to deliver, secure, maintain and support the Customer’s Services in accordance with documented instructions. This Agreement, its Annexes, agreed Special Terms and authorised use of configured functions form those instructions.

3.2 Where acting as controller, the Customer determines the purposes and essential means of processing and is responsible for the legal basis and required notices. Where acting as processor, it acts within the relevant controller’s documented instructions. In either role it must have authority to provide the material, instruct Ronja and obtain approvals required by its contracts with material owners. This Agreement does not override those contracts or itself authorise disclosure to Ronja.

3.3 Ronja shall immediately inform the Customer if, in its opinion, an instruction infringes data protection law and suspend performance of the affected instruction while the parties resolve it. If Union or Member State law requires processing without an instruction, Ronja shall inform the Customer before processing unless that law prohibits notice on important public interest grounds.

3.4 The Customer and its licensors retain their rights in Customer Data. Ronja receives only the rights necessary to perform its obligations. It shall not sell the material, disclose it to other customers, use it for advertising, or incorporate its contents or confidential business logic into another customer’s solution. General software and intellectual property ownership remain governed by the Service Agreement.

3.5 Ronja processes Usage Data as an independent controller under its privacy notice, to operate, secure, support and improve the Services, including product analytics through the analytics service listed in Annex 3C; Section 6.4 applies to a change of that service as if it were a Provider and Usage Data were Customer Data. Internal operations, support and reporting copies of Customer Content remain subject to the same purpose, access and deletion restrictions as their source. Removing names does not authorise reuse of confidential material.

3.6 Ronja acts separately as controller of information about its own business contacts, customer relationships, billing and website visitors, as described in its privacy notice. This includes its CRM processing using HubSpot and payment processing using Stripe. That role does not permit repurposing Customer Data. Service logs and user identifiers processed on the Customer’s behalf remain subject to this Agreement; Usage Data is governed by Section 3.5.

4 Confidentiality and trade secrets

4.1 Ronja shall keep Customer Data confidential, including the Customer’s and third parties’ trade secrets and non-public technical or commercial information, whether marked confidential or not. Disclosure is limited to Providers and authorised personnel who need access for the Services and are bound by enforceable confidentiality commitments or statutory duties, to Customer-managed Services under Section 6.6, and as legally required under Section 18.

4.2 An exception applies only to information Ronja can demonstrate was lawfully public without breach, already lawfully held without restriction, independently developed without use of the confidential information, or lawfully obtained without restriction from a third party. These exceptions do not displace obligations applicable to Personal Data.

4.3 Ronja shall train personnel, restrict and review access, and hold authorised personnel accountable for confidentiality. These obligations survive termination without a fixed expiry while the information remains confidential; trade secrets remain protected for as long as they qualify as such, and Personal Data remains protected for as long as it is retained.

5 Security

5.1 Ronja shall maintain the measures in Annex 2 with security appropriate to the risks to Customer Data. For Personal Data it shall take all measures required by Article 32 GDPR. Measures include confidentiality, integrity, availability, resilience, recovery and regular evaluation of effectiveness.

5.2 Ronja may improve or replace controls without materially reducing protection. Current certification evidence, scope and validity shall be provided under Section 11.

6 Providers and sub-processors

6.1 The Customer authorises the Providers listed in Annex 3, subject to Section 6.3. This Section protects all Customer Data, including trade secrets without Personal Data. A software or Model developer is not a Provider merely because its product is used.

6.2 Ronja may add or replace Providers under this Section. A new Model or Model version from a Provider already listed in Annex 3, served from a location already disclosed there, is not a Provider change. Every added Provider is bound to the commitments of this Agreement.

6.3 A new Provider that would receive Customer Content for a function the Customer selects, including an Inference Provider or a web search Provider, is not used for the Customer’s organisation until an administrator enables it in the Services, where the Provider, its country and the data sent are shown. That act is the Customer’s authorisation under this Section and, where relevant, its instruction under Section 7. Ronja adds the Provider to Annex 3 when it is offered. A Provider that Annex 3B lists as on from the start for organisations created on or after a stated date is, for such an organisation, authorised by the Customer’s acceptance of this Agreement, and an administrator can turn it off in the Services.

6.4 For every other added or replacement Provider, Ronja shall update Annex 3 and notify the Customer by email with the information Annex 3 states for each Provider, before the Provider receives Customer Data where practicable and otherwise promptly. The Customer may object within 10 business days of the notice on reasonable data protection, confidentiality, security or contractual compliance grounds. If the objection is not resolved within 30 days of the objection, the Customer may terminate the affected Services, and Section 13 applies.

6.5 Ronja shall conduct appropriate diligence, bind Providers to written obligations equivalent in substance to those applicable here, and remain responsible for their performance as if its own, including under Article 28(4) GDPR. A Provider’s standard terms do not override this Agreement. Annex 3 links each Provider’s own sub-processor list; Ronja supplies further information on the chain on request.

6.6 “Customer-managed Services” (each a “Customer-managed Service”) are the systems, services and accounts the Customer itself contracts for and connects to the Services or directs Ronja to exchange data with: for example an ERP, CRM, accounting or HR system, a file store, a database, an email account, a messaging platform such as Slack or Teams, an MCP server, or an external AI service, whether connected through a connector, a workflow, an API key, OAuth, the CLI, MCP or a bridge. Such a system is the Customer’s own recipient or source, not a Provider: Ronja sends data to it and receives data from it only on the Customer’s instruction under Section 3. The Customer is responsible for its selection, configuration, permissions, agreements and lawful, contractually permitted use of Customer Data. An Inference Provider engaged by Ronja remains a Provider even when selected by the Customer.

6.7 Ronja is not responsible for Customer-managed Services’ processing, including retention, caching, training, onward disclosure or deletion. Connecting a Customer-managed Service is the Customer’s instruction to exchange the relevant Customer Data with it wherever it is located; the Customer is responsible for that recipient’s terms and any transfer safeguards. Ronja remains responsible for its own processing, access controls and disclosures, and for its Providers.

7 Processing locations and transfers

7.1 Customer Content is stored and processed within the EU/EEA, including inference, document extraction, embeddings, execution environments, temporary files, content-bearing logs and backups. The exceptions are web search (Annex 3), which sends to the United States only the search query that Ronja’s AI agent composes, and which the Customer’s administrator can disable in the Services; email sent to Ronja’s inbound address for email-triggered automations, which Google Workspace stores in the EU and the United States (Annex 3) and which the Customer can avoid by connecting its own mailbox instead (Section 6.6); and the remote support access of Providers where Annex 3 discloses it. A Provider’s place of incorporation does not establish where processing occurs.

7.2 Any other processing or access outside the EU/EEA requires a prior, documented instruction from the Customer identifying the affected data, service, recipients and countries. An administrator’s enabling of a Provider or a setting in the Services is that instruction for what it enables, because the Services disclose the Provider, the country and the data sent before activation. The Customer’s acceptance of Annex 3 is that instruction for the processing and access locations it discloses when accepted; a later Provider change that would process or access Customer Data outside the EU/EEA requires an instruction under this Section. Exchanges with a Customer-managed Service are governed by Section 6.7.

7.3 For Personal Data, Ronja shall also establish a valid Chapter V transfer mechanism before the transfer, assess protection in the destination and apply supplementary measures where needed, and shall supply the transfer documentation on request.

7.4 “EU/EEA-only”, where agreed in Special Terms, means that Customer Content is stored and processed only in the EU/EEA except for the Provider remote support access that Annex 3 discloses, and that web search and email-triggered automations through Ronja’s inbound address are disabled for the Customer’s organisation. Ronja enforces it at every processing step and fails closed if no permitted location or Provider is available.

8 Data subject rights

8.1 Ronja shall assist with the Customer’s obligations concerning data subject rights under Chapter III GDPR, through appropriate technical and organisational measures, taking account of the processing and insofar as possible. It shall promptly forward requests received directly and answer only on documented instructions or as legally required. Where law requires an answer, Ronja shall notify the Customer of that requirement before responding, unless legally prohibited.

8.2 Assistance includes locating, exporting, correcting and restricting records and propagating deletions to Providers. Ronja shall respond within 10 business days, or sooner where the Customer’s statutory deadline requires. Charges for exceptional assistance must be reasonable, agreed in advance and never prevent or delay legally required assistance.

9 Security incidents

9.1 Ronja shall notify the Customer without undue delay, and within 48 hours of becoming aware, of a Personal Data Breach or of unauthorised access to, or disclosure, alteration, loss or destruction of, other Customer Data. Notice shall not await a complete investigation.

9.2 Notice shall give the available information on nature and timing, affected systems and material, relevant categories and approximate numbers of people and records, likely consequences, containment, remediation and a contact point. Missing information shall follow in stages without undue further delay.

9.3 Ronja shall contain, investigate and document the incident, preserve evidence and assist with assessment, mitigation and legally required notifications. The Customer controls notices to its customers and data subjects, except where Ronja has a mandatory duty.

10 AI processing and restrictions

10.1 Neither Ronja nor Providers may use Customer Data, including prompts, outputs, embeddings and confidential information, to train, fine-tune or improve general or shared AI models. Customer Content never appears in another customer’s results or solutions. Customer-specific training requires a separate express written instruction identifying the isolated model, purpose, data, Providers and safeguards.

10.2 Inference may use only the Customer Data necessary for the instructed task, and only permitted Providers and locations. Access restrictions apply to retrieval, outputs, tools and source material.

10.3 Annex 3 states, for each Inference Provider, the processing locations, the applicable retention and, where applicable, caching and review practices; Ronja provides further detail on request. The Customer’s selection within the configuration offered to it is a documented instruction, subject to Section 7 for any non-EU option.

10.4 Temporary inference caching is permitted to deliver and improve the performance of the Customer’s Services, subject to this Agreement. An Inference Provider may keep a cached prompt until one hour after it was last used; it then expires and is promptly deleted. Ronja-hosted history, results and indexes remain subject to Section 13.

10.5 The Customer may select Models and Inference Providers separately within the configuration offered to it. If a selected Model or its Inference Provider fails or is unavailable, Ronja may continue the task on a comparable Model or through another Inference Provider, but only one that Annex 3 lists and that is authorised for the Customer’s organisation under Section 6. A fallback never leaves the EU/EEA. Auxiliary functions, including extraction, embeddings and background tasks, run on Amazon Bedrock in the EU.

11 Evidence and audit

11.1 Ronja shall make available all information necessary to demonstrate compliance with this Agreement and Article 28 GDPR and allow and contribute to audits, including inspections, by the Customer or its mandated independent auditor. Relevant existing certificates, reports and security documentation may be used first where sufficient.

11.2 The Customer may audit once in any 12 months, and additionally after a Personal Data Breach or where a supervisory authority requires it, on 30 days’ written notice, at its own cost, with an agreed scope and proportionate safeguards for other customers, and without access to Providers’ facilities. Ronja first answers with existing certifications, reports and documentation; an inspection follows only where these do not reasonably demonstrate compliance.

11.3 The Customer may share this Agreement (including Annex 3), Ronja’s shareable security summary and certificates designated for onward sharing, with its affected customers, their professional advisers and competent authorities, for assessing or authorising use of the Services. Ronja gives standing consent for this limited sharing, subject to applicable confidentiality and any clearly disclosed third-party restrictions.

11.4 Detailed audit reports, penetration-test findings and sensitive security materials remain confidential. Ronja shall support necessary review under an appropriate confidentiality or controlled-access arrangement, including a report owner’s required terms. These protections do not restrict legally required disclosure or supervisory authority access. Ronja shall identify any onward-sharing restrictions when providing the material.

12 Compliance assistance

12.1 Taking account of the processing and information available, Ronja shall assist the Customer with its obligations under Articles 32–36 GDPR, including security assessments, breach assessment, DPIAs and prior consultation. Assistance shall include relevant data-flow descriptions, Provider and location information, controls, retention arrangements and responses to proportionate questions. Section 8.2 applies to response times and exceptional costs.

12.2 Where the Customer acts as a processor, Ronja shall provide the assistance needed for the Customer to discharge its obligations to the relevant controller.

13 Retention, return and deletion

13.1 Ronja shall retain Customer Data only as needed for the instructed Services and documented retention settings. Data the Customer deletes in the Services is recoverable from the trash for 30 days and is permanently removed from active systems within 30 days after that. Error diagnostics and logs expire within 90 days. On a documented deletion request, Ronja removes the identified data from active systems within 30 days; error diagnostics and logs expire as stated above, and Provider copies and backups as Section 13.3 states.

13.2 Before termination the Customer may export its data through the Services in a structured, commonly used format. Ronja deletes Customer Data from active systems within 30 days after termination or expiry of the Services, or on an earlier date the Customer chooses in writing; error diagnostics and logs expire as Section 13.1 states, and Provider copies and backups as Section 13.3 states.

13.3 Deletion covers originals and copies, extracted text, tables, embeddings, indexes, conversation history, outputs, temporary files, snapshots, content-bearing logs, internal exports and materialised copies in other Ronja environments, and Provider copies within the retention stated for each Provider in Annex 3. Backups expire on the following rotation and are used solely for disaster recovery and ransomware resilience: rolling recovery points are kept for up to 35 days and an immutable monthly recovery point for up to 12 months. Backups are isolated from ordinary processing and never used to serve the Services, and a restore reapplies deletions. Any extension of these retention periods requires the Customer’s prior, express and lawful instruction.

13.4 Mandatory retention of Personal Data requires Union or Member State law; for other Customer Data, mandatory applicable law governs. Ronja shall isolate legally retained material, limit its data and duration, notify unless prohibited and allow no other use. On request, Ronja shall confirm deletion in writing and identify legally retained material. Foreign demands are governed by Section 18 and do not themselves create a Personal Data retention exception.

14 Liability

14.1 Subject to Section 14.2, each party’s liability arising under or in connection with this Agreement is subject to the limitations and exclusions in the Service Agreement. Claims under this Agreement form part of the same aggregate liability as claims under the Service Agreement; this Agreement creates no separate or increased liability cap. Individually agreed liability provisions remain effective.

14.2 No cap or exclusion limits liability for fraud, wilful misconduct or gross negligence, liability that cannot lawfully be limited, mandatory rights of data subjects or authorities, or liability that applicable Standard Contractual Clauses prohibit the parties from limiting.

15 Duration and remedies

15.1 Incorporation or acceptance of this Agreement shall be recorded in writing, including electronically. It takes effect as incorporated into the Service Agreement or validly adopted under the applicable amendment procedure. It governs processing during the Services and until Customer Data has been returned and deleted as required. Provisions necessary for their purpose survive termination, including Section 4.

15.2 If Ronja materially breaches this Agreement and does not remedy the breach within 30 days of written notice describing it, or the breach cannot be remedied, the Customer may terminate the affected Services, and Section 13 applies. Other remedies are subject to Section 14.

16 Governing law

16.1 Swedish law governs this Agreement. The Stockholm District Court is the first instance forum, subject to mandatory law and the jurisdiction provisions of any applicable Standard Contractual Clauses.

17 Regulatory matters

17.1 To the extent legally permitted, Ronja shall promptly notify the Customer of regulatory investigations or measures materially affecting processing under this Agreement and cooperate with the competent supervisory authority. Notices and cooperation shall not require disclosure of other customers’ confidential information.

18.1 Ronja shall assess the legal validity of a demand for Customer Data, seek to redirect the requesting authority to the Customer where appropriate, notify the Customer unless prohibited, and challenge disproportionate or unlawful requests where there are reasonable grounds to do so. It shall seek permission to notify where notice is prohibited.

18.2 Any legally required disclosure shall be limited to what is necessary and documented. Ronja shall comply with applicable data protection law. Equivalent applicable safeguards shall be required of Providers.

19 Updates and email notice

19.1 Ronja may update this Agreement by publishing a dated version at https://ronja.tech/dpa/ and emailing the version, a summary of material changes and the effective date to the Customer’s designated contractual contact or, if none is designated, its account administrator. Ronja retains prior versions and a record of the notice.

19.2 An update required by law or a supervisory authority, or one that does not reduce the Customer’s protection, takes effect on the date in the email. Any other update takes effect 30 days after the email. If the Customer objects in writing before then, it may terminate the affected Services with effect before the update applies.

19.3 No update may permit training on Customer Data, move Customer Content outside the EU/EEA without an instruction under Section 7, reduce the overall protection of Personal Data, or amend signed Special Terms. Provider changes follow Section 6.

19.4 The first adoption of this version by an existing customer must comply with its then-applicable amendment procedure or a separately documented agreement. This Section does not retroactively shorten an earlier notice period or supersede a signed agreement’s change requirements.

20 Notices and communications

20.1 Formal notices and instructions shall be in writing, including email, to the contractual or security contacts designated in the order or Special Terms, as updated by written notice. Incident notices shall use the designated security contact or, if unavailable, a contractual contact; urgent additional channels may be used with prompt written confirmation. A known delivery failure shall be followed up without delaying an applicable deadline.

Annex 1 Processing specification

This Annex applies to functions actually supplied. The Customer’s order, authorised configuration and any Special Terms identify the relevant data sets, users and restrictions before processing starts.

ItemSpecification
Subject matter and purposeDelivering and operating the Customer’s instructed data, AI and business solutions, including onboarding, hosting, support and secure maintenance.
Duration and frequencyFor the instructed service period, followed by the deletion periods in Section 13. Processing may be continuous, scheduled, event-triggered or initiated by an authorised user.
OperationsCollecting, receiving, importing, storing, organising, linking, transforming, querying, retrieving, analysing, comparing, extracting, generating, executing, displaying, transmitting on instruction, exporting and deleting data; security and recovery operations.
Service surfacesConnected systems and APIs; data foundation and warehouse; files, documents and knowledge; search and embeddings; AI conversations and agents; code and sandbox execution; workflows and automations; hosted apps, dashboards, reports and integrations; support and implementation.
Data subjectsAs present in the instructed sources: the Customer’s and its customers’ personnel, contractors, contacts, customers, suppliers, partners and other individuals whose information is lawfully included.
Personal dataAs present in the instructed sources: names, work contact details, user and account identifiers, roles, communications, document contents, transaction and operational records, relevant device or activity identifiers, and generated information relating to individuals.
Other confidential materialTechnical specifications and drawings; product and process information; commercial terms and prices; source code and credentials; internal policies; customer and supplier material; related derived outputs and business logic.
Sensitive informationSpecial-category data under Article 9 GDPR and criminal-offence data under Article 10 GDPR are not required by default. Where intended, the Customer shall identify the categories, legal basis and additional safeguards in Special Terms before processing. All unintentionally received Personal Data remains protected.
Customer responsibilitiesObtain required permissions; instruct Ronja; identify data and retention needs; manage users and sharing; maintain notice contacts; respond to data subjects and regulators with Ronja’s assistance.
Contact and instructionsRonja: support@ronja.tech. Customer entity, address, authorised representative and notice/security contacts: as recorded in the order or Special Terms. The parties shall keep those records current.

Annex 2 Technical and organisational measures

The following technical and organisational measures apply to Customer Data.

ControlContractual measure
EncryptionTLS 1.2 or higher in transit and AES-256 at rest, including supported storage, temporary content and backups. Encryption keys and service credentials are access-restricted and rotated as appropriate.
Identity and permissionsUnique identities, role-based access and least privilege. MFA for Ronja personnel accessing Customer Data. Access is approved, reviewed regularly and promptly removed when no longer needed. The Customer controls authorised users and sharing within its environment.
SeparationLogical separation between customer environments. Access checks apply to source data, retrieval indexes, outputs, apps, workflows and logs. Customer material must not appear in another customer’s results.
Personnel and supportConfidentiality commitments and security awareness training. Access to content is limited to authorised operational, security or support needs, with time and scope limited as appropriate. Privileged access is logged; any requirement for prior Customer approval is recorded in Special Terms.
Network and executionNetwork segmentation, firewalls and monitoring of the production environment. Restricted service accounts and secrets management. Isolated execution environments with network destinations and tool permissions constrained to the authorised task.
AI processing controlsApproved Provider and Model configuration; verification of inference retention and permitted locations; fallback only within the EU/EEA, to the Models and Inference Providers that Section 10.5 permits; Special Terms enforced at every step.
Logging and monitoringCentralised logging and monitoring of access and processing. Sensitive content in telemetry is minimised, secrets are redacted and log access is restricted. Changes to privileged access, region, Provider and relevant processing policies are recorded.
Secure developmentChange review, vulnerability scanning and regular penetration testing; risk-based remediation and separation of development and production. Customer Data is not copied into unrestricted development or demonstration environments.
RecoveryAutomated protected backups, tested recovery procedures and documented recovery responsibilities. Backup and disaster-recovery locations comply with the agreed geographic restrictions.
Lifecycle and responseDocumented retention and deletion across stores and Providers; incident response procedures, investigation and notification under Section 9; regular evaluation of the effectiveness of controls.
Assurance evidenceRonja provides its current ISO 27001 certification evidence, with legal entity, scope, issuer and validity, and promptly notifies the Customer of a material lapse or withdrawal of any certification committed to the Customer.

Annex 3 Providers

This Annex lists every Provider with its legal entity, service, data, locations, agreement and retention; Section 6.4 requires the same information for a change. Each Provider’s own sub-processor list is linked in Annex 3D. Section 6 governs changes, and Special Terms may narrow this Annex. Annex 3C also lists the analytics service that receives Usage Data only; it is not a Provider (Section 3.5).

Annex 3A Infrastructure

Provider / servicePurpose and dataLocation and contractual basis
Amazon Web Services EMEA SARL, Luxembourg / Cloud infrastructureInfrastructure on which Ronja runs: compute, storage, databases, queues, execution environments, email delivery and backups. All Customer Data processed by the Services passes through or rests on it, operated by Ronja under its own keys and access controls.Production in Sweden (Stockholm); database backups copied to Ireland. AWS Customer Agreement and GDPR DPA. AWS support personnel worldwide may access Customer Data only as the AWS DPA permits. Retention as for Ronja’s active systems and backups (Section 13). No training.

Annex 3B AI inference

Provider / servicePurpose and dataLocation and contractual basis
Amazon Web Services EMEA SARL, Luxembourg / Bedrock (AI inference)Default AI inference and embeddings: prompts, relevant content, responses, embeddings and service metadata. AWS operates the Models; the Model developers (Anthropic for Claude, Cohere for embeddings) do not receive Customer Data. No retention beyond the response, except prompt caching as Section 10.4 states; invocation logging is switched off.EU regions only: Sweden, Germany, Ireland, France, Italy and Spain; inference never runs outside the EU/EEA. Agreements and support access as Annex 3A. No training.
evroc Sweden AB, Sweden / ThinkOptional AI inference for GLM 5.2: prompts, relevant content, responses and service metadata. The Model developer does not receive Customer Data.Sweden. evroc General Terms, Service Terms and DPA. Prompts and responses are not logged or stored; only request metadata (timestamps, sizes, error codes) is kept as billing records. No training.
Microsoft Ireland Operations Limited, Ireland / Azure OpenAIOptional GPT text and image inference: prompts, relevant content, responses and service metadata. Microsoft operates the service; OpenAI is the Model developer and does not receive Customer Data.EU: Azure Foundry resource in Sweden Central with Data Zone Standard deployments, so prompts and outputs are processed only within Microsoft’s EU data zone. Microsoft DPA and Product Terms. Prompts and outputs may be retained by Microsoft for up to 30 days for abuse monitoring and reviewed by authorised Microsoft personnel within the EU. No training.
Google Cloud EMEA Limited, Ireland / Gemini Enterprise Agent Platform (formerly Vertex AI)Optional AI inference, including as a fallback under Section 10.5: prompts, relevant content, responses and service metadata. For an organisation created before the date of this version, used only after an administrator enables it in the Services (Section 6.3); for one created on or after that date, on from the start. An administrator can turn it off in the Services. Google operates the service; a Model developer other than Google, such as Anthropic for Claude, does not receive Customer Data. No retention beyond the response, except prompt caching as Section 10.4 states and prompts that Google’s automated abuse classifiers flag, which Google may keep for up to 90 days in the EU for review by authorised Google personnel; request-response logging is switched off. Google treats the fingerprints it computes to match cached prompts as its own service data and uses them only to operate the cache.EU: Customer Content is processed only through Google’s EU endpoints, so prompts and responses are processed and stored within EU member states, and never through Google’s global endpoints. Google Cloud Platform Terms of Service, Service Specific Terms (including AI/ML Data Location) and Google Cloud Data Processing Addendum. Google personnel and sub-processors may access Customer Data only as that addendum permits; Google’s technical-support sub-processors, some outside the EU/EEA, see Customer Data only if Ronja shares it in a support case, which Ronja does not do. No training.

Annex 3C Operational services

Provider / servicePurpose and dataLocation and contractual basis
Functional Software, Inc., United States / SentryApplication error diagnostics: events may include user identifiers and short fragments of the data being processed when an error occurs.Stored in the EU (Germany); retained 90 days; support access by Sentry and its affiliates in the United States, Austria, Canada and the Netherlands. Sentry Terms of Service and DPA. No training.
Mixpanel, Inc., United States / MixpanelProduct analytics on Usage Data only (Section 3.5). Session replay is disabled.Stored in the EU (Google Cloud: Netherlands, Finland, Belgium and Germany); support and engineering access by Mixpanel, Inc. (United States) and Mixpanel International, Inc. (United Kingdom, Spain, Singapore, India and Israel). Mixpanel Terms of Use and DPA. Usage Data only; deleted within 90 days after the Services end, and earlier at the Customer’s request. No training.
Okta, Inc., United States / Auth0Authentication and user identity: account identifiers, authentication events and relevant user attributes.EU tenant hosted on AWS in Germany and Ireland; support ticketing in the United States and 24/7 support from Romania, as listed in Okta’s sub-processor list. Okta Master Subscription Agreement and DPA. Retention as for Ronja’s active systems and backups (Section 13). No training.
Perplexity AI, Inc., United States / Web searchWeb search for Ronja’s AI agent: receives only the search query the agent composes for a task. No files, tables, documents, conversation history or outputs are sent.United States. Perplexity API Terms and DPA; transfers under the Standard Contractual Clauses (Commission Decision (EU) 2021/914) incorporated in the Perplexity DPA. Prompts and responses are not retained; only billing metadata is kept. No training. Enabled by default; the Customer’s administrator can disable it for the organisation in the Services.
Google Cloud EMEA Limited, Ireland / Google WorkspaceRonja’s inbound address for email-triggered automations, used only for organisations that enable email triggers: the content and attachments of email sent to that address. A Customer’s own Gmail or Outlook account is a Customer-managed Service (Section 6.6).Stored in Google’s data centres in the EU and the United States (Google Workspace without a data-region policy); transfers under the Standard Contractual Clauses in the Google Cloud Data Processing Addendum. Google Workspace Terms of Service. Retention as for Ronja’s active systems and backups (Section 13). No training.

Annex 3D Provider reference documents

These official references identify the standard terms, data processing terms and published sub-processor list of each Provider and of the analytics service, and related data-handling documentation. They do not amend this Agreement. The version Ronja has accepted and evidence of its acceptance are kept in Ronja’s contract records; a bespoke signed contract is not required where a binding standard agreement supplies the necessary obligations.