DiluzaDiluzachevron_leftBack to site

Legal

Privacy Policy

Summary, in plain language

Diluza helps you clean up your photo library and your documents. Your photos and documents are analyzed entirely on your device: their content is never uploaded to us or to any third party. We run no server of our own and we never sell your data.

Three things do involve someone else, and each is described below: connecting a cloud account (Google Drive or OneDrive), buying a subscription (Google Play and RevenueCat), and audience measurement (Google Analytics for Firebase), which only runs if you consent to it.

1. Data processed on your device, not collected by us

To categorize your media, find duplicates, and let you review and delete them, the app reads, locally, on your device only, the following:

  • photo_libraryPhotos and videos and their metadata (file name, size, dimensions, creation date, album), via the READ_MEDIA_IMAGES and READ_MEDIA_VIDEO permissions.
  • descriptionDocuments, to find duplicate files. On Android 11 and later this uses the MANAGE_EXTERNAL_STORAGE permission, which Android grants only after you allow it explicitly in system settings. The app reads file names, sizes and content hashes; it does not open, index or transmit document contents.
  • location_offPhoto location (EXIF). The app declares ACCESS_MEDIA_LOCATION because the media library is read unredacted, but it does not extract, use, store or transmit the location embedded in your photos.
  • auto_awesomeOn-device machine learning. Categorization (for example pets, food) runs through an on-device library, Google ML Kit Image Labeling. Images are not sent to a server for analysis. Results (category, confidence score, label text) are stored only in a local database on your device.
  • fingerprintDuplicate detection. Content hashes (MD5, and quickXorHash for OneDrive) are computed to find exact byte-identical copies. Hashes are cached locally on your device.

This on-device data lives in a local SQLite database, on-device key/value storage, and the app's private files. It never leaves your device except through the optional features below, and it is removed when you uninstall the app. app.

2. Cloud accounts, optional and only if you connect one

If you choose to connect Google Drive or Microsoft OneDrive, you authorize the app via OAuth 2.0. In that case:

  • sync_altThe app communicates directly with Google's and Microsoft's APIs to;s APIs to list your files and their metadata and content hashes (to count photos and find duplicates) and to delete files that you select. Google Drive and OneDrive deletions are permanent and bypass the provider's trash.rash.
  • keyAccess tokens are stored on your device: the platform keystore for the long-lived refresh token, on-device storage for short-lived tokens. We do not receive or store your cloud credentials on any server of ours, because we operate none.
  • link_offYour use of Google Drive and OneDrive is also governed by Google'spos;s and Microsoft'spos;s own privacy policies. You can disconnect a cloud account at any time in the app, which removes the stored tokens and cached cloud data from your device.

The app integrates Google Drive and Microsoft OneDrive only. It does not access Google Photos.

Limited Use disclosure (Google API Services). Diluza's use of information received from Google APIs adheres to theo the Google API Services User Data Policy, including the Limited Use requirements. Data obtained from Google Drive is used solely to provide the in-app features you invoke (listing your files to count photos and find duplicates, and deleting the files you select), is processed only on your device, is never transferred to us or to any server (we operate none), and is never used for advertising.

3. Subscriptions and purchases

Optional subscriptions are sold through Google Play and managed with RevenueCat, a third-party subscription-management service. When you purchase or restore a subscription, RevenueCat processes purchase information (a purchase receipt or transaction, an app-generated user identifier, and device and platform information) to validate your entitlement. We do not receive or store your payment card details; those are handled by Google Play. See RevenueCat's privacy policyolicy and Google Play's privacy policy for details of their processing.sing.

4. Notifications

The app may send local notifications on your device, for example an Auto-Pilot alert when a background scan finds new duplicates, or a reminder about your free monthly allowance. These are generated on your device: there is no push server and no personal data is transmitted to send them. You can turn them off in the app (Profile, then Notifications) or in your device settings.

5. Audience measurement

