Privacy Policy
What HyperFrames collects, the model providers your prompts and images pass through, and how to delete your data.
Last updated: 2026-06-11
Introduction
HyperFrames ("we", "us") lets you generate video from a text prompt or an image by routing your request to leading AI video models (Kling, Google Veo, Wan and others). This policy explains exactly what we collect, who processes it on our behalf, and how you stay in control of it. We sell nothing about you.
What we collect
- Account information — your email address, and your name and profile photo if you sign in with Google or GitHub. Authentication is handled by better-auth.
- Prompts and uploaded images — the text prompts you write and any images you upload to drive a generation. These are the core input to the product.
- Generated videos — the videos produced from your prompts, kept in your library so you can download and reuse them.
- Usage data — which models you use, credits spent, generation history, and basic interaction logs used to operate the service and prevent abuse.
- Payment information — handled entirely by Stripe. We never see or store your full card number; we store only a customer reference and the records needed to apply credits to your account.
- Cookies — a session cookie to keep you signed in and a locale cookie to remember your language. We do not use third-party advertising cookies.
Where your prompts and images go (third-party processors)
HyperFrames is a routing layer over third-party generative video models. To produce a video, your prompt and any uploaded image are sent to the upstream model provider that runs the model you selected. We use these processors:
- fal.ai, Kie.ai, and Replicate — inference providers that run the generative video models. Your prompt and images are transmitted to whichever of these runs the model you chose, so it can generate your video.
- Cloudflare R2 — object storage where your generated videos and uploaded images are stored.
- Stripe — payment processing and billing.
- better-auth with Google and GitHub OAuth — account sign-in.
- Resend — transactional email (sign-in, receipts, account notices).
Each provider processes your data only to perform its function. We choose providers that operate under their own privacy and security commitments, but once a prompt reaches an upstream model provider, that provider's handling of the input is governed by its own terms.
How we use your information
- To generate, store, and deliver your videos.
- To track and apply your credit balance, and to auto-refund credits when a render fails.
- To process payments and send receipts and account notices.
- To operate, secure, and improve the service and to detect abuse.
Data retention
- Generated videos and uploaded images remain in your library on Cloudflare R2 until you delete them or delete your account.
- Account and billing records are kept while your account is active and for as long as needed to meet legal and accounting obligations.
- Prompts you send to upstream providers may be retained by those providers per their own policies.
Your rights and data deletion
You can access and export your data, delete individual generations, or delete your entire account from your settings. Deleting your account removes your stored videos and uploads. To request deletion or ask a privacy question, email [email protected].
Data security
Data is encrypted in transit. Access is restricted and reviewed. No system is perfectly secure, but we work continuously to protect your information.
Changes to this policy
We may update this policy. Material changes are reflected by the date at the top of this page, and where appropriate we'll notify you in the product.
Contact
Questions about privacy? Email [email protected].