usewolv
Télécharger l'app
Carte Communauté Pro Partenaires Télécharger l'app
Legal

Privacy Policy (GDPR)

Version 2.2 — 4 September 2026

This is a translation provided for your convenience. Only the French version of this document is legally binding (see section 19 of the Terms of Use).

1. Data controller

Fabrice Neulens, natural person, publisher of usewolv.

Contact for any question about your personal data: fabrice@usewolv.com.

2. Our commitments

3. Data processed, purposes and legal bases

4. Geolocation: your controls

5. Tachograph data — local by default, online only if you ask

The data from your driver card describes your professional activity in fine detail. We apply the most protective regime possible to it.

5.1 By default: everything stays on your device

Card reading, long-term history, counters and reports are calculated and kept locally on your phone. Without action from you, no tachograph data is sent to our servers and we have no access to it.

5.2 Online backup ("vault") — optional, based on consent

You can enable, from the application only, an online backup that means you lose nothing if your phone is lost or broken, and that lets you consult your data on a large screen from your browser.

Compliance discrepancies are an indicative aid, not binding: they constitute neither an official finding, nor evidence, nor a penalty. Only an official check and the records of your tachograph are authoritative.

The data kept locally on your phone is unaffected by this choice: it stays there, and is erased if you uninstall the application.

6. Document vault — encrypted on your device

6.1 By default, the images never leave your phone

6.2 Online backup — optional, based on consent, and unreadable by us

Reinstalling the application or moving to a new phone erases the images stored on the device. You may choose to back them up online. This backup is disabled by default and is enabled only through a dedicated consent screen, whose accepted version and date are recorded.

What is sent when you enable it:

Consequences, in both directions:

These images are hosted in a private space at Supabase, in Frankfurt (Germany), in the same way as the other data of the Service (section 7): the backup introduces no new processor.

6 bis. Universal logbook — anonymous by design

What the logbook contains, and what it does not

Your contributions to the universal logbook (difficulty of access, approach, manoeuvring, waiting times, practical landmarks) are recorded without any author identifier. None of this data carries your name, your username or your account identifier: it is technically impossible, for another driver as for the Publisher, to know who wrote what.

Your access codes and entry instructions belong to the personal logbook: they are encrypted on your device and are never transmitted to the universal logbook or to our servers. We do not hold the key: a phone lost without an online backup takes those codes away for good, and we are unable to restore them.

The token: editing what you wrote, without ceasing to be anonymous

So that you can come back to your contributions, your device keeps a token — a randomly drawn secret, held in your encrypted vault. Only its fingerprint is sent with the contribution. The database therefore still does not know who wrote: it only knows that whoever presents the right token is the author of that entry.

A consequence to be aware of: if you lose your phone without an online backup, your contributions remain in the logbook but become out of your reach — we cannot link them back to you, precisely because nothing links them to you.

The "voice": counting people without knowing who they are

So as not to display "33 drivers" when a single person has written three times, each contribution carries a voice: the fingerprint of your device's secret combined with the key of the place.

In other words: the database can know that two contributions at the same place come from the same phone. It can never know whose, nor link that phone to another place.

Removal of a mention by name

The logbook describes places, not people, and naming someone there is prohibited. If a natural person is nonetheless named or made identifiable, they may request removal at support@usewolv.com, with the subject prefixed [Signalement]. Depending on the case, the naming is removed while the practical information is kept, or the contribution is deleted. The operation is reserved to our administrators.

7. Recipients and processors

Your data is shared only with the technical providers that are strictly necessary:

The speech recognition used for hands-free input is the one of your device (iOS/Android): usewolv does not send your audio recordings to a third-party transcription service.

Data may in addition be disclosed where the law requires it (order from a competent authority).

8. Transfers outside the European Union

Your data is hosted in the European Union, in Frankfurt (Germany).

Some of our providers (Supabase, Google) are companies subject to United States law, even where the servers they operate are located in Europe. Where access from the United States may occur — for technical maintenance, for example — it is framed by the mechanisms provided for by the GDPR: European Commission standard contractual clauses and, where applicable, the adequacy decision applicable to certified companies.

9. Retention periods

10. Your rights

Under the GDPR, you have the rights of access, rectification, erasure, restriction, objection and portability.

11. Security

Encryption in transit, access control through database-level security rules (each user reaches only their own data), separation of administration roles, minimisation of usage-measurement data.

12. Cookies and trackers (website)

The usewolv.com showcase website uses no third-party advertising cookies. Only strictly necessary technical trackers may be used. Should audience-measurement tools be added, a compliant consent banner would be put in place.

13. Changes

Any substantial change to this policy is announced in the application at least 30 days in advance, with renewed consent where the law requires it. The version history is retained.