← KitchenSpring home

Security & Data Protection

Updated: October 2, 2026

KitchenSpring is designed to hold operational business information, so security and appropriate access control are part of the platform's development rather than an afterthought.

Current architecture

KitchenSpring currently uses Supabase for database and authentication services and Cloudflare for web delivery and related infrastructure. Access controls are being built around authenticated accounts, business membership and database-level Row Level Security (RLS).

Access controls

KitchenSpring's current database tables use Row Level Security. The platform is being designed so access to customer information can be limited according to the authenticated user, business and application role. Security permissions and privileged database functions are subject to ongoing review as development continues.

Data in transit and infrastructure

KitchenSpring relies on its infrastructure providers' secured web connections and platform protections when data is transmitted between supported devices and hosted services. We do not describe the service as breach-proof or guarantee that any internet-based system can eliminate all security risk.

Development security review

KitchenSpring is currently in active development. Security configuration is reviewed as features are added, including authentication, database permissions, privileged functions and access policies. Issues identified during development are treated as items to resolve before broad customer deployment.

Customer responsibilities

Customers should protect account credentials and device access, use appropriate passwords, restrict staff access to what is needed, and promptly report suspected unauthorized access.

Security incidents

KitchenSpring is developing formal incident-response and notification procedures. Where applicable law requires notification or reporting of a qualifying privacy or security breach, KitchenSpring will follow those requirements.

Security questions

A dedicated security and privacy contact channel will be published before general customer access. Until then, KitchenSpring remains in development and is not being represented as a finished production security program.

No inflated security claims: Security controls evolve as KitchenSpring is developed and tested. This page is intended to describe the current approach accurately, not to promise that security incidents are impossible.