Back to the product page

Privacy Policy for Reel Downloader

Controller and developer: Thomas Hoffmann
Gress-Straße 1
71384 Weinstadt, Germany
Privacy contact: info@diligo.online

1. Scope

This policy explains how the Android app Reel Downloader handles data. The app downloads supported media at the user’s request and stores it on the user’s device. The developer does not operate a Reel Downloader account service, analytics service, or cloud download history for the current production version.

2. Data stored on the device

For an infrequent review request and optional app recommendation, the app also stores a local count of successfully saved download tasks and a flag for a single review attempt. Each task counts at most once. These values are not sent to an analytics service and survive deletion of individual history entries. Clearing app data or uninstalling removes them. Recommending the app sends only general text and the public store link to an app you select, without download links or media files.

The app stores download links, normalized links, media titles, queue and error states, settings, a broad age group, local diagnostic logs, and references to downloaded files on the device. Downloaded media is saved in the app folder or a folder selected by the user. This data is used only to provide the requested download, history, playback, retry, settings, and monetization features.

The user can remove history entries and local sessions in the app. Downloaded files can be deleted through the app or Android’s file tools. Uninstalling the app removes its private data; media deliberately published to a shared or user-selected folder may remain until the user deletes it.

When the user starts a download, the app sends the requested link and technically necessary network requests directly from the device to the relevant source provider. The provider receives network information such as the IP address and request headers and processes it under its own terms and privacy policy. The developer does not receive a copy of the link or media through a Reel Downloader server.

Availability depends on the provider, region, link type, and visibility of the content. The app does not bypass access controls or digital rights management.

4. Optional Instagram, Facebook, and Threads sessions

For content that a provider does not make available anonymously, users may voluntarily sign in through an embedded provider webpage. The provider handles the login page and credentials. Reel Downloader does not read or store the password.

If the user selects “Save session,” provider cookies and the browser user-agent are copied into the app’s private, backup-excluded storage. They are used only for user-requested access to that same provider. These files are not protected by an additional Reel Downloader password. Users can delete each session from the app at any time. Deleting a local session does not delete or change the account held by the provider.

5. Diagnostics, clipboard, notifications, and storage

Technical diagnostics remain local and are not sent to the developer automatically. They may contain the source host, processing messages, time, and failure details. They are shared only if the user deliberately copies or sends them.

The app reads clipboard text only after the user taps the paste action. Notifications show download progress when permission is granted. Storage access is used to save and open requested media. On older Android versions the app may request the legacy storage permission needed to publish a file.

6. Extractor updates

If the user manually requests an extractor update, the app contacts GitHub to retrieve official release information, the download, and its checksum. GitHub receives the usual network information and processes it under its privacy statement. The app verifies the checksum before installing the update and keeps a local rollback copy.

7. Purchases, advertising, and third-party SDKs

Google Play processes voluntarily submitted ratings and review text publicly, or privately in closed tests. Reviews can be deleted through the Google Play or Google account.

The planned Google Play launch version is funded by two restrained banner placements and offers the one-time, non-renewing purchase “Remove ads.” Closed test versions use only official Google test ads and generate no advertising revenue.

Reel Downloader is intended exclusively for adults aged 18 or older. Before previewing, downloading or signing in to a provider, the user confirms that they are at least 18. No date of birth is collected. Only this choice is kept in the app’s private storage, excluded from Android backup, and it can be changed. Without confirmation, these features, advertising and purchase offers remain blocked. For confirmed adults, Google UMP updates the consent status required in the relevant region. Privacy and advertising options remain accessible in the app.

Google Mobile Ads and the User Messaging Platform may, where permitted by age, region, and consent, process network and device data, app/advertising identifiers, diagnostic, consent, ad, and interaction events, and security and fraud-prevention data. Reel Downloader does not provide download links, media titles, files, provider cookies, or local history to the advertising SDK. No ad request is made without confirmed 18+ access.

Purchases are handled by Google Play. Once the product is activated, the app sends the product ID, package name, purchase token, and purchase state over an encrypted connection to the developer’s purchase-verification service. The service checks the entitlement through the Google Play Developer API and retains only the data required for verification, restoration, cancellation, refund, abuse prevention, and legal records. The developer does not receive full payment details. A confirmed purchase suppresses ad requests; pending or unverifiable purchases block advertising as a precaution.

8. Security, retention, and deletion

The app blocks cleartext network traffic and uses Android’s private app storage for settings, local history, diagnostics, and saved provider sessions. No security measure can eliminate all risk, especially when a third-party session is stored on a device.

Private app data remains until the user deletes it, clears app storage, or uninstalls the app. Shared downloaded files remain until the user deletes them. The developer normally cannot remotely identify or delete local-only data because it is not held on a Reel Downloader server.

9. International processing

Source providers, GitHub, Google Play, or other services selected by the user may process data in countries outside the user’s country. Their own privacy policies and transfer safeguards apply to that processing.

Processing required to provide user-requested app functions, the purchase and its verification, and contractual or pre-contractual requests is based on Article 6(1)(b) GDPR. Where consent is required for advertising or access to a device, processing is based on Article 6(1)(a) GDPR; it can be changed or withdrawn for the future in the privacy and advertising options. Security measures, fraud prevention, local error diagnostics, and other support requests are based on Article 6(1)(f) GDPR; the legitimate interest is the secure, abuse-resistant, and reliable operation of the app.

Recipients are limited to the source providers selected by the user, GitHub when the user manually requests an extractor update, Google for distribution, advertising, consent, and purchase verification, and STRATO as the email service provider when support is contacted. For email requests, the sender address, message content, and technical delivery data are processed until the request is resolved; statutory retention duties may require longer storage. See STRATO’s Privacy Policy for further information.

Subject to the legal requirements, users have rights of access, rectification, erasure, restriction, data portability, and objection. Users may also lodge a complaint with a data protection authority; the competent authority is generally the State Commissioner for Data Protection and Freedom of Information of Baden-Württemberg, Germany. The developer cannot remotely apply these rights to data held only on the device because the developer has no access to it. On-device deletion options are described in section 8.

11. Questions and changes

Privacy questions can be sent to info@diligo.online. This policy will be updated when the app’s data practices change. The effective date above identifies the current version.