ReelWatchQueue Privacy Policy · Updated 2026-07-22

A short note on your data.

ReelWatchQueue does not collect, transmit, or share any personal information.

ReelWatchQueue is an offline watchlist and rating log for films, series, documentaries, anime and shorts — you queue what you mean to watch, log each sitting with a rating, a mood and a note, and review the patterns on a twelve-week grid. The sections that follow describe, in plain language, what the app does and does not do with the things you type into it.

I · Collection

Information we collect

None. The app has no sign-up, no login, no email capture, and no identifiers of any kind. Nothing you type is sent anywhere.

II · Storage

What lives on your device

For the app to work, the following is kept in the operating system's local storage — a local Hive database plus the platform's standard preference store — on your phone, and nowhere else:

None of it is uploaded. Uninstalling the app removes every byte.

III · Permissions

What the app asks for

ReelWatchQueue requests no runtime permissions. It does not ask for camera, microphone, location, contacts, photos, storage, or notification access, and none of those permissions are declared in the shipped Android manifest or the iOS property list.

The Android INTERNET permission is present only in the debug build, where the Flutter tooling requires it for hot reload. It is not declared in the release manifest, and the app contains no networking code in any build.

IV · Network

What goes over the wire

Nothing. The app is fully offline: no HTTP client, no socket code, no remote configuration, no crash reporting, and no update check. It works identically in airplane mode.

The one exception worth naming: the "Share your record" button hands a short block of plain text — your totals — to your device's own share sheet. You choose the destination app, and that app's own privacy policy governs whatever happens next. ReelWatchQueue itself sends nothing.

V · Third parties

Who else is involved

No one. There is no analytics SDK, no advertising SDK, no crash-reporting SDK, and no attribution SDK.

The app is built with Flutter and uses these open-source packages purely for on-device functionality: hive and hive_flutter (local database), shared_preferences (first-run flag), provider (state management), fl_chart (charts), flutter_animate, confetti, icons_plus, gap, collection, intl (UI, icons, formatting), and share_plus (the system share sheet described above). None of them contact a server on the app's behalf.

VI · Children

Younger readers

Because ReelWatchQueue collects nothing and transmits nothing, it poses no data-collection risk to children, and it is not directed at children in particular. No personal information is knowingly or unknowingly gathered from users of any age, so there is nothing for a parent or guardian to request the deletion of beyond uninstalling the app.

VII · Your rights

What you can do

Your data never leaves your device, so you control it directly. Edit or delete any queue entry from the title's detail screen, remove a title from the queue with a swipe, and uninstall the app to delete the local database and preference store outright — every title, log entry, setting and badge goes with it.

There is no backup on our side to request, correct, or erase, because there is no server.

VIII · Revisions

Changes to this policy

If anything in this policy changes, the date at the top of the page will be revised, and material changes will appear in the app's release notes. Because the app ships no remote content, any change arrives with an app update.


Questions, corrections, or concerns are welcome. Write to [email protected].
© 2026 ReelWatchQueue