Privacy Policy

Email: hello@baymity.com

No data protection officer has been appointed. You can direct every privacy request to the controller using the email above.

This Policy covers Baymity’s website and web application, including when added to your device's home screen, accounts, listings, bookings, public discovery, optional alerts, promotion tools, payments, payouts, ratings, access coordination, and complaint handling. We receive data directly from you, from another user involved in a booking or report, from the authentication and payment providers you use, and automatically from your browser or device.

If you provide another person’s data, such as a Host’s contact details or complaint evidence, you must be entitled to do so and give that person relevant information where required.

A separate recovery register records erasure requests, processing restrictions, and alert withdrawals so that restoring an older backup does not undo them. It contains case, account, or booking identifiers, action dates, and, where needed, a hash of the email address for matching older records. These identifiers remain personal data; hashing is not anonymisation. The register does not copy the deleted profile or complaint evidence. It is encrypted in transit and at rest, held separately from the backup archives, and accessible only to authorised operators for handling your rights, security, and recovery checks. The legal bases are Art. 6(1)(c) GDPR for fulfilling data-protection duties and Art. 6(1)(f) GDPR for secure recovery and preventing unlawful reuse of data.

Completed decisions are removed from the active recovery register 90 days after completion. Unfinished cases are retained only while needed to resolve and review them. Previous register versions are scheduled for deletion one day after they become previous versions. Protection against early deletion lasts seven days from each version's creation and can delay that cleanup; provider processing delays can also extend physical retention.

If a specific record must be retained for a legal duty or documented legal claim, Baymity retains only the necessary data for that purpose and applicable period. Other eligible data is deleted or anonymised without undue delay. Earlier backup copies follow the separate, limited recovery schedule in Section 11.1; a backup is not a reason to extend ordinary account use or the statutory time for responding to your request.

Email, account and legal-acceptance data are required to create and use an account. An account-free Guest must instead provide a booking name, email address, vehicle plate, booking-specific legal acceptance, and payment permission. Listing, availability, authority, Stripe onboarding, and payout information is required to act as a Supplier. Booking times, contact details, vehicle identification, payment information, and booking-specific payment permission are required to make and perform a booking. Additional identity, tax, trader, or property information may become mandatory under law.

Without required information Baymity may be unable to create an account, publish a listing, confirm a booking, process a payout, investigate a complaint, or continue the relevant service. Complaint photographs are normally optional; submit only what is necessary and avoid including people, homes, access credentials, or unrelated vehicles.

Visitors can browse active listing addresses, access mode, account-free booking settings, and published vehicle limits without signing in. Public listing links can also identify the building, level, and space number. Search results contain listing descriptions, garage details and instructions, and Supplier display/rating information. Keep confidential entry credentials out of fields displayed in search or promotion tools. The Explore directory and public listing lookup do not include Supplier email or phone details.

After a booking, Baymity shares the information reasonably needed for performance among the Supplier, Guest, and approved Host. This can include names, contact details, vehicle plate, booking times, location, access instructions, and status. Complaint evidence is limited to involved users, authorised reviewers, service providers, advisers, or authorities as required for the case.

An account-free Guest manages the reservation through a high-entropy confirmation link sent to the supplied email address. Anyone with that link may be able to view and manage the booking until it expires, so the recipient must keep it confidential. Suppliers see the booking contact and vehicle details needed to perform the Parking Agreement.

A public listing QR code or booking link is different from a confidential booking-management link. Anyone receiving a flyer or public listing link can follow it and pass it on. Taking down a listing does not recall printed flyers, downloads, or copies held by others. Visit sharing includes address and times, but does not insert the booking-management token, vehicle plate, or Guest contact details. Email and messaging links used to contact a booking participant may instead prefill relevant booking and vehicle details; review the draft before sending it through your chosen provider.

Complaint photographs are stored in a private object store. Access is restricted to the uploader, authorised booking participants after approval, and authorised reviewers through short-lived links. Automated screening is a risk-reduction measure and can be wrong; Baymity may require human review, reject unrelated or harmful material, and provide a review route.

Baymity does not sell personal data. Relevant recipient categories include:

