larpyourresume.

Your resume stays yours.

This notice describes how larpyourresume handles account information, resumes, uploaded source documents, and optional AI generation.

Who operates this service

Operator details must be configured before public launch. A privacy contact must be configured before public launch.

What we store

We store your account email, resume content, document settings, names, and edit timestamps to provide your workspace. If you upload a previous resume, we extract its text and store the text, source filename, and approval timestamp with that resume. For uploads attached to a single resume, the PDF exists only during extraction and is then removed. My CV stores your original PDF, extracted text, reviewed profile, and version identifier at account level for reuse across applications. Replacing or deleting My CV removes that saved source and profile; generated resumes remain. You can remove older resume-specific extracted text separately.

When you use AI

After your explicit approval, we send uploaded CV text for profile extraction, or your reviewed CV profile (or older resume-specific source), job description, and instructions to Google’s Gemini API or OpenAI, according to your account’s AI access. This may include personal information in your resume. Each provider applies its own contractual processing, security, and retention rules; we do not promise zero retention or EU-only processing for these APIs. OpenAI requests are sent with response storage disabled (store: false); this does not eliminate provider abuse-monitoring retention. We do not use your resumes to train our own models. Generation is optional and manual editing and profile corrections do not send your resume to an AI provider. Profile extraction does not spend an app credit.

Google Gemini API terms · Google abuse monitoring and retention · OpenAI API data controls

Accounts, storage, and payments

Supabase provides authentication and database storage. Google may process your account information if you choose Google login. Stripe handles checkout and payment details; we receive payment status and subscription and credit purchase records, not your full card details. Hosting and these providers may involve international processing and their contracted subprocessors.

Cookies and browser storage

Updated 17 October 2026. This application uses storage for sign-in, abuse prevention, recovering work you request, and remembering that you dismissed the cookie notice. It does not install analytics or advertising cookies. Local storage and session storage are included in this notice even though they are not cookies.

Strictly necessary storage for a service you request does not require cookie consent under the applicable ePrivacy rules (including § 25(2) TDDDG in Germany). Where personal data are involved, we rely on providing the requested service (GDPR Article 6(1)(b); KVKK Article 5(2)(c)) and, for necessary security and notice-preference handling, legitimate interests (GDPR Article 6(1)(f); KVKK Article 5(2)(f)). Clicking “Got it” acknowledges this notice; it is not consent to tracking, AI processing, or international data transfers.

Display preference

The larp-theme local storage entry remembers your chosen light or dark appearance until you change it or clear browser storage. Without a saved choice, the signed-in workspace follows your device appearance. Public pages always use light mode and do not change your saved workspace preference.

Sign-in cookies

Supabase authentication uses first-party cookies named sb-<project-ref>-auth-token and related *-code-verifier cookies, sometimes split into numbered chunks. They hold session credentials and secure sign-in verification data when you use authentication. Supabase receives authentication data to provide sign-in. The current SDK sets a maximum cookie lifetime of 400 days from a write or refresh; this is not a guarantee that your session stays valid that long. Signing out clears the authentication cookies; completed sign-in flows remove their verification data.

Protecting signup and free AI

Cloudflare Turnstile checks email sign-in and signup, new browsers using free AI, and suspicious repeated Free-account use. Cloudflare receives technical browser and network information to perform these checks. Supabase validates the email authentication challenge; our server validates the free-AI challenge. See Cloudflare’s privacy policy.

After AI verification, the first-party __Host-larp-browsercookie stores a random, signed browser identifier for 30 days. It is inaccessible to page scripts and stays after sign-out so switching accounts does not reset the abuse check. It contains no resume content. We store a keyed hash of the identifier and recent account associations for 30 days after their last use. Flagged accounts may need another verification after 24 hours. These records may briefly remain after account deletion to prevent repeated signup abuse.

Signup limits use a keyed hash of the request IP address (IPv6 addresses are grouped by network). Signup records expire after 24 hours; browser signals and flags expire after 30 days. Scheduled cleanup runs hourly. These are security signals, not proof of a person or physical device. Clearing this cookie requires a new check before free AI; manual editing and PDF downloads remain available.

Remembering this notice

larp-cookie-notice is first-party local storage containing only the notice version, acknowledgement time, and expiry time. It remembers dismissal for 180 days in this browser and is not sent to our server. After expiry or a material notice update, we show the notice again. The old record remains in browser storage until replaced by a new acknowledgement or cleared. Reading this policy does not extend that period. A previous cookie-choice record is removed when you dismiss the updated notice.

Recovering your work

If browser draft recovery is available in your editor, first-party local storage entries beginning larp-draft:v1: save unsynced edits, including the resume name and document content, every 10 seconds and when the page is hidden or left. Drafts are separated by account, resume, and editor tab. Synced drafts are removed; drafts older than seven days are removed when the editor next checks storage for that account. Signing out or deleting a resume or account through this browser clears the relevant drafts. Entries beginning larp-draft-reset:v1: coordinate that cleanup across tabs. These reset markers contain identifiers, not resume content, and remain until browser storage is cleared. Draft content is sent to your account when you save or restore and save it.

If you request AI generation, larp-generation: session storage holds its request identifier and start time so the editor can recover the result after a reload. It contains no resume text or prompts. It is removed when the result is resolved or the browser ends the tab session; browsers may restore session storage when restoring tabs. The identifier is sent to our service to check your request.

Your controls and other services

Cookie information remains available through the Privacy link in the site footer. You can clear or block cookies and website storage in your browser. Blocking authentication cookies can prevent sign-in; clearing draft storage removes unsynced backups. If storage is blocked or cleared, or you use another browser or device, the notice may appear again. The site remains usable without dismissing the notice.

Google sign-in and hosted payment pages have their own storage and privacy notices when you choose to visit them. Our acknowledgement does not grant consent to those services. See the provider and operator information above and your rights below. If we introduce optional analytics, advertising, or other non-essential storage, we will ask for a separate choice before activating it, with rejection and later withdrawal available.

Retention and your controls

Your documents and extracted source text remain until you delete them or your account. Export your data or delete your account in workspace settings. Deletion removes active workspace data; the short-lived abuse records described above remain until their security retention period expires. Provider backups expire under their configured retention schedules. Payment records may need to remain for accounting and legal obligations and are detached from your deleted account in this application. Provider-held transaction records follow the payment provider’s retention obligations. Allowance usage records remain until account deletion to track monthly limits and prevent duplicate charges; they do not contain resume content. CV creation totals and activity metadata also remain until account deletion, including after an individual CV is deleted. This history includes CV titles, language, creation method, timestamps, and AI source and model identifiers, but no document bodies or prompts. It is included in your account export.

Your rights

Depending on your location, you may have rights to access, correct, erase, restrict, object to processing, or obtain a portable copy of your data, and to complain to your local data protection authority. Withdrawing permission for future AI processing does not undo processing already completed. Contact the operator for requests not covered by workspace controls.

Security and operational records

Access is limited to your account. The application does not intentionally log resume bodies or AI prompts. Short-lived rate counters, credit balances, and generation status records help prevent abuse and recover failed requests. Do not include information about other people unless you are entitled to use it.

Back to workspace