Privacy Policy
Effective 22 September 2026
Reelopedia saves short-form videos you share to it and organises them automatically. To do that it has to store the links you send and the text it derives from them. This page sets out exactly what is kept, who else sees it, and how to get rid of it.
This policy covers the Reelopedia Android application and its backend
service at api.reelopedia.app. In this policy,
"Reelopedia", "we", "our", and "us" refer to the operator of the app, whose
registered developer details are held by Google Play.
What the app collects
Account information
You can sign in either with your Google account or by creating an account with an email address and password. Either way the app receives and stores your email address, display name, and the account identifier issued by Firebase Authentication.
If you sign in with Google, Reelopedia never receives your Google password. If you create an account with a password, that password is handled entirely by Firebase Authentication — it is never sent to or stored on Reelopedia's own server, and nobody operating this service can read it. The same is true of a password you add later from Settings → Set a Password to an account you first created with Google.
Email accounts have to be verified before they can be used. A six-digit code is sent to the address you gave, and the code and its expiry are stored until it is used. An account that is never verified is deleted automatically after seven days.
Content you save
When you share a video or photo post to Reelopedia — from Instagram, YouTube, X, Facebook, or TikTok — the app stores the link and retrieves publicly available information about it: its caption or text, the author's username, its images or thumbnail, its view count, and its duration.
If you add your own note or tags when saving, those are stored with the video and are also sent to the categorisation service described below, because they are the strongest signal about why you saved it.
Information derived from that content
To categorise a video, the service analyses it and stores what it finds:
- On-screen text read from video frames or post images
- A transcript of the spoken audio
- A summary, description, tags, and category generated from the above
- A numeric representation of the content, used to power search and to detect duplicates
The video file itself is discarded after processing. Only the derived text and the thumbnail are retained.
Subscription information
If you buy a subscription, Google Play handles the payment. Reelopedia never sees your card or payment details. It stores only the purchase token and product identifier Google returns, so it can confirm with Google that your subscription is still active.
Notifications and diagnostics
The app stores a notification token so it can tell you when a video has finished processing. It also sends crash reports to Firebase Crashlytics when something goes wrong, which include device model, operating system version, and the technical details of the failure.
Consent record
The date and time you accepted this policy and the Terms of Service is stored, so you are not asked again unnecessarily and so you can be re-asked if these terms materially change.
What the app does not collect
Reelopedia requests only two Android permissions — internet access and permission to show notifications. It has no access to your location, contacts, camera, microphone, messages, or the contents of any other app's screen, and it does not track you across other apps or websites.
One clarification about storage, because "no file access" would not be
accurate. When you tap Save Media on a video, the app
writes that one file into Movies/Reelopedia or
Pictures/Reelopedia on your device, so it appears in your
gallery. That is the only thing it writes, it happens only when you ask for
it, and the app cannot read your existing photos, videos,
or any other file on your device.
Who your data is shared with
| Recipient | What they receive | Why |
|---|---|---|
| Supabase | Everything stored by the service — your account record, your saved videos, and all text derived from them — plus the thumbnail images | Hosting the database and the image storage the service runs on |
| Google Firebase | Email, display name, account identifier, notification token, crash reports | Sign-in, push notifications, crash diagnostics |
| Google Gemini API | A saved video's caption, on-screen text, transcript and a few frames; the note and tags you added; the folder names already in your library; and, for a YouTube link, the link itself. Also the questions you type into search, with the titles and descriptions of the videos that matched | Generating the category, summary, and tags, and answering your search questions |
| Google Play Billing | Purchase token and product identifier | Verifying that a subscription is active |
| Brevo | Your email address, and the verification code being sent to it | Delivering account verification emails |
| Hetzner | Everything the service processes passes through this server | Hosting the application server itself, in Germany |
Speech transcription, on-screen text recognition, and search indexing all run on Reelopedia's own server. That content is not sent to a third party for those steps. The two steps that do involve an outside service are categorising a saved video and answering a search question, and that service is Google Gemini.
How Google's AI service handles it. Reelopedia uses the no-cost tier of the Gemini API. Under Google's terms for that tier, the content sent to it and the answers it returns may be used to improve Google's products, and may be reviewed by people at Google, who see it with the account, key and project details removed. Reelopedia will move to the paid tier of the same service, where Google does not use this content to improve its products, as the service grows — and this page will say so when it does.
The note on a saved video is optional. Leave it empty and nothing you wrote is stored or sent; the video is still categorised from its own content.
One thing to be aware of about thumbnails. Thumbnail images are stored at unlisted public web addresses so the app can display them quickly. They are not linked from anywhere and cannot be browsed or searched, but anyone who obtains the exact address of a thumbnail could view that image without signing in. Everything else — your account, your saved videos, and all text derived from them — requires a valid sign-in to access.
Your data is not sold, rented, or shared with advertisers. It is not shared with anyone else except where the law requires it.
How long it is kept
Saved videos and everything derived from them are kept until you delete them or delete your account. Account information is kept for as long as the account exists. Crash reports are retained by Firebase Crashlytics according to Google's own retention schedule.
Deleting your data
You can delete an individual saved video from inside the app at any time.
You can delete your entire account from Settings → Delete account in the app. This permanently removes your account record, every video you have saved, and everything derived from them. It cannot be undone.
If you cannot access the app, email the address below from the account's email address and the deletion will be carried out for you.
Getting a copy of your data
Settings → Export produces a complete copy of your saved videos and everything derived from them, as JSON or CSV. This is available on every tier, including the free one — getting your own data back out is not a paid feature.
Depending on where you live you may also have the right to ask what is held about you, to have it corrected, to have it deleted, and to object to how it is handled. The export and delete-account features above cover the first three directly and instantly; for anything else, or if those are not working for you, write to the address at the bottom of this page.
Security
Traffic between the app and the server is encrypted in transit. Access to your data requires a valid sign-in token issued by Firebase. No system is perfectly secure, and this is a single-developer project rather than an audited enterprise service — please weigh that when deciding what to save.
Children
Reelopedia is not directed at children under 13, and accounts are not knowingly created for them. If you believe a child has an account, contact the address below and it will be removed.
Changes to this policy
If this policy changes in a way that materially affects how your data is handled, the effective date above will change and you will be asked to review it the next time you open the app.
Contact
Questions about this policy, or requests relating to your data, go to support@reelopedia.app.