Privacy Policy

Last updated: July 14, 2026

beGraphic ("beGraphic", "we", "us") provides an AI-assisted video editing product at begraphic.dev. This Privacy Policy explains what data we collect, how we use it, and your rights. Questions: contact@begraphic.dev.

1. What we collect

Account data

When you sign up, we collect your email address (via magic link or Google OAuth). If you sign in with Google, we receive your email address only, no profile photo, contacts, or other Google data.

Payment data

Subscriptions are processed by Stripe. beGraphic never sees or stores your full card number; we receive only a Stripe customer ID, the last four digits of your card, and subscription status.

Product data

We store the footage you upload, the prompts and style choices you make, the transcripts and edit decisions produced from your footage, and the videos you create in your projects. This data is yours, you can request its deletion at any time. Uploads and renders are stored in Amazon S3 and delivered via signed URLs.

Brand kit data

The brand choices you make, such as fonts, colors, and caption placement, are stored in our Supabase project so they can be reapplied to your later videos. Your brand kit is private to your account.

Auto Cut uploads

When you use Auto Cut, the videos you upload are stored in Amazon S3, private to your account and delivered via signed URLs. To build the transcript that drives the edit and the captions, the audio from your clips is sent to AssemblyAI for speech-to-text transcription. Your raw uploads are deleted automatically on a retention schedule (7 days after you export a cut, or 30 days if you never export it).

Usage analytics

We use PostHog to understand which features are used and how. PostHog also records session replays so we can debug UX issues. Replay runs on the whole site, including these public marketing pages, not only inside the product. Text you type into form fields is masked before it leaves your browser, so replays do not capture what you enter.

Marketing pages may include a Meta (Facebook) Pixel for ad attribution. The Pixel does not fire on authenticated product surfaces (anything under /studio).

Error monitoring

We use Sentry to catch crashes and errors. Sentry receives stack traces and minimal user identifiers (your account ID) to associate errors with your session.

2. How we use your data

  • To provide the product (render videos, store projects, charge subscriptions).
  • To send you transactional emails (sign-in links, payment receipts, render notifications).
  • To improve the product (analytics aggregates, debug logs).
  • To enforce our terms (anti-fraud, abuse prevention).

We do not sell your data, train AI models on your prompts or renders without consent, or share your project content with third parties beyond what's required to deliver the service.

3. AI model usage

When you generate a video, your prompt, style picks, and (for Auto Cut) the transcript of your footage are sent to Anthropic (Claude API) to produce the scene plan. Per Anthropic's data policy, prompts and outputs are not used to train Anthropic models when sent through the API. Renders are produced by Remotion on AWS Lambda. Code-only rendering, no third-party model inference at render time.

For Auto Cut, the audio from your uploaded clips is sent to AssemblyAI to produce a verbatim transcript. That transcript is then sent to Anthropic (Claude API, under the same data terms as above) to decide which words to keep; the cut itself is assembled and captioned by our own code.

4. Subprocessors

The third parties we share data with:

  • Supabase: auth + database (user records, projects, brand kits).
  • Stripe: payment processing.
  • AWS: render compute (Lambda) + render storage (S3).
  • Anthropic: AI scene generation + Auto Cut edit decisions.
  • AssemblyAI: speech-to-text transcription for Auto Cut (audio from your uploaded clips).
  • Resend: transactional email delivery.
  • PostHog: product analytics + session replay.
  • Sentry: error monitoring.
  • Inngest: background job orchestration.
  • Vercel: application hosting.
  • Meta (Facebook): marketing-page ad attribution only.

5. Your rights

You can:

  • Access the data we hold on you.
  • Correct inaccurate data.
  • Delete your account and all associated data.
  • Export your projects and renders.
  • Opt out of analytics or session replay.

Email contact@begraphic.dev to exercise any of these rights. We respond within 30 days.

6. Cookies

We use first-party cookies for authentication (Supabase session tokens) and analytics (PostHog visitor ID). The Meta Pixel sets third-party cookies for ad attribution on marketing pages only.

7. Data retention

We keep your data while your account is active. After account deletion, we remove personal data within 30 days. Anonymized analytics aggregates may be retained for product improvement. Stripe retains payment records as required by their financial regulations (typically 7 years).

8. International transfers

beGraphic infrastructure is hosted in the United States (AWS us-east-1, Vercel, Supabase US region). If you access the product from outside the US, your data is transferred to and processed in the US.

9. Changes to this policy

We'll notify you by email at least 14 days before any material change. Non-material clarifications may go live without notice. Check the "Last updated" date above.

10. Contact

Questions, concerns, or data requests: contact@begraphic.dev.