Data Deletion
Version of June 23, 2026 · English (service translation, Italian original prevails)
Service translation. In case of dispute, the original Italian version prevails: data-deletion.html
This page explains clearly what happens when you want to delete the data associated with your use of Privavis and how to actually request it. The guiding principle is simple: since Privavis is an application that operates entirely on your device and does not use its own application servers, data deletion in most cases translates into a local action that you can perform autonomously.
1. What data exists and where it lives
1.1 Local data on your device
Everything that Privavis "knows" about you (privacy profiles you have created, apps marked as trusted, Privacy Score history, interface preferences, archive of generated GDPR requests, pre-modification snapshots of the rollback function) lives exclusively in the app's internal storage on your Android device. It never leaves the phone except for the exceptions described below.
1.2 Optional Google Drive backup (only if activated by the Premium user)
If you have activated the Drive backup function (Premium, opt-in), your configuration data (profiles, preferences, GDPR request archive) is synchronized to the "Privavis Backups" folder of your personal Google Drive, with the restricted drive.file scope: Privavis can read and write only the files it has created. Those files are yours and are managed by your Google account.
1.3 Premium subscription (Google Play Billing + RevenueCat)
If you are a Premium user, two records related to your subscription exist:
- On Google Play: the receipt of your purchase, managed entirely by Google. We do not have access to payment data (credit cards, IBAN, etc.).
- On RevenueCat (subscription management provider that we use): an anonymous user identifier (App User ID randomly generated by the app, not linked to any of your personal data) and the status of the Premium entitlement (active/not active). No name, email, location, or other personal data is transmitted to RevenueCat.
1.4 Email communications (only if you have written to us)
If you have written to us at hello@privavis.com or privacy@privavis.com, your email and the content of the message are kept in the developer's mailbox for the time necessary to respond and to document the correspondence.
2. How to request deletion
2.1 Deleting local data on the device
It is the simplest and most immediate action, available to everyone, at any time:
- Go to Android Settings → Apps → Privavis
- Tap "Uninstall"
By uninstalling the app, Android automatically deletes all the data that Privavis had stored locally. Nothing remains on the device.
2.2 Deleting the Google Drive backup (if Premium user with active backup)
The backup files are yours in your personal Drive. You can delete them directly:
- Open drive.google.com in the browser, or the Drive app on the phone
- Search for the "Privavis Backups" folder
- Delete the folder (it will be moved to the Drive Trash)
- Empty the Drive Trash for definitive deletion
You can also revoke Privavis's authorization to access your Drive from the Google security panel (myaccount.google.com/permissions → find "Privavis" → Remove access). From that moment Privavis will no longer be able to read or write files on your Drive.
2.3 Cancelling the Premium subscription
To cancel the Premium subscription:
- Open Google Play Store → your profile → Payments and subscriptions → Subscriptions
- Select Privavis Premium
- Tap "Cancel subscription"
The subscription will remain active until the end of the period already paid. You will not be charged for the next renewal. To request a refund, follow the standard Google Play procedure.
To request the deletion of your anonymous App User ID data from RevenueCat, write to us at privacy@privavis.com indicating a specific request: we will contact RevenueCat on your behalf.
2.4 Deleting email correspondence
If you have written to us and want us to delete the history of correspondence, write to us at privacy@privavis.com indicating "correspondence deletion request" as the subject. We will proceed within 30 days of the request (standard GDPR Art. 17 deadline), except where retention is required for legal obligations (e.g., tax requests).
3. Tabular summary of actions
For each type of data, here is the quickest and most effective action for deletion:
- Local data (profiles, preferences, score, GDPR request archive, snapshots): uninstall the app from your device. Time: immediate.
- Google Drive backup (Premium): delete the "Privavis Backups" folder from your personal Drive. Time: immediate.
- Premium subscription: cancel from the Play Store app in the Subscriptions section. Time: charging stops at the next cycle.
- Anonymous App User ID on RevenueCat: request by email to privacy@privavis.com. Time: within 30 days.
- Email correspondence: request by email to privacy@privavis.com. Time: within 30 days.
4. What we cannot delete
For legal and technical reasons, some data is not deletable even at your request:
- Google Play payment receipts: the accounting record of any Premium transactions you may have made is kept by Google Play as required by Italian and European tax regulations (10 years). Privavis does not have direct access to such receipts, but receives monthly aggregated summaries for its own tax declaration.
- Aggregated and anonymous technical logs: the provider hosting this site (privavis.com) keeps technical access logs (e.g., visitor's IP address, time) for 14 days for security and debugging purposes. Such logs do not contain personally identifying data beyond the IP and are rotated automatically.
5. Contacts
For any request relating to the deletion of your data or for clarifications on this procedure:
- Privacy email: privacy@privavis.com
- General email: hello@privavis.com
- Full Privacy Policy: privavis.com/privacy.html
We will respond within 30 days of receipt of the request, as provided for by Art. 12 of the GDPR. For manifestly unfounded, excessive, or repetitive requests, we reserve the right to charge a reasonable cost or to refuse the request, as provided for by Art. 12.5 of the GDPR.
← Back to home