Cookie Policy

Current use of cookies

The core application does not intentionally set advertising, profiling, or cross-site tracking cookies. It does not require an account cookie to build a CV. The hosting or security layer may use strictly necessary technical controls to route requests, prevent abuse, or maintain authorized access to a private deployment.

Necessary controls are not used to read CV fields or photographs. Browser developer tools and privacy settings can show storage associated with the domain.

Local storage used by the CV builder

BuildMyCV uses local storage to remember the draft, optional portrait, selected template, colors, typography overrides, page settings, and save status. Local storage is not technically a cookie because it is not automatically attached to every request. It remains in the browser and is accessed by application code on the same origin.

This device-local storage provides return-and-continue functionality without an account or CV upload. It may persist until the user clears the draft or browser data.

Why storage is necessary

Without local storage, refreshing or closing the page would normally discard the draft. Stored values support autosave, restoration, design preferences, optional photo display, and user-requested JSON export.

• CV draft fields and repeated entries
• Optional locally processed portrait
• Template and page-size selection
• Global and per-field typography settings
• Colour, spacing, and photo visibility preferences

Managing or deleting storage

Users can choose Clear all data in the builder or remove the portrait separately. Browser settings can delete cookies and site data for buildmycv.live. Private-browsing sessions may remove data automatically when the session ends.

Clearing browser storage is permanent because BuildMyCV has no server account copy. Export important drafts to a secure JSON file first if they may be needed later.

Optional analytics

Analytics are disabled unless the owner configures a provider. If introduced, BuildMyCV should prefer aggregated, privacy-conscious measurements and must never place CV text, names, contact details, employment history, portrait data, or JSON content in an event.

Before a non-essential cookie or identifier is enabled, the owner must update this policy, name the provider, purpose, duration, and access, and implement consent controls where required. Rejecting analytics must not block the builder.

Third-party links and email

Following an external link or opening a pre-addressed support email can involve another provider with its own cookies and storage. BuildMyCV does not control those settings. Review the third party’s policies before supplying personal information.

Changes and contact

The policy will be updated if storage behavior or providers change. The updated date indicates the current version. Questions can be sent to Support@buildmycv.live without including sensitive CV information.