Privacy policy
Last updated 3 August 2026
Written to describe how Reelgate actually works, not by a lawyer. It has not been through legal review and is not a binding agreement. Have counsel review it before you rely on it.
Two kinds of people
Reelgate holds data about two groups: account holders, who sign up and own a workspace, and viewers, who are sent a link. Viewers never create an account, and most of what is recorded about them exists so the workspace owner can see who watched what.
What we hold about account holders
Your email address, your display name, and the workspace you own — its name, branding and plan. Payment records hold the amount, currency, plan and the processor's reference, never your card number.
What we hold about viewers
For each watch session: which link was opened, when, how far through the video the viewer got, and which seconds of it were actually watched. Also the browser, operating system and device type parsed from the user-agent string, and an approximate country and city.
Email addresses of viewers
A link set to specific people records the address the one-time code was sent to, so the owner can see who used it. Password-protected and open links record no address at all, and sessions on them are counted as anonymous throughout the analytics.
IP addresses are hashed, not stored
A viewer's IP address is used to rate-limit password and code attempts. It is hashed before it is written down, and the raw address is never stored. That is enough to stop someone guessing a password, and not enough to look up where a particular person was.
Watch analytics
The player reports which spans of the video were watched. Unique watch time is the union of those spans, so replaying a scene does not inflate it. The result is aggregated per video into five-second buckets. This is what makes the heatmap, and it is visible to the workspace owner only.
Who else processes this data
Supabase hosts the database and authentication. Bunny.net stores and delivers the video. Paymob processes payments. Resend delivers transactional email. Each sees only what it needs to do its job.
What is not collected
No advertising or cross-site tracking. No third-party analytics script. No tracking pixels in the emails Reelgate sends. Reelgate does not read the contents of your videos.
How long it is kept
Account and video data lives until you delete it. Watch events accumulate as sessions happen; a retention policy for them is still being finalised and will be documented here before general availability rather than applied quietly.
Viewers asking about their data
Reelgate is a processor here, not the controller — the workspace owner decides who gets access and holds the relationship with you. If you were sent a link and want your record removed, reply to the email that delivered it. If the owner does not respond, contact us and we will pass it on.
Security
Every table is protected by row-level security, so one workspace cannot read another's rows even if a query is wrong. Passwords on share links are hashed with Argon2id; one-time codes are hashed with a separate secret so that a leak of one does not compromise the other. Video is delivered over signed, short-lived URLs.