Access starts with the right account
Use your own account, keep credentials private and give each person only the access needed for their work.
Verified publication
Security
Understand access, safe support boundaries and the route for reporting a concern without treating this overview as a policy.
Share only what the workflow needs
Keep passwords, payment credentials and sensitive health information out of free-text enquiries. Data-handling details belong in approved policy documents.
Report a concern
Use the enquiry form for a security or privacy concern so it can be routed with the relevant workspace context.
Contact us about securityHow should each person access a workspace?
Use an individual account and only the access needed for the work assigned to that person.
What should stay out of a support message?
Never include passwords, card details or sensitive health information in free text.
Where are data-handling commitments published?
Only an approved policy document can state a legal or data-processing commitment; this overview does not replace one.
How can I report a security concern?
Use the security contact path with the workspace context and the observed issue, without sending credentials.
Bukiby
Security begins with clear operating boundaries
A secure setup is easier to review when accounts, permissions and sensitive fields have an explicit purpose.
One person, one account
Individual accounts keep access and responsibility attributable instead of sharing credentials.
Only the data the task needs
Collect and expose the minimum context required for the intended service workflow.
A visible route for concerns
Security and privacy questions use a dedicated contact path and should never contain credentials or payment data.
Bukiby
Designed for real operating contexts
The same product language must work for a focused solo practice, a coordinating team and an owner reviewing more than one location.
Built around the way service work is organised
The structure changes with the people delivering the service, the places they work and the client journey around each booking.
Independent providers
Keep services, working time and client context together without building a large back office.
Clinics and small teams
Give each person a clear place in the schedule while retaining a shared operating view.
Multiple locations
Separate location context and availability while keeping ownership and review visible.