The studio owns its client records
beseensolution processes client data on behalf of the studio that entered it, and does not sell it or share it with other studios.
Privacy
This policy covers the beseensolution web platform and the beseensolution mobile app used by studio owners and staff.
beseensolution is booking and studio-operations software. Each studio decides what client information it keeps; beseensolution processes those records on that studio’s behalf. This page describes what is collected, which service providers process it, and how an account and its data are deleted.
beseensolution processes client data on behalf of the studio that entered it, and does not sell it or share it with other studios.
Removing a person removes the login and profile details. Transaction records a studio is required to keep stay in its books without a usable login attached.
Each studio’s records are scoped to its own tenant and access policies.
beseensolution stores the operating records a studio needs to run appointments, plus the accounts of the people who use it.
Data is used to operate the workflow the studio configured: showing appointments, sending confirmations and reminders, synchronising an optional external calendar, and producing the studio’s own operational and payroll reports. beseensolution does not sell personal data and does not use client records for advertising.
These providers process data on beseensolution’s behalf. The list reflects the current integrations and is updated as the product changes.
An account holder or a studio owner can request removal through the contact page. Deletion removes that person’s login and profile details. Transaction and payroll entries naming the person are retained in the studio’s books, because a studio is required to keep its financial record; those rows no longer carry a usable login. A studio owner can request removal of the studio’s entire dataset.
Records are stored in Supabase and served through Vercel. Tenant identifiers and database row-level security scope every record to the studio that owns it, and privileged service credentials are held server-side only. Records are retained while the studio’s account is active. The security page describes the current controls and their stated limits.
The studio decides what client information to collect and keep. beseensolution processes those records on the studio’s behalf and provides the means to correct or delete them.
No. Records are scoped by tenant identity and access policies, and automated tests cover important isolation paths. The security page has more detail.
The login and profile details are removed. Transaction and payroll rows naming you stay in your studio’s financial record without a usable login attached.
No card data is described as stored by beseensolution. Any future payment processor integration will document its own compliance boundary separately.
Raise it on the contact page and the team will confirm what is stored and what is out of scope.
Start free