• Supabase for authentication, database, storage, and related backend services;
• Amazon Web Services (AWS) as a recovery-service provider for encrypted backup storage, temporary export processing, protected recovery credentials and operational alerts. Independent backups and export processing are configured in Frankfurt, Germany; the production Supabase project is in Ireland. Authorised local recovery work is performed in a restricted workspace in Germany;
• Vercel for hosting the web application, executing server-side functions, maintaining deployment and operational logs, and optional cookieless Vercel Web Analytics for aggregate usage statistics;
• Resend for authentication and transactional email, delivery and bounce handling, and related troubleshooting; see the Resend Privacy Policy;
• Cloudflare Turnstile for bot detection and abuse prevention on authentication, account-free booking, and optional alert requests; see the Cloudflare Turnstile Privacy Addendum;
• OpenAI, when configured, for automated safety screening of complaint images before they are made available to other booking parties. The submitted image is transmitted for this screening; Baymity stores the screening result and review metadata, not an advertising profile;
• Stripe, including the relevant Stripe Payments Europe and group entities, for hosted Supplier onboarding, identity and account verification, saved payment credentials, direct charges, fraud and sanctions screening, authentication, application fees, refunds, disputes, and Supplier payouts; see the Stripe Privacy Policy;
• PayPal only for legacy payment and payout records, provider reconciliation, refunds, disputes, or legal retention relating to a transaction previously processed through PayPal;
• Google for Google sign-in, embedded Google Maps previews in Guest and Supplier views, and external Maps links. A visible embedded map can contact Google without a separate click on an external link; see the Google Privacy Policy;
• OpenStreetMap Foundation / Nominatim for resolving a Guest's destination and a Supplier's garage address for coverage, nearby search, optional alerts, and aggregated demand planning; see the OpenStreetMap Foundation Privacy Policy;
• professional advisers, insurers, banks, auditors, and debt or claims handlers where needed;
• courts, law-enforcement, tax, regulatory, and other public authorities where legally required; and
• a successor operator in a lawful business transfer, subject to applicable safeguards.

Baymity configures its server-side application functions to run in Dublin, Ireland (EU). Vercel also provides global content delivery and supporting services, including deployment management, security, operational logs and optional web analytics. This region setting does not restrict all Vercel processing, including support and administration, to Ireland or the EEA.

Processors receive only the data needed for their task and are contractually bound where required. Stripe may act as Baymity's processor for some platform functions and as an independent controller for regulated payment, verification, fraud, security, and Connected Account purposes. Cloudflare processes Turnstile signals on Baymity's behalf to provide the security service and may process limited signals as an independent controller to improve its bot-detection systems. Authentication and mapping providers may likewise act as independent controllers for their own purposes. Their own privacy information applies to that processing.

If a cardholder dispute is opened, Baymity may provide Stripe, the relevant card network, acquiring bank, or card issuer with the booking-confirmation IP address and the limited request context described above, together with the booking, payment, consent, complaint, and communication records needed to establish, exercise, or defend the claim. This evidence is not used for advertising or general behavioural profiling.

Depending on provider configuration and your choices, a recipient may process data outside the European Economic Area. Baymity uses an applicable safeguard, such as an adequacy decision, participation in the EU–US Data Privacy Framework where valid for the recipient, or the European Commission’s Standard Contractual Clauses supplemented where necessary. You may request information about the safeguard relevant to your data. Choosing EU application-function, database or backup regions does not by itself rule out all non-EEA provider support or administrative processing; applicable provider terms and transfer safeguards must also be considered.

Baymity uses cookies, local storage, and session storage for authentication, security, legal-acceptance handoff, saved preferences, form drafts, and other functions described above. Section 25(2) TDDDG permits storage or access without consent only where it is strictly necessary for transmission or for a digital service you expressly request. Other device storage or access requires prior consent under Section 25(1) TDDDG; a legitimate interest under the GDPR does not by itself replace that consent.

The language cookie is named baymity_locale. Baymity local-storage entries include the selected Guest/Supplier view, cookie settings, dashboard and tour preferences, saved booking defaults, and flyer drafts. Session storage keeps unfinished forms, scroll position, and booking request/access credentials needed to resume the current flow. Supabase also stores authentication-session credentials. Clearing site data can sign you out and remove drafts; it does not cancel a booking or delete server-side records.

When a Guest opens Stripe's Payment Element or a Supplier opens Stripe-hosted onboarding, Stripe receives technical data such as IP address, device, browser, page interaction, and security signals and may use cookies or similar storage needed for payment authentication, fraud prevention, and service security. Stripe is responsible for explaining its own storage and independent processing in its privacy information.

