Legal

Privacy policy

Version 1.0 · Effective 11 October 2026

Cuisy is the team, channel and shift app for kitchen brigades. This page explains in plain words what we collect and why, where it is stored, who can see it and when we delete it.

In short: no ads, no selling of data, no tracking or analytics SDKs. Data is stored on servers in the European Union. You can delete your account from the app at any time.

1. Who is responsible

Cuisy is built and run by Yunus Senem (independent developer, Antalya, Türkiye), who is the data controller. For privacy questions and requests: [email protected] or the contact page.

2. What we collect

Data Why Who sees it
Account: e-mail address (may be Apple's "Hide My Email" relay address), Apple or Google account ID, the refresh token Apple issues when you sign in with Apple (so the link to your Apple account can be revoked when you delete your account), a one-way hash of your password when you sign in with e-mail Signing you in, protecting your account, password reset and verification e-mails Only you
Kitchen CV: name, rank, station specialties, city, short bio, profile photo; experience (venue, city, rank, head chef's name, dates) Letting your brigade know you, building teams, showing your career All signed-in Cuisy users
Certificates: documents such as hygiene certificates or references (file, title, issuer, expiry date) Keeping your documents in one place and sharing them with your chef if you choose Only you; the Executive Chef of a kitchen you share them with; when you apply to a job post, the documents you pick, to that business while your application is live
Transfer preferences (optional, only if you turn on "Open to transfer"): whether you are open to a move, when you can start, preferred cities (up to 5, abroad included), desired rank, your "Hide from my current kitchen" and switch-off settings Letting chefs at other kitchens and verified businesses find you in chef discovery While on: Executive and Sous Chefs of any kitchen and, for verified business accounts, the owner and the recruiters the owner added, together with your name, rank, specialties, city and last 2 jobs. Your current kitchen (while "Hide from my current kitchen" is on) and people you blocked or who blocked you do not see it; other users never see it and your profile never shows it. While off: only you
Business account (optional, only if you apply on behalf of a business): business name, type, city, country, website, tax number (VKN), the authorised person's name and job title, tax certificate or business licence, optionally a corporate e-mail address on the website's domain (for the verification code) Checking by hand that the business is real, protecting cooks from fake job posts Tax number, contact details and document: only you and Cuisy moderators (never looked up in an external registry; recruiters you add to your team do not see them). Once verified, the business name, type, city and website: signed-in Cuisy users, with a "Verified business" badge
Job posts and applications: a verified business's post (title, rank, station, city, season, housing/transport/meals, optional salary range, description); when you apply, your short note, the documents you choose to share and the application's status Businesses posting jobs, cooks applying with their Kitchen CV and seeing the outcome Posts: signed-in Cuisy users. Applications: only you and the business you applied to (its owner and the recruiters the owner added). With your application the business sees your profile and experience (already visible to signed-in users); your documents only if you pick them and only while the application is live (access ends when you withdraw or the post closes)
Core team listings and offers: the listing of the Executive Chef who owns the kitchen (availability, preferred cities, optional note, the members they picked and their ranks); each member's consent ("I'm going with the team") and when it was given; a verified business's offer (season, city, package, message) and the answer. If the offer is accepted, contact details for both sides: the Executive Chef's name, Kitchen CV, account email and phone; the business contact's name, title, account email and phone Letting an Executive Chef offer their team in one listing, businesses make the team an offer and both sides get in touch once it is accepted Listing and consents: the Executive Chef and the members added to it; other members of the kitchen don't see it. Verified businesses see only an anonymous summary (rank mix, specialties, cities and total years of the members who confirmed, and the Executive Chef's experience summary); names, photos, the kitchen name and the note are never shown. Offer: the business and the Executive Chef. Contact details open only to the two sides of an accepted offer
Kitchen membership: kitchen, rank, department, join date, invite code use Managing the team and permissions Members of the same kitchen
Messages: what you write in channels, photos you share in channels (file and its dimensions), sent and edited times, read status Making channels work Kitchen members allowed to see the channel; the moderation team too for a reported photo
Shift and prep data: shift plans, prep lists (when these features are used) Running the kitchen day to day Members of the same kitchen, by rank
Safety: content and people you report, the reason and a copy of the content at that moment; people you block Fighting harassment and objectionable content Reports: only the moderation team. Blocks: only you
Purchase information (Cuisy Plus): store (Apple App Store or Google Play), product, subscription status (active, grace period, expired, refunded), transaction ID (original transaction ID on iOS, purchase token on Android), period end, auto-renew flag, environment (production or sandbox) and your Plus end date. Your card or payment details never reach Cuisy; Apple or Google takes the payment Turning Cuisy Plus on and off when it ends, following renewal and refund notifications, preventing the same purchase from being linked to another account Subscription record: only you. Your Plus status (including its end date) and "Plus" badge are also visible to other signed-in Cuisy users; Plus members are highlighted in chef discovery
Device and session: push notification token, notification preferences (channels you muted), a randomly generated anonymous installation ID for app updates, session records, IP address, device and OS details, language preference Sending notifications, downloading the latest app version, managing sessions, preventing abuse Only you

We do not collect location, contacts, microphone or health data, and we do not accept health reports. Your photo library is accessed only when you pick a profile photo, a certificate or a photo to share in a channel; the camera is not used.

3. Where we store it

All app data is kept on Cuisy's own Appwrite server (appwrite.ynssenem.dev) running in Hetzner Online GmbH data centres in the European Union (Germany and Finland). Connections are always encrypted (HTTPS/TLS); document files and channel photos are stored encrypted on the server.

4. Who we share it with

We never sell your data or use it for advertising. Only to run the service:

5. How long we keep it

6. Your rights

You can access, correct and delete your data, object to processing and ask for a copy. You can edit your profile in the app and delete your account under Profile → Settings → Delete account. If you cannot open the app, use the account deletion page. Users in Türkiye can also read the KVKK privacy notice for their rights under Article 11. We answer requests within 30 days.

7. Children

Cuisy is for kitchen professionals and is not designed for anyone under 16. If we learn that someone under 16 has created an account, we delete it.

8. Changes

When this policy changes, the version number and effective date are updated. We announce important changes in the app.