This notice describes what the Mekano app and its servers do with personal data, and says nothing they do not do. Reading it is not consent, and nothing here depends on your consent unless it says so.
1. Who is responsible
Mekano is operated by Adventa Tech AB (org. no. 559595-0535, Blåbärsvägen 9 C, 806 35 Gävle, Sweden). Contact for everything in this notice: info@zyntravision.com.
2. Our role and the workshops' role
- Adventa Tech AB is an independent controller for the data of the Mekano platform: accounts and sign-in, bookings, payments, messages in the app, reviews, complaints, and the checks we make of workshops and mechanics.
- Each workshop or mechanic you book is a separate business and an independent controller for the customer records it keeps for its own work (for example its job notes, invoices and warranty records).
- Where we produce something in the workshop's name and on its behalf, such as the receipt for your repair, we act as the workshop's processor under a data processing section in our agreement with the workshop.
3. What we process, why, and on what legal basis
Account and sign-in. Your name, email address, phone number and language, and how you sign in: an email code, Apple, Google, a passkey, or BankID through Idura where BankID sign-in is enabled. Why: to give you an account and keep it secure, and so that the workshop of your booking can call you about it. Legal basis: contract (GDPR art. 6.1 b); account security: legitimate interest (6.1 f).
BankID. When you use BankID, Idura passes us your personal identity number (personnummer) and your name as BankID gives them. We do not store your personal identity number. We keep a keyed fingerprint of it (a one-way code that lets us recognise the same person again) and, for a mechanic's identity check, the last four digits and the name. The last four digits of a BankID sign-in are kept for at most 15 minutes, so that a mechanic's identity check can use that sign-in, and are then cleared. Legal basis: contract (6.1 b); for workshops, also legal obligation (6.1 c, below).
Your vehicles. Registration number, make, model, year, colour and fuel type that you enter. Why: to book the right service for your car. Legal basis: contract (6.1 b).
Bookings and the place of the service. The service, the time, the price, the address and its position on the map. If you use "use my location" to search, the position is used for that search and is not stored. Why: to make and carry out the booking and send the mechanic to the right place. Legal basis: contract (6.1 b).
Payments. Card and Klarna payments are handled by Stripe. We receive references, amounts and the payment's status, never your full card number. When you choose Klarna, we pass your email address to Klarna through Stripe so the payment can be made. Why: to take the payment and to refund it. Legal basis: contract (6.1 b); bookkeeping: legal obligation (6.1 c).
Messages, extras, complaints and reviews. The messages between you and the workshop, extra work you approve or decline, complaints and the photos and files you add, and reviews. A review is shown with your first name and your comment to other signed-in users. Why: to carry out and document the service, handle complaints and disputes, and help customers choose. Legal basis: contract (6.1 b); legal claims and reviews: legitimate interest (6.1 f).
Photos of the work. Photos a mechanic takes of the job. Why: to document the work for both of you. Legal basis: contract (6.1 b); legitimate interest (6.1 f).
The mechanic's position on the way to you. Only while the mechanic is on the way to your booking ("en route"), also when the app is in the background on the mechanic's phone. Only the latest position is kept; there is no history of where a mechanic has been. It is deleted when the mechanic arrives, completes the job or pauses sharing. Why: to show you when the mechanic arrives. Legal basis: contract (6.1 b); for the mechanic: legitimate interest (6.1 f).
Notifications. Your phone's push-notification token and the notifications we send you. A notification on the lock screen never shows an amount, a name, an address, a phone number or an identity number. Why: to tell you about your bookings. Legal basis: contract (6.1 b).
Workshops and mechanics. The identity check of the person who represents the workshop (Stripe Identity, below; BankID through Idura only where it is switched on); your company's organisation number, legal name, legal form, addresses (for a sole trader often the home address), VAT number, F-skatt and VAT status; the certificates and the liability insurance proof you upload; your application documents; your working hours, service area and offers; and the data the platform must report about sellers (DAC7). For a sole trader (enskild firma) the organisation number is the owner's personal identity number, and we say so openly: it is the company's identifier. It appears in full only where the law requires it — in the receipt records kept in the workshop's name, on Mekano's commission invoice to the workshop and in the DAC7 report to the Swedish Tax Agency. Everywhere else it is shown masked, as ••••1234, and customers never see it in full. To check that an application has not changed we use a keyed code (HMAC) of the number, never the number itself. Why: to verify who the seller is, list the workshop, pay it and report as the law requires. Legal basis: contract (6.1 b); legal obligation (6.1 c); preventing fraud: legitimate interest (6.1 f).
Identity check of a workshop's representative (Stripe Identity). Before a workshop can receive bookings, the person who represents it verifies their identity with Stripe Identity in the app: they photograph an ID document (driving licence, national ID card or passport) and take a live selfie, and Stripe checks the document and that the selfie matches its photo. Stripe captures and checks the document and the selfie. Stripe keeps the images in Mekano's Stripe account on our behalf, as our processor; our administrators can view them there to review the check. We do not copy the images, the document number, the date of birth or the address to our own systems. In our own systems we keep only the result: the status of the check, the verified first and last name, the type of document and the country that issued it, and, if the check fails, Stripe's reason code. An administrator then reviews the result before the workshop is approved. Comparing the selfie with the photo in the document is processing of biometric data; Stripe does it for this check, with the person's explicit consent given in Stripe's own flow before the biometric comparison (GDPR art. 9.2 a). Stripe is also an independent controller for its own processing of this data, under Stripe's own privacy notice. BankID through Idura is used for this check only where it is switched on. Why: to verify the workshop's representative. Legal basis: contract (6.1 b); legal obligation (6.1 c).
Payouts to workshops. When a workshop sets up payouts, the personal identity number, date of birth, home address, bank account and the photos of the ID document go straight to Stripe. Mekano never stores the ID document photos or these details; we keep only that they were sent, the last four digits of the bank account and the Stripe account reference. For the DAC7 reporting we read back from Stripe the account holder's name, the bank's name and country and the last four digits. When you accept Stripe's terms, your IP address and device information go to Stripe as Stripe requires. As a record of the acceptance we keep only the time and a keyed code (HMAC) of the IP address, from which the address cannot be read back; we do not keep the device information. Legal basis: contract (6.1 b); legal obligation (6.1 c).
Bookkeeping. Receipts, invoices, payouts and vouchers. Why: accounting. Legal basis: legal obligation (6.1 c), bokföringslagen.
What you accepted. Which version of the terms and of this notice you accepted, the statements you confirm at checkout (including a request that the work starts within the withdrawal period), with the time, language and app version; and a withdrawal from a booking that you send us, with the email address its acknowledgement goes to. Why: to show what was agreed. Legal basis: legal obligation (6.1 c); legitimate interest (6.1 f).
Security records. What was done in an account and when, a hashed IP address, and error and payment-failure records. Why: security, preventing fraud and misuse, finding faults. Legal basis: legitimate interest (6.1 f).
We do not use your data for advertising, we do not sell it, and the app contains no advertising, analytics or crash-reporting tools. The app's fonts are built into the app; it does not download fonts from Google or anyone else.
4. Who receives it
- The workshop or mechanic you book: what it needs for the booking — your name, your mobile number, the service, the time, the address and its position, the vehicle and your messages with it. The workshop sees your mobile number only for a booking you have made, from when it accepts the booking until the booking is completed or cancelled, so that it can call you about the visit.
- Customers see a workshop's business name, organisation number (never a sole trader's), address, phone number and email, its rating and reviews, and how far away it is — never the position of its base.
- Service providers that process data for us: Stripe (payments, refunds and payouts to workshops); Stripe Identity (the identity check of a workshop's representative: the ID document and the live selfie, kept in Mekano's Stripe account on our behalf, section 3; Stripe is also an independent controller for its own processing); Idura (BankID identification, in the EU — Denmark), only where BankID is switched on; BolagsAPI (company lookup for limited companies, in Sweden, using the organisation number; never a sole trader's); the EU's VIES service (checking a VAT number, where that check is switched on); Supabase (our database and private file storage, in Ireland — EU); Render (application hosting, in Frankfurt, Germany — EU); ZeptoMail by Zoho (sending email, in the EU/EEA, or outside the EEA under EU standard contractual clauses); Google Firebase Cloud Messaging and Apple (push notifications: your device token and the notification text); Fortnox (bookkeeping: amounts and references; where a voucher names the workshop's organisation number, for a sole trader that is the owner's personal identity number); Google Maps SDK (the maps in the app: Google receives your device's IP address and the map areas shown); Cloudflare (every request to our servers passes through Cloudflare's network in front of our hosting provider Render, and Cloudflare hosts the administrators' site: it handles your device's IP address).
- Apple and Google sign-in: when you choose to sign in with them, they are controllers for their own sign-in service.
- Klarna, when you choose to pay with Klarna: Klarna is a separate controller for its own processing (for example its credit assessment and its payment terms) under its own privacy notice; we pass on what the payment needs through Stripe.
- Authorities, when the law requires it — for example the Swedish Tax Agency (Skatteverket) for the platform reporting of sellers (DAC7) and for bookkeeping.
5. Transfers outside the EU/EEA
Our database and file storage (Supabase, Ireland) and our application (Render, Frankfurt) are hosted in the EU; Idura (Denmark) and BolagsAPI (Sweden) process data in the EU. ZeptoMail sends our email from the EU/EEA, or from outside the EEA under the European Commission's standard contractual clauses. Some providers (Stripe, Apple, Google — including Firebase Cloud Messaging and Google Maps — and Cloudflare) may process data outside the EU/EEA, for example in the USA. Where they do, the transfer relies on the EU–US Data Privacy Framework or on the European Commission's standard contractual clauses.
6. How long we keep it
- Signed-in sessions: deleted 30 days after they end (expired or signed out).
- Repeat-request records (technical records that stop a payment or booking from being made twice; they can contain our reply to your request): deleted after 24 hours, or after 30 days if the request never finished.
- BankID sign-in attempts: deleted 30 days after the attempt; the deletion runs the next time anyone starts a BankID sign-in. The last four digits of a sign-in are cleared after 15 minutes by a regular clean-up.
- The mechanic's position: only the latest, deleted when the mechanic arrives, completes the job or pauses sharing.
- File uploads that were never finished: deleted after 30 minutes.
- Messages in the app: deleted 12 months after the booking they belong to ended.
- Reviews: kept while your account is open. When your account is deleted the review stays, shown as written by "Former customer", without your name.
- Verification records of workshops and mechanics (the identity check — the Stripe Identity result, or BankID where it is switched on — and the company, F-skatt and VAT checks): kept while the account is open and deleted 1 year after it is closed, unless the bookkeeping or the DAC7 rules require them for longer.
- The ID document images and the selfie of the identity check: kept by Stripe in Mekano's Stripe account. We ask Stripe to delete them when we delete the verification records (above), and, for an earlier check that failed or was replaced, 30 days after a newer check was approved. Stripe's deletion can take up to four days.
- Application documents of workshops and mechanics: kept while the account is open and after it is closed, as proof of what was checked; no deletion period has been set for them. You can ask us to erase them (section 8).
- Certificates and insurance proofs of workshops and mechanics (the file uploaded and the security-checked copy we make of it): deleted 1 year after the account is closed, and 1 year after the certificate is rejected or replaced by a newer approved one. The certificate that currently qualifies an open workshop is kept. Nothing is deleted while a complaint or a payment dispute about the workshop's bookings is open. What was checked and when (the certificate's number, issuer and dates) is kept.
- Bookkeeping records (bookings, payments, refunds, payouts, receipts and invoices): kept until the end of the seventh year after the end of the financial year they belong to, as bokföringslagen requires, with as little personal data as possible. What the DAC7 rules require about a seller is kept as long as those rules require.
- Records of what you accepted and of payment and accounting actions: kept as evidence; not deleted.
- Photos of the work: deleted 3 years (1,095 days) after the job ended, never while a complaint or dispute about it is open.
- Security records: kept to protect accounts and to investigate misuse; no deletion period has been set for them.
- Notifications, complaints and their files, sign-in codes, and reports under the Digital Services Act: kept; no deletion period has been set for them. You can ask us to erase them (section 8).
- When you delete your account, section 7 applies.
7. When you delete your account
When you delete your account in the app, it is closed at once: you are signed out on every device and Mekano stops sending notifications to your phones. For 30 days you can undo this by signing in again.
After those 30 days we delete or anonymise your personal data: your name, phone number and email address, your vehicles, the addresses of your bookings, your phones' notification tokens, your passkeys, your sign-in links (email, Apple, Google and BankID) and your sessions, and your Sign in with Apple consent is revoked. During the 30 days we keep of your email address only a keyed, non-reversible marker (a code from which the address cannot be read back), so that signing in with a code sent to that address can reopen the account; after the 30 days the marker is deleted too. Your reviews stay, shown as written by "Former customer". Messages are deleted 12 months after the booking ended (section 6).
What we keep, and why: your bookings, payments, refunds, receipts and invoices, because bokföringslagen requires it, until the end of the seventh year after the financial year they belong to, with as little personal data as possible. For a workshop or mechanic the same applies; in addition, what the DAC7 rules require about a seller is kept as long as they require, and identity and verification records are deleted 1 year after the account is closed unless those rules need them for longer; the files of its certificates and insurance proofs are deleted 1 year after the account is closed (section 6). A workshop's payout account stays with Stripe under Stripe's own terms.
8. Your rights
You have the right to access your data, to have it corrected, to have it erased, to restrict its processing, to object to processing based on legitimate interest, and to receive your data in a format you can move to someone else (portability).
- Access and portability: in the app, Profile → Settings → Privacy policy → "Download my data" gives you one file (JSON) with the data we hold about you. Your personal identity number is shown masked in it. Not in the file today: photos of the work, complaint files, application documents, reports under the Digital Services Act, refunds and payment disputes, the payout account holder's name, additional tax identification numbers and the business details prefilled for Stripe; ask us for them.
- Correction: change your details in the app, or write to us.
- Erasure: Profile → Settings → "Request account deletion" (section 7 says what it does). The app confirms it with a code sent to your verified email address; if your account has none, write to us. Write to us to erase more.
- Restriction and objection: write to info@zyntravision.com.
You can complain to the Swedish Authority for Privacy Protection (Integritetsskyddsmyndigheten, IMY), www.imy.se.
9. Changes
When this notice changes, its version changes and the app asks you to read the new one.
Version 2026-10-4 · Adventa Tech AB · 559595-0535