Privacy Policy — trildaScan¶
English · Français
© 2025-2026 trildaDevCenter — Paul Plaquette, Montpellier, Occitanie, France. All rights reserved.
Last updated: 31 August 2026
Who we are¶
trildaScan is published by Paul Plaquette, trading as trildaDevCenter, Montpellier, France, who is the data controller for the processing described below.
Contact: trildadevcenter@gmail.com — please put the application name in the subject line.
What this policy covers¶
trildaScan for Android and iOS. The desktop and web builds of trildaScan display no advertising at all, so the advertising sections below do not apply to them.
Each platform uses its own advertising setup: the Android and iOS applications are registered separately with Google AdMob and share no identifier. Should another platform ever carry advertising, it may use a different provider, and this policy will say so.
The short version¶
- trildaScan works without an account, and we operate no server. We receive nothing.
- Everything you scan stays on your device, unless you deliberately send it somewhere.
- Looking up a book or a product sends the code you scanned — nothing else — to the metadata source you chose.
- Advertising is served by Google AdMob. If you consent to it, it is personalised: your advertising identifier is read and a profile is used to choose the ads. In Europe that consent is gathered before a single ad is requested, through an IAB TCF v2.2 form you can reopen and revoke at any time.
- There is no analytics, no crash reporting, no marketing e-mail and no push notification.
1. What stays on your device¶
Your library of scanned codes. For each code: its exact content, its format, the kind of content it holds, the date and time of the scan, and whatever description a metadata lookup returned. A code you scan can itself be personal data — a contact card, a Wi-Fi password, an event, an address. It is stored exactly as it was read. We never see it.
A device identifier. A random 16-character value drawn on first run, kept in the application's settings. It is deliberately not a hardware identifier and needs no permission; its only job is to reconcile copies of your own library when two devices have changed the same entry. It is not an advertising identifier and is never used for advertising.
Your settings. Theme, handedness, whether the welcome sequence has been seen, which metadata sources are enabled and in what order, whether duplicate scans are kept.
Credentials for a storage destination you configure. They never go into the settings file. On Android they are encrypted with AES-GCM under a key held by the Android Keystore; on iOS they are placed in the Keychain. Desktop and web builds have no hardware-backed store, so values are held as they are — a reason not to configure a sensitive account there.
Diagnostic traces. Written to the system log; on iOS also to a file inside the application's own container, emptied at every launch. They are never transmitted.
Deleting a code marks it deleted and keeps a marker, so that the deletion can reach your other copies rather than the entry coming back at the next merge. Uninstalling the application removes all of it.
2. What leaves your device, and to whom¶
a. Metadata lookups. When you scan a book or a product, trildaScan can ask Open Library, Google Books, the Bibliothèque nationale de France or Open Food Facts what the code corresponds to. What is sent is the code that was read — an ISBN, an EAN — and nothing that identifies you. As with any HTTPS request, the service sees the network address the request comes from. Cover images are fetched from Open Library's image server. You choose in Settings which sources are enabled and in which order; disable them all and no lookup ever leaves the device.
b. The medicine database, which you download if you want it. To name a medicine box from the code printed on it, trildaScan needs an extract of the French public medicine database (ANSM, HAS, UNCAM), published under an open licence. That extract does not ship with the application: it is offered to you, with its size, the first time a medicine is identified, and you can also install it, update it or remove it from Settings. Nothing is downloaded without your agreement.
What our server learns at that point is that a device wants the medicine database, and nothing else: never which medicine you scanned. The lookup then happens entirely on your device, offline, with no request accompanying a scan.
c. A storage destination you set up yourself. trildaScan can copy your library to a WebDAV server that you name, with credentials you supply. The data goes to your server, under your control. We are not involved and receive nothing.
d. A link you open. Opening an address found in a QR code hands it to your browser or to
the relevant application, and from that point the destination's own policy applies. The same
holds for the link we offer to the public Vidal page under an identified medicine: tapping
it sends the box's code to vidal.fr and takes you out of the application. As long as you do
not tap it, nothing is sent.
e. Advertising, covered in the next section.
3. Advertising, consent, and the IAB framework¶
trildaScan is free and paid for by advertising: a banner under the scanner, a banner every few entries in the library, an ad card in the same list, and one full-screen ad shown once when the welcome sequence closes.
Advertising is served by Google AdMob, which acts as an independent controller for what it collects. AdMob may process:
- the device advertising identifier — AAID on Android, IDFA on iOS;
- the network address, and the approximate location it implies;
- device information: model, operating system, language;
- your interactions with the ads shown.
Your consent comes first¶
In the European Economic Area, the United Kingdom and Switzerland, a consent form is put to you before any ad has been requested. On a first launch it comes at the end of the welcome sequence, after the screens that explain the application; after that, for as long as you have not answered, it is presented at startup. It is built with Google's User Messaging Platform, a Consent Management Platform registered with IAB Europe and certified for the Transparency & Consent Framework (TCF) v2.2.
The form offers Allow, Refuse, and Manage options if you would rather decide purpose by purpose and vendor by vendor. The close button in the corner counts as a refusal — closing the window is an answer, and it is recorded as one. Your answer is kept on the device as a TC String and made available to the vendors you allowed.
- You accept → the advertising is personalised, and here is what that covers: your device advertising identifier is read, the ads you are shown and the ones you tap are tied to it, and Google together with the vendors you allowed use that to build an advertising profile and draw the next ads from it. That profile lives with them, never with us. It is profiling in the sense the GDPR gives the word; it produces no decision about you beyond which advertisement you are shown.
- You refuse → the advertising becomes non-personalised: it is chosen from context — your language, your country, where the slot sits on screen — rather than from who you might be. Ads do not disappear; they stop being tailored to you. Google may still write on the device what advertising needs to function at all, such as not showing you the same ad ten times over, but nothing of it is used to target you.
- Nothing is requested from the ad network before you have answered. On the very first launch this means the full-screen ad has had no opportunity to load, and simply does not appear.
The vendors, and the detail of the purposes¶
The form is not a plain yes or no. Manage options opens the detail: each purpose — measuring how an ad performed, developing services, personalising content — can be accepted or refused on its own, and the vendors taking part in it are named and counted there. That list belongs to the TCF framework and changes without us, so the form shows it rather than this page repeating it, where it would go stale.
Some vendors declare a legitimate interest for certain purposes rather than asking consent. The same screen lets you object to it, purpose by purpose.
How long any of it is kept, and by whom, is each vendor's own affair: the form links to their policies, and Google's is linked below.
On iPhone and iPad, a second question¶
Immediately after the consent form, iOS asks whether trildaScan may track you across other companies' applications and websites — Apple's App Tracking Transparency prompt. If you decline it, the IDFA is not available to the application, whatever your answer to the previous form.
Changing your mind¶
Settings → Privacy reopens the consent form whenever you want, and lets you withdraw a consent you had given. Withdrawing is as easy as giving: the same screen, the same buttons, no extra step. Withdrawal applies from that moment on; it cannot undo processing already carried out, and it does not make the advertising disappear — it stops being personalised.
Legal basis¶
Your consent (GDPR art. 6(1)(a)) for reading or writing identifiers on your device and for personalised advertising. Everything described in section 1 happens on your device and is not transmitted to us.
Google's practices are described in its own Privacy Policy and in how Google uses information from sites or apps that use its services.
4. Advertising and marketing — what we do not do¶
- No marketing e-mail. There is no mailing list, and therefore nothing to unsubscribe from.
- No notification, promotional or otherwise. The application asks for no notification permission.
- No analytics, no crash reporting, no attribution SDK. None is present in the application.
- We never sell or share your personal information, in the sense United States privacy laws give those terms, and we carry out no cross-context behavioural advertising beyond the AdMob choice described above, which is yours to make and to revoke.
- We do not choose which ads you see. Their content comes from Google's network, within the content rating declared for the application. An unsuitable ad can be reported to Google through the control shown on the ad itself, and to us at the address above.
- The Apps page inside trildaScan presents other trildaDevCenter applications. It is plain information: no tracking, no identifier, and no communication with any server.
5. Permissions the application asks for¶
Camera — needed to read a code. It is requested the first time you open the scanner. Refuse, and the scanner cannot work: trildaScan says so plainly and offers the way to your system settings. Nothing else is affected, and you can still read a code from an image you already have.
Photos — choosing an image goes through the system picker, which hands over only the image you selected. The image is decoded on your device and never uploaded.
Vibration and network access, for scan feedback, for the lookups described above, and for downloading the medicine database if you ask for it.
On Android, the advertising SDK adds permissions of its own to the installed package — advertising ID access, the Android AdServices ones for attribution and topics, plus wake lock and foreground service. They appear on the store listing because they are part of the package, not because the application asks you for them while it runs.
6. Children¶
trildaScan is not directed at children, and we knowingly collect no data from them. If you believe a child has provided personal data through the application, write to us and we will help you remove it.
7. How long data is kept¶
What section 1 describes stays until you delete it, or until the application is uninstalled. Your consent choice is kept until you change it; the form comes back if the list of purposes or vendors changes.
8. Your rights¶
Under the GDPR you have the right of access, rectification, erasure, restriction, objection and portability. Because your data lives on your device, you exercise most of these directly: every entry can be read, edited and deleted in the application, and your library can be copied to a destination you control.
For anything else, write to trildadevcenter@gmail.com. For data held by Google as a result of advertising, requests should be addressed to Google, which is the controller of it.
You may also lodge a complaint with your supervisory authority — in France, the CNIL.
9. Security¶
Every network call is made over HTTPS. Credentials for a storage destination are kept in the platform's protected store, as described in section 1. We hold no server and no copy of your data, which removes an entire class of risk — but no method of transmission or storage is ever completely secure.
10. International transfers¶
Google may process advertising data outside the European Economic Area, under the safeguards set out in its own privacy policy. The metadata sources you can enable are operated by Open Library (United States), Google (United States) and Open Food Facts (France).
11. Changes to this policy¶
This policy may be updated. Any change is published on this page with a new date, and a change that affects what you consented to brings the consent form back.
12. Contact¶
trildadevcenter@gmail.com — with the application name in the subject line.