Authentication, account-free booking, and alert forms use Cloudflare Turnstile where configured to distinguish legitimate requests from automated abuse. Cloudflare receives technical and interaction signals such as IP address, browser and device characteristics, request context, and the Turnstile result. The check is used for authentication security, not for Baymity advertising or audience analytics. Baymity sends the short-lived Turnstile token to its authentication service for server-side validation and does not treat a client-side result alone as proof that a request is legitimate.

Baymity loads cookieless Vercel Web Analytics only after you explicitly consent to Analytics. The Analytics switch is off by default. Before consent, the provider script does not load and no analytics page views or custom events are collected or queued for later replay. You can decline without affecting your ability to use Baymity, or withdraw consent at any time through Cookie Settings. Settings saved under the earlier default-on policy do not count as consent: a new opt-in is required; prior declines remain effective. Acknowledging this Privacy Policy or accepting the account Terms does not give Analytics consent. Baymity records the consent-notice version, your choice and its timestamp in browser storage.

Vercel describes the service as cookieless, with a visitor hash that resets after 24 hours. Data includes general device, browser, country and referrer information and categorical journey events. Baymity strips URL queries and fragments, replaces confirmation tokens with a generic path, and excludes admin and diagnostic pages. Custom events exclude addresses, contact details, plates, account and booking identifiers, payment details and free text. Baymity does not enable analytics cookies, identify users to Vercel, or link these statistics to account profiles.

The legal basis for optional analytics is Art. 6(1)(a) GDPR and, where device access requires consent, Section 25(1) TDDDG. Withdrawal stops future collection immediately and is respected across tabs and on later visits; it does not affect the lawfulness of processing before withdrawal. No advertising pixel is active. These settings do not control server-side demand aggregation or embedded Maps previews, which are described separately. See the Vercel Web Analytics privacy information.

Google Maps is also embedded in address previews. When your browser loads a preview, it sends Google the map address and technical request data, including your IP address and browser information; Google may use its own cookies or similar technologies. The current previews can load when displayed, without a separate map-consent step. External Maps links contact Google when opened. Google's privacy information applies to its own processing. Baymity-hosted guide videos, fonts, and flyer assets do not use an embedded YouTube, social-network, or third-party video player.

Server-side geocoding sends the typed destination to the configured geocoding provider, separately from any Google preview. It can run after automatic search updates and for demand aggregation, coverage checks, and optional alerts. Distance estimates for nearby and wider-area results are straight-line distances, not pedestrian routes. Nominatim is the default pilot provider; its privacy information is linked above.

Search filters use address, requested time, availability, existing reservations, optional vehicle dimensions, account-free booking settings, Supplier eligibility, and payment readiness. Exact/supported-address results use total Guest price; nearby results use distance before price. Later-time suggestions prioritise the earliest suitable start. Section 8 of the Terms explains the relative ranking parameters and public discovery. Suppliers can set a minimum Guest rating, and the application can automatically prevent a booking when the current rating is below that threshold. The relevant rating and threshold are shown to the Guest.

This rule supports marketplace trust and the Supplier's booking conditions under Art. 6(1)(f) GDPR. If an automated decision produces legal or similarly significant effects, the additional requirements and safeguards of Art. 22 GDPR apply. You may contest an incorrect rating or restriction, explain your position, and request human review at hello@baymity.com. Material complaint and account-blocking decisions are not made solely by an automated process.

Stripe also applies automated security, fraud, sanctions, authentication, and account eligibility rules. A Stripe decision can require further information, reject a payment, or restrict charges or payouts. Those provider decisions are governed by Stripe's own privacy information. Baymity can explain the platform status it received and help route a review request, but cannot override a decision reserved to Stripe, an issuer, or a payment network.

Relevant on-screen guidance can depend on your selected Guest/Supplier view, existing account setup, or whether you already offer a space. The invitation to become a Supplier is displayed in the app; using the app does not opt you into an email marketing list.

Baymity’s legitimate interests include operating a trustworthy marketplace, preventing duplicate or fraudulent bookings, protecting users and property, securing accounts and payments, resolving complaints, improving reliability, exercising or defending legal claims, and communicating about the service. Baymity balances these interests against user rights and uses proportionate access, minimisation, retention, and review controls.

