About this policy
Draft — pending owner approval. This Privacy Policy is not final and is not ready for production use. Proposed effective date: [EFFECTIVE DATE].
The proposed data controller is [COMPANY LEGAL NAME], [REGISTERED ADDRESS], KVK [KVK NUMBER], VAT [VAT NUMBER]. Privacy contact: [CONTACT EMAIL]. These details require owner confirmation.
A Buyer obtains source code, a Cook offers it, and a Dish is an app source-code listing. A License records permission to use a Dish. A Kitchen Report assesses a particular version using automated checks and AI analysis.
Account and public information
We retain legacy display-name data in existing accounts, but no longer collect, edit or show display names. Your username is your only public personal name. We process email, account identifiers, sign-in and session records, username, avatar, profile details, country and preferences. Email magic-link, GitHub and Google sign-in are available. When you use GitHub or Google, the provider supplies verified account and profile information for sign-in and account linking.
First and last names entered in profile settings are optional and private. They are never shown to other users, including the other side of an order. Usernames, studio details, published Dishes, requests, comments and votes may be public. Request budgets are public. Purchases and private profile names are not public profile information.
Orders, delivery and safety
We process order amounts and status, payment references, License details, acceptance records, support selections and payout eligibility. Stripe handles payment details and Connect Express identity, bank and tax onboarding. We retain the connected-account identifier and relevant status; card and bank credentials are collected through Stripe. Payments currently use Stripe test mode.
Downloads generate evidence: time, License and version identifiers, hashed IP address, user agent and archive hash. Archives carry a per-License watermark and LICENSE-COOKTHISAPP.txt. These help deliver purchases, prevent abuse and investigate redistribution and payment disputes. Hashing an IP address does not make the associated record anonymous.
We also process search queries and related telemetry, notifications, submitted reports, dispute evidence and admin audit history. Avoid submitting unrelated personal information in uploads, searches or evidence.
Source-code analysis and AI
Uploaded source and related files are processed in isolated environments for ingest, scanning and build checks. Relevant source excerpts, descriptions and evidence are sent through OpenRouter to a third-party AI provider for Kitchen Reports. Report results may be published with the Dish; complete private source is not made public before an authorized delivery.
AI may also assist an admin with dispute recommendations. A human decides the dispute. Automated checks and AI can make mistakes and do not guarantee safety or ownership. Do not upload credentials, secrets or personal data you lack permission to share. This draft makes no promise that all AI providers offer zero retention or exclude training; provider terms and safeguards require confirmation before launch.
Purposes and grounds
We use account, order, source and delivery information to provide the marketplace and perform our contracts. Limited security, search, moderation and dispute records support legitimate interests in operating and protecting the service, improving discovery and defending claims, subject to applicable rights. We retain and disclose records to meet legal obligations, including applicable accounting, tax and reporting duties.
Transactional emails, such as sign-in links, receipts, purchase and sale notices and required service notices, are always enabled. Marketing emails require opt-in consent, recorded with the choice, time and source. Change or withdraw that consent in profile settings; withdrawal does not undo earlier lawful processing. Other optional notification categories have their own preferences.
Recipients and transfers
Service providers process information needed for hosting, databases, storage, email, security, payments and analysis. Stripe processes payments and Cook onboarding. OpenRouter and a third-party AI provider process the analysis inputs described above. Authorized admins review moderation and dispute evidence. Payment-dispute evidence may be provided to Stripe and relevant payment institutions.
Public information is visible to visitors. Purchased support contact information is shared through the support flow after the Buyer's agreement. Optional private profile first and last names are not disclosed to the other party. Authorities may receive information where legally required. DAC7 reporting may apply to Cook activity; applicability depends on the activity and law, not simply on whether a Cook is a company.
Some providers may process data outside your country. Applicable international-transfer safeguards and the final provider list must be confirmed before production approval; we do not claim all processing stays in the EU.
Retention
- Notifications: 90 days.
- Search logs: 13 months.
- Download history: 3 years.
- Raw uploads: deleted 7 days after successful processing. This does not delete normalized source, purchased versions or Kitchen Reports needed for the marketplace.
- Regenerable delivery archives: eligible for cleanup after 90 days without activity; they can be rebuilt for valid entitlements.
- Orders, Licenses, ledger entries and audit records: kept as legally required, including for accounting, disputes and compliance. They are not erased by short-term cleanup jobs.
Scheduled cleanup may take additional time to complete or retry. Normalized source and reports have separate retention from raw uploads; purchased-version records are preserved for Buyer access. Exact statutory schedules, legal holds and backup deletion must be finalized before launch.
Your choices and rights
Edit profile and notification preferences in settings. Where applicable, you may request access, correction, export, deletion, restriction or portability, object to processing based on legitimate interests, and withdraw consent. Contact [CONTACT EMAIL] to exercise rights or raise a privacy concern. We may need to verify your identity. You may also complain to the competent data protection authority.
Deletion does not require erasing records needed by law or for claims. Deleting a Buyer account ends that login's access without by itself revoking the legal License. Deleting a Cook account unpublishes Dishes while preserving existing Buyers' purchased-version access. This draft does not promise an operational self-service export or deletion feature for every record.
Cookies
Only essential session, security and preference cookies are used today. There are no analytics or marketing cookies. See the Cookie Policy. Server-side search logs exist independently of analytics cookies.
DMCA agent contact
Pending owner confirmation — no designated agent contact has been published.
- Designated agent name: [DMCA AGENT NAME AND ADDRESS].
- Postal address: [DMCA AGENT NAME AND ADDRESS].
- Email address: [CONTACT EMAIL].
Bracketed fields are not working contact channels. See the DMCA / Copyright Policy.