What we store and what we don't.

What we store

• The job description you paste, and the optional details you add: company, job title, level, interview date, recruiter notes, and the background text you write.
• An optional job link, saved as a reference only. We do not fetch or read it.
• The generated map: rounds, confidence states, signals, exposure, and the next action.
• A browser-generated anonymous id and session id, used to tie your map to your browser and to measure use of the preparation and purchase flow.
• Campaign fields from the link you arrived on, including utm_source, utm_medium, utm_campaign, utm_term, and utm_content, plus ad click identifiers such as gclid, gbraid, wbraid, msclkid and fbclid, the page you landed on, the referring site, and the time. We keep your first visit and your most recent campaign visit in your own browser's storage, and store them with your map and with any purchase, so we can tell which campaigns pay for themselves.
• For a purchase: the Stripe transaction identifier, amount, currency, item information, and the campaign fields above. We use these records for fulfillment and measurement.
• If you sign in, your email address is processed through Supabase Auth, which provides the site's authentication service.
• If you pay, Stripe processes the payment and provides transaction and customer identifiers. We do not receive or store your full card number or card security code.

Who can see it

• You, in the browser that created the map, or in your account once you sign in.
• Anyone you give a share link to sees the generated map only. The share view does not include the raw job description, recruiter notes, candidate background, or email. Generated output can still reveal or infer information from what you submitted, so review it before sharing.
• Our service providers, as needed to run the product: Lovable for hosting and the AI gateway, Supabase for the database and authentication, OpenAI for the selected generation model routed through Lovable AI, Perplexity for optional public search, Stripe for payments, and Google for analytics and advertising measurement.

AI processing

• The text you submit is sent through Lovable AI to the configured OpenAI model to generate your map. That is how the product works.
• Do not paste confidential information or anything you are not allowed to share outside your employer. Generated output can repeat or infer submitted information. Review it before creating or sending a share link.

Public-web research

• When you give a company and a job title, we run one bounded public web search through Perplexity to look for reports about that company's interview process.
• Only the company name, job title and level are sent to that provider. Your job description, recruiter notes and background text are never sent to it.
• Public results are supporting evidence, labelled as such. They are never presented as confirmed rounds.

Google Analytics and Google Ads measurement

• We load one Google tag and configure Google Analytics 4 and Google Ads. We send page and funnel events such as landing, form start, map submission, free-map completion, offer view, pricing view, checkout start, and verified purchase. We do not use a Google Tag Manager container.
• Google may receive page URLs, ad-click and campaign information, event names, and browser or device information. For a verified purchase, the event includes the Stripe checkout session identifier as the transaction identifier, value, currency, and one Full Interview Map item with price and quantity. It does not include card details.
• In the EEA, UK and Switzerland, Google Consent Mode defaults deny advertising and analytics storage, advertising user data and ad personalization. We show no consent banner and do not lift those defaults; Google may still receive cookieless measurement signals. Elsewhere, normal measurement applies.
• You can manage cookies in your browser and advertising preferences through Google My Ad Center. Blocking cookies does not prevent all cookieless signals.
• Our event code does not add your job description, recruiter notes, candidate background, name, email, or card details to Google event parameters. Commerce metadata described above is payment-related data and is sent after a verified purchase.

What we do not do

• We do not sell your data.
• We do not use a Google Tag Manager container.
• Our application code does not put your job description, recruiter notes, background, name, email, or card details into campaign or analytics event fields.
• We do not publish your map or interview details for marketing. A share link you choose to send makes the generated map available to anyone who has that link.

Retention and deletion

• Your interviews and maps are kept until you ask us to delete them. We do not currently run an automatic deletion schedule.
• To have your interviews and maps deleted, email support@llminterview.com. A self-service delete button is not built yet. We do not promise deletion from provider logs or backups on a timetable we cannot verify.

Providers and limits

• Lovable provides hosting, cloud services and the AI gateway. See Lovable Cloud documentation and Lovable AI documentation.
• Provider policies are available from OpenAI, Perplexity, Supabase, Stripe, and Google.
• We have not verified or promised account-specific processing regions, provider training or retention settings, zero-retention status, encryption-at-rest configuration, certifications, backup deletion timing, breach-notification timing, or opt-outs beyond what the providers publish and the product code controls.

Who runs this