Security and your data
Your operational records deserve clear answers.
BakeryMS stores business records and personal data needed to run bakery workflows. Here is how access and data handling work, and what to confirm before onboarding.
Access
Different responsibilities. Different access.
Staff use accounts and roles appropriate to their work. Business data is scoped to the signed-in organisation, with application checks and database row-level security. Agree who should administer your business and review access when people change roles or leave.
Hosting
Cloud services behind the platform.
The platform uses Supabase for its database and document storage and Vercel for hosting. Connections use HTTPS. Supplier document content is processed by an AI provider during invoice extraction; a person must approve the results before costs update.
Continuity
Backup arrangements need a defined scope.
Database backups are provided through Supabase; retention and restore options depend on the configured service plan. Uploaded documents are stored separately from database records. Confirm backup coverage, document retention and recovery arrangements during onboarding. This page does not promise a recovery deadline or uptime SLA.
Personal information
Clear responsibility for employee and customer data.
Your business determines how its employee and customer data is used in operational workflows. BakeryMS provides the software. Personal-data deletion requests are handled manually; operational and accounting records may need to be retained. Review the privacy policy and agree processing terms for your rollout.
Access to your records
Discuss exports before you start.
Reporting includes export options, but export formats and coverage depend on the workflow. Tell us which records you need for accounting or a future migration so we can confirm the scope. Contact hello@bakeryms.com for data-handling questions; the privacy policy explains personal-data rights.
Keep exploring