Sub-processors
Last updated: November 12, 2026
Eyevinn Technology AB (organization number 556919-9952), which operates the Open Source Cloud platform at osaas.io, engages the third-party sub-processors below to help deliver the Services. Where you use the Services to process personal data, you are the controller and we act as your processor under GDPR Article 28; these sub-processors process personal data on our behalf and on your documented instructions. This page is maintained as the canonical, current list and is also the mechanism by which we notify customers of sub-processor changes (see "Changes to this list" below).
For our standard Data Processing Agreement, contact privacy@eyevinn.se. For how we process data as an independent controller (account, billing, platform operations), see our Privacy Policy.
Where your data is processed
Our primary processing infrastructure is located in Sweden (EU/EEA). Data processed via the Services is hosted in the EU/EEA on this primary infrastructure. Since 25 August 2026 the platform, its API layer and its backend services run on Elastx, a Swedish infrastructure provider. Some sub-processors that provide ancillary functions (authentication, payment, and the AI features) operate from outside the EU/EEA; for those, we rely on the safeguards in the table below. Since 21 October 2026, backup copies of the platform's own database are stored with Elastx in Sweden. Older copies remain with Amazon Web Services in its Stockholm region (eu-north-1) until they expire, as listed under "Infrastructure and hosting" below. If you enable CDN acceleration, copies of the content you accelerate and your end users' request data are also processed at Varnish edge locations; Elastx provides this feature through Varnish, as listed under "Content delivery" below.
Current sub-processors
This list covers sub-processors engaged in the delivery of the Services under our Terms of Service, including the platform, the workloads you deploy on it, and the account, billing and support functions that support them. Providers used only to publish this public website and our documentation are not part of that processing and are not listed here.
Our own advertising measurement is not part of that processing either. If an account user agrees to it when creating a workspace, we send Google a hashed copy of that user's email address to measure our own ads on Google. We do this as controller, with Google as our processor; it involves no data you process with the Services, and Google is not a sub-processor for the Services. It is described in our Privacy Policy under "Google Ads (Enhanced Conversions)".
Infrastructure and hosting
| Sub-processor | Purpose | Location | Safeguards for any non-EU transfer |
|---|---|---|---|
| Elastx AB | Compute, storage, networking, and managed Kubernetes for the Services. Where your application and its data are hosted. Since 21 October 2026, also storage of backup copies of the platform's own database, in Elastx's backup storage service The Vault in Sweden. Elastx also resells, and provides first- and second-line support for, the optional CDN acceleration feature, which Varnish operates (see "Content delivery" below). | Stockholm, Sweden (EU/EEA) | For hosting: EU/EEA-resident; no Chapter V transfer arises; Data Processing Agreement in place. For CDN acceleration, see "Content delivery" below. |
| Amazon Web Services | Storage of backup copies of the platform's own database (accounts, workspaces and service configuration) made before 21 October 2026, in Eyevinn's own AWS account. No new copies are stored with AWS. Each remaining copy is deleted 30 days after it was made, the last of them by about 20 November 2026, and AWS will then be removed from this list. | Stockholm, Sweden (AWS region eu-north-1, EU/EEA) | Stored in the EU/EEA region we selected. Under the AWS Data Processing Addendum, which is incorporated in the AWS Service Terms, AWS does not move the data out of that region except as necessary to provide the service or to comply with the law or a binding order of a governmental body, and the EU Standard Contractual Clauses (2021/914) incorporated in that addendum apply to any such transfer. |
Payment processing
| Sub-processor | Purpose | Location | Safeguards |
|---|---|---|---|
| Stripe (Stripe Payments Europe, Ltd. and affiliates) | Processes subscription payments. Stripe acts as an independent controller for payment data under its own privacy policy, so this falls outside our Article 28 processor chain, listed here for transparency. | EU (Ireland) with US operations | Stripe's Data Processing Agreement and EU Standard Contractual Clauses where applicable. PCI-DSS Level 1. |
Authentication (only where you choose that sign-in method)
| Sub-processor | Purpose | Location | Safeguards |
|---|---|---|---|
| GitHub, Inc. (Microsoft) | OAuth sign-in when you sign in with GitHub. Minimal data (token, user ID, email). | US with EU data centers | EU Standard Contractual Clauses (2021/914); Microsoft EU Data Boundary. |
| Google LLC | OAuth sign-in when you sign in with Google. Minimal data (token, user ID, email). | US with EU data centers | EU Standard Contractual Clauses (2021/914) and a transfer impact assessment are the operative safeguard for this transfer. Google additionally holds an active EU-US Data Privacy Framework certification (verified 2026-08-19); we do not rely on the Framework for this transfer. |
| Apple Inc. | "Sign in with Apple" when you choose it. Minimal data (token, user ID, relay email). | US with global operations | EU Standard Contractual Clauses (2021/914) and Apple's data-processing terms are the operative safeguard for this transfer. Apple is not certified under the EU-US Data Privacy Framework (verified against the Framework participant list 2026-08-19); we do not rely on the Framework for this transfer. |
Email magic-link and passkey (WebAuthn) sign-in involve no third-party identity sub-processor.
Content delivery (only where you enable CDN acceleration)
| Sub-processor | Purpose | Location | Safeguards for any non-EU transfer |
|---|---|---|---|
| Varnish Software AB (Stockholm, Sweden), engaged by Elastx AB | Provided through Elastx AB, which resells the CDN service. Content delivery network (CDN) for the endpoints on which you enable CDN acceleration. Caches and delivers that content, and processes your end users' request data at the edge, including IP address, requested URL, user agent and timestamp. | Varnish's European edge network. We have asked Elastx and Varnish for the country of each edge location and for the name and location of the infrastructure partner it uses, and will list them here once Varnish confirms them. | Not yet confirmed. We have asked Elastx and Varnish whether any processing of, or access to, this data takes place outside the EU/EEA. This entry will state the safeguard, or that no Chapter V transfer arises, once Varnish confirms. |
Analytics (self-hosted on our EU infrastructure)
| Tool | Purpose | Location | Note |
|---|---|---|---|
| Umami Analytics | Privacy-focused, cookieless web analytics. No cookies and no personal identifiers. | Self-hosted on our Stockholm (EU/EEA) infrastructure | Self-hosted; no third party has access, so not a separate sub-processor. |
AI model providers (the OSC AI assistant and the ask-osc-architect MCP tool)
OSC's AI features send prompt and operational content to a third-party AI model provider. These are the AI assistant in the web console and the ask-osc-architect tool, which is available to any connected MCP client and needs no separate activation. We enforce a 7-day retention limit and pseudonymize user identifiers; the providers do not use this content to train their models under their commercial API terms.
| Sub-processor | Purpose | Location | Safeguards |
|---|---|---|---|
| Anthropic, PBC | AI model provider (Claude API) for OSC's AI features. | United States | EU Standard Contractual Clauses (2021/914), Module 3 (processor-to-processor), together with a transfer impact assessment and the supplementary measures described above, are the operative safeguard for this transfer. Data Processing Agreement in place. This recipient is not certified under the EU-US Data Privacy Framework (verified against the Framework participant list 2026-08-19); we do not rely on the Framework for this transfer. |
| OpenAI, L.L.C. (OpenAI Ireland Ltd. for the EEA) | AI model provider (GPT API) for OSC's AI features. | United States | EU Standard Contractual Clauses (2021/914), Module 3 (processor-to-processor), together with a transfer impact assessment and the supplementary measures described above, are the operative safeguard for this transfer. Data Processing Agreement in place (effective 1 June 2026). This recipient is not certified under the EU-US Data Privacy Framework (verified against the Framework participant list 2026-08-19); we do not rely on the Framework for this transfer. |
Changes to this list
Update of 12 November 2026. Our data processing agreement with Elastx AB has been replaced by a new agreement, signed by both parties and in force from 9 November 2026. This update does not change the list of sub-processors on this page.
Update of 23 October 2026. Since 21 October 2026, backup copies of the platform's own database are stored with Elastx AB in Sweden instead of with Amazon Web Services. No new copies are stored with Amazon Web Services, and the copies that remain there are deleted 30 days after they were made. This is a change of role among sub-processors already listed, with no new international transfer and no new category of processing.
Update of 19 October 2026. Amazon Web Services has been added to this list. It stores backup copies of the platform's own database in its Stockholm region (eu-north-1). It was already doing so before this update, and earlier versions of this list should have named it. Varnish Software AB is now shown as engaged by Elastx AB, which resells the CDN acceleration feature. The Varnish change is a change of role among sub-processors already listed, with no new international transfer and no new category of processing.
Update of 12 October 2026. Varnish Software AB has been added as a sub-processor for CDN acceleration, an optional feature that is off unless you enable it (see "Optional features you enable" below). CDN acceleration has been available to customers since 12 October 2026. Elastx AB remains the sole provider of the hosting infrastructure for the Services.
Update of 10 September 2026. Akamai Technologies, Inc. has been removed. Eyevinn no longer uses Akamai for any part of the Services, and from that date Elastx AB was the sole infrastructure provider for the Services, apart from the database backups with Amazon Web Services (see the update of 19 October 2026). Content delivery for customers who enable CDN acceleration has since been added (see the update above).
Update of 28 August 2026. Elastx AB is the infrastructure provider for the Services, and the Akamai entry has been narrowed to components that have not yet migrated. Cloudflare, Inc. has been removed because it is not engaged in the delivery of the Services as scoped above.
Except as described under "Optional features you enable" below, we will notify customers at least 30 calendar days before a material change to this list, by which we mean adding a new sub-processor, or replacing one in a way that introduces a new international transfer or a new category of processing. Notification is by:
- updating this page (the canonical, current list); and
- emailing the account contact on record.
A change of role among sub-processors already listed here, where no new international transfer and no new category of processing arises, is published on this page rather than notified in advance.
If you object to a new sub-processor on reasonable data-protection grounds within 30 days, we will discuss it in good faith; if unresolved, you may terminate the affected Services without penalty. This applies to all customers, whether or not a separate Data Processing Agreement has been signed.
Optional features you enable. Some sub-processors are engaged only for an optional feature that is off unless you switch it on yourself, such as CDN acceleration. Such a sub-processor is listed on this page, and is named, with a link to this page, on the screen where you enable the feature, before you enable it. By enabling the feature you authorise that sub-processor for the content and personal data processed through that feature, so no 30-day advance notice is given for it. If you do not enable the feature, that sub-processor processes none of your data. You can withdraw that authorisation at any time by disabling the feature, after which we stop routing your content and your end users' requests through that sub-processor. If we later add or replace a sub-processor for an optional feature you have already enabled, the 30-day notice and the objection right above apply to you.
Questions
Contact privacy@eyevinn.se.