Privacy

Experiences submitted to Blanked

A random browser identifier is stored in a secure, same-site, HTTP-only cookie so the same browser can update its own experience without an account and duplicate submissions can be limited. It is not a verified person ID. Experiences attached to different live roles at one employer can remain separate; an employer-only submission is one general experience per browser. Clearing browser data breaks that update link, and Blanked does not fingerprint people to recreate it.

Local browser storage

Skipped employer IDs, broad US/UK/Global preference, optional broad job interests, capped feed-affinity scores, campaign attribution, engagement count, prompt dismissals and ad interval state may be stored locally. Feed affinity gradually decays and can be reset through Tune feed. The hosting service's country-level request signal may suggest a broad market and currency format; browser language and timezone are the fallback. Blanked does not request location permission or retain a city, coordinates or the raw country header.

Structured experience details

Experiences submitted to Blanked contain the employer, application stage, broad market, response status and submission time. Blanked may also ask for an optional broad role area, public job title, rough response or waiting-time bucket, reported outcome, round count, interview formats and whether the candidate would apply again. When an experience starts from a live role, its public job title, level and office location may be attached automatically. Custom titles help group similar applications and are not shown verbatim in public comparisons.

What is not displayed

Blanked does not display candidate names, usernames, identifying biography, exact interview questions, precise dates or traceable wording. It does not ask direct contributors for names, emails, phone numbers, CVs, demographics, exact application dates or precise personal location. Private audit information used for correction, removal and quality checks is not included in public pages, APIs, metadata, analytics or content exports.

Anonymous analytics

When configured and allowed by the visitor, PostHog Cloud EU receives a small set of manual product events about page visits, campaign entry, feed relevance, contribution completion, rankings, sharing, installation, feedback and ad performance. PostHog uses its own anonymous browser identity, separate from the functional duplicate-prevention cookie. Blanked does not identify people, send its database anonymous ID, capture typed text or track drag frames. Optional session replay is disabled by default; when explicitly enabled it is sampled, masks all inputs, blocks input elements, strips query strings from recorded URLs and does not run on the privacy or terms pages. Analytics never blocks contributing and is completely inactive when disabled or declined.

Advertising disclosure

Blanked can show internal house messages or Google AdSense. If AdSense is enabled, Google and its consent platform may use advertising cookies or similar technologies subject to the choices presented to you. Blanked does not send an individual candidate experience history or inferred employment status to advertisers. Advertising consent and choices must be handled through Google Privacy & Messaging or another appropriate certified consent platform where required.

Aggregate data and no sale of individual histories

Blanked does not sell individual candidate histories or raw browser identifiers. Aggregate rankings and employer insights are displayed publicly and may later support sponsorship or other commercial services. Those summaries do not reveal browser identifiers or private audit information.

Contact and review

This notice is product information, not a claim that legal compliance has been independently reviewed.

Questions: mustafakhalid14526@outlook.com.