This policy applies to the Glownomics website, application, booking pages, QR check-in, AI phone receptionist, income-verification links and support channels. The operator’s legal name and address have not been confirmed; see Contact or email [email protected] while this document remains a draft.
Email, display name, user identifier, sign-in sessions, role, language choice, recovery requests and account-protection events. If a user deliberately chooses Google or Facebook sign-in, that provider may send a verified email, name, provider account identifier and profile image to Supabase Auth.
Salon name and settings, ownership, memberships, technician profiles, services, working hours, turn status and change history.
Name, phone, email, notes entered by the customer or salon, services, selected professional, time, booking status, check-in and contact-consent choices.
Caller number, call and business identifiers, intent, outcome, summary or message, appointment, transfer state, duration, usage and notification history. Routine calls are not recorded; audio is not stored; QA transcripts are retained only after affirmative caller consent.
Services, prices, tips, technician shares, payout records, adjustments, reasons, expenses, mileage, receipts and OCR results. Do not enter card numbers, SIN/SSNs or full tax identifiers in Glownomics.
Private customers, services, appointments, tickets, expenses, mileage, receipts and independent-business records belonging to the Studio operator.
Support-case content, privacy requests, feedback, minimal diagnostics, error logs, synchronization events and notification history.
Plan, subscription state, Stripe customer and subscription identifiers, billing period and payment events. Stripe receives and processes card information on Stripe-hosted pages; Glownomics does not receive full card numbers.
The browser may store preferences, sign-in sessions, PWA cache and queued offline operations in local storage or IndexedDB. Pending data can remain on the device until it synchronizes or is cleared.
We use data to authenticate users; operate salon and Studio workspaces; record tickets, turns, hours and payouts; provide booking, check-in, AI-receptionist, import, export, optional OCR suggestions and verification links; send enabled notifications; administer subscriptions; prevent fraud and cross-tenant access; recover data; answer support requests; and improve reliability.
Glownomics stores minimal first-party product events for signed-in accounts in the application infrastructure. Users can turn this choice off in the app; the account-scoped preference is applied before optional events are sent. Events are designed not to contain customer names, ticket contents or financial amounts.
Public pages use Cloudflare Web Analytics to measure aggregate page views, referral source, device and performance. Cloudflare rules limit this to public marketing and demo pages; it is excluded from the signed-in application, customer booking, check-in and token routes. The in-app analytics choice controls account product events, not aggregate public-page measurement. Glownomics does not use an advertising network or behavioral advertising tracker.
Glownomics does not sell a salon's customer list or use that list to advertise another business.
Providers may process data outside the user’s country. Exact primary storage location, transfer mechanism and applicable legal terms require owner confirmation before this policy is finalized.
The application keeps data while the account or record is needed to provide the service, preserve audit history and handle requests. Some queue and customer retention settings can be configured by the salon owner. For the AI receptionist, call summaries and messages are retained for 30 days and then deleted; QA transcripts require affirmative caller consent and are retained for no more than 7 days; audio is not stored. Other default periods, backup retention and legal exceptions have not been confirmed.
Every account, including Free, can download one portable JSON file containing its permitted account data, owned salons, technician history and private Studio records. Users can also correct editable information or create an export, correction, restriction or deletion request in Settings. Customer deletion may anonymize identity while preserving ticket and financial-history integrity. Cancelling a paid plan does not automatically delete records. Backup copies may expire only through the backup cycle once retention decisions are confirmed.
Glownomics uses authentication sessions and browser storage needed for sign-in, preferences, PWA cache and offline synchronization. No advertising cookie is confirmed in the current repository. Booking-management and verification links use unpredictable tokens with expiration or revocation depending on the link type; users should not forward them to unauthorized people.
Glownomics uses HTTPS in transit, Supabase Auth, tenant separation, Row Level Security, server-side authorization, hashed tokens for certain public links and audit history for important actions. Migration procedures include backup and restore checks. No system is perfectly secure; report concerns through the Security instructions.
Glownomics is a business operations tool and is not designed for children. The minimum account age and child-data process require a legal decision before the final policy is published.
We will update the date and provide appropriate notice when this draft or policy changes materially. While legal decisions remain pending, send questions, data requests or privacy reports to [email protected] or use the in-app privacy-request flow.