Sub-processor Register
Parkmo engages the third parties listed below to process personal data on its behalf. The list is current as of the “Last modified” date above and is maintained as the authoritative roster; changes are communicated under the notification policy in § 2.
For the wider data-protection context see the Privacy Policy.
1. Current sub-processors
| Provider | Service | Data category | Processing location | Transfer mechanism |
|---|---|---|---|---|
| Scaleway SAS | Kubernetes hosting, PostgreSQL hosting, attached block storage | All personal data we hold | Paris, France (fr-par) |
EU — none required |
| Scaleway Object Storage | Storage of invoice PDFs with compliance-grade retention locking | B2B billing contact data, invoice line items, IBAN reference | Paris, France (fr-par) |
EU — none required |
| Sinch Email API (Mailgun Technologies, Inc.) | Outbound transactional email (booking confirmations, password resets, invoice delivery) | Recipient email, message content, delivery metadata | EU region | EU region selected; EU-US DPF for any group-level metadata flow; SCCs as fallback |
| Cloudflare, Inc. | Authoritative DNS for parkmo.io, parkmo.dev, country TLDs |
DNS query metadata at edge POPs | Global anycast | EU-US DPF (self-certified); SCCs as fallback |
| Google Ireland Ltd. / Google LLC | (a) OIDC sign-in (“Sign in with Google”); (b) Google Workspace Directory API — only when a B2B customer connects their Workspace domain | (a) OIDC subject, email, name, profile picture, Workspace domain; (b) employee directory entries from the connected Workspace | Google Ireland contracting | EU-US DPF for onward US transfers; SCCs as fallback |
| Stripe Payments Europe, Limited (SPEL) — from the launch of paid bookings | Payment processing for end-user booking payments (Stripe Connect, direct charges) and operator payout/KYC onboarding | Payment metadata Parkmo discloses to Stripe: booking reference, amount, currency, end-user receipt email. Operator business and representative data entered during onboarding flows from the browser to Stripe directly | Ireland (SPEL); onward intra-group transfer to Stripe, Inc. (US) | EU contracting entity; EU-US DPF for onward US transfers (Stripe, Inc. is self-certified); SCCs as fallback |
Role note on Stripe. Stripe is only partially a sub-processor. With Stripe Connect direct charges, each operator (parking-lot operator / facility manager) contracts Stripe directly under the Stripe Connected Account Agreement, and cardholder data flows from the end user’s browser to Stripe without touching Parkmo’s systems — for payment data, Stripe is the operator’s payment processor (and an independent controller for its own fraud-prevention and regulatory processing), not Parkmo’s sub-processor. Stripe appears in this register because Parkmo does disclose limited personal data to Stripe when orchestrating payments (booking reference, amount, end-user receipt email, operator prefill data). See the Privacy Policy §§ 3.2.2 and 3.6.
The booking app and the tenant app do not load analytics SDKs. From the launch of paid bookings, the booking app loads Stripe.js on the payment step only (strictly-necessary fraud-prevention cookies; see the Cookie Policy). Cloudflare touches every name resolution but holds no application-layer personal data.
2. Notification policy
When Parkmo intends to add, replace, or remove a sub-processor that processes personal data for our B2B customers:
- The roster above is updated, and a short change log appended at the bottom of this page with the date, the change, and the reason.
- Subscribed customers receive an email notice at the technical contact named in their DPA. The notice is sent at least 30 days before the new sub-processor begins processing the customer’s data.
- The customer has until the start date to object in writing ([email protected]). If we cannot accommodate the objection (e.g., the change is to remediate a compliance issue), the customer may terminate the affected service with no early-termination penalty.
The 30-day notice can be compressed to 7 days for urgent security replacements (e.g., a sub-processor announces a serious breach and we need to switch to a backup quickly); customers are still entitled to object.
For sub-processors that touch only Parkmo-as-controller data (e.g., the marketing-site analytics, billing-related vendors that handle Parkmo’s own books), this notification policy does not apply because Parkmo is the controller of that processing.
3. Subscribing to changes
Customers who want notice of the changes above should send [email protected] an email with subject subscribe sub-processor updates. We maintain the subscription list in a dedicated mailbox; the list is itself processed under Art. 6(1)(b) GDPR (contract performance with the customer) and retained for the duration of the customer relationship + 90 days.
4. Change log
- 2026-06-11 — Removed Microsoft Corporation (Clarity). The session-replay/heatmap tool was removed from the marketing site entirely; no Parkmo surface sends data to Microsoft.
- 2026-06-11 — Added Stripe Payments Europe, Limited (effective from the launch of paid bookings) for end-user booking payments and operator payout onboarding via Stripe Connect direct charges. Reason: payment-acceptance feature for operators.