chefKompanySign in

Privacy policy

Current platform notice · Updated 13 October 2026

Information used by the platform

Account email, profile name and authentication information support sign-in and account security. Business applications include owner, kitchen address, country and time zone for onboarding and review. Subscription choices, meal bookings, changes and payment records support meal planning and account tracking. Delivery addresses and coordinates are requested when delivery is selected.

Access and service providers

Supabase supports authentication and database storage; Hostinger hosts the website. Google handles Google sign-in for platform administrators. Platform administrators have oversight access, and authorised kitchen staff can access records needed to manage their business and its customers. Passwords and authenticator codes should never be shared with kitchen staff.

Browser storage

The application uses browser storage for sign-in sessions. The older preview area uses an access-session cookie. Google Analytics reporting and advertising integrations are not currently connected.

Your information

You can edit your profile name and sign out of your account, including all devices. To request correction, deletion or information about stored records, contact our contact person. Some operational records have audit history; deletion and retention requests require review.

A detailed retention schedule, legal operator details and international privacy arrangements must be finalised before wider commercial launch. This notice describes the current implementation and is not a claim of global regulatory compliance.