Privacy Policy

Last updated: October 13, 2026

Who we are

ReelMint Studio (“ReelMint”, “we”) is a video-creation studio at reelmint.io that helps creators plan, generate, edit, and publish short-form videos. This policy explains what data we collect, why, and how you can remove it.

Data we collect

  • Account data — your name, email address, and password hash (or your Google account email if you sign in with Google), plus your workspace membership and role.
  • Content you create — scripts, scenes, images, voiceovers, and rendered videos you produce in the studio, stored so you can edit and publish them.
  • API keys you provide — if you connect your own AI provider keys, they are encrypted at rest and used only to run generations you request. They are never shown back in full or shared.
  • Usage and log data — standard server logs (request paths, timestamps, errors) used for reliability and abuse prevention.

Google user data

If you connect a Google account, ReelMint requests only the scopes it needs to do what you ask:

  • Sign-in (openid email profile) — verifies who you are and creates your session. We store your email and display name.
  • YouTube publishing (youtube.upload) — uploads videos you created in the studio to your own YouTube channel, only when you press publish.
  • YouTube channel info (youtube.readonly) — reads your channel name and the status of videos the studio uploaded, so the app can show what was published.
  • YouTube Analytics (yt-analytics.readonly) — reads view and engagement metrics for your channel to show performance of your published videos inside the studio.
  • YouTube comments (youtube.force-ssl) — reads comments on your own videos to surface content-idea suggestions inside the studio. We never read or write comments on any channel other than yours, and never post on your behalf.

We store the OAuth refresh token for your connection, encrypted, scoped to your workspace. We do not read your Gmail, contacts, Drive, or any data outside the scopes above. We do not sell Google user data, use it for advertising, or allow humans to read it except with your consent, for security, or where required by law.

ReelMint’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Publishing to YouTube uses YouTube API Services. By connecting a YouTube account you also agree to the YouTube Terms of Service, and Google’s Privacy Policyapplies to Google’s handling of your data.

Instagram user data

If you connect an Instagram professional (Business or Creator) account, ReelMint uses Instagram’s API with Instagram Login and requests only what its features need:

  • Profile and media (instagram_business_basic) — your account ID, username, profile picture, follower and media counts, so the studio can show which account is connected.
  • Publishing (instagram_business_content_publish) — posts reels you created in the studio to your account, only when you press publish or at a time you scheduled.
  • Insights (instagram_business_manage_insights) — reads performance metrics (such as views, reach, and interactions) for your account and posts to show them in the studio’s analytics.
  • Comments (instagram_business_manage_comments) — if you turn on Auto-DM for a reel, receives comments on that reel to match them against the trigger you set, and posts the public reply you configured. We store the commenter’s Instagram user ID, username, and the comment needed to run and show that automation.
  • Messages (instagram_business_manage_messages) — sends the private replies and follow-up messages you wrote to people who commented on your reel or replied in that conversation. We never send unsolicited messages.

We store the access token for your connection, encrypted, scoped to your project. If you enable AI-written replies, the comment text is sent to the AI provider configured for your workspace to draft the reply. We do not sell Instagram user data, use it for advertising, or share it with third parties for their own purposes. Meta’s Privacy Policyapplies to Instagram’s handling of your data.

How we use data

Solely to provide the service: authenticate you, store and render your projects, run the AI generations you request, publish to channels you connected, and show you analytics. We do not sell personal data or share it with third parties for their own purposes.

When you run an AI generation, the relevant content (e.g. your script text) is sent to the AI provider configured for your workspace (such as Google Gemini, OpenAI, Anthropic, or ElevenLabs) to produce the result you asked for, under that provider’s terms.

Cookies

ReelMint uses a single HttpOnly session cookie to keep you signed in. It expires after 30 days and is removed on sign-out.

Our marketing site (reelmint.io) uses the Meta Pixel, which sets advertising cookies and shares page visits and waitlist sign-ups with Meta Platforms so we can measure and improve our ads on Facebook and Instagram. When you create a ReelMint account, the app also tells Meta that a sign-up happened (nothing about what you do inside the app). Meta processes this data under its own privacy policy. You can opt out of ad personalization in your Facebook ad preferences or by blocking third-party cookies in your browser.

Storage, security, and retention

Data is stored on our servers with access controls per workspace; credentials and provider keys are encrypted at rest, and connections use HTTPS. We retain your data while your account is active. Backups are kept for disaster recovery and expire on rotation.

Revoking access and deleting data

Changes

We will post any changes to this policy on this page and update the date above. Material changes affecting Google user data will be communicated before they take effect.

Questions? Contact hitesh.u@brilworks.com.