A. English Privacy Policy

1. Controller and contact

Vedle s.r.o., IČO 24572314, Nové sady 988/2, 602 00 Brno, Czech Republic, is the controller for the VedleGo platform's own account, marketplace and support processing. Privacy requests and legal notices: podpora@vedlego.cz. A Provider may act as an independent controller for personal data received to perform the Service.

2. Who and what data

At Provider registration, the in-app application asks for the business name, IČO, a short description, the services offered and the hourly rate; the Provider's name, e-mail address and phone number come from their user account. The application has no address or service-location field and may include an optional profile photo; the Provider's registered office is taken by VedleGo from the public ARES register at approval (section 5). If VedleGo is a reporting platform operator under the DAC7 rules (Act No. 164/2013 Coll.), Providers who receive payments will also be asked once for their date of birth and tax identification number (DIČ), which are then reported once a year to the Czech tax administration as a legal obligation; Providers are informed before any such collection starts. A residential address is not published by VedleGo by default; information independently available in public registers may remain public. For Customers and platform use, we process necessary identification/contact information (the phone number is optional; sign-in is by e-mail and password or Google sign-in, and on iPhone also by Sign in with Apple — a user who hides their e-mail address with Apple is known to VedleGo only by Apple's relay address), provider profiles and authorizations, services, prices, availability, bookings, the service location each Provider advertises (shown on the map), job addresses and any map coordinates, which the Provider to whom the booking request is sent can access from the request stage, before accepting it (the Provider does not see the Customer's phone number), support correspondence, ratings and permitted photos, transaction records, a push-notification device token, security logs, error and crash reports from the app (section 6), and, on the website, cookie choices. The app has no in-app messaging. Booking e-mails: for each confirmation stage of a booking (request received, booking confirmed, payment could not be completed, card hold released) VedleGo keeps in its own database an outbox record with a copy of the recipient's e-mail address and of the message as sent (subject and text), the booking details the message was built from (service, the Provider's business name, date, time, duration, address, amounts and, where recorded, the times of the early-performance statements), the version and hash of the Terms attached to a confirmation, and the e-mail service's message identifier. VedleGo keeps the accounting document it issues for its platform fee and the payment records from Stripe; the document for the service itself is issued by the Provider. Stripe may collect additional regulated identity/payment information directly under its own onboarding process; Card payments, including Apple Pay on iPhone, are processed by Stripe; VedleGo does not collect full payment card numbers. Search text typed in the app is processed on the device and is not sent to VedleGo's servers or third parties; external AI processing of search queries is switched off.

Contract and pre-contract steps (GDPR Art. 6(1)(b)): accounts, bookings, notifications, support of performance and related payment processing where the data subject is party to the contract. Legal obligations (Art. 6(1)(c)): tax/accounting records, platform trader traceability, lawful official requests and relevant reporting such as DAC7 where applicable. Legitimate interests (Art. 6(1)(f)): fraud detection, IT security, error and crash reports that keep the app working, enforcing platform rules, proportional incident handling and genuine booking reviews, subject to balancing and objection rights. Consent (Art. 6(1)(a)) where required for optional cookies, direct marketing or optional precise-device-location uses. Some business contact-person information relies on legitimate interests rather than an individual contract. Location in particular: the service address and its map coordinates are processed to perform the booking contract; a Customer's optional use of the device location ("use my location", Providers nearby) relies on consent, given through the operating system's permission after the app explains the purpose, withdrawable at any time in the device settings — the address can always be typed instead; a Provider's position when going online and at the arrival check relies on VedleGo's legitimate interest in confirming that the booked service is performed at the agreed place.

4. Location and device access

