Terms of Service

Acceptance

By using Zero to Studio, creating an account, installing the SDK, or sending data to the service, you agree to these Terms.

If you have questions before using the service, contact studio4any@gmail.com.

Service purpose and beta nature

Zero to Studio helps early builders collect launch signals, feedback, waitlist and beta interest, basic traffic, returning-user context, and cashflow estimates.

The product is still early. Features, limits, pricing, retention windows, and public SDK behavior may change as the service matures.

Account and project responsibilities

• You are responsible for keeping your account secure and for activity under your account.
• You are responsible for the project settings, install snippets, project keys, and public collection pages you create.
• Project keys are publishable install keys, not database credentials. Still, you should not post private account credentials, service-role keys, or admin tokens in public code.
• You must have the right to send the data you provide to Zero to Studio and to install the SDK in the products where you use it.

Allowed use

• Use Zero to Studio to collect product analytics signals, launch readiness signals, feedback, waitlist requests, beta requests, and cashflow events for your own projects.
• Use the SDK and public forms in a way that is transparent to your users and consistent with your own privacy policy.
• Send only the event properties needed for your project dashboards and founder review.

Restricted use

• Do not send passwords, card numbers, authentication secrets, private messages, exact location, health data, government identifiers, biometric data, or other sensitive personal data.
• Do not use Zero to Studio for unlawful surveillance, hidden tracking, spam, fraud, harassment, security testing against third parties, or data collection without appropriate rights or notice.
• Do not attempt to bypass rate limits, quotas, authentication, validation, public API controls, or retention limits.
• Do not use the service to process regulated payment, medical, financial, child, or employment data unless Zero to Studio has explicitly agreed in writing.

Cashflow signals are estimates

Cashflow data in Zero to Studio is based on events sent by your app or integration. It is not verified revenue, accounting advice, tax advice, payment processing, or a substitute for your payment provider records.

Availability and changes

We may change, suspend, or discontinue parts of Zero to Studio, including beta features, SDK behavior, limits, or public pages. We will try to avoid unnecessary disruption, but the service is provided as an early product.

Disclaimers and liability

Zero to Studio is provided on an as-is and as-available basis. To the maximum extent permitted by law, we disclaim implied warranties of merchantability, fitness for a particular purpose, and non-infringement.

To the maximum extent permitted by law, Zero to Studio will not be liable for indirect, incidental, special, consequential, exemplary, or punitive damages, or for lost profits, lost data, or business interruption.

Governing law

These Terms are governed by the laws of the Republic of Korea, without regard to conflict-of-law rules. If a mandatory consumer protection law in your location applies, nothing in these Terms limits rights that cannot be waived by contract.