PrestaOne Service Provider and Sub-processor List
Last updated: 2026-09-16
PrestaOne (MB "Elevio") uses the following providers to deliver the Service. A provider is a sub-processor only where it processes personal data on a Customer's behalf under the DPA. Some providers instead process PrestaOne controller data, and Stripe may also act as an independent controller for its regulatory, fraud-prevention and payment-network obligations. The role, data, location and transfer safeguard are listed below. Where practicable, we notify Workspace owners by email at least 14 days before a new sub-processor starts processing personal data on a Customer's behalf; urgent security, legal or continuity replacements may be notified as soon as reasonably possible (DPA §5).
| Provider | Relationship | Purpose | Personal data involved | Location | Transfer safeguard |
|---|---|---|---|---|---|
| Google Analytics / Google Ads (Google Ireland Ltd.) | Processor for PrestaOne controller data | Limited cookieless website measurement by default; optional analytics cookies after consent; website setup-start conversion measurement and campaign bidding | Page views, campaign labels, referring origin, consent state, timestamp, browser/device information, approximate location and final store/download destination category; IP processed to deliver the request and derive location; pseudonymous cookie/session identifiers only after consent | Google's global infrastructure | Google Ads Data Processing Terms; applicable SCCs and transfer safeguards |
| Google Cloud / Firebase (Google Ireland Ltd.) | Processor / sub-processor, depending on data | Authentication (including Google sign-in), EU database, backend functions and push outbox | Account email/UID, provider account identifier and optional provider profile fields, random device ID, pseudonymous stability key, device/push/connection records, hashed rate-limit records; signaling references, amount/currency and delivery records | EU: Firestore eur3 (Belgium/Netherlands), functions europe-west1 (Belgium); identity-provider processing may use Google's global infrastructure | Google Cloud DPA; SCCs where required |
| Google Firebase Cloud Messaging (Google Ireland Ltd.) | Sub-processor for Customer signaling; processor for app-user push | Android push delivery | Push token; event type, internal Store/object reference and order amount/currency | Global delivery network | Google Cloud DPA / SCCs |
| Apple services (Apple Distribution International Ltd.) | Service provider for app-user authentication; sub-processor for Customer signaling; processor for app-user push | Sign in with Apple and iOS push delivery | Apple account identifier or relay email; push token, event type, internal Store/object reference and order amount/currency | Global service and delivery network | Apple developer privacy terms / SCCs |
| Expo (650 Industries, Inc.) | Sub-processor for Customer signaling; processor for app-user push/build operations | Expo Push API relay and app build infrastructure | Push tokens and notification payloads. Expo states message content is kept only in memory/queues until handoff and push receipts are cleared after 24 h | USA | EU–US Data Privacy Framework; DPA/SCCs |
| Resend (Plus Five Five, Inc.) | Processor for PrestaOne controller data | Transactional email, including one-time sign-in codes and service/billing notices | Recipient email, one-time code or service message content, delivery metadata | USA | EU–US Data Privacy Framework (+ UK extension); DPA/SCCs |
| Sentry (Functional Software, Inc.) | Processor for PrestaOne controller data | Operational JavaScript/native crash and error reporting, independent of optional usage tracking | Stack traces, technical breadcrumbs, device/OS and app/build metadata and internal Store ID; default PII disabled, JavaScript reports sanitised | EU: ingest and storage in Germany (de.sentry.io) | EU data residency; DPA and applicable transfer safeguards |
| Stripe (Stripe Payments Europe, Ltd.) | Processor and, for specified regulated purposes, independent controller | Subscription billing, hosted customer portal, invoicing, tax and fraud prevention | Billing identity/contact/address, country/tax ID, payment method, invoice/transaction and fraud data; PrestaOne receives provider references and subscription/seat state | Ireland and Stripe group/service-provider locations | Stripe DPA; DPF/SCCs as applicable |
| Cloudflare (Cloudflare, Inc.) | Processor for PrestaOne controller data | Edge networking and country-code geolocation Worker | IP address and request metadata processed at the edge. Our Worker code does not persist or explicitly log raw IP; Cloudflare may process service/access logs under the applicable configuration and terms | Global edge network | Cloudflare DPA; DPF/SCCs as applicable |
| Hetzner (Hetzner Online GmbH) | Processor for PrestaOne controller data | Server hosting the prestaone.app website and the account.prestaone.app customer portal | Waitlist email addresses; anonymous pageview records (path, referrer, campaign parameters, country code, browser language, mobile flag); web server logs | EU: Helsinki, Finland | Hetzner DPA (Art. 28 GDPR); no transfer outside the EEA |
Notes:
-
Optional account-linked app usage events and consent records are stored in Google Cloud / Firebase. Usage events include screen/action names, outcomes, timings and app/device metadata. They are separate from essential connection, authentication and billing records.
-
The Customer's full business records (orders, products, customer records, direct buyer identifiers and message content) do not reach PrestaOne or its providers. They flow directly between the Customer's devices and server. The limited signaling exception is listed above and described in DPA §1.3.
-
PrestaOne's own Firebase push retry/delivery outbox may retain signaling and recipient snapshots for up to 30 days before TTL deletion. This is separate from Expo's transient delivery queue and 24-hour receipt retention.
-
Visitor analytics collected by the PrestaOne Module are stored only in the Customer's own database; no sub-processor receives them.
-
The website waitlist and historical first-party pageview records are held on the website server. Public website pages send limited cookieless measurements to Google Analytics with Consent Mode v2 storage and advertising permissions denied by default. Analytics cookie/session identifiers are added only after consent. The final store/download action may be imported from GA4 into Google Ads as a
setup_startconversion; it does not identify a later app installation, account, store connection or purchase. That data is PrestaOne controller data and is not Signaling Data under the DPA; the hosting provider is not a sub-processor for Customer data.
Questions: [email protected]