Transparency

What We Track, Why, and How It's Used

Complete transparency about the data we collect from both job seekers and recruiters.

Sections7

Sections in this document; the ring is the words in each, in order.

Words1,082

Counted rather than estimated; the ring is how they divide between the longest parts.

Minutes to read5

At 200 words a minute; the ring is each part's share of the time.

Last updatedCurrent

The version you are reading.

The document, one section at a time.

Section 01 / 07

Our Approach to Data

Resumetricx collects only the data necessary to provide you with valuable CV analytics and insights. We believe in minimal data collection, maximum transparency, and zero tolerance for misuse.

Our Promise: We never sell your data, we never share it with third parties for marketing, and we give you full control over your information.

What a browser could be asked for
Who the reader is · Precise location · Device fingerprint · Other open tabs · Browsing history · Third-party cookies · Biometrics
What we ask for when your CV is opened
Open time · Seconds per section · Scroll depth and re-reads · Device, browser, screen size · IP address
What is kept against your CV
Open time · Seconds per section · Scroll depth and re-reads · Device, browser name, operating system · Country · A name, only if the reader typed one

Read it top to bottom. Nothing in the first tier is taken from a reader’s browser and then deleted — it is never requested, so it never exists. The one thing that narrows between the second and third tiers is what the browser volunteers on its own: the IP address is used to work out the country and then not stored, and the screen size, browser version and language are dropped rather than kept. The last line of the third tier is the only item that arrives by being given rather than measured — a reader who wants you to know they read it can type their name into a card on the document, and nothing appears there unless they do.

Section 02 / 07

Data We Collect from Job Seekers (You)

Account Information

What: Name, email address, password (encrypted), profile photo (optional)

Why: To create and secure your account, send you notifications, and personalize your experience

How it's used: Account authentication, email notifications about CV views, password recovery

CV Content

What: Your CV text, sections, formatting, work experience, education, skills

Why: To display your CV to recruiters and generate analytics on section engagement

How it's used: Rendered on your unique CV link, analyzed for section-level engagement metrics

Usage Analytics

What: Pages you visit, features you use, time spent on platform, device type

Why: To improve our platform, fix bugs, and understand which features are most valuable

How it's used: Aggregated analytics to improve UX, identify popular features, optimize performance

Payment Information (Premium Users)

What: Billing address, payment method (processed by Stripe - we don't store card numbers)

Why: To process subscription payments and provide receipts

How it's used: Billing, invoicing, subscription management. Card details are handled securely by Stripe.

Section 03 / 07

Data We Collect from Recruiters (CV Viewers)

View Timestamp

What: Date and time when CV was opened

Why: To show you when recruiters viewed your CV

How it's used: Displayed in your analytics dashboard as "Viewed on [date] at [time]"

Engagement Metrics

What: Time spent on each CV section, scroll depth, re-reads, total view duration

Why: To show you which parts of your CV capture recruiter attention

How it's used: Section-level heatmaps, engagement scores, optimization recommendations

Device Type

What: Device type (mobile, tablet, desktop), browser name and operating system. Not the browser version, not the screen size and not the language — those are dropped in the browser and again on the server, so a stale cached page cannot reintroduce them.

Why: To help you optimize your CV for different devices

How it's used: Device breakdown analytics (e.g., "60% viewed on mobile")

Country

What: Country only — derived from the IP address, which is not stored. Nothing narrower is kept: no city, no region, no coordinates.

Why: To show you roughly where your CV is being read

How it's used: Geographic distribution (e.g., "Viewed from the United Kingdom")

Uploaded CVs, Shared Unchanged

What: When the file was opened, for how long, the device type and the country — and nothing else. No section timings, no reading order, no scroll depth inside the document.

Why: So someone who already has a CV they like can find out whether an application was read, without rebuilding it here first

How it’s used: Shown to the CV’s owner as an open and a duration. The reader sees a notice on the document saying exactly this, including the fact that which parts they read is not recorded, and can switch it off in one click.

Reader-Supplied Identity (Only If They Offer It)

What: A name, and optionally a company, an e-mail address and a short note — typed by the reader into an optional card on your CV. Nothing is inferred, looked up or matched: if the card is ignored, this category is empty, which is the normal case.

Why: Because a reader who wants you to know they read your CV currently has no way to tell you, and asking them is the only lawful way to find out

How it's used: Shown to you, and only you, against that one reading — always labelled as typed by the reader and not verified by us. It is never verified, never enriched, never shared, and readers who have objected to tracking are not shown the card at all.

Section 04 / 07

What We DON'T Collect

Inferred Recruiter Identity

We never work out who a recruiter is — no fingerprinting, no lookups, no matching against a profile. A name appears only where one was typed into the optional card

Browsing History

We don't track what recruiters do outside of viewing your CV

Sensitive Personal Data

We don't collect race, religion, health data, or other sensitive categories

Third-Party Cookies

We don't use third-party tracking cookies or advertising pixels

Social Media Data

We don't scrape or collect data from your social media profiles

Biometric Data

We don't collect fingerprints, facial recognition, or any biometric data

Section 05 / 07

How We Protect Your Data

Encryption

All data is encrypted in transit (TLS/SSL) and at rest (AES-256)

Secure Infrastructure

Hosted on enterprise-grade cloud infrastructure with regular security audits

Access Controls

Strict employee access controls with multi-factor authentication and audit logs

Regular Backups

Automated daily backups with 30-day retention for data recovery

GDPR & CCPA Compliance

Full compliance with international data protection regulations

Section 06 / 07

Site Visit Counts

On our public marketing pages we count visits, first-party and without cookies. Each count records the page path, the country and city derived by our hosting provider from the request, the referring site's domain, and the time. That is the whole record.

No identifier of any kind: no cookie, no fingerprint, no user id even when you are signed in — two visits from the same person cannot be joined.
No IP address is stored: the hosting provider derives country and city and the address goes no further.
Signals are honoured automatically: a Do Not Track or Global Privacy Control browser setting stops the count before any request is made, and we have no way to override it.
Scope: marketing pages only. The tool screens you work in are never counted, and readers of shared CVs remain covered by the separate, country-only rules above.

Section 07 / 07

Data Retention Policy

While active
Your data is retained
For as long as your account is active and you continue using Resumetricx.
2 years idle
We send a reminder
If you have not logged in, you hear from us before anything is removed.
3 years idle
Account may be deleted
After three years of inactivity we may delete the account and its data.
Within 30 days of deletion
Permanently removed
When you delete your account, your data is permanently removed — except legal and financial records we are required to keep.

Reading data sits outside this timeline, on its own clock: raw view events are deleted after 90 days and per-document aggregates after two years, whatever your account is doing.

Active Accounts: We retain your data as long as your account is active and you continue using Resumetricx.

Inactive Accounts: If you don't log in for 2 years, we'll send you a reminder. After 3 years of inactivity, we may delete your account and data.

Deleted Accounts: When you delete your account, we permanently remove your data within 30 days (except for legal/financial records required by law).

Analytics Data: Raw view and interaction events are deleted after 90 days; per-document aggregates after two years. Both schedules run automatically and independently of your account, and §13 of the Terms states the same two periods.

Reader-Supplied Identity: A name a reader typed into the card on your CV is stored as part of that single reading, and has no separate lifetime — when the reading goes, it goes with it. It is never copied into a contact list, a profile, or anything that outlives the reading it came from.