StudioFlow

Privacy Policy

How StudioFlow collects, uses, stores, and protects workspace, client, and Google account data.

Effective & Last Updated: November 17, 2026Support & Privacy Contact: studioflow.id@gmail.com

1. Overview & Scope

This Privacy Policy describes how StudioFlow (accessible at https://studioflow.my.id) processes information when photography and creative studios use our workspace platform, as well as when studio clients access public booking, tracking, and photo selection gallery links.

If you have questions about this policy or wish to exercise your data rights, contact us at studioflow.id@gmail.com.

2. Information We Collect

We collect only the information needed to operate the features you choose to use:

  • Account & Authentication Data: Name, email address, optional profile avatar URL, password hash (for email/password accounts), and email verification or password reset codes. When signing in with Google, we request only basic identity scopes (openid, email, profile).
  • Workspace & Studio Operations Data: Studio profile details (business name, contact phone, email, address, bank account details for client invoices), services, packages, client records, booking schedules, invoices, payment records, operational expenses, crew assignments, WhatsApp templates, and activity logs.
  • Photo Selection & Client Portals: Gallery metadata, public share tokens, optional expiration timestamps, encrypted optional gallery access passwords, selected photo file IDs/filenames, and client notes submitted through booking, tracking, or gallery selection forms.
  • Google Calendar Connection Data (Optional): If you connect Google Calendar inside the Calendar page, we store your connected Google account email/name/avatar, encrypted OAuth tokens, granted scopes, auto-sync preference, primary calendar identifier, and booking-to-event mapping metadata (Google Calendar event ID, event link, last sync timestamp, and sync status).
  • Subscription & Billing Metadata: Subscription plan tier, trial/billing period dates, and Midtrans transaction identifiers and payment status. StudioFlow does not collect or store full credit card numbers or banking credentials.

3. Google API Services Usage (Calendar & Limited Use)

Connecting Google Calendar to StudioFlow is optional and uses incremental authorization only when initiated by an authenticated workspace user with scope https://www.googleapis.com/auth/calendar.events for automatic booking synchronization to your primary Google Calendar.

Within the Calendar workflow, StudioFlow uses Google Calendar access strictly to create, update, or remove booking events on your primary Google Calendar when StudioFlow bookings are created, rescheduled, cancelled, or deleted. StudioFlow does not read or import unrelated personal events from your Google Calendar.

Google API Limited Use Disclosure: StudioFlow's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. StudioFlow does not sell Google user data, does not use Google user data for targeted advertising, does not transfer Google user data to third parties except as strictly required to provide or secure the service, and does not use Google Workspace or Google Calendar data to train artificial intelligence or machine learning models.

4. How We Use Information

  • Authenticate users, manage multi-tenant studio workspaces, and enforce access control.
  • Operate booking calendars, invoicing, crew assignments, and client photo selection galleries.
  • Process subscription upgrades and verify payment notifications.
  • Send requested transactional emails such as registration verification OTPs and password resets.
  • Maintain audit logs, prevent abuse, and troubleshoot technical issues upon request.

5. Infrastructure Providers & Data Sharing

We do not sell, rent, or trade your personal or client data. We rely on trusted sub-processors solely to run the application:

  • Google Cloud / Google APIs: Authentication, Google Calendar synchronization, and public Google Drive folder photo indexing.
  • Supabase (PostgreSQL): Cloud database storage with Row Level Security enabled.
  • Cloudflare (Workers): Web application, edge caching, and API hosting.
  • Midtrans: Subscription checkout and payment verification.
  • SMTP Email Service: Delivery of verification codes and password reset emails.

Client-facing booking, tracking, and gallery links display only the specific booking, invoice status, or gallery details you explicitly publish or make visible to clients.

6. Data Security & Cookies

  • Google OAuth access and refresh tokens, as well as optional gallery passwords, are encrypted at rest on the server using AES-256-GCM before storage and are never exposed to client browsers.
  • Authentication and session state use HttpOnly cookies signed with HMAC-SHA256 over HTTPS in production.
  • Account passwords are salted and hashed with PBKDF2-SHA256.

7. Data Retention, Disconnection & Your Rights

You retain full ownership of your studio records and media assets. At any time, you may:

  • Disconnect Google Calendar: Click Disconnect inside the Calendar settings to revoke tokens with Google and wipe stored OAuth credentials from StudioFlow without affecting existing calendar events, or revoke access from Google Account Permissions.
  • Export or Delete Workspace Data: Delete bookings or galleries directly in the dashboard, or email studioflow.id@gmail.com to request permanent account and workspace deletion.

8. Policy Updates

We may update this Privacy Policy as StudioFlow evolves. Material changes will be reflected by updating the Effective Date at the top of this page.