You may object at any time to processing based on Art. 6(1)(f) GDPR for reasons arising from your particular situation. Baymity will stop unless compelling legitimate grounds or legal claims justify continued processing. You may object to direct marketing at any time without giving reasons.

Baymity uses risk-appropriate technical and organisational safeguards, including encrypted transport, authentication, access controls, row-level database policies, restricted service credentials, payment-provider separation, event logging, and incident handling. Raw tax, VAT, operator-tax, and optional financial-account identifiers are additionally protected with application-level authenticated encryption and are masked in ordinary account and dashboard views. No internet service can guarantee absolute security. Contact Baymity promptly if you suspect account, access-code, payment, or personal-data misuse.

11.1 Backups, recovery and deletion

Recovery copies are encrypted and available only to authorised operators for security recovery and restricted restore checks. The archive-decryption key is held separately from the cloud backup storage. Backups are not used for marketing, ordinary account access or rebuilding a deleted user's profile. GitHub is used to version and test backup source code; this backup workflow does not send production dumps or recovery credentials to GitHub.

These periods run from the snapshot's creation, not from the date of your deletion request. A snapshot taken before eligible data was erased from active systems can retain the earlier data until that copy expires. New snapshots reflect the active data after erasure, including only any records that must still be retained on a separate legal basis. Submitting a request is not confirmation that its review and active-system erasure have finished; we explain the outcome and any justified retained categories.

Independent backup storage is versioned: scheduled expiry makes the old copy a previous version, and permanent deletion follows the additional one-day rule. Storage-provider date rounding and asynchronous cleanup mean physical deletion can take longer than the scheduled 30 or 56 days plus that version-cleanup day; these are not exact-hour deletion guarantees. Independent copies also have seven days of additional protection against early deletion or overwriting from their creation. That period does not restart when you request deletion. Recovery copies must not be kept indefinitely or have their lifetime routinely extended.

Decrypted working files and temporary restore projects are removed after the recovery check or task. Any downloaded encrypted copy must follow the original snapshot's retention period and be removed when no longer needed. A separate, documented legal preservation duty concerns only the necessary records and purpose; it does not justify retaining every ordinary recovery snapshot indefinitely.

Before a restored environment returns to ordinary use, completed erasure requests and processing restrictions must be reconciled against the current request record and reapplied. The restored environment remains isolated while this is checked. Keeping an earlier encrypted snapshot does not waive your deletion or objection rights or permit ordinary reuse of data that is no longer lawful to process.

Subject to the GDPR’s conditions and exceptions, you have the following rights:

• Access to your personal data
• Correction of inaccurate or incomplete data
• Deletion where no overriding duty or legal ground requires retention
• Restriction of processing
• Data portability where the statutory conditions apply
• Objection to processing based on legitimate interests
• Withdrawal of consent at any time for future processing
• A complaint to a competent data protection authority

Send a request to hello@baymity.com. You can also open Profile details and use Delete account and personal data to submit, follow, or cancel an erasure request before processing. An account-free Guest can contact Baymity by email without creating an account. Baymity responds without undue delay and within one month of receiving your request. Where necessary because of the complexity or number of requests, this period may be extended by up to two further months; Baymity will inform you of the extension and its reasons within the first month. Baymity may request proportionate information to verify identity. You also have the right to complain to the authority responsible for Baymity, currently the State Commissioner for Data Protection of Lower Saxony, or to the supervisory authority where you live or work.

Active-system erasure and backup expiry are different steps. Section 11.1 explains why earlier recovery copies may remain for their scheduled period and the checks required before any restore. Necessary deletion-audit and legally retained transaction records have their own limited purposes and retention rules; pseudonymised records can still be personal data. You can ask us which categories remain and why.

For processing for which Stripe is an independent controller, you may also exercise rights directly through Stripe. Baymity will reasonably assist in identifying the correct recipient for a request concerning a Baymity booking.

Baymity accounts are for adults aged 18 or older. Baymity does not knowingly offer accounts to children. Contact Baymity if you believe a child has supplied account data.

Baymity will update this Policy when processing, providers, retention, or law changes. Material changes will be communicated in an appropriate form. Where a new purpose requires consent, it will not begin merely because this Policy changed; Baymity will request that consent separately.