Privacy information.

Notice version 2026-09-10-v2

Who handles the inquiry

The legal operator must be identified before public intake is activated. Privacy contact: support@lunchbreak.com.

What the form collects

The valuation form collects your company name, first and last name, role, email, and optional phone number and website. It then asks for your business type, employee-count range, years operating, tools used, and operating status.

Each time you continue to the next step, those answers are saved with your email and a dated progress history. Completed steps are retained even if you leave before sending the final request, and may be used to follow up about your inquiry.

Do not include raw datasets, customer details, passwords, access tokens, bank details, or confidential material. There are no file uploads or connected accounts at this stage.

Expert applications

When you apply for an expert role, we collect your name, email, LinkedIn profile link, and the role you selected. These details are saved only when you submit the application, together with its date and the contact notice shown to you. Unsaved entries remain in page memory and are not stored in your browser or saved as partial leads.

Approved staff use this information to review your professional background and contact you about suitable expert projects. We keep a record of follow-up status. Applying registers your interest; it does not create an employment agreement or guarantee a project. No résumé upload or connected LinkedIn account is required.

Technical quote and partner inquiries

The code quote form collects a technical inventory, languages or formats, approximate scale and history, and the asset owner’s follow-up details. The referral form collects the referrer’s own name, email, firm or practice, role, and optional non-confidential context. Do not include third-party contact details in a partner inquiry.

Partner details are used to discuss eligibility and referral terms. We retain the version of the advertised offer and the notice acknowledged with the inquiry. No introduction, acquisition, or fee agreement is created by submitting the form.

Why it is collected

The information is used to assess the inquiry, clarify authority and suitability, arrange follow-up, and keep a record of the review. It does not authorize a sale, transfer, model training, or other use of the underlying company records.

Who can access it

Approved staff can access requests through a restricted review workspace. Hosting and database service providers process information on the operator’s behalf. The planned production stack uses Vercel for the application and MongoDB for request storage. Cloudflare R2 is reserved for a later, separately authorized file phase; this form does not transfer datasets there.

Storage and retention

The production retention period and the process for withdrawal or deletion requests must be agreed and published before public intake opens. Local preview records remain in a separate database on this computer until the project owner authorizes their removal.

The deployment region and any contractual location requirements must be confirmed before actual exports are requested. This notice makes no data-residency commitment.

Cookies and measurement

Unsaved edits remain in page memory; completed steps are stored on the server. Answers are not saved to browser storage. A short-lived essential cookie records successful submission confirmation. Staff sign-in uses an essential session cookie. Staff sessions expire after eight hours; confirmation expires after 30 minutes.

No third-party analytics or session replay is installed. Anonymous daily counters measure assessment starts, completed steps, and validation failures only when you allow optional measurement, without recording field values. An essential preference cookie remembers your choice for 180 days. Use Cookie settings in the footer to change it, or read our Cookie Policy. Saved request and workflow counts help measure completion and qualification. The server limits request size and uses temporary hashed rate-limit identifiers to reduce abuse. Full form contents are not intentionally written to application logs.

Your choices

You can leave the form before submitting, omit optional details, and ask for correction or withdrawal using the published privacy contact once intake launches. Requests about access, deletion, or other applicable privacy rights should also go to that contact.

Later review is separate

Any collection of actual datasets requires a separate agreed scope, authority checks, and appropriate handling terms. Removing names alone does not guarantee anonymity.