Privacy Policy

Who operates Zero to Studio

Zero to Studio is currently operated as an early-stage product/project under the Zero to Studio name. For privacy or data requests, contact studio4any@gmail.com.

If a formal company entity, address, or dedicated privacy officer is added later, this policy will be updated before those details are relied on publicly.

What we collect

We collect the information needed to run the product, show project dashboards, and receive signals sent by projects that install the SDK or use public collection forms.

• Account information such as email, display name, authentication profile data, plan, and preferences.
• Project settings such as project name, URL, slug, platform, launch status, collection mode, beta access settings, and public install keys.
• SDK events such as page_view, app_open, screen_view, cashflow, feedback_submit, waitlist_signup, and beta_signup.
• SDK context such as anonymous id, session id, platform, page URL, page title, screen name, returning-user context, and explicitly provided event properties.
• Public form submissions such as feedback messages, ratings, waitlist emails, beta tester emails, names, and optional notes.
• Operational records such as notification state, rate-limit records, timestamps, and retained raw or aggregate event data.

What we do not intentionally collect

The SDK is designed for explicit product signals, not surveillance. It does not intentionally collect automatic clicks, heatmaps, session replay, screen recordings, keystrokes, card data, passwords, or precise location.

Because developers can send custom event properties, project owners must avoid sending sensitive information to Zero to Studio.

• Do not send passwords, authentication secrets, API tokens, or one-time codes.
• Do not send credit card numbers, bank details, payment authentication data, or billing credentials.
• Do not send private messages, health data, government identifiers, biometric data, exact location, or other sensitive personal data.
• Do not send full page contents, form field contents, screenshots, screen recordings, or raw keyboard input.

How we use data

• To provide dashboards, feedback inboxes, project setup, notifications, public signup pages, and basic account settings.
• To calculate launch and product signals such as traffic, returning users, feedback, waitlist and beta interest, and cashflow estimates.
• To protect the service with rate limits, event quotas, validation, abuse prevention, and operational logs.
• To improve Zero to Studio using aggregated or product-operational information where appropriate.

Sharing and sales

Zero to Studio does not sell personal information or share it for cross-context behavioral advertising. We may use infrastructure providers, such as hosting, database, authentication, and email services, to operate the product.

We may disclose information if required by law, to protect the product or users, or as part of a future business transfer, provided the receiving party is expected to honor these privacy commitments.

Retention

Raw and aggregate event retention may depend on the account plan and product settings. The current plan model includes raw event retention windows and longer aggregate windows for product reporting.

Public collection submissions and account records are kept while needed to provide the service, resolve requests, maintain records, or protect the product.

Your choices and requests

You can contact studio4any@gmail.com to request access, correction, deletion, or export of personal information connected to your account or a public form submission.

For United States users, including California users, you may use the same contact channel to ask what categories of personal information we collect, request deletion or correction, or ask whether information has been sold or shared for advertising. Zero to Studio does not sell personal information or share it for cross-context behavioral advertising.

For Korean users, you may use the same contact channel to ask about access, correction, deletion, suspension of processing, or withdrawal requests related to personal information handled by Zero to Studio.

Changes to this policy

We may update this policy as Zero to Studio changes. If a change materially affects how data is collected, used, or shared, we will update the date above and provide a reasonable notice in the product or on the website.