Sign In

Privacy Policy

Last modified: 2026-10-02

1. Who we are

This Privacy Policy describes how Parkmo UG (haftungsbeschränkt) (“Parkmo”, “we”, “us”) processes personal data.

  • Parkmo UG (haftungsbeschränkt)
  • Solalindenstraße 83, 81827 Munich, Germany
  • Registered with: Amtsgericht München, HRB 255210
  • VAT ID: DE328424517
  • Managing director: Andrii Kalinichenko
  • Privacy contact: [email protected]

We have not appointed an external Data Protection Officer (DPO). For data-protection questions write to the address above.

How the Parkmo app accesses, uses, stores and shares Google user data is set out in § 3.7.

2. Scope

This policy applies to:

  • Marketing site at parkmo.io and country-TLD equivalents (parkmo.de, parkmo.fr, etc.) — Parkmo is the controller.
  • Public booking forms at booking.parkmo.io and country-TLD equivalents — the operator of the parking lot, building, or facility shown on the page is the controller, and its privacy notice, linked from each booking page, governs. Parkmo acts as the operator’s processor under a Data Processing Agreement. § 3.2 describes that processing for transparency; § 3.2.1 is where Parkmo becomes controller.
  • Authenticated tenant application at app.parkmo.io / admin.parkmo.io used by employees of Parkmo’s B2B customers — your employer is the controller and its privacy policy governs. Parkmo acts as a processor under a Data Processing Agreement with the employer.
  • Sign-in and sign-up at auth.parkmo.io and join.parkmo.io, including Sign in with Google — for employees of B2B customers the employer is the controller, as above; for an account you create for your own company, Parkmo is the controller. What Parkmo receives from Google and how we use it is set out in § 3.7.

3. Personal data we process and why

3.1 Visitors to the marketing site

Data Purpose Legal basis (GDPR) Retention
IP address, user agent, request path, response status, timestamps (server access logs) Operate, secure, and analyse the website; protect against attacks Art. 6(1)(f) — legitimate interest in operating a secure service 7 days
Cookies and similar storage — see the Cookie Policy As listed per category Strictly-necessary cookies: Art. 6(1)(f); all other cookies and SDKs (analytics, marketing): Art. 6(1)(a) consent + § 25 TTDSG Per cookie; see cookie policy
Contact-form / sales-form submissions Reply to your enquiry Art. 6(1)(b) (pre-contractual measures) for sales enquiries, Art. 6(1)(f) for general support 24 months after last contact
Newsletter email address Send the newsletter you opted into Art. 6(1)(a) consent; double opt-in Until you unsubscribe, then 90 days for proof-of-consent

3.2 End users of the public booking forms (booking.parkmo.io/…)

Data Purpose Legal basis Retention
Email address Send booking confirmation, payment link, cancellation link Art. 6(1)(b) (contract performance with the end user; bookings are contracts of carriage for the parking space) 24 months after the booking end
Vehicle license plate Authorise entry at the lot; resolve incidents (wrong-lot exit, double-booking) Art. 6(1)(b) (contract performance) Same as above
Booking time range (start, end), location, resource Provide the booking Art. 6(1)(b) Same as above
Booking access logs (IP, user agent, timestamps) Fraud prevention, security Art. 6(1)(f) 30 days
Payment data for paid bookings — see § 3.2.2 Pay the operator for the booking Art. 6(1)(b) Card data: not held by Parkmo. Payment metadata: 24 months after booking end

The operator of the lot or facility is the controller of this data. It receives the email and license plate to perform the booking contract — providing the parking space. Parkmo processes the data on the operator’s behalf and on its instructions (Art. 28 GDPR). Please send requests about this data to the operator; if you send them to us, we forward them.

3.2.1 Linking your prior bookings to a Parkmo account (“identity merging”)

