This policy applies to the Glownomics website, application, booking pages, QR check-in, AI phone receptionist, income-verification links and support channels. Glownomics is operated by SO TIEM SOFTWARE, a Saskatchewan sole proprietorship, from 506-510 Perehudoff Crescent, Saskatoon, Saskatchewan S7N 4H6, Canada. Privacy questions and requests may be sent to support@glownomics.com or through Contact.
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; callers are told the call is transcribed, and the text transcript is kept with the call summary so the business's managers can follow up; if a business turns that notice off, callers do not hear it and no transcript is kept; QA transcripts are retained only after affirmative caller consent.
Calls to the public demo line are counted by a scrambled form of the caller's number only, and no transcript or recording is kept. If a caller asks the demo receptionist to text them the sign-up link, Glownomics keeps the number they called from to send that link and to follow up about Glownomics by text or phone, then deletes it after 180 days, or sooner on request. A text sent to the demo line's number is emailed to the Glownomics team so we can reply. Reply STOP to any text to stop them.
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.
An owner or manager can choose the voice callers hear. After a one-time payment for “Your own voice”, they can record or upload up to two voices of their own at a time after confirming that it is their voice or that they have the speaker’s written permission, that callers will hear it introduced as the business’s virtual assistant, and that the recording is sent to create the voice. The recording is sent once to Retell and Cartesia to create the voice; Glownomics does not keep it. Glownomics keeps the signed confirmation (the name typed, the statements and the time) and the voice identifier, and uses the voice only for that business’s receptionist. Removing the voice stops its use at once; on request, Glownomics asks the providers to delete it.
Glow answers most typed questions in the browser. A question that uses an AI ask sends its text, with today’s date, the time zone, the user’s role and the currency, to OpenAI to choose an action, with storage turned off; the figures in the answer come from the workspace’s own records. Voice input uses the browser’s built-in speech recognition: Glownomics receives only the resulting text, never audio, but some browsers, including Chrome, send the audio to the browser maker to transcribe it. Receipt photos given to Glow are read on the device and are not uploaded; only the expense the user confirms is saved. In the AI receptionist portal, Glow answers from a reviewed help guide and the business’s own records. A question the guide cannot place may use an AI ask: only its text and the portal language are sent to OpenAI, with storage turned off, to choose matching help topics; OpenAI does not write the answer. Glownomics keeps that question with the business for 30 days to improve the help guide, then deletes it.
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 also counts visits to its public pages with its own measurement: which page was opened, its language, the name of the website that linked to it, and a few actions such as tapping a call or sign-up button, trying a demo or starting to sign in. A random code kept only for that browser tab ties one visit together; it is not a cookie and it is gone when the tab closes. Glownomics does not store your IP address, device details or anything you type (only a one-way scrambled form of the network address is used to limit abuse), keeps these events for 90 days and uses them only to see how many people visit and how far they get. They are not used for advertising and are not shared.
Glownomics does not sell a salon's customer list or use that list to advertise another business.
Glownomics’s primary database is hosted by Supabase on Amazon Web Services in the United States (Oregon). The providers above may process data in the United States and other countries. Our agreements with them require them to protect it and use it only to provide their services, but data held outside Canada is subject to the laws of the country where it is held and may be accessed by its courts, law enforcement and national-security authorities.
When a business owner connects Google Calendar, Glownomics asks Google for permission to see the list of the owner’s calendars, see free and busy times, and see, create, change and delete events. Glownomics uses this access only to: show the owner’s availability to the AI receptionist and in the owner’s portal; create, move and cancel the appointments that the owner’s callers ask for, with the client’s name, service, phone number and a Glownomics reference in the event; keep the owner’s Glownomics schedule in step with changes the owner makes in Google Calendar; and create a separate bookable-hours calendar when the owner asks for one. Events are read only to find busy time and to follow changes to appointments; their contents are not used for anything else.
During a call, the open times Glownomics found are shared with the voice provider (Retell) so the receptionist can offer them to the caller. Glownomics stores only what those appointments need (times, event identifiers and the booking details above), and keeps Google access tokens encrypted. Google user data is never sold, never used for advertising, never used to train generalized AI or machine-learning models, and never shared except with the service providers above that run the requested features, when required by law, or with the owner’s consent. People at Glownomics do not read it unless the owner asks for support, for security reasons, or when required by law.
An owner can disconnect Google at any time in the receptionist settings or at myaccount.google.com/permissions. Disconnecting stops access immediately; stored calendar data can be deleted on request through the in-app privacy-request flow or support@glownomics.com.
Glownomics’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.
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, messages and call transcripts 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 records are kept while the account is open and afterwards only as long as needed for billing, tax, dispute and legal obligations, then deleted or anonymized.
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. Deleted data can remain in encrypted recovery copies until those copies are replaced; it is not put back into the service except to recover from an incident.
Glownomics uses authentication sessions and browser storage needed for sign-in, preferences, PWA cache and offline synchronization. Glownomics does not use advertising cookies. 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. Accounts are for people 18 or older (see the Terms of Service). We do not knowingly collect children’s personal information; if you believe a child’s information was entered, contact us and we will delete it.
We will update the effective date and provide appropriate notice when this policy changes materially. Send questions, data requests or privacy reports to support@glownomics.com or use the in-app privacy-request flow.