Privacy policy
Last updated: November 2026 (provisional version, subject to legal validation)
Status of this document
This policy describes the processing actually in place on the date shown. It has not yet been reviewed by a lawyer: the legal bases, retention periods, the classification of several processing operations and the minimisation analysis of the date of birth and phone number are proposals “to be validated”.
The French, English and Spanish versions have the same content and grant the same rights. Provisions specific to a country appear in the national annexes (“France annex”; other countries will be added later).
Confirmed items (facts verified in the service)
The following facts match how the service currently works:
- the data controller is ETHER SOLUTIONS, reachable at the contact address given below;
- your e-mail, phone, date of birth, country and city of residence, identity and plate are never shown to other members, nor in the QR code or URL; only the pseudonym and the optional photo are visible;
- no advertising cookie or audience-measurement tool is used; the cookie choice is valid for 180 days;
- message photos are stored privately, served through temporary links and stripped of their metadata (EXIF);
- the transfer safeguards cited are only those we verified in the providers' public documents;
- exporting your data (Settings > My data) and deleting your account (Settings > Delete my account) are available;
- the optional deletion feedback is linked neither to your account nor to your e-mail address.
Items to be validated
The following points are WeGari proposals not yet legally validated; the sheets below mark them “proposed” or “to be validated”:
- the legal basis of each processing operation;
- retention periods (their automatic application is not yet enabled for all data);
- the necessity of the date of birth and phone number in light of data minimisation;
- the classification of the rules engine under Article 22 GDPR (automated decision);
- the classification of cookies and trackers (consent exemptions);
- Google-related transfers (entity and safeguards not verified) and the region of the production Supabase project (Paris planned);
- the legal basis of the profile photo and of the planned push notifications, and the rules applying to minors;
- who may view deletion feedback (today: administrators, with strong authentication).
1. Principle
WeGari lets you contact the person responsible for a vehicle through a QR code, without revealing their contact details. We collect only the data useful to the service and say, for each item, why. We do not claim that a collection is legally required when it is not: it is then requested by WeGari for the service to work. See also the terms of use.
2. Data controller
ETHER SOLUTIONS (Simplified joint-stock company (SAS), SIREN 103 015 434), 29 rue Clément Michut, 69100 Villeurbanne, France. See also the legal notice. Contact: contact@wegari.com or the Contact page.
Contact point for your personal data: contact@wegari.com. No data protection officer is appointed (appointment is not mandatory according to our analysis).
3. Data processed, purposes, legal bases, recipients and retention
For each item: what is collected, the purpose, the proposed legal basis (to be validated), the recipients, the proposed retention period (to be validated) and the justification of necessity. “Proposed” marks a point not yet validated by a lawyer.
Identity: first name and last name
- What is collected
- First name and last name entered at sign-up or in the profile (prefilled from Google if you use it, editable).
- Purpose
- Identify the account holder in case of dispute or request from the authorities. Never shown to other members.
- Proposed legal basis (to be validated)
- Legitimate interest (security, abuse prevention): proposal.
- Recipients
- You; authorised staff (administrators, with strong authentication and logged access); Supabase (hosting).
- Proposed retention period (to be validated)
- Lifetime of the account; deleted with the account.
- Necessity
- Requested by WeGari to complete the profile (a condition for adding a vehicle). No legal obligation to collect them is claimed; their necessity is to be validated.
Contact: e-mail and phone
- What is collected
- E-mail address (sign-in and notifications) and phone number (unverified, private).
- Purpose
- E-mail: create and secure the account, send the service's e-mails. Phone: have a private means of contact and limit multiple accounts; never displayed.
- Proposed legal basis (to be validated)
- E-mail: performance of the contract. Phone: legitimate interest. Proposals.
- Recipients
- You; authorised staff (the phone can only be viewed with strong authentication, logged access, and is masked elsewhere); Supabase; Resend (e-mails).
- Proposed retention period (to be validated)
- Lifetime of the account; a new number goes back to “unverified”.
- Necessity
- The e-mail is necessary for the account. The phone is not necessary for contact between members: its necessity is to be validated (internal minimisation analysis).
Sign-in credentials
- What is collected
- Password (stored in hashed form by the authentication service, never readable), session token (browser local storage), Google account identifier where applicable.
- Purpose
- Authenticate and secure your access.
- Proposed legal basis (to be validated)
- Performance of the contract: proposal.
- Recipients
- Supabase (authentication).
- Proposed retention period (to be validated)
- Lifetime of the account; the session token is deleted on sign-out or expiry.
- Necessity
- Indispensable to access an account.
Date of birth
- What is collected
- Date of birth entered in the profile.
- Purpose
- Compute your age on the server to apply the rules by country and vehicle category (driving age when you declare that you drive) and to protect minors. Never public; the date is never returned to the back office or to other members.
- Proposed legal basis (to be validated)
- Legitimate interest (apply the service's rules, protect minors): proposal.
- Recipients
- You; Supabase. Neither other members nor the back office.
- Proposed retention period (to be validated)
- Lifetime of the account; deleted with the account.
- Necessity
- Minimisation analysis, set out honestly: if the only goal were a minimum sign-up age, a simple age declaration would collect less data. WeGari keeps the date because age rules depend on the country and the vehicle category. No legal obligation to collect it is claimed. This choice remains to be validated.
Country and city of residence
- What is collected
- Country and city of residence (never the exact address). For France, the city may be suggested by the official geo.api.gouv.fr API, queried by our server: your browser does not contact it and no input is logged.
- Purpose
- Determine the applicable rules and the availability of the service by country; aggregated statistics (cities grouped below 5 members). Never in the QR code, URL or public profile.
- Proposed legal basis (to be validated)
- Performance of the contract (rules of the right country); legitimate interest (aggregated statistics): proposals.
- Recipients
- You; authorised staff (aggregated statistics only); Supabase; geo.api.gouv.fr (city search text, France only, through our server).
- Proposed retention period (to be validated)
- Lifetime of the account; the log of country changes (identifier, date, old and new countries, no city) is kept 12 months.
- Necessity
- The country is necessary to apply the rules of the right country. The city is requested to complete the profile and for aggregated statistics: its necessity is to be validated.
Registration and use countries, relationship to the vehicle
- What is collected
- Country of registration, country of habitual use (optional), category, your declared relationship to the vehicle (owner, certificate holder, driver, other), any declaration of parental consent, version of the rules applied.
- Purpose
- Apply the rules of the right country when the vehicle is added and keep a declarative record of the assessment. Never public.
- Proposed legal basis (to be validated)
- Performance of the contract; legitimate interest (evidence of the assessment): proposals.
- Recipients
- You; Supabase; authorised staff (viewing of records, logged).
- Proposed retention period (to be validated)
- Lifetime of the vehicle; deleted with the vehicle or the account.
- Necessity
- These countries are given by you and never inferred from one another or from your residence; they are necessary to apply the relevant rules.
Licence plate
- What is collected
- Plate number of a registered vehicle (car, motorcycle), stored in normalised form.
- Purpose
- Print it on the sticker you download (car and motorcycle); no plate for a bicycle or kick scooter. Never shown publicly by WeGari (scan page, URL, QR code).
- Proposed legal basis (to be validated)
- Performance of the contract: proposal.
- Recipients
- You; Supabase.
- Proposed retention period (to be validated)
- Lifetime of the vehicle; deleted with the vehicle or the account. A plate change means printing a new sticker.
- Necessity
- Necessary only for the sticker of a car or motorcycle; not requested for bicycles and kick scooters.
Pseudonym
- What is collected
- Public pseudonym of 2 to 30 characters, not unique. If you make no choice it may be initialised with your first name; you can change it at any time.
- Purpose
- Identify you to other members without revealing your identity.
- Proposed legal basis (to be validated)
- Performance of the contract: proposal.
- Recipients
- Members you exchange with; Supabase.
- Proposed retention period (to be validated)
- Lifetime of the account.
- Necessity
- Public by design; you can choose a pseudonym that does not identify you.
Profile photo (optional)
- What is collected
- Image that you choose to upload.
- Purpose
- Personalise your public profile.
- Proposed legal basis (to be validated)
- Consent (voluntary action) or contract: classification to be validated.
- Recipients
- Members you exchange with; Supabase (storage).
- Proposed retention period (to be validated)
- Until replaced or until the account is deleted.
- Necessity
- Optional: the service works the same without a photo.
Vehicles and QR codes
- What is collected
- Vehicle type, make, model, colour, private label, QR code tokens, scan count, status (active, archived).
- Purpose
- Generate the QR code and let people contact you.
- Proposed legal basis (to be validated)
- Performance of the contract: proposal.
- Recipients
- You; Supabase. A person scanning the QR code sees only the vehicle's type and public description.
- Proposed retention period (to be validated)
- Lifetime of the vehicle or the account; a revoked QR code stops working.
- Necessity
- Necessary for the QR code to work. The private label is never public.
Messages and contact reasons
- What is collected
- Message content (plain text, at most 500 characters), reason chosen among ten, dates, read status, participants and conversation status (open, ended).
- Purpose
- Allow an exchange between a user and the person responsible for a vehicle.
- Proposed legal basis (to be validated)
- Performance of the contract: proposal.
- Recipients
- The other participant; Supabase; authorised moderation staff when a report warrants it.
- Proposed retention period (to be validated)
- Ended conversation and its messages: 12 months after the last message (unless a report is still open). When an account is deleted, its messages remain visible to the other participant under “Deleted account” until that deadline.
- Necessity
- Necessary for messaging. Free text may contain data you choose to put in it: avoid unnecessary data.
Photos attached to messages (optional)
- What is collected
- One photo per message (2 MB, JPEG, PNG or WebP), re-encoded: EXIF metadata (GPS position, device) removed.
- Purpose
- Illustrate the vehicle's situation, for certain reasons only.
- Proposed legal basis (to be validated)
- Performance of the contract (optional feature): proposal.
- Recipients
- The two participants (temporary links); Supabase (private storage); authorised staff only if the conversation is reported, with strong authentication.
- Proposed retention period (to be validated)
- 90 days after the conversation ends; immediate deletion when the account is deleted; kept longer only if a report is still open (evidence).
- Necessity
- Optional. Private storage, temporary links, metadata removed.
Notifications and service e-mails
- What is collected
- In-app notifications; transactional e-mails (account confirmation, password reset, new message without revealing its content, support replies); sending queue. Push notifications are planned but not active.
- Purpose
- Inform you of a new message and of support replies. No marketing e-mail.
- Proposed legal basis (to be validated)
- Performance of the contract: proposal; the new-message notification can be turned off in your preferences.
- Recipients
- You; Resend (e-mail delivery: recipient address and content); Supabase.
- Proposed retention period (to be validated)
- Sending queue: 30 days; in-app notifications: deleted with the account (90 days after being read: proposal).
- Necessity
- Confirmation and reset e-mails are necessary for account security; message notifications can be turned off.
Contact form and support tickets
- What is collected
- Category, subject, message, account identifier and e-mail (or the e-mail entered by a visitor), ticket number (WG-…), status, replies, staff internal notes, hashed IP fingerprint and user agent (anti-spam signals).
- Purpose
- Reply to your requests (support, personal data, dispute), prove the reply to rights requests and prevent spam.
- Proposed legal basis (to be validated)
- Legitimate interest (handling requests); legal obligation for requests to exercise rights: proposals.
- Recipients
- Authorised support staff; Resend (reply e-mails); Cloudflare Turnstile (anti-spam token); Supabase.
- Proposed retention period (to be validated)
- 12 months after closure; 3 years for personal-data requests (proof of the reply); hashed IP and user agent: 30 days; tickets of a deleted account: deleted with the account.
- Necessity
- Necessary to handle a request and prove it was handled.
Reports, blocks and disputes
- What is collected
- Reports of messages or members, blocks, vehicle disputes, moderation decisions and internal notes.
- Purpose
- Prevent harassment and abuse, protect members.
- Proposed legal basis (to be validated)
- Legitimate interest (security): proposal.
- Recipients
- Authorised moderation staff; Supabase.
- Proposed retention period (to be validated)
- 3 years after closure (proposal).
- Necessity
- Necessary to handle abuse and keep evidence of it.
Audit log
- What is collected
- Staff actions and sensitive operations (identifiers, field names; never the values or message content).
- Purpose
- Traceability and security: who did what.
- Proposed legal basis (to be validated)
- Legitimate interest (security, accountability): proposal.
- Recipients
- Authorised administrators; Supabase.
- Proposed retention period (to be validated)
- 12 months; 3 years for sanctions and roles (proposals). The log is immutable: any purge requires a dedicated owner procedure.
- Necessity
- Necessary to detect and prove abusive use of access.
Rate limits (anti-abuse)
- What is collected
- Hashed fingerprints (IP address, device) tied to counters. The IP address is never stored in clear for this purpose.
- Purpose
- Limit spam and abuse.
- Proposed legal basis (to be validated)
- Legitimate interest (security): proposal.
- Recipients
- Supabase (database).
- Proposed retention period (to be validated)
- 24 hours.
- Necessity
- Necessary to protect against abuse; the IP address is not readable.
Cookie choice
- What is collected
- Your choice, its date, the versions of the policy and of the list, a random proof identifier. No IP address, no user agent, no account identifier.
- Purpose
- Remember your choice and be able to show that it was collected.
- Proposed legal basis (to be validated)
- Obligation to be able to demonstrate consent / legitimate interest: proposal; the choice cookie is exempt.
- Recipients
- Supabase.
- Proposed retention period (to be validated)
- Choice valid for 180 days in the browser; proof: 13 months (proposal); cookie configuration history: lifetime of the service (traceability, immutable).
- Necessity
- Necessary to respect and prove your choice.
Account deletion feedback (optional)
- What is collected
- Reason (closed list), free comment (500 characters), tenure bracket, language, whether you had vehicles, week of deletion, country (only if it has at least 5 members). No identifier, e-mail, pseudonym, IP or exact date.
- Purpose
- Improve the service.
- Proposed legal basis (to be validated)
- Legitimate interest (improving the service): proposal.
- Recipients
- Administrators (administrator and super administrator, with strong authentication; each viewing is logged without content); Supabase.
- Proposed retention period (to be validated)
- Comment: 90 days then erased; rows: 12 months.
- Necessity
- Optional; never conditions the deletion. The comment may contain data you enter: avoid entering any.
Data received from Google (if you use it)
- What is collected
- E-mail address (confirmed by Google), first name and last name to prefill your profile, Google account identifier. Never your contacts, files or Google passwords. No identity verification.
- Purpose
- Create your account and sign you in, at your request.
- Proposed legal basis (to be validated)
- Performance of the contract (sign-in you requested): proposal.
- Recipients
- Google (authentication); Supabase.
- Proposed retention period (to be validated)
- Same as the account.
- Necessity
- Only if you choose “Continue with Google”.
These legal bases and retention periods are proposals; they will be confirmed or corrected after legal validation.
4. Processors, recipients and transfers
- Supabase (Supabase Pte. Ltd., 65 Chulia Street #38-02/03, OCBC Centre, Singapore 049513): database, authentication and storage; data hosted in the European Union (AWS Paris region). According to Supabase's privacy policy, transfers to the United States and Singapore rely on the European Commission's standard contractual clauses.
- Application host: Vercel Inc., 440 N Barranca Avenue #4133, Covina, CA 91723, United States (vercel.com). Vercel states that it adheres to the EU-US Data Privacy Framework and provides standard contractual clauses in its data processing agreement.
- Resend (Plus Five Five, Inc., 2261 Market Street #5039, San Francisco, CA 94114, United States): sends transactional e-mails; receives the recipient address and the e-mail content. Resend states that it relies on standard contractual clauses and adheres to the Data Privacy Framework.
- Cloudflare Turnstile (Cloudflare, Inc., 101 Townsend Street, San Francisco, CA 94107, United States): anti-bot only (no hosting); receives the technical information needed for verification. Cloudflare states that it adheres to the Data Privacy Framework.
- Google, only if you choose “Continue with Google”: Google authenticates your account. The safeguards applying to Google-related transfers have not been verified here: to be validated.
- geo.api.gouv.fr (French public service): city suggestions for France; called by our server with the search text only, without logging.
We do not sell your data. Other members only see your pseudonym, your photo if any and, from a QR code, the vehicle's type and public description.
The transfer safeguards stated are only those verified in the providers' public documents (consulted on 14 November 2026); no other safeguard is claimed.
5. Retention periods
The periods for each item appear in the sheets above; they are proposals to be validated. To date, their automatic application is not yet enabled for all data: in the meantime your data is deleted when you delete your account or on request.
Providers' technical logs (IP addresses, requests): 30 days at most are targeted (provider settings to be checked).
6. Your rights
You have the rights of access, rectification, erasure, restriction, objection and portability. You can export your data (JSON) in Settings > My data, edit your profile and delete your account in Settings > Delete my account. The export does not contain other people's messages or internal moderation notes (protection of third parties).
For any other request, write to contact@wegari.com or use the Contact page (category “My data”). You may object to processing based on legitimate interest, and withdraw consent at any time for processing based on consent.
To protect your account we may ask you to confirm your identity before acting: a reply from the account's e-mail address, or a request made while signed in. We do not ask for an identity document unless justified. We reply within one month (the period set by the GDPR).
You may lodge a complaint with the supervisory authority of your country of residence (in France: the CNIL, see the France annex).
7. Account deletion
In Settings > Delete my account: deletion is carried out end to end. What is deleted, anonymised or kept:
- deleted: vehicles, QR codes, blocks, profile photo, message photos (files included), profile and identity (first name, last name, phone, birth, country, city), roles, support tickets, disputes, notifications, push subscriptions and sending queue;
- anonymised: your messages remain visible to the other participant under "Deleted account" (the other participant's legitimate interest in keeping the history: proposal), until their purge planned 12 months after the conversation closes (this automatic purge is not yet scheduled);
- kept: reports (3 years, proposal) and the audit log (immutable; no personal content in its details);
- stored with no link to you: the optional reason and comment given at deletion, if you entered any.
8. Automated decisions
When you add a vehicle, a rules engine automatically assesses, on the server and without human intervention, the applicable conditions from information you declare: category, countries of residence, registration and use, relationship with the vehicle, age calculated from the birth date and, where applicable, declaration of the legal representative's consent. Possible outcomes: addition possible, addition with conditions to know, parental consent to declare, further information needed, or refusal (country not enabled, enabled driving rule not met). These checks concern declarations: they do not certify your identity, your licence or your insurance.
The rules and their source are displayed. You can ask for an explanation of the outcome, give your views, ask for review by a person and challenge the outcome through the Contact page (category "My vehicle"); the detailed procedure is to be defined. This assessment only concerns adding a vehicle and does not affect your account or your messages. No profiling for commercial purposes is carried out.
Analysis (to be validated): the assessment is fully automated but, in our interpretation, it produces neither a legal effect nor a similarly significant effect within the meaning of Article 22 GDPR (it only concerns adding a vehicle to a free service, leaves the account intact and can be corrected by an accurate declaration or a review). This qualification has not been validated by a lawyer; as a precaution, the safeguards of Article 22(3) (human intervention, expressing your view, challenge) are offered in all cases.
9. Minors
No general minimum registration age is set or technically checked at this stage (point to be validated); the rules of the country concerned apply. The birth date is used to calculate age in order to apply rules by country and vehicle category; it is never public.
A minor can exercise their rights themselves. The legal representative can write through the Contact page about any request concerning a minor's account, including its deletion; we reply within one month (Article 12 GDPR), asking for the minimum needed to find the account and no identity document by default (see section 3 of the terms of use).
Optional processing based on consent (profile photo, planned but inactive push notifications) depends on the age of consent set by each country (Article 8 GDPR; 15 in France). No technical age check is applied to date for this processing and a legal representative's declaration is never verified: point to be validated.
10. Sign-in with Google
If you use “Continue with Google”, we receive your e-mail address (confirmed by Google), your first name and last name (to prefill your profile) and a Google account identifier. We receive neither your contacts, nor your files, nor your Google passwords, and we do not verify your identity. Your Google name is never displayed; your public pseudonym can be changed at any time. Google-related transfers remain to be validated.
11. Cookies and local storage
See the cookie policy. In short: no advertising cookie or audience-measurement tool; the choice is valid for 180 days and can be changed at any time through “Cookie settings”; strictly necessary trackers (sign-in session, remembering the choice, security) do not require consent, and the language is placed under the “Preferences” consent as a precaution. This classification is to be validated.
12. Security
Measures actually in place and verified:
- row-level access control (RLS) on all database tables;
- passwords stored in hashed form by the authentication service;
- photos stored privately, served through temporary links, metadata removed;
- strong authentication (MFA) for staff and logged staff access;
- rate limits computed from hashed fingerprints; the IP address is not stored in clear for this purpose;
- identity data (first name, last name, phone, birth, country, city) with no direct access from the browser;
- encryption of exchanges (HTTPS);
- service secrets kept on the server side only.
We claim no certification. No measure guarantees absolute security; in the event of a data breach, the persons concerned and the authority will be informed as required by regulation.
13. Changes to this policy
This policy may change; the date of the last update is shown at the top of the page. Important changes will be brought to your attention by a means still to be chosen (e-mail or a message in the service); earlier versions are not yet archived online (to be validated).
France annex
Provisions specific to France. They supplement the common rules without changing them.
- Supervisory authority: the CNIL (cnil.fr).
- Cookies: the CNIL's guidelines and recommendation of 17 September 2020 were consulted; the classification remains to be validated.
- Minors: Article 45 of the French Data Protection Act sets 15 as the age at which a minor can consent alone to certain online services; our internal analysis considers that it does not impose a sign-up age for a contract-based service. This point is to be validated.
Other countries (annexes to come)
A national annex will be added for each enabled country (supervisory authority, local rules). No other country's rule is presented as applicable until it is validated.