If you later create a Parkmo account using the same email address you previously typed into a booking form, we link the bookings you made anonymously to your new account so you can see, manage, and re-use them after you sign in. Concretely:

  • The link is triggered only by a signup whose email has been verified (either through Parkmo’s email-verification step, or through a federated provider like Google or Microsoft that vouches for the address).
  • We move the references on your historical bookings from the temporary guest record to your new account. The “host” relationship of each booking — the operator who owns the resource — is not affected.
  • We then erase the personal data from the now-redundant guest record: the email is replaced with an internal sentinel string, names are set to null, and the record is marked deleted. The bookings themselves remain available to you.
  • The link is a one-shot operation that runs once at signup. It is not repeated for subsequent bookings.

Legal basis. Art. 6(1)(b) GDPR — performance of the contract you enter into with us when you sign up. Art. 6(1)(f) (legitimate interest in providing a coherent experience across anonymous and authenticated sessions) applies as a fallback basis. The operator whose booking form you used instructs us to show your bookings in your account; from the moment of linking, Parkmo is the controller of your account, including that view of your bookings.

Edge cases.

  • Different email on signup. If you sign up with an email different from the one you used at the booking form, your anonymous bookings are not linked. You can ask us at [email protected] to perform the link manually after we verify both addresses.
  • Shared inbox / family address. If two different natural persons used the same email at the booking form and one of them signs up, the other person’s bookings will be moved onto the signed-up person’s account. If this affects you, contact [email protected] for a separation.
  • Bookings you have asked us to erase before signing up. These have already been deleted; they are not resurrected by the link.

This processing has been assessed under a Data Protection Impact Assessment.

3.2.2 Paying for a booking (Stripe)

This section applies from the launch of paid bookings.

Payments for bookings are processed by Stripe. Our contracting entity is Stripe Payments Europe, Limited, Dublin, Ireland. The payment is made directly to the operator of the lot or facility: the charge is created on the operator’s own Stripe account, and Parkmo never receives or holds your money.

  • Your card or payment details are entered into a payment form provided by Stripe and are transmitted directly from your browser to Stripe. Parkmo does not receive, store, or process your card number, CVC, or bank details at any time.
  • When you provide personal data in connection with a payment, Stripe receives that personal data and processes it in accordance with Stripe’s Privacy Policy, available at stripe.com/privacy. Stripe also processes payment data for its own fraud-prevention and legal-compliance purposes as an independent controller.
  • Parkmo receives and stores only payment metadata: the amount, currency, payment status, payment-method type (e.g. “card”), the email address used for the receipt, and Stripe’s reference IDs. We use it to confirm, release, or refund your booking. Legal basis: Art. 6(1)(b) GDPR (performance of the booking contract).
  • The Stripe payment form sets strictly-necessary fraud-prevention cookies on the payment step only — see the Cookie Policy.

3.3 Account holders in the tenant app

When the data subject is using Parkmo because their employer or another B2B customer has signed up, the employer is the controller. Parkmo’s processing in that scenario is described in the customer’s DPA with us. The categories of data we touch in that processor role are:

  • Identity: name, business email, role, department.
  • Authentication: hashed credentials (via Ory Kratos, self-hosted), session tokens, OIDC subject identifiers if the customer uses Google or another federated provider.
  • Booking history: which resource the user booked, when, from where (IP for security only).
  • Optional profile data: language, timezone, profile picture if uploaded.

3.4 Billing data (B2B customer accounts only)

Data Purpose Legal basis Retention
Company name, billing address, VAT ID, contact name Issue invoices, comply with VAT law Art. 6(1)(c) (legal obligation under § 14 UStG, § 147 AO) + Art. 6(1)(b) (contract performance) 10 years (§ 147 AO)
IBAN, BIC, SEPA mandate reference, mandate date Collect SEPA direct debits Art. 6(1)(b) 10 years (§ 147 AO)
Invoice PDFs (issued to your company) Tax + accounting records Art. 6(1)(c) 10 years (§ 147 AO)

For Parkmo’s own invoices to its B2B customers we do not use a third-party payment processor: direct debits are initiated by Parkmo’s bank against the SEPA mandate you grant, and the IBAN is stored encrypted at rest in our database hosted at Scaleway, Paris (fr-par). (End users’ payments to operators are processed by Stripe — see § 3.2.2; operators’ payout onboarding — see § 3.6.)

