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
- We never sell or rent your personal data.
- No individual advertising profiling: sponsored content is contextual (place category, area), never targeted at your profile or your movements.
- The Service is reserved for adults: we do not knowingly process children's data.
3. Data processed, purposes and legal bases
- Account and profile
- What it is: email, pseudonym, photo, language, vehicle
- Why: providing the Service, securing your account
- Legal basis: performance of the contract
- Consents
- What it is: acceptance of the Terms (version), marketing choice
- Why: GDPR record of consent
- Legal basis: legal obligation / contract
- Geolocation
- What it is: device position, last known position
- Why: map and nearby places, routes, road reports, Hurle, status/presence according to your settings
- Legal basis: consent (system permission, revocable)
- Vehicle dimensions
- What it is: height, weight, ADR
- Why: calculating suitable truck routes
- Legal basis: performance of the contract
- Published content
- What it is: posts, reviews, photos, comments, contributions to place records
- Why: community space, place records
- Legal basis: performance of the contract
- Messaging
- What it is: private messages, attached files
- Why: messaging between members
- Legal basis: performance of the contract
- Reports and moderation
- What it is: content reports, sanctions
- Why: community safety, moderation obligations
- Legal basis: legitimate interest / legal obligation
- Tachograph data (device)
- What it is: driver card readings, .ddd/C1B files, activity histories
- Why: compliance-support tools (display, reports)
- Legal basis: processed on your device — see section 5.1
- Tachograph data (online vault)
- What it is: saved readings, card identity, detailed days, compliance discrepancies, counters,
.dddfiles you deposit - Why: backup, consultation and deposit via browser
- Legal basis: consent, separate and revocable — see section 5.2
- What it is: saved readings, card identity, detailed days, compliance discrepancies, counters,
- Document vault
- What it is: images of scanned documents
- Why: personal vault
- Legal basis: encrypted on your device — see section 6
- Universal logbook — contributions
- What it is: what you write about a place (difficulty, approach, manoeuvring, waiting times observed, landmarks) — without any author identifier
- Why: to pass on to other drivers what you only know by having been there
- Legal basis: performance of the contract — see section 6 bis
- Personal logbook — access codes
- What it is: keypad codes, entry instructions, private notes
- Why: to find them again on site
- Legal basis: encrypted on your device, never transmitted — see section 6 bis
- Document expiry dates
- What it is: document type, label, expiry date, reminder enabled
- Why: expiry reminders (including by notification)
- Legal basis: performance of the contract
- Notifications
- What it is: device tokens (push)
- Why: application notifications
- Legal basis: performance of the contract
- Emails
- What it is: address, preferences
- Why: service emails; promotional emails only with opt-in
- Legal basis: contract (service) / consent (promotional, revocable at any time)
- Usage measurement
- What it is: usage events, screens viewed, sessions
- Why: internal statistics, improving the Service
- Legal basis: legitimate interest (minimised data, never transferred)
4. Geolocation: your controls
- Position is processed only if you allow it at system level (iOS/Android/browser); you may withdraw that permission at any time.
- We keep no history of your movements. Only your last known position is stored, and it is overwritten with each update: there is nowhere any trace of your past journeys. The exception is items you deliberately publish that carry a location (a geolocated post, a report, a Hurle alert), which follow the fate of that content.
- Your visibility settings in the application determine what the community sees (status, presence on the map), including an invisible mode.
- The Hurle feature broadcasts your position only at the moment you trigger an alert.
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.
- Legal basis: your consent (Art. 6(1)(a) GDPR), given through a dedicated screen, separate from acceptance of the Terms, and revocable at any time.
- Data concerned:
- your card readings: the raw content read from the driver card (activity and identification), the reading date, the period covered and a technical fingerprint used to avoid storing the same reading twice;
- the identity shown on your card: holder's name, card number and expiry date;
- your days: daily totals (driving, work, availability, rest) and the detail of the periods that make them up;
- the compliance discrepancies identified by the calculator (overruns, insufficient rest, etc.), stored with your days;
- a snapshot of your current counters (remaining driving time, breaks, rest) so that you find the same view on the web as in the application;
- the
.dddfiles you deposit yourself from the browser. The deposit box is temporary: once the file has been incorporated into your vault, it is removed from it. An unreadable file stays there, so that your data is never deleted without your knowledge.
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.
- Hosting in the European Union, with access strictly limited to you alone by the database security rules ("visible to you only").
- Never transmitted to an employer or to a third party. No facility to make this data available to a transport company exists in this service; were such a feature ever created, it would require your separate and explicit consent.
- Reversibility: switching the backup off stops any new upload; the "empty my vault" function (in the application as well as on the portal) immediately deletes the data already online, and the application returns to local operation.
- Retention: for as long as your consent is active. Withdrawal of consent, emptying the vault or closing the account result in deletion of the online data.
- Web access: logging in to the portal uses your usewolv account; sessions expire and you can sign out of all your devices.
- Where the calculations happen: whether you read your card in the application or deposit a file on the portal, driving-time and compliance calculations run on your own device — in the application, or directly in your browser for a web deposit. No third-party service analyses your activity: our servers only store and synchronise the result, so that the application and the portal display exactly the same figures.
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
- The images of your scanned documents are encrypted and stored on your device. By default they do not pass through our servers and are inaccessible to the publisher. Biometric protection (Face ID / fingerprint) can be enabled.
- Only the expiry information (document type, label, expiry date, reminder enabled) is recorded on our servers, so that we can send you reminders and you can find them again on another device.
- The text recognition (OCR) that detects dates runs on your device and serves only to pre-fill your reminders. No human processing is applied to your documents.
- Deleting a document erases the encrypted file and the associated expiry entry; deleting your account erases the recorded expiry entries.
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:
- the images of your documents, already encrypted on your device (AES-256-GCM). We receive files for which we do not hold the key;
- the decryption key, itself encrypted with a key derived from a recovery code generated on your device, displayed once, and which we do not keep.
Consequences, in both directions:
- We are technically unable to read your backed-up documents, to display them, to analyse them or to communicate them intelligibly to a third party, including to an authority that might request them. All we hold are encrypted files and a key that is itself encrypted.
- If you lose your recovery code, and if none of your devices still holds the key, your backup becomes permanently unusable. We can neither reopen it nor regenerate the code.
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.
- It is stable for a given place: two contributions at the same spot from the same device are recognised as one person.
- It changes from one place to another: it is impossible to follow someone from site to site.
- It is never readable by a user or by a partner: it serves only for counting and for letting you return to your own contributions.
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:
- Supabase (Supabase Inc.)
- Role: hosting of the database, of authentication and of files
- Where the data lives: servers in the European Union — Frankfurt, Germany (AWS
eu-central-1)
- HERE Technologies (HERE Global B.V., Netherlands)
- Role: route and traffic calculation — receives the departure/arrival points and the vehicle dimensions, without identity
- Where the data lives: EU
- Google Firebase Cloud Messaging
- Role: delivering push notifications to your device: we pass to Google the technical token of your device and the content of the notification (never your position or your tachograph data)
- Where the data lives: Google infrastructure (framed transfer, see section 8)
- Brevo (Sendinblue SAS, France)
- Role: sending service emails and, with opt-in, promotional emails
- Where the data lives: EU
- Apple / Google
- Role: distribution platforms, notifications, speech recognition performed by the system on your device
- Where the data lives: depending on your device
- EasyHost (Belgium)
- Role: hosting of the usewolv.com showcase website
- Where the data lives: EU
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
- Account and profile: lifetime of the account, then deletion
- Records of consent: 5 years after closure of the account (legal evidence)
- Published content (posts, reviews, photos): lifetime of the account; factual contributions to place records remain in the database, dissociated from your identity
- Private messages: lifetime of the participating accounts
- Position: no history of movements is kept: only your last known position is stored, overwritten with each update, and deleted with your account
- Hurle alerts and road reports: deleted or anonymised when the alert expires, aggregated statistics retained
- Tachograph data (device): kept on your device for as long as you wish; erased if you delete them in the application or uninstall it
- Tachograph data (online vault): for as long as consent is active; deleted upon withdrawal of consent, emptying of the vault or closure of the account
- Vault — document images: on your device, until you delete them or uninstall the application
- Vault — expiry entries (server): until you delete them or close your account
- Universal logbook — contributions: kept for as long as they are useful to the community; without an author identifier, they are not personal data
- Personal logbook — access codes: on your device, until you delete them or uninstall the application
- Usage measurement: 24 months, then automatic deletion (daily purge)
- Moderation sanctions: for as long as necessary to manage repeat offences, then deletion
10. Your rights
Under the GDPR, you have the rights of access, rectification, erasure, restriction, objection and portability.
- Account deletion: the "Delete my account" button in the application settings. It immediately erases your profile and all data attached to it (content, personal contributions, messages, expiry entries, settings), and signs you out. Deletion of your login credentials and of technical backups takes place within 30 days at the latest.
- Data kept on your device (tachograph, vault) is erased by uninstalling the application.
- To exercise your rights: fabrice@usewolv.com. We reply within one month.
- You may lodge a complaint with the Data Protection Authority (APD/GBA, Belgium — www.autoriteprotectiondonnees.be) or with the authority of your country of residence.
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.