Privacy Policy

1. Controller and contact

The controller of data related to InRoll is ZARAZWSIECI MIKOŁAJ BOŃKOWSKI. Privacy contact: [email protected].

InRoll does not require a user account.

2. Photo library and local data

InRoll is used to review and organize photos and videos made available to the app by the user. Core gallery analysis runs on the device.

User decisions, gallery index data, cleanup progress, similar-photo groups and optional media-location metadata are stored locally in the app’s private database.

3. Photo and video access

The app requests photo/video library access only to display media, create cleanup sessions and perform actions selected by the user.

Where the operating system supports limited or selected-photo access, InRoll can work with that subset. Users can change access later in system settings.

4. Deletion and system trash

Swiping an item does not delete it. An item marked for deletion is first shown in Review, and the final move to Trash/Recently Deleted requires a separate user action and operating-system confirmation.

Retention and recovery rules for system Trash/Recently Deleted are controlled by the operating system and Photos/Gallery app.

5. Similar Photos

Similar-photo suggestions are calculated locally on the device. InRoll does not send photos, videos, thumbnails, filenames, library asset identifiers, EXIF data, similarity vectors or similarity scores to its own server.

A suggestion does not automatically select or delete any file. The user always makes the final decision.

6. Location from media metadata

Optional place search uses only coordinates already stored in metadata of an accessible photo or video. InRoll does not request the device’s current location and does not track the user by GPS.

If the user chooses place naming, the operating system reverse-geocoding service may translate stored coordinates into a place label. Depending on the platform, that system service may use network resources. The photo or video file itself is not sent for place naming.

7. Purchases and RevenueCat

If Pro features are enabled, payment is processed by Apple App Store or Google Play, while RevenueCat may manage purchase entitlements.

Payment providers may process product, transaction, storefront and basic device/app information needed for billing and entitlement restoration. InRoll does not send photo-library content or photo metadata to them as part of purchase handling.

8. Network, advertising and analytics

Core gallery features do not use a media-upload backend. The app does not include an account system, advertising SDK or general behavioral analytics SDK.

Network access may be used by Apple/Google/RevenueCat for purchases. On iOS, if the user explicitly opens Full Preview for an item stored in iCloud, the Photos framework may download that selected item from iCloud to the device.

9. Retention and deletion

InRoll working data is stored locally until the user removes it, clears app data or uninstalls the app in accordance with operating-system behavior.

Purchase records held by Apple, Google or RevenueCat are subject to the relevant provider’s retention rules.

10. User rights

Where personal data is processed, users may exercise rights available under the GDPR, including access, rectification, erasure, restriction, objection and the right to lodge a complaint with a supervisory authority.

Privacy requests can be sent to [email protected].

11. Changes to this policy

This policy may be updated when InRoll features, providers or data practices change. The current version is published at this address.