Privacy Policy
This Privacy Policy explains how BuildMyCV handles CV drafts, optional photographs, design preferences, contact messages, and technical data. The core builder is account-free and processes CV content on the user’s device.
This content reflects the current BuildMyCV product but should receive jurisdiction-specific legal review before commercial publication.
Scope and operator information
This policy applies to the BuildMyCV website, CV builder, templates, articles, and support pages at buildmycv.live. It does not cover an employer, recruitment platform, browser vendor, email provider, or another website reached through an external link.
Before public launch, the site owner must add the operator’s registered name, business address, applicable jurisdiction, and any legally required representative or data-protection contact. This product-specific policy is not a substitute for advice from a qualified privacy professional.
CV information stays in the browser
Names, email addresses, telephone numbers, locations, employment history, education, skills, summaries, links, and design settings entered in the builder are stored in browser local storage. BuildMyCV does not intentionally transmit CV content to its application server. There is no BuildMyCV account and no central copy that support staff can retrieve.
Local storage remains on the device and browser profile until the user clears the draft, clears site data, uses private-browsing controls, or the browser removes stored data. People using a shared device should clear the draft after use and avoid saving sensitive information in a shared browser profile.
Optional CV photographs
Photo upload is optional and available only for templates marked as supporting a photograph. Accepted JPG, PNG, and WebP files are checked for type and size, resized so the longest edge does not exceed 600 pixels, and re-encoded as JPEG in the browser. This reduces file size and ordinarily removes embedded camera metadata from the stored copy.
The processed portrait is stored with the local draft and appears only when a compatible template is selected and photo visibility is enabled. BuildMyCV does not intentionally upload the portrait. Users should consider local hiring practices and discrimination risks before including a photograph.
Imports, exports, PDF creation, and printing
A JSON export may contain the complete CV draft, including an encoded photograph. Treat exports as sensitive, store them securely, and share them only with trusted recipients. Imported JSON is processed locally and checked against expected fields, lengths, and limits.
PDF creation uses the browser print workflow. BuildMyCV prepares print styling but does not need to receive the CV. Browser and operating-system print services may keep their own recent-file or print history under settings controlled by their providers.
Contact form and support email
The contact form prepares a message in the user’s email application using a mailto link. The user can review or cancel it before sending. If sent, the email provider and BuildMyCV support mailbox process the sender’s address, message, and voluntarily included details.
Users should never send a full CV, government identifier, password, payment information, medical information, or confidential employer material through support email. Support messages should be retained only as long as reasonably necessary to answer the request, maintain security, and meet legal obligations.
Technical logs, analytics, and cookies
The hosting provider may process limited technical information such as IP address, request time, browser type, requested URL, and security events to deliver and protect the service. BuildMyCV does not use CV content as analytics data.
Optional analytics are disabled unless configured. If enabled later, the owner must update this policy, provide legally required consent controls, document providers and retention, and ensure event payloads never contain CV fields, portrait data, or imported content. The Cookie Policy explains current storage.
Security, retention, and user choices
BuildMyCV uses content restrictions, input validation, file limits, and local processing to reduce risk. No website or device can be guaranteed completely secure. Users are responsible for device access, browser security, exported files, and checking recipients before sharing a CV.
Users can remove a portrait, clear all builder data, delete site data through browser settings, or export a copy before clearing. Because BuildMyCV has no account-linked server copy, it cannot restore a locally deleted draft or respond to access requests for CV content it never received.
International use, children, and policy changes
BuildMyCV is available internationally, but privacy rights and employment practices differ. The site owner should document the lawful basis, transfer safeguards, and local rights applicable to the final business operation. The service is not directed to children who cannot lawfully consent without a parent or guardian.
Material changes will be reflected by a new updated date and, where appropriate, a visible notice. Questions can be sent to Support@buildmycv.live without attaching personal CV content.