Privacy Policy
Last updated: October 29, 2026
1. About ProdBeast
ProdBeast is a video review and publishing platform that helps content teams manage freelancer video submissions, review them collaboratively, and publish approved videos to YouTube. This policy covers the ProdBeast website, mobile companion app, and connected service. The mobile app lets existing account holders review workspace videos and leave feedback; uploading, billing, and YouTube publishing are website features, not features of the current mobile app. For any queries, contact us at contact@prodbeast.in.
2. Information We Collect
- Account information: Your name, email address, account identifiers, workspace memberships, and role. Supabase Auth processes your sign-in credentials and manages authentication sessions.
- Organisation profile: Your organisation's name and logo, uploaded during onboarding and stored to identify your team within the platform.
- Review content and activity: Comments, mentions, attachments submitted through supported website features, timecodes, review decisions, and version/status history, including the author and time of each action. The service also stores video names, source identifiers, versions, thumbnails, and playback metadata.
- Video content: Videos made available through your connected Drive or service storage, and copies processed by Mux for playback.
- Notifications: When you enable mobile push, we store a push token linked to your account and email, your device name or model, platform, and the registration time. Expo and Apple process the token and notification payload to deliver alerts. Payloads may include video titles, author names, comment excerpts, and a link to the video. Browser push uses a browser subscription instead.
- Technical and support data: Our infrastructure and service providers process network information such as IP addresses and request headers. Error reporting can retain error messages, stack traces, request paths, device/browser information, and related diagnostic context. Support requests contain the information you choose to send.
- Website billing: Subscription, payment-status, and billing information is processed with Razorpay for paid website services. The mobile app does not collect payment details or offer purchases.
- YouTube publish metadata: Titles, descriptions, tags, and scheduling details you provide when publishing a video.
- Website analytics: Vercel Analytics measures website usage. PostHog records website page visits, interactions, referral/campaign information, and errors. Signed-in website activity is linked to your account ID, name, email, role, organisation, and plan. Website session recording may be enabled, with form-input masking configured; visible page content can still appear in recordings. We do not send video files to PostHog as analytics events.
- Mobile analytics: The native mobile app does not embed PostHog, an advertising SDK, or session replay. Requests from the app still reach our service infrastructure, and uncaught server errors can be reported to PostHog and our own error-reporting system.
3. Organisation Structure and Access Control
ProdBeast supports organisation and personal workspaces. Access is controlled by workspace membership, roles, and project permissions. Review content and the identity of its author are available to people with access to the relevant workspace or video. Website users can also create review links, which make the linked content available to people holding the link, subject to its settings.
- Organisation administrators: Org admins may invite new members, update member names and roles, and remove members from their own organisation. They cannot access other organisations' data.
- Organisation data: Organisation name and logo are stored in Supabase (PostgreSQL and Supabase Storage respectively). Logos are stored in a public storage bucket to enable display within the platform.
4. Google Drive and YouTube — Your Own Accounts
When you connect Google Drive or YouTube on the website, you grant ProdBeast scoped access to your own Google account via OAuth 2.0. Before access is granted, Google's OAuth consent screen will display the exact permissions being requested so you can review and approve them. We store connection credentials, including OAuth tokens, and relevant file/channel identifiers and metadata to provide the connection. Drive originals are stored in your Drive; playback copies and thumbnails may also be processed or stored by our service providers.
ProdBeast uses this access solely to:
- Google Drive API: Upload, organise, read, and stream files for the connected workspace, according to the permissions you grant. Server and worker infrastructure may relay video bytes to provide playback, transcoding, or publishing.
- YouTube Data API: Publish approved videos from your Drive to your YouTube channel on your behalf, using metadata you provide.
For in-platform video playback, ProdBeast uses Mux — a third-party video streaming service. Mux processes and holds video copies and serves streams and thumbnails. Expiry is configurable and may be disabled to keep playback available; publishing a video does not guarantee immediate deletion of its Mux copy. Supported service-storage videos can also reside in Supabase Storage.
5. Google API Limited Use Disclosure
ProdBeast's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements:
- Google user data is used only to provide the video review and publishing features described in this policy — for no other purpose.
- We do not use Google data to serve advertising.
- We do not sell or transfer Google user data to third parties, except as necessary to operate the platform (e.g. streaming via Mux).
- We do not allow humans to read your Google data without your explicit request for support, or unless required by law.
- We do not use Google data to train AI or machine learning models.
6. Data Storage and Security
Account and application data (user profiles, comments, status history, organisation records) are stored in Supabase (PostgreSQL and Storage). Organisation logos and website comment attachments use public storage URLs, so a person with the URL may access them. Video delivery uses Mux or authenticated service routes and signed storage URLs, depending on the source. The website and API are hosted on Vercel, with worker infrastructure for video processing. Resend delivers email. The mobile app stores its sign-in session, workspace choice, and notification read state locally so these persist across launches. We use access controls and secure transport to protect data.
7. Data Sharing
We do not sell or rent your personal information. Data is shared only with the third-party services used to operate the platform — Supabase, Google, Mux, Resend, Vercel, PostHog, Expo, Apple (for iOS push delivery), and Razorpay (website billing). Data is also shared with authorised workspace participants or review-link recipients as described above. We do not use native mobile app data for targeted advertising across other companies' apps or websites, or share it with data brokers. We may disclose data if required by applicable law.
8. Data Retention
Account data is retained for as long as your account is active. Organisation data (name, logo, member list) is retained for as long as the organisation is active on the platform. You may request deletion of your account and associated data by contacting us. Org admins may remove members at any time; removal of membership is different from deleting an individual's account or the organisation's records. Deleting a video can retain a recovery snapshot of its metadata, comments, versions, and history; the recovery archive is configured for 30 days. This is not a backup of the original video bytes. Mux retention follows the configured expiry and deletion processes rather than publication status. Technical logs, diagnostics, and provider backups have separate retention settings; we do not promise immediate erasure from all systems. We explain applicable retention and any required exceptions when handling a deletion request.
9. Your Choices and Requests
You may access, correct, or request deletion of your personal data by contacting contact@prodbeast.in. For an organisation-managed account, the organisation administrator controls membership and workspace records; personal-data requests and deletion of the organisation's workspace are handled separately. In the iPhone app, Account → Delete account sends a deletion request: we email you within 7 days to confirm, then delete your login and personal data. Workspaces that belong to an organisation, and their videos and comments, stay with that organisation. You can disable mobile notifications in your device settings. Signing out attempts to unregister that installation from push delivery; an offline sign-out may delay this cleanup. You can also revoke ProdBeast's access to your Google account at any time through your Google Account permissions.
10. Changes to This Policy
We may update this policy from time to time. Material changes will be communicated via email or a notice on the platform. Continued use of ProdBeast after changes constitutes acceptance of the updated policy.
11. Contact
For privacy-related questions or data requests, contact:
ProdBeast
contact@prodbeast.in