Privacy Policy

What we collect

When you create an account, we collect your name, email address, and a password (stored as a hash — we never see the plaintext). If you sign up as a creator, we also collect your public handle, bio, avatar, and timezone.

When you book a session as a guest without an account, we collect your name and email. This is the minimum needed to send you a confirmation and let you back into the room.

We log technical information automatically: IP address, browser type, pages visited, and actions taken in the app. This is used for security, debugging, and product improvement.

What we don't collect

We don't collect your payment details. When you pay for a session, you're paying through Stripe — your card number goes directly to Stripe, not to us. We see only the transaction ID, the amount, and a confirmation that it succeeded.

How we use it

• ·To run the booking, payment, and studio room features you signed up for.
• ·To send you transactional emails — booking confirmations, reschedule notifications, payment receipts.
• ·To debug problems, prevent abuse, and improve the product based on aggregate usage patterns.
• ·We do not sell your data. We do not share it with advertisers. We don't run ad networks on the platform.

Who we share with

We use a small number of third parties to run Studio Comms, and we share only what's needed for each one to do its job:

• ·Stripe — payment processing. They handle card data; we don't.
• ·Resend — transactional email delivery (booking confirmations, etc.).
• ·Cloudflare — DNS, edge routing, and email forwarding for our domain.
• ·PostHog — product analytics, used to understand how features are used.

We will update this list if we add or remove a service that handles user data.

Your rights

You can request a copy of the data we hold about you, ask for it to be corrected, or ask us to delete your account and associated data. Email legal@studiocomms.live and we'll respond within a reasonable timeframe.

Some data we may need to retain for legal or financial reasons (Stripe transaction records, for example). We'll explain what and why if it comes up.

Security

Passwords are hashed with Argon2. Connections to the platform are encrypted in transit over HTTPS. We're a small team and we take security seriously, but no system is perfect — if you notice a vulnerability, please email legal@studiocomms.live and we'll respond promptly.

Changes to this policy

When this policy changes meaningfully, we'll update the "Last updated" date at the top and, for material changes, email registered users. Continued use of the platform after a change means you accept the updated policy.

Contact

Questions, requests, or concerns: legal@studiocomms.live