3.5 Job applicants

Out of scope for this document. A separate applicant-privacy notice applies; ask [email protected] if you applied.

3.6 Operators accepting payments (Stripe Connect onboarding)

This section applies from the launch of paid bookings.

If you operate a lot or facility on Parkmo and enable payments, you open a payment account with Stripe through an onboarding form embedded in Parkmo. You contract directly with Stripe under the Stripe Connected Account Agreement.

  • The identity and business information you enter (including identity documents and details of beneficial owners) is transmitted directly from your browser to Stripe, which is responsible for the legally required identity verification (KYC/AML) as an independent controller. Stripe’s Privacy Policy applies: stripe.com/privacy.
  • Stripe can obtain information from credit agencies to verify your identity. That information will be used for the purposes described in Stripe’s Privacy Policy.
  • Parkmo receives from Stripe only the status of your account (e.g. whether charges and payouts are enabled and which verification requirements are outstanding) and stores a record of your acceptance of Parkmo’s platform terms (timestamp, IP address, terms version). Legal basis: Art. 6(1)(b) GDPR.

3.7 Google user data (Sign in with Google)

You can sign in to the Parkmo app with your Google account at auth.parkmo.io. This section describes how Parkmo accesses, uses, stores and shares the data it receives from Google (“Google user data”).

  • How we access Google user data. Only when you choose Sign in with Google, through Google’s consent screen. For sign-in, Parkmo requests only the openid, email and profile scopes, that is, your basic profile. We do not request access to Gmail, Google Drive, Google Calendar, your contacts or any other Google data, and we do not call Google APIs with your account.
  • Which Google user data we keep. Your Google account ID, your email address and whether Google has verified it, your first and last name, and your language setting. Google’s sign-in response also contains a link to your profile picture and, for Google Workspace accounts, your organisation’s domain: we do not copy the picture link into your account, and we use the domain only as a security check before a Google sign-in is linked to an existing account.
  • How we use Google user data. Only to create your Parkmo account, sign you in, show your name and email address in the app, send you the emails your account and bookings require, and link bookings you made earlier with the same verified email address (§ 3.2.1). We do not use it for advertising, do not sell it, and do not use it to develop, improve or train generalised AI or machine-learning models.
  • How we store Google user data. In our self-hosted identity service (Ory Kratos) and our database in Scaleway’s data centre in Paris, France, encrypted in transit and at rest (§ 8). The sign-in tokens Google issues, which contain the profile information above, are kept in encrypted form and are not used to access Google APIs.
  • How we share Google user data. Only with the sub-processors that host and operate Parkmo (§ 5), and where the law requires it. Owners and admins of the company account you belong to see your name and email address in the app. Parkmo staff read Google user data only in three cases: with your consent, to investigate security incidents or abuse, and to comply with the law.
  • Retention and deletion. We keep Google user data for as long as your account exists. You can delete your account yourself on the Account page in Parkmo, which deletes your Google account ID and the profile data received from Google at once. If you own a company account, the company has to be closed first: write to [email protected]. Your rights are set out in § 6.
  • Revoking access. You can remove Parkmo’s access at any time at myaccount.google.com/permissions. Parkmo then receives nothing more from Google; if you later sign in with Google again, Google asks for your consent again. Revoking access does not delete your Parkmo account or the data already received; to have them deleted, see the previous point.
  • Changes. If we change how Parkmo accesses, uses, stores or shares Google user data, we update this section and notify affected users by email before the change takes effect, and ask for consent again where the law requires it.
  • Legal basis. Where Parkmo is the controller (§ 2), Art. 6(1)(b) GDPR — providing the account and the sign-in method you chose.

Parkmo’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

4. Cookies and tracking

See the Cookie Policy. The marketing site does not use Google Analytics or any other analytics tool, and we do not use session-replay tools.