Precise device location is used only while the app is in use (foreground), never in the background, and only at these moments: Customers when choosing "use my location" for the booking address and when viewing nearby Providers; Providers when going online (a one-off position snapshot kept while online) and when verifying arrival at a job (if the booking has coordinates, the arrival distance and position are stored). What the app displays: the app does not display a Provider's position to the Customer — it shows the job status and, on the map, the service location the Provider advertises. Backend access: the Provider's stored position (the snapshot taken when going online) can be released only to that booking's Customer, only while the booking is on the way, arrived or in progress, and only for an active account; the current app does not display it. The Provider to whom the Customer sends the booking request can access its service address and any map coordinates from the request stage, before accepting it. Booking location: the map coordinates of the service address are stored with the booking. They come either from the address the Customer types — the phone's address-lookup service turns it into coordinates (on iPhone Apple's, on Android the device's geocoding service; the typed address is sent to that service, so it is not processed only on the device), and coordinates are stored only when the exact building is found — or, when the Customer chooses "use my location", from the device's position at that moment. They are used to show the address on a map in the app and to verify the Provider's arrival at the job; without stored coordinates, arrival is confirmed with the Customer's PIN. The Customer, the Provider to whom the booking request is sent (from the request stage, before accepting it) and authorised VedleGo administrators can see them. They are kept with the booking and removed when a deletion of the account is processed under section 8; for a booking still open at that time, they are removed once it is settled and the deletion is processed again. Device permissions do not replace a valid GDPR basis. The arrival position stays with the job while the account exists and is cleared when the account is deleted (section 8).

5. Verification and criminal history

No documents are uploaded to the VedleGo app as part of initial Provider registration. Each application is reviewed manually before approval. At approval VedleGo looks up the IČO in the public business register ARES: an IČO that cannot be found there, or that belongs to a dissolved business, is not approved, and the registered office recorded in ARES is stored with the date of the lookup; a business name that differs from the register is shown to the reviewer. VedleGo performs no further checks unless it requests documents where a specific service requires them. Identity documents and criminal-record extracts are examined where legally justified but are not copied, uploaded to VedleGo or retained. VedleGo keeps only necessary professional certificates, IČO/business-authorization confirmations (where actually collected), and proportionate verification records. VedleGo does not record or keep information on criminal convictions. Stripe's separate legally required KYC process may request documents directly from Providers.

6. Recipients and processors

