Privacy policy
What information this version of RTV handles, and why.
Scope
This notice applies to the RTV website at rtv.com (also accessible through rtv-298.pages.dev) and its supporting RTV API. It describes the current discovery, submission and listing-claim features. It does not cover the independent websites you visit through source links.
Creator uploads and authorization
Creator submissions now include uploaded posters and promotional images, a synopsis, AI production notes, credits, optional website and trailer links, contact email, signing name, and authorization version/text/time. Images are stored in a private Supabase Storage bucket and are served publicly through RTV only while their submission is approved. Admin review uses the privately stored display copies. Festival images are resized in the browser before upload; RTV does not retain the original full-resolution festival image. Do not include private information in images or their metadata; approved images are public.
To limit abuse, RTV stores a keyed hash derived from the network address and request category, with request counters. Rate-limit entries older than two days are removed during later limit checks. The raw address is not stored in this rate-limit table; hosting infrastructure may still log it.
Information processed
- Browsing: our hosting infrastructure can process IP addresses, request times, browser information, requested URLs and diagnostic logs to deliver the service and investigate failures.
- Source clicks: RTV increments a listing’s outbound-click counter when you follow a source link. These counters are aggregate activity, not an authenticated user profile.
- Submissions: we store the title, source link, notes and any optional email address you provide to review your request.
- Ownership claims: we store the selected listing, email address, creator or company name and evidence link for verification.
- Public source information: we store video and creator metadata obtained from YouTube, including public engagement counts and thumbnail links.
How information is used
Information is used to operate discovery and rankings, review submissions and claims, address corrections, and maintain service reliability. Supplying an email in a form is for handling that request; it is not a newsletter signup. If you separately select the optional RTV email updates checkbox, we store your email, name, consent wording, time and submission source to send future calls for entries, festival and platform news, and event updates. Not subscribing does not affect submission or judging. You can unsubscribe through any promotional email without creating an account; necessary submission-related messages may continue. We retain consent and withdrawal records to honor your preferences and demonstrate permission.
A submission’s title, source link and relevant description may become public if it is accepted. Submission and claim email addresses are not part of the public ranking response. Do not put passwords, API keys, payment information or sensitive personal details in forms.
Service providers and external sources
RTV uses Cloudflare for website/API delivery and operational logs, Supabase for database storage, and Resend for email delivery. We record email content, recipient, delivery status and errors for administration. These services may process information outside your country. Their own privacy notices describe their processing practices: Cloudflare and Supabase.
YouTube thumbnails load from external image servers, which can receive ordinary network request information. Following a video link opens its source platform, where that platform’s privacy and cookie practices apply. See Google’s Privacy Policy.
Cookies, browser storage and retention
The public RTV frontend does not intentionally set advertising cookies or save your form entries in browser storage. Search and tab choices are kept only in page memory. Infrastructure providers may use technical mechanisms for security and service delivery.
Submitted records and indexed metadata are currently kept in the service database; this version does not provide an automatic account-deletion feature or a fixed automatic deletion schedule for submitted records. Diagnostic-log retention depends on hosting configuration. Contact RTV to request review, correction or deletion of information associated with you.
Your choices and requests
You may browse without submitting an email, choose not to follow external links, and contact RTV about access, correction or deletion. We may need enough information to verify that a request relates to you or your work. Applicable privacy rights depend on your location.
Send privacy requests to hello@rtv.com, with “Privacy request” in the subject. Include the relevant listing or submission details, but do not send passwords or credentials. Material changes to this notice will be reflected in the date on this page.
YouTube discovery choice
RTV uses YouTube API Services in its separate discovery collection. You can browse creator listings without loading that collection. Loading YouTube discovery requires agreement to the privacy notice and YouTube terms; the choice lasts only for the current page. External thumbnail requests are made only after that choice.
Festival submissions
Direct festival entries include contact email, authorized submitter name, film information, private viewing link and optional password, eligibility information, consent version and time, and optional showcase permission and its conditions. RTV uses them to administer entries, conduct review and contact filmmakers. Private viewing credentials and contact details are not published. Submitted publicity materials may be displayed only within the recorded permission. Earlier interest-only submissions do not authorize full-film playback. Full-film rights require a separate recorded opt-in. For correction, withdrawal or deletion requests, contact hello@rtv.com with the submission reference. Do not include your screener password in a public message.
Film profiles and audience activity
Approved publicity materials may appear on credited Film Profiles and festival discovery pages under the recorded permission. Contact email, student evidence and private screener passwords are not published. RTV counts profile visits and audience votes, using a hashed network identifier for rate limits; these counts are not video plays. Public showcase players contact YouTube or Vimeo only after a visitor chooses to load them. For removal or permission withdrawal, contact hello@rtv.com with the film reference.
RTV Originals application information
For Originals applications, RTV collects project descriptions, names, email addresses, country, production plans, budget information, portfolio links, submitted PDFs and application acknowledgements. We use this information to assess projects, request further materials, communicate decisions and administer production milestones. Internal notes, ratings, reviewer labels and payment records are available only to authorized administrators.
Application PDFs are stored privately and are not published as Festival profiles. Selected projects need a separate agreement before public use of film content. Supabase provides database and document storage; Cloudflare handles the website and requests; our existing email provider delivers application messages. Service processing may occur outside your country.
Private material invitations expire and should not be forwarded. Request logs and rate-limit identifiers help prevent abuse. Contact hello@rtv.com to request access, correction, withdrawal or deletion, subject to legitimate operational and legal retention needs. Applications do not subscribe you to marketing email.
RTV Watch
RTV records verified sign-in email, film metadata, order amounts and price versions, payment references, rights confirmations, upload status and editorial review history. Sign-in tokens are stored hashed and expire. External players connect to YouTube or Vimeo after you choose to load the player; Cloudflare Stream receives direct RTV-hosted video uploads and playback connections; Stripe processes payment details; our email provider delivers requested sign-in links. RTV does not store full raw video in Supabase or publish private Festival screener details. Playback-start counts use a daily salted hash derived from connection information to limit duplicate counts. Counting records are retained for approximately 32 days. For rights or account requests, contact hello@rtv.com.