PRIVACY_POLICY.EXE
Last Updated: October 7, 2026 // Status: Active
> 01_LOCAL_CV_STORAGE
CraftCV uses a local-first editor: CV data is saved in your browser's localStorage, without application-level encryption. We do not maintain a central database of user CVs. Export JSON for a portable backup; clearing browser storage removes the saved local copy.
Your saved CV stays in browser local storage. AI features and ATS analysis transmit content for processing; analytics and session recording are described below.
> 02_AI_PROCESSING_PROTOCOL
When you choose features that require server or AI processing:
- CV content is sent through our server to the configured external AI provider for processing. Provider handling depends on its own policies.
- AI Optimize: In the standard editor flow, structured name, email, phone and profile-link fields are masked in the browser before transmission. Identifiers in free-text CV fields or chat messages may still be sent.
- PDF Import & ATS analysis: The PDF is uploaded to our server for text extraction. Import sends up to 15,000 characters of extracted text to the configured provider. ATS checks run on the full extracted text and filename; up to 15,000 characters may be sent for AI review when available. Neither flow masks that text, and neither sends the original PDF to the AI provider.
- Job descriptions: When supplied for keyword analysis or ATS review, job-description text is sent to the configured provider without PII masking.
- Generate TL;DR: The selected entry's title, role, description and CV language are sent to the provider without PII masking. This flow does not use AI Optimize's patch-grounding checks.
- Storage and retention: The application does not save uploaded PDFs or AI request content to a central CV database. Aggregate usage and token counters are saved server-side. Connection identifiers and request timestamps are held in memory for rate limiting. Error logs can include provider errors or response excerpts; their retention depends on deployment logging. External AI and analytics services handle data under their own policies; we do not promise zero retention by those services.
> 03_ANALYTICS_&_SUBPROCESSORS
GTM is loaded when a GTM_ID is configured. The deployment uses the following services for measurement and consent; tags, cookie lifetimes and consent behavior are configured outside this repository in GTM and the service settings:
- Google Analytics 4 (GA4) / GTM: Traffic and feature-usage analytics.
- Microsoft Clarity: Visual session recording for debugging UI issues.
- CookieYes: Consent management.
CONTACT_COORDINATES
For security concerns or data inquiries:
andrea@craftcv.online