Privacy Policy and Your GDPR Rights
This Privacy Policy explains how CVizza handles personal data when you visit cvizza.com, create an account, and use our candidate profile, CV creation, and application-tracking tools.
1. Who is responsible for your data
The controller responsible for personal data processed through CVizza is:
- Privacy contact: [email protected]
You can contact us about this policy or to exercise your data protection rights.
2. Information we process
Account and authentication information
We store your username, email address, account name, password hash, account status, and relevant account timestamps. We also process confirmation and password recovery codes, their expiry information, and authentication tokens.
Passwords are stored as hashes rather than readable passwords. If you enable two-factor authentication, we store authenticator configuration, including the secret needed to verify time-based codes.
Your account name and the name used in your candidate profile can differ.
Candidate profiles and CVs
We process the career information you enter, such as:
- Name, contact details, location, professional headline, and summary.
- Work experience, education, skills, languages, certifications, and projects.
- Dates, descriptions, links, skill levels, and experience information you provide.
- CV names, document content, template selections, ordering, and saved versions.
Some text is stored both as Markdown and as rendered HTML for display. This represents the same content in different formats.
Saved CV versions and the profile revisions they reference preserve the information associated with an application. Editing or removing an item from a current draft does not automatically remove it from earlier saved versions.
Vacancies, applications, and activity
We store vacancy URLs or text you supply, fetched source content, cleaned text, extracted details, extraction metadata, and reviewed vacancy snapshots.
Application records can include employer information, status, salary expectations, private notes, activity comments, event dates, and attached CV versions. Vacancy descriptions or comments may contain information about other people, such as recruiters or hiring managers.
Only include information you are entitled to provide. Avoid unnecessary sensitive information, such as health details, political opinions, or identity-document numbers.
Technical and security information
Requests to the website and its providers may involve IP addresses, browser and device information, request paths, timestamps, cookies, and security challenge results. Infrastructure and application logs may record technical information needed to investigate faults or abuse.
We also use temporary browser storage during account and vacancy-import workflows. See our Cookie Policy for details.
Staff records
For staff accounts, we additionally retain permissions, template-management credentials in hashed form, credential usage metadata, audit events, and editorial history associated with information posts and site settings.
3. Why we process data and the legal bases
Where the GDPR applies, each processing activity needs an appropriate legal basis. The intended bases for CVizza are set out below and must reflect the service actually provided.
| Purpose | Information involved | Legal basis |
|---|---|---|
| Create and manage your account; provide profile, CV, and application tools | Account details and the content you save | Performance of our contract with you, Article 6(1)(b) |
| Send confirmation, recovery, and other necessary account emails | Email address and account message content | Performance of our contract, Article 6(1)(b) |
| Protect accounts, prevent abuse, investigate faults, and audit staff actions | Authentication, security, technical, and audit records | Legitimate interests in operating a secure and reliable service, Article 6(1)(f), subject to assessment and your rights |
| Respond to requests and comply with applicable legal duties | Relevant account, correspondence, and transaction records, where applicable | Legal obligation, Article 6(1)(c), where a specific obligation applies; otherwise contract or legitimate interests as appropriate |
| Optional website audience measurement | Analytics identifiers and browsing information | Consent, Article 6(1)(a), where required; see the current implementation limitation below |
Accepting a privacy policy is not blanket consent to every processing activity. Optional analytics must not be treated as necessary to provide your account.
4. Website analytics and cookies
When enabled, CVizza uses Google Analytics 4 to measure website visits and navigation, including dashboard routes. The integration removes query strings and fragments, replaces CV and application identifiers in tracked paths, and uses a generic page title. It does not deliberately add account IDs, email addresses, CV text, application notes, or form contents to analytics events.
Analytics can still involve online identifiers and technical information; these measures do not make all analytics data anonymous. The integration disables Google Signals and advertising personalization.
Current implementation: CVizza does not yet include an analytics consent or preferences panel. Where Analytics is configured, the script loads automatically. This policy does not itself obtain consent. Analytics must be disabled or gated by a suitable consent mechanism wherever prior consent is required.
Authentication and security cookies serve different purposes from audience measurement. More details are in our Cookie Policy.
5. Vacancy imports and optional AI processing
When you import a vacancy URL, CVizza requests content from that website. The website can receive our server's request and technical connection information. JavaScript rendering may be used to load a posting, but CVizza does not share your CVizza login credentials with the vacancy website.
We first use deterministic extraction. If configured and needed, Google Gemini may receive cleaned vacancy content and known vacancy facts to assist extraction. The current integration limits supplied job text to 30,000 characters and does not intentionally include your CV, candidate profile, account details, or authentication tokens.
CVizza currently uses the Gemini API Free Tier for vacancy extraction. The integration does not intentionally send private account records, CVs, application notes, or candidate profiles. However, imported vacancy text can contain personal information, such as a recruiter's name or contact details; the current integration does not guarantee removal of all such information.
AI output may be incorrect. You review extracted information before confirming an application. This assistance does not make hiring decisions or automatically submit applications to employers.
6. Who may receive information
Authorized personnel may access information when necessary to operate, support, secure, or administer CVizza. Records are protected by account ownership and permission checks.
The current deployment design uses these providers:
| Provider | Purpose and potentially relevant data |
|---|---|
| DigitalOcean | Application hosting and managed PostgreSQL; account and workspace data processed by the service. The configured hosting region is Amsterdam. |
| Cloudflare | DNS, proxying, security checks, Turnstile, and R2 object storage; traffic and security information, and stored artifacts as applicable. |
| Resend | Transactional account email delivery; recipient address and message content, including account codes where relevant. |
| Google Analytics, when enabled | Website audience measurement and associated technical information. |
| Google Gemini, when enabled | Vacancy content and facts supplied for extraction. |
CVizza does not automatically send your profile, CV, notes, or tracked applications to employers. You choose how to share downloaded documents. Templates and website information posts are separate from private candidate records; published site content is publicly accessible.
We may also disclose information where required by law or necessary to establish, exercise, or defend legal claims, subject to applicable safeguards.
7. International processing
Although the configured DigitalOcean application and database region is Amsterdam, this does not mean every provider processes all information only in the European Economic Area. Security, email, storage, analytics, and AI services may involve processing elsewhere.
Where personal data is transferred outside the EEA, an applicable GDPR transfer mechanism is required, such as an adequacy decision or appropriate contractual safeguards.
8. How long information is kept
Account and workspace information is retained while needed to provide the service. Application history and saved CV versions are designed to remain available even when current drafts change. Archiving an application hides it from ordinary active views; it does not erase its data.
The current implementation does not provide automatic age-based cleanup or a self-service account deletion workflow. Database relationships protect historical records from accidental deletion. These technical rules do not override applicable erasure rights.
Information retained for a legal obligation or legal claim must be limited to what is necessary for that purpose. Cookie lifetimes are described separately in the Cookie Policy.
9. Security
The production deployment is designed to use HTTPS, authenticated access, account ownership checks, permission-controlled staff tools, private media storage, and password hashing. Staff administration requires two-factor authentication.
Exported CV files are generated on demand rather than automatically retained as exported documents in object storage. Their underlying content and saved versions remain in the database. Template artifacts are stored separately.
No system can guarantee absolute security. Protect your credentials and use two-factor authentication where available.
10. Your GDPR rights
Where applicable, you may request:
- Access: information about processing and a copy of your personal data.
- Rectification: correction of inaccurate or incomplete information.
- Erasure: deletion where the legal conditions are met.
- Restriction: limits on processing in the circumstances provided by law.
- Portability: eligible data in a structured, commonly used, machine-readable format.
- Objection: objection to processing based on legitimate interests, subject to applicable conditions.
- Withdrawal of consent: withdrawal where processing relies on consent, without affecting the lawfulness of earlier processing.
These rights are not absolute. For example, some records may need to be retained to comply with a legal duty or defend a claim. Historical CV integrity alone is not a blanket reason to refuse erasure.
You can edit many current profile and workspace fields yourself. For access, export, deletion, or other requests not supported by the interface, contact [email protected]. Downloading a CV is not the same as obtaining a complete personal-data export.
We may request proportionate information to verify your identity. Under the GDPR, requests are generally answered within one month; where legally permitted, an extension may apply and you must be informed of it and the reasons.
You may complain to a competent supervisory authority, particularly in the EU country of your habitual residence, place of work, or the alleged infringement.
Further explanations are available from the European Commission on individual data protection rights and the GDPR text.
11. Automated decisions and future integrations
The current service assists with vacancy extraction and record management. It does not implement automated hiring decisions or decisions intended to produce legal or similarly significant effects on you.
Google sign-in and Google Drive/Docs integration are planned rather than part of the current implementation. This policy will need updating if those features or materially different processing activities are introduced.
12. Changes and contact
We may update this policy as the service or its processing changes. The publication date above identifies the current version. Material changes should be communicated through an appropriate notice.
For privacy questions or requests, contact [email protected]