Privacy Policy

This policy explains what Blinkvid processes when you create a video, how external services participate, and the controls available to you.

1. Data we collect

• Account data such as your email, profile name or image, authentication records, and security metadata.
• Creation data such as prompts, selected settings, uploaded source images, generated results, task status, and safe provider reference IDs.
• Billing data such as the selected product, provider customer/order identifiers, payment status, and credit-ledger entries. Blinkvid does not place prompts, filenames, source URLs, or source media in checkout metadata.
• Product events needed to understand whether setup, generation, download, and checkout flows work. Ordinary product analytics exclude raw prompts, filenames, media URLs, and raw provider errors.

2. AI and infrastructure processing

When you request a video, we save a short list of Blinkvid pages you visited and a general traffic source, when available, with that request. Authorized staff can review these details, prompts, and completed videos to understand and troubleshoot the creation experience.

When you explicitly request generation, Blinkvid sends the necessary prompt, generation settings, and approved source snapshot to KIE, the primary video provider. Blinkvid's active generator supports video only. APImart may receive one video fallback only after a definitive KIE rejection or confirmed terminal failure with a compatible setup. Explicit content, person, portrait, identity, consent, or safety restrictions are not retried with another provider; unknown outcomes are not resubmitted.

Cloudflare Workers AI checks uploaded images and, before they are sent to the video-generation service, assesses them together with your requested motion and instructions describing how you want to use them. OpenAI separately checks relevant prompts and images. These checks do not verify identity, age, consent, ownership, or whether an image is real or AI-generated. A rejected, uncertain, or unavailable intended-use assessment stops generation. A safety check does not itself start video generation.

Before video generation, Waffo Prompt Sift also receives the generation prompt, any negative prompt, and reference-role text for a text-only safety check. Blinkvid does not attach image or video files, media URLs, or account identifiers to this scan; information you include in the prompt is part of the text sent. Generation proceeds only after an allow decision; a pending review or unavailable check delays generation, and a block stops it. Blinkvid records the categorical decision, a text hash, the scan request ID, and retry timing in its existing safety audit records, without copying the prompt into that audit record.

Before a generated video is displayed, Cloudflare Media extracts 4–12 representative frames based on duration. When generated audio is enabled, Cloudflare Workers AI transcribes the audio. OpenAI then reviews those frames and the transcript. This is a sample review, not an inspection of every frame.

Cloudflare Workers, D1, private R2, and Queues provide application execution, database storage, private media storage/delivery, and background processing. Waffo handles hosted checkout for one-time packs and recurring plans, subscription management, and payment, renewal, and refund events. Historical Neon and Creem records may remain in isolated backup, audit, or rollback material, but neither service is part of the active request path. Each active service receives only the information needed for its role and may process it under its own service terms and Blinkvid's provider agreements.

Source images and generated results stay in private Cloudflare R2 storage. Blinkvid delivers these files after checking the owner’s login or through signed, time-limited access tied to their account. Blinkvid does not publish storage identifiers or direct public R2 file links. Removing a public Blinkvid share disables the Blinkvid page; the applicable deletion process removes the stored file separately.

When configured, PostHog receives sanitized product events and an opaque account ID, Plausible receives site measurement, and Google Ads receives origin-and-path page measurement. These analytics paths exclude raw prompts, filenames, media URLs, query strings, and raw provider errors. Resend processes email delivery, and Google processes the information needed when you choose Google sign-in.

Blinkvid records your rights and consent declaration for each upload, safety decisions, verification values derived from source files and instructions, the version of the safety rules applied, and account and generation identifiers. These records enforce safety rules and prevent an approval from being reused after the material changes. The approval record stores those verification values rather than raw prompts or signed source links. A declaration or approval record does not verify identity or prove consent. These security records are separate from source media and may remain for the applicable operational or legal period after a source file is deleted; privacy and deletion requests can be sent to support@blinkvid.net.

3. Retention and deletion

• Guest setup data stays on the current device and expires after 24 hours or explicit discard. Guest source files remain local until an authenticated, explicit generation flow needs to upload them.
• Tracked uploads that are not attached to a valid creation, and tracked sources for failed generations, are deleted within 24 hours. Source snapshots attached to a creation expire after 30 days; the completed result and non-media setup can remain, but a new source-based version then requires another upload.
• Removing a creation disables its Blinkvid public share page immediately and moves it to private Trash for seven days. Restore does not republish the former share page. Delete permanently now, or expiry of the recovery window for a terminal creation, removes its Blinkvid-stored result media and source association and clears the creation content from active product surfaces. A source object shared with another active creation remains only for that other creation's retention window.
• Billing, fraud-prevention, security, dispute, and legally required records are separate from creation content and may be retained for their applicable operational or legal period.

4. Your choices

• You can remove and restore eligible creations from My Creations, permanently delete an eligible terminal creation, review purchase and payment history, control creation sharing, and unsubscribe from marketing independently. If you have a recurring plan, you can open Settings → Subscription management to manage or cancel automatic renewal through Waffo. Cancellation stops the next renewal at the end of the current paid period; one-time credit packs never renew.
• Account deletion, creation deletion, a cash-refund request, and a rights report are separate actions. Contact support before permanent account deletion if you may qualify for a seven-day zero-use refund.

5. Rights, safety, and contact

For privacy questions, access or deletion assistance, or a likeness/copyright report, email support@blinkvid.net. A public-content report can be made without a Blinkvid account; the required details are listed in the Acceptable Use Policy.