If the operator of a lot or facility has set up its own Google Analytics 4 measurement ID for its booking page, that page loads Google’s gtag.js and sends page-view data to the operator’s Google Analytics property. The property and its data belong to the operator; Parkmo does not read them. The booking page also loads Stripe.js on the payment step (§ 3.2.2). The tenant app loads no analytics SDKs.

5. Where your data goes

We use the following sub-processors. The current list is also published at parkmo.io/sub-processors:

Provider Role Location of processing Transfer mechanism
Scaleway SAS Cluster hosting, database hosting (k3s on bare-metal in Scaleway’s data centres) Paris, France (fr-par) EU — no transfer mechanism required
Scaleway Object Storage Invoice PDF storage (WORM retention for tax compliance) Paris, France (fr-par) EU — no transfer mechanism required
Sinch Email API (formerly Mailgun) Sending of transactional and invoice emails EU region (smtp.eu.mailgun.org) EU region selected; Sinch is a US group
Cloudflare, Inc. Authoritative DNS for parkmo.io, parkmo.dev, and country TLDs Global anycast; DNS metadata only US controller; EU-US DPF self-certified for the DNS service
Google Ireland Ltd. / Google LLC OIDC sign-in (“Sign in with Google”, § 3.7). Workspace Directory API (used only by B2B customers who connect a Google Workspace domain). Parkmo does not use Google Analytics; where a booking page loads it, the property is the operator’s own (§ 4). Sign-in via Google Ireland; Workspace data resident in EU as Google offers EU-US DPF for any onward US transfer
Stripe Payments Europe, Ltd. (from launch of paid bookings) Payment processing for bookings (§ 3.2.2) and operator payout accounts (§ 3.6). Card data goes from your browser to Stripe directly; Parkmo shares only booking reference, amount, and receipt email Ireland; Stripe-internal transfers to Stripe, Inc. (US) EU contracting entity; EU-US DPF for Stripe’s US transfers; SCCs as fallback

We do not transfer personal data outside the EEA on any basis that is not listed above. We never sell personal data.

6. Your rights

You have, under the GDPR:

  • Right of access (Art. 15) — confirm what we hold about you and obtain a copy.
  • Right to rectification (Art. 16) — correct inaccurate or incomplete data.
  • Right to erasure (Art. 17) — delete your data unless we have a competing legal duty (typically tax retention for invoice rows).
  • Right to restriction (Art. 18) — pause processing while a dispute is resolved.
  • Right to data portability (Art. 20) — receive your data in a structured, commonly used, machine-readable format and have it transmitted to another controller.
  • Right to object (Art. 21) — including unconditional objection to direct marketing.
  • Right to withdraw consent (Art. 7(3)) — without affecting prior processing carried out on consent.
  • Right to lodge a complaint (Art. 77) with a supervisory authority. Parkmo’s lead authority is the Bayerisches Landesamt für Datenschutzaufsicht (BayLDA), Promenade 18, 91522 Ansbach. You may also complain to the authority of your habitual residence or place of work.

To exercise any right, email [email protected]. We respond within one month (Art. 12(3) GDPR); complex requests may be extended by a further two months with notice. We may ask for proof of identity proportionate to the request.

7. Automated decision-making

Parkmo does not make decisions with legal or similarly significant effect on data subjects on the basis of automated processing alone (Art. 22 GDPR). Booking availability is determined algorithmically from inventory and rules, but the determination does not have a legal effect on you within the meaning of Art. 22.

8. Security

Personal data is encrypted in transit (TLS 1.2+) and at rest (Scaleway block-storage encryption; SSE-S3 for object storage; pgcrypto / column-level encryption for sensitive fields where used). Access to production systems is restricted to named engineering staff, requires SSO with hardware-key MFA, and is logged.

9. Changes to this policy

Substantive changes (added sub-processors, new data categories, new purposes, new legal bases) are published on this page with the revised date in the header and, where required, notified to affected data subjects by email. The previous version is retained internally for the duration of any open data-subject request plus the retention period for the data the request concerns.

book anything, anytime, anywhere.
  • Imprint
  • Privacy
  • Terms
  • Cookies
  • Billing