Privacy Policy

What this policy covers

This policy explains how text2shader collects, uses, and shares information when you use our website and rendering service. It also explains what happens when you delete a render.

Information we collect

Google account and sign-in information

When you sign in with Google, we receive your name, email address, profile image, and Google account identifier. We keep the account identifiers, authentication tokens, and session records needed to sign you in and protect your account. We request only the openid, email, and profile permissions.

Prompts, scenes, and renders

We store the prompts you submit, the scene files and shader source created from them, the generated video, poster, and embed files, and basic records such as render status and creation time. Prompts may contain personal information if you include it, so please do not put sensitive personal information in a prompt.

Credits and purchases

We keep a credit ledger showing grants, purchases, render charges, and returned credits. When paid credit packs become available, Polar will handle checkout as the merchant of record. We expect to receive the purchase and transaction details needed to add credits and provide support; Polar handles payment details under its own privacy policy.

[REVIEW] Confirm the exact Polar checkout fields received and update this paragraph before paid purchases launch.

Technical information

Our sign-in and hosting systems may process information such as your IP address, browser or device details, session cookie, request times, and security logs when you use the service. We also record operational and billing metadata about generation requests, such as usage, cost, timing, and outcome.

How we use information

We use this information to:

• create and manage your account and sessions;
• turn your prompts into scenes and renders;
• host, display, download, and delete your renders;
• maintain your credit balance and process purchases;
• operate, secure, troubleshoot, and improve the service; and
• meet legal obligations and enforce our terms.

Public render URLs

A completed render is hosted on our CDN at public embed, video, and poster URLs. No text2shader sign-in is required to open those URLs. Anyone who receives a URL may view, copy, or share the render. The embed file contains the scene data and shader source, which are also public by URL. Do not create or publish material you want to keep private.

When information is shared

We use service providers to run text2shader:

• Google provides account sign-in under its Privacy Policy.
• Cloudflare provides website delivery, databases, workflows, rendering infrastructure, object storage, and the public CDN. Cloudflare explains its practices in its Privacy Policy.
• OpenRouter receives your prompt, supporting scene data, and preview images and routes them to a generation provider. The selected provider also processes that material to return a result. See OpenRouter's Privacy Policy and provider data policies for details.
• Polar will process checkout and related purchase information as merchant of record under its Privacy Policy.

These providers handle information under their own terms and privacy policies. We may also disclose information when required by law, to protect people or the service, or as part of a merger, acquisition, financing, or sale of the business.

[REVIEW] Confirm the production OpenRouter routing, prompt-logging, training, and provider-retention settings. Provider retention policies can vary. Also confirm whether analytics or advertising services will be used and whether a no-sale statement is accurate.

Retention and deletion

We keep account, render, and credit records while needed to provide the service, maintain accurate transaction records, resolve disputes, secure the service, and meet legal obligations.

When you delete a render, we remove its hosted embed, video, poster, and related objects from our origin storage after any active publication has stopped. The deleted render no longer appears in your account. When cleanup finishes, its hosted files are no longer served. Copies that other people have already downloaded or reshared are outside our control. Limited database records may remain where needed for security, transaction integrity, legal compliance, or backup recovery.

[REVIEW] Set concrete retention periods, define backup deletion timing, and confirm exactly which database records remain after render or account deletion.

Your choices

You can delete an individual render from your account. You can also revoke text2shader's Google access from your Google Account. Depending on where you live, you may have rights to request access to, correction of, or deletion of your personal information.

[REVIEW] Add the account-deletion process and a monitored privacy contact email before launch.

Children

[REVIEW] Set the minimum age and the process for handling information submitted by a child before launch.

Security

We use technical and organizational measures intended to protect information. No method of storage or transmission is completely secure.

Changes to this policy

We may update this policy as the service changes. We will post the revised policy here and update the date above.

[REVIEW] Decide how users will be notified of material changes.

Contact

Questions, privacy requests, and account deletion: support@text2shader.com.