Vigie privacy policy

1. Who publishes the app

Vigie is published by Audran Scieur.

Privacy contact: contact@vigie-application.com.

This policy explains which data the Vigie app may access, use, store or transmit when you use the Vigie Android app.

2. General principle: local operation

Vigie’s monitoring features use no publisher back-end: no account required, no analytics and no advertising.

The app does not transmit your monitored numbers, your contacts, your alert history, your rules, your calendar or your location to a server controlled by Audran Scieur.

The data Vigie needs in order to work is stored locally on your Android device, unless you deliberately trigger a backup, a sync or an export to your own Google Drive account, or unless an interaction with Google Play is required for a purchase, a subscription or a restore.

In plain terms: Vigie receives no monitoring-related data. The only deliberate transmissions are the Google features you trigger and the support form described below.

3. Data used locally

Phone numbers and call history

Vigie uses the numbers you configure to detect important calls and trigger a priority alert.

The app may access the phone state and the incoming call number where Android allows it. This information is used solely to compare the incoming call with your local rules.

The alert history is kept locally on the device in order to show recent triggers. In the Pro version, the history can be complete, filterable and exportable.

Contacts

If you allow it, Vigie can access your contacts to help you pick a number to monitor more easily.

Contacts are not sent to the publisher. Vigie only copies the information needed for the rule you choose to create, for example a label and a number.

Custom sounds

In the Pro version, you can select a custom audio file. Vigie copies that file into the app’s private storage on your device.

Calendar

In the Pro+ version, if you enable calendar-based rules, Vigie can read events marked as “busy” in order to enable or disable certain rules during your meetings.

Calendar events are processed locally and are not sent to the publisher.

Location

In the Pro+ version, if you enable geographic zone rules, Vigie can use the device location to determine whether you are inside or outside a configured zone.

Location is used solely to apply your local geofencing rules. It is not sold, used for advertising or sent to the publisher.

If the app requests background location access, it is so that zone rules can keep working even when Vigie is not open on screen.

Bluetooth, camera, audio and notifications

Vigie may use:

• Bluetooth, to route audio to a device of your choosing;
• the camera, solely to drive the LED flash during an alert;
• audio settings, to play the alert at a sufficient volume;
• notifications, to keep monitoring active and allow an alert to be stopped quickly.

These accesses serve only the features visible in the app.

4. Google Drive sync and exports

The Pro+ version can use your own Google Drive account.

There are two uses:

• Rule sync: Vigie creates an archive encrypted on the device, then saves it in the app’s private area on your Google Drive. That file does not appear in “My Drive”.
• History export: if you explicitly ask for it, Vigie can create a CSV or JSON file visible in your Google Drive.

The publisher does not receive these files and has no access to your Google Drive account. Exchanges with Google Drive are governed by Google’s own terms and policies.

For encrypted sync, the encryption key stays on the device in the Android Keystore wherever possible. The publisher does not hold that key.

5. Google Play payments

Vigie Pro and Pro+ purchases and subscriptions are handled by Google Play.

Vigie does not receive or store your bank details, card numbers or payment methods. Google Play processes the payment under its own terms.

The app may check locally whether a Pro or Pro+ purchase or subscription exists, in order to unlock the paid features.

6. Bug reports

The “Report a bug” link opens a form hosted on vigie-application.com in your browser. The app sends no data automatically and contains no secret and no tracking SDK. That page does, however, belong to the website, which measures its traffic: see section 7.

Before sending, your email address is verified by Google or by a link received by email. Google may also pass on your name. An encrypted support session is then kept for 30 days in a secure cookie, unreadable by the page’s code.

If you submit the form, the publisher receives that verified identity, the title, severity, frequency and description of the problem, along with the optional fields you fill in: on-screen message, phone and Vigie version. Do not enter a phone number or any sensitive data there.

This information is used solely to reproduce, fix and track the bug. This processing rests on the publisher’s legitimate interest in providing support and improving Vigie’s reliability. The IP address is used only to limit abuse; its rate-limiting fingerprint expires after one hour and is not recorded in the ticket. Tickets are kept for as long as tracking the bug requires and can be deleted on request, with their reference.