Processors: Supabase Pte. Ltd. (Singapore; database, sign-in and file storage, stored in Supabase's EU region in Ireland), Stripe Payments Europe Ltd. (Ireland; payments and payouts — for its own legal obligations, such as verifying Providers' identity (Providers accept Stripe's own terms for their Stripe account), preventing fraud and complying with financial regulation, Stripe acts as an independent controller under its own privacy policy), Google LLC (USA; push notifications through Firebase Cloud Messaging), Plus Five Five, Inc., trading as Resend (USA; transactional e-mail), Vercel Inc. (USA; website hosting), GoDaddy.com, LLC (USA; domain, DNS and the podpora@vedlego.cz mailbox), Cloudflare, Inc. (USA; Turnstile, a bot check on the website's provider sign-up form, which processes technical data about the browser and the connection — the IP address, browser and connection signals; Cloudflare also uses these signals as an independent controller to improve Turnstile) and Functional Software, Inc. (USA; Sentry, error and crash reports). Google Maps (map display; Google Maps Platform, contracted with Google Cloud EMEA Ltd., Ireland) and Google Sign-In (Google Ireland Ltd.) are provided by Google as an independent controller under Google's own terms and privacy policy. On Android, the address a Customer types is converted into map coordinates by the device's geocoding service (section 4). Crash reports are stored in Sentry's EU data region (Germany). They contain the error type, the stack trace, the error text (for errors in the app's own code with e-mail addresses, numbers, identifiers and quoted text removed), the app version and technical facts about the device (model, operating system and, for crashes of the phone's system layer, details such as memory, language and time zone), and a random installation identifier created by the crash-reporting library; on iPhone they also contain a one-way hash derived from the device and the app, which is the same in every report from VedleGo on that iPhone; no account identifier, screenshots or screen recordings are ever attached. The filter removes e-mail addresses, numbers, identifiers and quoted text from the error text of the app's own code, but it cannot recognise every personal detail written as free text, and it does not apply to crashes of the phone's system layer, whose error text is produced by the operating system's crash library; such a report could therefore, in rare cases, contain a fragment of text that was on the screen or in the app's memory at the moment of the crash. We do not use crash reports for any purpose other than finding and fixing errors. Sentry is set not to store the sender's IP address, and the approximate location it derives from that address is removed when a report arrives. On iPhone, Apple Distribution International (Ireland) provides Sign in with Apple and Apple Pay: Apple processes the user's Apple Account and Apple Pay data under its own terms and passes VedleGo only the sign-in identity (the name and the e-mail or relay address the user chooses to share) and Stripe only the payment token. On iPhone, the address a Customer types for a booking is also sent to Apple's address-lookup service, which turns it into map coordinates (section 4); Apple Distribution International Ltd. (Ireland) provides this lookup under Apple's own privacy policy as an independent controller, and the data may be processed in the USA (section 7). Recipients: the Provider to whom the booking request is sent can access its service address, notes and any map coordinates from the request stage, before accepting it, and the accepting Provider sees the Customer's name; in the app the Customer sees the Provider's name, rating and the job status. In the booking confirmation e-mail the Customer also receives the Provider's business name, IČO, registered address (taken from ARES at approval) and the contact details recorded in the Provider's account (e-mail address and, where given, telephone number), as the supplier's identification required by consumer law and as the addressee for a withdrawal. Data may also be shared as necessary with professional lawyers/accountants, insurers where involved, and competent authorities where lawful. We do not sell personal data.

7. International transfers

Supabase Pte. Ltd. (Singapore) receives data under the European Commission's standard contractual clauses; the data is stored in the EU (Ireland), and Supabase's support staff and sub-processors, including Supabase, Inc. in the USA, may access it from outside the EEA under the same clauses. Transfers to the USA: Stripe (Stripe, LLC), Google (Google LLC), Vercel Inc., GoDaddy, Cloudflare, Inc. and Sentry (Functional Software, Inc.) are certified under the EU-US Data Privacy Framework, with the standard contractual clauses as fallback where their terms provide them; Resend (Plus Five Five, Inc.) and Apple rely on the standard contractual clauses. Resend sends e-mails from its EU region (Ireland) but keeps account data and delivery logs in the USA. Sentry keeps crash reports in its EU data region; its US parent relies on the EU-US Data Privacy Framework, with the standard contractual clauses as fallback (Sentry data-processing addendum 5.1.0, Schedule 3). No search queries are sent to an external AI provider (that feature is switched off).

8. Retention

We retain personal data only for necessary purposes and applicable legal periods. While an account exists, its account data and its booking, payment, photo, dispute and arrival records are kept; no record is yet deleted automatically because of its age. When an account is deleted, the following are removed when the request is processed: the notes and map coordinates of its bookings (of a booking still open at that time, once it is settled and the deletion is processed again), the Provider's notes and arrival position on finished jobs, the reviews it wrote and its uploaded photos (photos of an unsettled booking or an open dispute are removed once it is settled); the service address is replaced on bookings that were never paid and kept on paid bookings; a Provider's business name, IČO, address and profile are cleared. The remaining records are kept without the user's name and contact details but stay linkable — they are not anonymous — until one retention date recorded for the deletion request: 10 years after the request is processed if any booking of the account was paid, otherwise 3 years after it. Deleting them after that date is a manual step. The app keeps on the device a per-account booking summary without the address, coordinates or notes; entries older than 30 days are deleted and the cache is cleared at sign-out. The push-notification token is cleared from the account when the user signs out of the app. Booking e-mail outbox records follow the retention of the booking they belong to. When an account is deleted, the copy of the recipient's address and of the message text is cleared from the records of messages already sent or closed, and from a message still being sent as soon as it is finished; the service address and the Provider's business name are removed from the record when the booking or the Provider is scrubbed. The cached copy of the Terms document attached to confirmations contains no personal data. Resend, which delivers the messages as VedleGo's processor, keeps its own copy of the address and message content; its data-processing terms set no fixed period for these message records. When handling a deletion request, VedleGo asks Resend in writing to erase the messages sent to that address and records the date of that request with the deletion request; under those terms VedleGo is responsible for passing erasure requests to Resend, Resend deletes data on VedleGo's instruction, and it deletes the data held for VedleGo within 90 days after VedleGo's Resend account ends. Sentry deletes crash reports automatically after at most 90 days. Only necessary professional certificates, business authorization/IČO confirmations actually collected, and minimal lawful verification records are retained for justified periods; the registered office taken from ARES is kept with the Provider's record and cleared when the Provider's account is deleted. No identity-document copies or criminal-record extracts are retained by VedleGo.

9. Rights

Eligible individuals may request access, correction, erasure, restriction, portability, object to legitimate-interest processing, and withdraw consent without affecting prior lawful processing. Requests: podpora@vedlego.cz. Account deletion: in the app (Profile → Delete account) or through VedleGo's web deletion page; the account is closed immediately and erasure is completed within 30 days of receipt, except data VedleGo must keep by law or because of an open booking, payout or dispute, which are kept as described in section 8; completion is confirmed by e-mail. Individuals may complain to the Czech supervisory authority, Úřad pro ochranu osobních údajů (www.uoou.gov.cz), and seek judicial protection. Rights are subject to statutory exceptions and identity verification.

10. Cookies and marketing

Necessary cookies/technical storage support core functionality. Optional preference, analytics and marketing tools require transparent categories, appropriate consent or another legally valid basis and an effective choice mechanism. On the website, the only optional tool is Google Analytics 4 (traffic measurement; Google Ireland Ltd.). It is loaded only after the visitor chooses 'Accept all' in the banner — not before a choice and not after 'Reject'. The banner gives both buttons equal prominence and never blocks the page; the choice can be changed at any time through 'Cookie settings' at the bottom of the page. The Meta Pixel and other marketing tools are not used. Refusing optional tracking must not prevent access to essential services. The app shows no advertising and uses no advertising identifiers or cross-app tracking. Email marketing follows GDPR and applicable Czech electronic-communications rules.

11. Security and incidents

We use role-based access, encryption where appropriate, authentication, audit logs, minimization, incident procedures and verified provider/processor access. We assess personal-data breaches, notify the data-protection authority within 72 hours where required by GDPR Art. 33 and inform affected people under Art. 34 when applicable. Photo metadata (EXIF, including GPS) is stripped and images are downsized before storage. Profile photos are stored in a bucket reachable by public link; job-evidence, review and dispute photos are stored in non-public buckets. A complaint photo from inside a home is restricted evidence, not public portfolio content.

12. Automated decisions and updates

Three fixed rules decide a booking without a person reviewing each case: (1) a booking request that the Provider has not accepted lapses after 10 minutes if the job starts within 3 hours, after 30 minutes if it starts within 24 hours, and after 3 hours otherwise; the booking is cancelled and the hold on the card is released; (2) a booking whose payment is not completed within 15 minutes is cancelled and nothing is charged; (3) when the Provider marks a job as finished, the Customer has 24 hours to confirm it or report a problem in the app; if neither happens, the job is approved automatically and the Provider's earnings are released (Terms, section 8(c)). After automatic approval the report option in the app is closed; the Customer can still complain to podpora@vedlego.cz, where a person reviews the case, and the Customer's statutory rights for defective performance are not affected. These rules use only the times and the status of the booking. Search results are ordered by whether the Provider is online now, then by distance, then by the Provider's average customer rating and then by the number of reviews; no other evaluation of a person is made. If you disagree with the outcome of one of these rules, write to podpora@vedlego.cz: a person at VedleGo reviews the case, and you can explain your view. Material privacy-notice changes will be communicated appropriately; the latest date will be shown. Each published version of the Terms and the Provider Agreement is kept with its date and a fingerprint (hash) of its content, and acceptances are recorded with the version accepted.

13. Provider application on the website

When you send the provider application form on vedlego.cz, we process your name, phone number, e-mail address, the service category and area of Brno you choose, and — if you fill them in — your IČO and a note; we also record how you reached the form (for example the advertising campaign). Purpose: to contact you about joining VedleGo as a provider and about your registration in the app. Legal basis: your consent (GDPR Art. 6(1)(a)), which you can withdraw at any time by writing to podpora@vedlego.cz; withdrawal does not affect processing before it. We keep the application as long as needed for that purpose and at most until you withdraw consent. The form is protected against bots by Cloudflare Turnstile; applications are stored with Supabase and our team is notified by e-mail through Resend (section 6). Your rights are described in section 9.