← extracook.life

Privacy Policy

Last updated: 2026-09-14 • Terms version: 1.0

In short: we keep only what is needed to connect restaurants and cooks. Your phone number is not visible to everyone — only to the restaurant whose shift you expressed interest in.

Data controller

The controller is the provider of the extracook.life platform.

LEGAL ENTITY: [COMPANY LEGAL NAME]

REGISTERED OFFICE: [ADDRESS]

COMPANY / TAX ID: [COMPANY / TAX ID]

REGISTRATION: [GEMI / REGISTRATION NUMBER]

CONTACT EMAIL: [LEGAL EMAIL]

What we process and why

Account data (email, user id, role): to create and operate the account — lawful basis: performance of the service contract.
Cook profile (name, age, city, experience, roles, cuisines, workplaces, short description, photo, phone): to present you to a restaurant after you express interest — lawful basis: performance of contract.
Business data (name, area, address, map link): to publish listings — lawful basis: performance of contract.
Shift data (role, dates, hours, pay, notes, status): to display and manage listings — lawful basis: performance of contract.
Location (approximate coordinates, radius): to show relevant listings within the radius you choose — lawful basis: performance of contract, with device permission where required.
Availability and expiry: to match current needs — lawful basis: performance of contract.
Interest records: so the restaurant knows who is interested — lawful basis: performance of contract.
Notification and news preferences: to send optional notifications — lawful basis: consent, withdrawable at any time.
Proof of Terms acceptance (version, timestamp, role, page, browser technical identifier): to demonstrate compliance — lawful basis: legitimate interest / legal obligation.
Technical security logs and user reports: for security, fraud prevention and content moderation — lawful basis: legitimate interest and legal obligations.

Contact details

Restaurants do not automatically see cooks' phone numbers.

A cook's contact details become available only after that cook explicitly expresses interest in that restaurant's specific shift.

Location

Location is used to show relevant listings within the radius the user selects.

We ask for device permission only when needed, do not collect continuous background location, and never show a cook's exact location to restaurants — only an indicative distance.

Recipients and processors

Hosting, database and authentication infrastructure providers acting as processors under contract.

Other users, to the extent the service requires (e.g. the restaurant sees the profile of a cook who expressed interest).

Competent authorities where there is a lawful request.

Where transfers outside the EEA occur, appropriate safeguards (e.g. standard contractual clauses) apply.

Retention

Account and profile data: while the account exists.

Listings and interest records: for a reasonable period after the shift, for history and dispute handling.

Proof of acceptance and reports: as long as required for legal compliance and claims.

After account deletion only legally required data is retained.

Your rights

You have the right of access, rectification, erasure, restriction, objection and portability, and can withdraw notification consent at any time without affecting your account.

Requests: [LEGAL EMAIL]

Account deletion: send a deletion request from your account email or via the contact page.

You have the right to lodge a complaint with the competent data protection authority.

Security

We apply role-based access, database-level access rules, encrypted transport and data minimisation.

Cookies and local storage

We use only strictly necessary cookies and local storage (session, language, notification preferences). No advertising or third-party analytics cookies.