The app includes Google Analytics for Firebase, for one narrow purpose: attributing subscription events so we can tell whether the paid tier works. Firebase generates a pseudonymous app instance identifier and collects technical and usage data such as app version, device model, operating system, coarse region derived from your IP address, and app-open and subscription events. RevenueCat forwards subscription events to that Google Analytics property, keyed on the same identifier.

  • image_not_supportedMeasurement never touches the content of your photos, videos or documents. It records how the app is used, not what is in your library.
  • blockWe do not integrate advertising SDKs, we do not use an advertising identifier, we do not build profiles or cross-app tracking, we never sell your data, and there is no automated decision-making.
  • infoMeasurement currently starts when you first open the app, and the app does not yet offer an in-app switch for it. Uninstalling the app stops it. We are adding a consent choice and an opt-out control; until then, if you want your measurement data deleted, write to us and we will have it removed from the Google Analytics property.

Internal event counters used purely for in-app logic stay in memory on your device and are never transmitted.

6. Background processing

The app may run a periodic background task (using RECEIVE_BOOT_COMPLETED and FOREGROUND_SERVICE) to analyze newly added photos and detect duplicates. All of this runs on your device; it does not upload your photos.

7. Legal bases

Under Article 6 of the GDPR, each purpose rests on a specific legal basis:

PurposeLegal basis
Reading and analyzing media and documents on your devicePerformance of the contract, Art. 6(1)(b), plus the Android permissions you grant
Connecting and cleaning a Google Drive or OneDrive accountConsent, Art. 6(1)(a), given by connecting the account
Selling and validating a subscriptionPerformance of the contract, Art. 6(1)(b)
Local notificationsConsent, Art. 6(1)(a)
Audience measurementConsent, Art. 6(1)(a) GDPR and Art. 82 of the French Data Protection Act

8. Recipients and transfers outside the EU

We have no server, so there is no database of ours holding your data. The recipients are the services you use:

  • cloudGoogle LLC (Google Drive API, Google Sign-In, Google Play, Google Analytics for Firebase) and Microsoft Corporation (OneDrive API).
  • card_membershipRevenueCat, Inc., as a processor for subscription management.

These providers are established in the United States, so the data described in sections 2, 3 and 5 may be transferred outside the European Union. Such transfers rely on the safeguards in Chapter V of the GDPR: the EU-US Data Privacy Framework where the provider is certified, and otherwise the European Commission'spos;s standard contractual clauses. You can ask us for the specific safeguard applying to a given provider.

9. Retention

  • smartphoneOn your device (classifications, hashes, preferences, cached cloud data): until you uninstall the app or clear its data.
  • link_offCloud tokens and cached cloud data: deleted as soon as you disconnect the account in the app.
  • receipt_longSubscription records at RevenueCat and Google Play: for the life of the subscription plus the period their own policies and applicable accounting law require.
  • query_statsMeasurement data: retained for the period configured in the Google Analytics property, 2 months by default, then deleted.

10. Children

The app is not directed to children under 15, the age of digital consent in France, and we do not knowingly collect personal data from them.

11. Your rights

You have the rights of access, rectification, erasure, restriction of processing, objection and portability, and the right to withdraw your consent at any time. Because the app's processing happens on your device and we hold no account about you, most of these are exercised directly:ctly:

  • deleteErasure of on-device data: uninstall the app or clear its data in Android settings.
  • link_offCloud access: disconnect the account in the app, and revoke Diluza's access in your Google or Microsoft security settings.ings.
  • toggle_offMeasurement: uninstall the app, or ask us to delete your measurement data. An in-app opt-out is on the way.

For anything else, write to contact@diluza.com. We answer within one month, as required by Article 12 of the GDPR.

This policy and the processing it describes are governed by French law and by the GDPR. If you believe your rights are not respected, you can lodge a complaint with the CNIL, the French supervisory authority, at cnil.fr.

12. Changes to this policy

We may update this policy. Material changes will be reflected by updating the effective date above and the hosted version linked from the app.

13. Contact

Bastien Botrel, contact@diluza.com

Terms of usechevron_rightBack to site