Security and privacy
Gluyee holds appointment and customer data for businesses, so access control and separation between accounts are treated as core, not as add-ons.
Role-based access control
Permissions are granted per role across the workspace, so a receptionist, a practitioner and an owner see different things. Access checks run on the server, not in the interface.
Two-factor authentication
Accounts support TOTP two-factor authentication with backup codes, so a stolen password alone is not enough to reach a workspace.
Tenant isolation
Every query is scoped to the organisation that owns the data. A booking, service or customer belonging to one business is never reachable from another.
Encrypted credentials
Stored integration credentials are encrypted at rest, and credential secrets are never returned in API responses.
Append-only change history
Service configuration changes are recorded in an append-only audit trail, so you can see what changed and when.
Booking price snapshots
The price at the time of booking is stored with the booking and never rewritten, so later edits to a service cannot alter historical records.
Our approach to security
Gluyee is designed with security and privacy practices in mind, including access controls, protection for sensitive credentials and safeguards for business data. We continue to review and improve these measures as the platform evolves.
If your business has questions about security, privacy or how your information is handled, please contact our team. You can also reach out to report a security concern.