Privacy Policy

ReelSaveHub is built around a simple principle: the less of your data we hold, the less there is to protect, lose, or misuse. There's no account to create, no profile to build, and no media stored on our servers. This page explains, section by section, exactly what that means in practice — what little we do handle, what we deliberately don't, and how the one feature that touches something genuinely sensitive (your own private content, via a session cookie) is handled.

ReelSaveHub's backend processes requests to do its job, but doesn't build a record of who you are.

When you submit a request, our rate limiter briefly holds your IP address in memory — only for the duration of the current rate-limit window — purely to enforce a per-IP request cap and keep the service available for everyone. It's never written to a database, a log file, or any persistent store, and it's discarded automatically once the window expires.

Beyond that in-memory rate-limiting use, we don't currently log or store request-level data at all.

To be equally clear about what we don't do:

• No accounts, sign-in, or user profiles — ReelSaveHub doesn't ask for a username, email address, or password to use the public downloader.
• No storage of Instagram credentials. The only feature that touches an Instagram credential-like value at all is the separate own-private-content tool, and even there, nothing is stored — see the dedicated section below.
• No server-side storage of Instagram media. When you paste a link, our backend fetches the corresponding media directly from Instagram's own content delivery network and streams it straight to your browser. It's never saved, cached, or copied onto our servers at any point.
• No advertising or tracking cookies, and no third-party analytics or ad-network scripts of any kind.

A small amount of information is stored locally in your browser — never sent to our servers — purely to remember your preferences between visits:

• Your light/dark theme choice.
• Whether you've installed ReelSaveHub as an app, or dismissed the install prompt, so we don't ask again on every visit.

Because none of this is a tracking or advertising cookie, and none of it is shared with us or anyone else, ReelSaveHub doesn't show a cookie-consent banner — there's nothing here that requires one. If you'd rather not keep this locally, clearing your browser's site data for ReelSaveHub removes it.

ReelSaveHub's installable app also caches its own interface files (the code that renders the page) on your device for faster loading and offline access to the app shell. It does not cache Instagram media, or responses from our API, on your device.

• The cookie you paste is used only in memory, only for the single request you submit.
• It is never written to a database, a log file, or any cache, at any point.
• The browser session created to use it is closed at the end of that one request, and the cookie is discarded with it.
• We verify, on our server, that the content you're requesting actually belongs to the account the cookie authenticates as, before returning anything.
• This feature isn't linked from our main navigation and isn't indexed by search engines — it's there if you know to look for it, not pushed on anyone.

ReelSaveHub keeps its list of third parties short, on purpose:

• Supabase, our database provider, is configured to host anonymized request logs — but as described above, that logging isn't active yet, so Supabase doesn't currently receive any data from ReelSaveHub. If that changes, this section will change with it.
• Instagram's own content delivery network, which is where the media you download actually comes from. We don't route it through, or store it on, our own infrastructure.

ReelSaveHub doesn't use any advertising networks, third-party analytics platforms, or session-replay/tracking tools.

Because ReelSaveHub doesn't create an account or a personal profile for you, there generally isn't a stored personal data record to access, correct, or delete beyond what's already described on this page — the request-and-delete process that makes sense for a service with accounts doesn't have much to attach to here. In practice, your choices are:

• Stop using the service at any time — no account to close, nothing to cancel.
• Clear your browser's local storage/site data for ReelSaveHub to remove your saved theme preference and install-prompt history.
• If you've used the own-private-content feature, there's nothing to request deletion of afterward — the session cookie you provided was already discarded at the end of that single request, as described above.

If you believe we're handling something incorrectly, or have a question this page doesn't answer, contact us — see below.

ReelSaveHub is not directed at children under 13, and we do not knowingly collect information from anyone, regardless of age — in practice this is straightforward, since collecting personal information isn't part of how the service works in the first place.

If this policy changes in a way that matters, we'll update this page and the "Last updated" date above. We'd encourage checking back occasionally if you're a regular user, rather than assuming this page never changes.

Questions about this policy? Reach out via the contact page.