Skip to content
q.cv
PrivacyTermsContact

QCV / YOUR INFORMATION

Privacy notice

Updated 1 September 2026

QCV is provided by Team.Shiksha. This notice explains how information is handled when you visit q.cv or use the QCV application. Contact connect@q.cv with privacy questions or requests.

On this page
  1. Information you provide
  2. Sign-in and account messages
  3. Private records and public CVs
  4. Service providers and billing
  5. Cookies, browser storage and site services
  6. Saved history and retention
  7. Your choices and requests
  8. Changes to this notice

Information you provide

We store the email and account details used for registration and sign-in, waitlist, referral and direct-invitation records, and the career information you choose to enter. If an approved user invites you, we store the email address they entered, who supplied it, invitation status and related access record. Career information can include your name, headline, location, links, work and education history, skills, job preferences and optional compensation details.

CV documents, saved versions, import provenance, selected templates, publication settings and generated PDFs are stored to provide editing, recovery, publishing and downloads. Markdown and QCV JSON imports retain normalized content and source information; they do not send your file to an external parsing provider. Support messages contain the information you send us.

Sign-in and account messages

Email sign-in uses a one-time code and magic link. AutoSend processes the recipient email and message to deliver the sign-in request. QCV stores hashed sign-in credentials; the sign-in email is sent with open and click tracking disabled.

If you choose LinkedIn sign-in when it is available, LinkedIn provides a provider identifier and available basic identity claims, such as name, picture, locale and email. For this launch, an email supplied by LinkedIn can connect the first LinkedIn sign-in to the QCV account with that same email address. After an identity is connected, its stable provider identifier remains authoritative even if LinkedIn later reports a different email. QCV keeps that different address as private identity history without changing your primary sign-in email; it is not used for sign-in, account matching, merging, notifications or a public profile. This is not access to your full employment history, education history or contacts.

AutoSend also holds waitlist contact and status information. Account updates, such as welcome, invite approval, direct-invitation and referral messages, use AutoSend when lifecycle delivery is enabled. QCV sends a direct access invitation only when an approved user enters a recipient email and submits the invitation form; it does not access address books, bulk-import contacts, send automated invitation reminders or send invitations merely because a social card was shared.

Private records and public CVs

Your career profile and draft CVs start private. Publishing is an explicit action and requires the relevant account access and public visibility setting. Review the preview carefully: visible text and links you publish can reveal personal information. Public CV pages and their available PDF downloads can be viewed, copied and indexed by others.

Hidden CV sections and private source metadata are excluded from the public CV representation. Current compensation entered in the dedicated private compensation field is not included in public profiles. Information you type into visible CV text is different: it becomes public if you publish it.

Unpublishing or turning off public visibility prevents future public access through QCV. It cannot recall copies already downloaded, screenshots, or copies held by search engines or other people. Recruiter discovery, hiring-partner access and job-application workflows are not part of this launch.

Service providers and billing

Railway hosts QCV application services and its database. Cloudflare provides domain and delivery infrastructure; generated PDF artifacts use private Cloudflare R2 storage when PDF delivery is enabled. Private storage does not make an artifact public: QCV checks access before serving a download.

When Cloudflare-managed PDF rendering is enabled, Cloudflare processes the selected CV’s rendered text, layout and bundled fonts to generate the PDF. This includes a private draft if you request a draft export. QCV does not send account sign-in credentials, hidden sections or private source metadata as part of that rendered document. A managed rendering session is separate from the private R2 storage used for the resulting PDF.

When managed LinkedIn PDF text import is enabled and you submit a PDF, QCV first scans the file on its Railway service. Files admitted by that scan are sent to a temporary Cloudflare browser session to extract text for your review. The original PDF is not stored in public storage or retained by QCV after processing; confirmed imports retain normalized text and source information. Extraction does not publish a CV or update your career profile, and you must confirm the preview before it creates or replaces a CV.

If you start a trial or buy a subscription, Kelviq provides hosted checkout and subscription management. We send an account-linked customer identifier and selected plan to Kelviq. QCV stores subscription identifiers, entitlement status and necessary payment-event facts; it does not collect card details through its own CV editor. Kelviq handles the billing information you provide on its pages.

Authorized people operating QCV may access information needed for support, administration, abuse handling and security. Providers process information needed to perform their services. Their infrastructure may process data outside your country; this notice does not promise storage in a particular country.

Cookies, browser storage and site services

QCV uses session and security cookies for sign-in and request protection, and a signed referral cookie for attribution. The editor may keep unsaved draft content in your browser’s local storage for recovery. On a shared device, sign out and consider clearing QCV site data after saving; clearing browser data can remove an unsaved recovery copy.

The public QCV homepage uses Google Analytics to measure visits and usage. Analytics does not load on sign-in, application, public CV, referral or legal pages, or on URLs containing a query or fragment. Some application and marketing pages also load fonts from Google. These services can receive technical information such as the page address, browser or device information and network information. Browser settings or extensions can restrict these requests. There is no separate cookie-consent preference panel in this launch.

QCV and its hosting providers also process technical request and security information to deliver pages, diagnose failures, limit abuse and protect accounts. Do not place sign-in credentials, provider keys or other secrets in your CV or a support message.

Saved history and retention

Saved CV versions, publication history and normalized import sources are retained so that edits can be recovered and published or exported records can be explained. Archiving or unpublishing a CV is not account deletion and does not automatically erase its history or private PDF evidence.

QCV does not currently publish a single fixed deletion deadline for every type of record or automatically prune all saved versions. Account operation, recovery, security, payment records and applicable obligations affect what must be retained. Contact us to request deletion and an explanation of the records affected; some records or backups may need to be retained rather than removed immediately.

Your choices and requests

You can edit supported profile fields and CV content, choose what to publish, and withdraw public CV access through the application. For access, correction, a copy of your information, account deletion assistance, or a privacy concern, email connect@q.cv. We may need to verify account control before acting so another person cannot obtain or delete your records.

Depending on the law that applies to you, you may have additional rights concerning your information, including the right to object to certain processing or complain to the relevant privacy authority. Contact us about your request. This notice does not replace those rights.

Changes to this notice

We will update this page as QCV’s data practices change and show the updated date. New provider connections or future recruiter features need their own clear explanation; this notice does not authorize undisclosed access to your private CVs.

Questions or a request?

Contact Team.Shiksha about QCV support, billing or privacy.

connect@q.cv

Built by Team.Shiksha

Privacy noticeTerms of useBack to QCV