Privacy Policy

1. Information we collect

• Account information — email address, and authentication identifiers if you sign in via a third-party provider.
• Billing information — processed by our payment processor (Stripe); we do not store full card numbers.
• Usage metadata — which model and provider a request was routed to, timing, cost, and status of each API call, used for billing, routing decisions, and the dashboards under /usage and /logs.
• Request content — prompts, reference files, and generated outputs pass through our routing layer to fulfil your request, and we keep a copy. For text (chat) requests we store the full message array and the model's reply. For image, video, audio and other media requests we store the request parameters you sent (including the prompt and any reference-file URLs). We also copy generated outputs, and in some cases input media, into our own storage. This is what powers the request logs under /logs, which only your account (and our staff, for support, billing and safety review) can see. See Data Privacy & Logging for the technical detail, and section 4 below for how long each kind of data is kept.
• Content you save — files and settings you choose to keep in Studio, such as uploaded reference assets and saved elements or voices, plus anything you post to the community or attach to a review.
• Support communications — anything you send us via email or Discord.

2. How we use information

We use this information to operate and bill for the service, route requests to the right model provider, detect abuse, and communicate with you about your account. We do not sell your personal information.

3. Sharing with model providers

To fulfil a request, the content of that request (prompt, reference files) is sent to the underlying model provider you selected or that our router selected on your behalf (e.g. OpenAI, Google, Kling, MiniMax, and the other providers listed on /models). Each provider processes that content under its own terms. We do not share account or billing information with model providers beyond what's required to route and pay for usage.

4. Data retention

How long we keep your data depends on what it is:

• Usage metadata (routing, cost, timing, status) — for as long as your account is active, for billing and support.
• Prompts, replies and request parameters in your request logs — currently kept for as long as your account is active; we do not yet delete them automatically on a schedule. You can ask us to delete them at any time (section 5).
• Generated images and videos — copies hosted in our storage are deleted 30 days after generation, and the link we return stops working at the same time. You can delete them sooner yourself, or ask for a shorter lifetime when you make the request (section 5). Save anything you want to keep.
• Audio and input media kept for debugging — speech-to-text input audio and text-to-speech, music and sound-effect output audio are kept for 30 days, or 24 hours if the request sends "store": false, then deleted. Image- and video-request input references are kept for 30 days; store: false does not apply to them.
• Temporary upload staging — reference files uploaded for a single generation call are deleted after 30 minutes (the request's own 30-day debugging copy above is separate).
• Film Restorer projects — working files and results are deleted after 14 days.
• Response cache (opt-in) — expires after the time-to-live you set, 5 minutes by default and at most 24 hours.
• Content you save or post — Studio assets, saved elements and voices, review attachments and community posts are kept until you delete them or ask us to delete your account.
• Safety review records — if a prompt is flagged by our content checks, we keep an excerpt and the outcome of the review for as long as needed to enforce our Content Policy and meet legal obligations.
• Model providers — copies held by the providers who process your request are governed by their own terms (section 3), not by these periods.

5. Your rights

You can view your request logs and usage in your dashboard, and delete individual API keys and saved assets there. You can permanently delete the stored files of your generated images and videos yourself, but only 24 hours after they were generated, either in bulk from the request log or per video with DELETE /v1/videos/{id}, or have a video's or image's output removed automatically by sending "store": false (deleted 24 hours after it finishes, or after an image is generated) or "output_ttl_secs" (never shorter than 24 hours) with the request. Deleting an output removes the file from our storage and does not remove the request log entry. To access or export your account data, delete your request logs, or close your account and delete its data, email contact@zeus.rocks. Depending on where you live, you may have additional rights under laws such as the California Consumer Privacy Act (CCPA) or the GDPR; contact us to exercise them.

6. Cookies

We use essential cookies to keep you signed in and to remember basic preferences. We do not use third-party advertising cookies to track you across other sites.

7. Children's privacy

VideoRouter is not directed at children under 13, and we do not knowingly collect information from them. Separately, generating any sexual content depicting or sexualizing minors — including child sexual abuse material (CSAM) — through the Service is strictly prohibited; see our Content Policy and Terms of Service §4.

8. Changes to this policy

We may update this policy from time to time. Material changes will be reflected by updating the effective date above.

9. Contact

Synvia Corp, Newark, California · contact@zeus.rocks · Discord