Privacy Policy

What this policy covers

This policy explains how text2shader collects, uses, and shares information when you use our website, rendering service, or a render embedded on another website. Contact us at support@text2shader.com.

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

We keep a ledger of credit grants, render charges, and returned credits. Paid checkout is closed during early access.

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.

Product interactions and feedback

We use a first-party browser identifier to connect visits, sign-in, generation requests, result viewing and playback, optional thumbs feedback, regeneration, download requests, and embed copying. We record limited campaign, device-category, and timing information. When you sign in, these records can link to your account and the relevant renders.

These interaction records do not include typed prompt text, email addresses, IP addresses, raw browser headers, or authentication credentials. Prompts and account information are stored separately as described above. Feedback is optional and can be changed or cleared.

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;
• operate, secure, troubleshoot, and improve the service;
• understand where people have difficulty and which results they find useful; and
• meet legal obligations and enforce our terms.

We do not sell personal information or use it for advertising.

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. Every request requires zero data retention and denies provider data collection for storage or training. To lower cost, we ask our model provider to briefly cache the processed form (model activations) of our own fixed instructions and example scenes, never your prompt. The provider processes requests under zero-data-retention terms. Providers may retain non-content usage metadata. See OpenRouter’s Privacy Policy.

These providers handle information under their own terms and privacy policies. We may also disclose information when required by law or to protect people or the service.

Retention and deletion

We keep account, render, and credit records while needed to provide the service, maintain accurate accounting, secure the service, and meet legal obligations. Private render artifacts and terminal Workflow history have seven-day retention targets; expiry and cleanup can take longer. Workflow history can contain prompts and generated source and cannot be erased early per account.

Product interaction events and feedback history expire after 90 days. Expired records are excluded from product reports and current feedback; scheduled cleanup may take longer to remove them from storage. Changing or clearing a vote updates your current feedback, while earlier changes remain in its history until expiry or render deletion. Limited records remain to keep changes and one-time regeneration allowances consistent. API call logs are visible for at most 30 days, though physical cleanup can lag. Workers Logs are configured for seven-day retention. Database recovery history can retain earlier data for up to 30 days.

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. A pseudonymous render record and credit and provider-call accounting may remain after stored prompt and source are cleared.

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. Revoking Google access does not delete your text2shader account. You can delete your account from your account page. This closes access and removes your hosted work and active identity data. Pseudonymous accounting records, platform history, and copies outside our control may remain as described above. For an account closed after a confirmed underage ban, we keep a minimal token-free Google sign-in identifier and ban record to prevent re-registration. If you cannot use the account page, contact support@text2shader.com for help.

Children

Accounts are for adults aged 18 or older. Contact us if you believe a minor has provided information.

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.

Contact

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