7. Analytics and advertising

In the app

The Vigie app uses no analytics. It does not measure your usage and does not send analytics events to Firebase Analytics, Google Analytics or any equivalent tool.

Vigie uses no advertising SDK and does not sell personal data.

No audience-measurement or crash-reporting SDK will be built into the app. Should that choice change, this policy would be updated before the release concerned is published.

On the vigie-application.com website

The website — which hosts this policy as well as the “Report a bug” form — measures its traffic with Umami, free software self-hosted on the publisher’s servers (deployed via Coolify). This measurement concerns only your browser when you open the site: the Android app takes no part in it and loads no tracker. No data is passed to an advertising network or to a third-party analytics service.

This measurement works without cookies and without any advertising identifier. It records only:

• the page viewed and the page of origin (referrer);
• the device type, the browser, the operating system and the language;
• the country and approximate region, derived from the IP address without that address being recorded;
• clicks on the app download buttons.

These statistics are aggregated: they cannot identify you, are not cross-referenced with other sources and do not follow your browsing from one site to another. This measurement sets no cookie and requires no consent.

This measurement concerns the website only: the Android app sends no data of this kind.

Cookies set by the website

The website sets no advertising cookie and no audience-measurement cookie. Two technical cookies exist, and only those two:

• vigie_locale — remembers the language you chose, so it can be served back to you on your next visit. Lifetime: 12 months.
• Support session cookie — is only set if you identify yourself on the “Report a bug” form, as described in section 6. It disappears at the end of the session.

Both cookies are strictly necessary for a service you explicitly request: showing the site in your language, and attaching your report to your identity. As such they fall under the trackers exempt from consent, and the site therefore displays no cookie banner.

8. Security

Local data is stored in the Android app’s private area. Drive backups of your rules are encrypted on the device before being sent.

Communications with Google Play, Google Drive and the support form use the security mechanisms provided by Android, Google Play services and HTTPS/TLS.

9. Retention and deletion

You can delete Vigie’s local data by deleting the rules in the app, by turning off Drive sync, or by uninstalling the app.

Uninstalling removes the data stored locally by the app, except for files you deliberately exported to an external location, for example Google Drive or a file chosen through the Android picker.

For any privacy-related request, please contact: contact@vigie-application.com.

10. Your rights

Under the General Data Protection Regulation (GDPR) and the French “Informatique et Libertés” act, you have the following rights over the data processed by Vigie:

• Right of access: ask which data concerning you is processed by the app.
• Right to rectification: change your rules, numbers and preferences yourself, directly in the app.
• Right to erasure: delete a rule or a number from the app, or delete all local data by uninstalling Vigie. For files you exported to Google Drive, deletion happens from your Google Drive account.
• Right to portability: the Pro+ version lets you export your rules to a file you can reuse or transfer.
• Right to object and to restriction: you can turn monitoring off in the app or uninstall Vigie at any time. For a bug report, you can exercise these rights by contacting the publisher.

For local data, most of these rights are exercised directly in the app. For a bug report, contact the publisher with the email address used and, if possible, its reference.

For any question about these rights, you can contact the publisher: contact@vigie-application.com. You also have the right to lodge a complaint with the French data protection authority (CNIL).

11. Data recipients

Monitoring data is not transmitted to a publisher server. Voluntary bug reports are accessible only to the publisher in its tracking tool, and to the technical providers strictly required for hosting and for sending email.

Google services may be involved only when you use the corresponding features:

• Google Play, for purchases and subscriptions;
• Google Drive, for user-triggered sync or export;
• Google Play services, for certain Android features such as location/geofencing, Google authentication and Play Integrity.

The publisher does not receive Drive files, payment methods, bank details, or any analytics stream coming from the app.

12. Changes

This policy may be updated to reflect changes to Vigie, to its permissions or to its features. The update date shown at the top of the document will be changed accordingly.