ST STUDIO - PRIVACY POLICY

1. What we collect

1.1 Account information

• Email address
• Username/profile information you choose to provide
• Account identifiers (e.g., user ID)

1.2 Account service records

• Account status and enabled service capabilities
• Security, continuity, and device-link records

1.3 Content you upload or publish (directory/community)

• Pipes (.tea packages) and related metadata (titles, descriptions, tags)
• Preview media and any other files included in a published .tea package
• Comments, profile content, and other User Content you post

1.4 Usage and diagnostics (Services)

• IP address, device/browser information
• Logs related to security, abuse prevention, and reliability
• Error and performance data (to improve stability)
• Page routes, service activity, and session identifiers; events can be associated with your account when you are signed in

1.5 Local-first data (Studio App)

The Studio App may store projects, prompts, generation history, and other working data locally on your device. Local generation is distinct from online features: downloads, resource lookups, account services, publishing, sync, remote engines, and connected providers communicate over the network. The data shared depends on the feature and configuration. A remote engine or provider can receive prompts, media, workflow inputs, or credentials needed for the action you choose; its own terms and privacy policy apply.

1.6 Sync data

If you enable sync features, we may store working data associated with your account, including settings, snippets, project and canvas data, workflow graphs, prompt text (including positive and negative prompts), and run parameters. These records can contain personal information you put into them; review what you choose to sync.

Profile Continuity is designed to sync supported working records rather than generated media or model files. Publishing a package or preview is a separate upload and can share those files.

1.7 Discovery and workflow tools

Model information lookups send identifiers such as model checksums to our Services to retrieve or enrich matching information. Where unknown-model reporting is enabled, observations can also include a model name, size, type, and extracted metadata. Workflow Doctor reads supported workflow files in your browser and sends a sanitized inventory of workflow requirements to our enrichment service; the browser also keeps a local report. The inventory can include node and model identifiers, checksums, and source information. We may store identifiers to improve catalog matching and queue missing resource information for enrichment. These online lookups are separate from running a model locally.

1.8 Support and reports

When you contact us or report content, we receive the contact information, links, descriptions, and other information you submit. Please avoid sending secrets or unnecessary sensitive material.

2. How we use information

We use information to:

• Provide and operate accounts and directory/community features
• Provide sync and continuity features (if enabled)
• Maintain security, prevent abuse, and enforce policies
• Improve reliability and performance
• Communicate service updates and respond to support requests

3. Sharing and disclosures

We use service providers for hosting, account and database services, storage, analytics, and support. The Services use Vercel for web hosting and web analytics, Supabase for account and database services, and Cloudflare R2 for hosted files such as published .tea packages and previews. Support messages are processed through our email and support systems. Where enabled, Cloudflare Turnstile helps protect feedback forms against abuse and receives verification data, including an IP address.

Publishing content makes the listing and associated files available through the Services according to their visibility settings. Hosted packages may contain the extra files included by their publisher. Expiry of a temporary download link does not mean the stored file is deleted.

Third-party downloads and connected providers receive the requests and information needed to provide their services. Their collection and handling of information are governed by their own policies. Review them before connecting a service or sending private content.

We do not sell your personal information.

We may disclose information if required by law, to protect rights/safety, or to respond to valid legal requests.

4. NSFW controls and previews

NSFW settings affect preview display in supported interfaces. They are not a promise that an uploaded file or a shared asset URL is confidential or inaccessible elsewhere. Do not publish previews or packages containing material you intend to keep private. We may restrict or remove content to comply with policy, legal obligations, or platform requirements.

5. Cookies and similar technologies

We use cookies/local storage to support login, security, preferences, and locally saved reports. We also collect service usage events and use web analytics to understand visits and reliability. You can control cookies through browser settings.

6. Data retention

We retain personal information as needed to provide the Services and comply with legal obligations. You may request deletion subject to lawful retention requirements (for example, security and audit records).

7. Security

We use reasonable safeguards to protect information. No system is 100% secure.

8. Your rights and choices

Depending on your location, you may request access, correction, or deletion of your personal information by contacting support@sweettea.co.

9. Children

The Services are not intended for children under 13.

10. Changes

We may update this Privacy Policy and will revise the revision date when we do. Updates apply when published, subject to any notice or consent required by law.

11. Contact

Tea Time Labs (New York, USA)

Support: support@sweettea.co. For content or rights concerns, see how to report.