Skip to main content
Advoke CVResume Builder
  • Templates
  • Editor
  • Examples
  • Guides
  • About

Legal

Privacy PolicyTerms of UseCookiesAccessibilitySecurityDisclaimerData HandlingContact
Policy

Cookies

Last updated: 1 March 2025

Zero tracking cookies

Advoke CV does not set any cookies — not for tracking, not for analytics, not for advertising, not for personalization.

What we do not use

No Set-Cookie headers are sent. No third-party cookies. No session cookies. No persistent cookies. No first-party cookies of any kind. If you open your browser's developer tools and inspect the cookies tab while using Advoke CV, it will be empty for this site.

What we do store: localStorage

Advoke CV uses your browser's localStorage, which is a separate browser API from cookies. It stores small amounts of data on your device, never sends it to a server, is not shared across sites, and is not accessible to third parties.

The following keys are stored under the advoke: namespace:

  • advoke:draft:<id> — your saved resume drafts (one entry per draft)
  • advoke:index — a lightweight index of your draft list
  • advoke:prefs — your theme preference and editor state
  • advoke:flags — feature flag overrides you have set
  • advoke:schema-version — the schema version used to migrate old drafts

You can inspect, export, or delete this data at any time:

  • Use the editor's Draft manager to see and delete drafts.
  • Use the editor's Export JSON option to back up drafts.
  • Use the editor's "Delete all data" option to remove everything Advoke CV has stored.
  • Or clear your browser's site data for advoke-cv.pages.dev.

sessionStorage

Advoke CV may use sessionStorage for transient state such as which editor section was last open. Session storage is cleared automatically when you close the tab or browser. It is never transmitted and is not accessible across sessions.

Third parties

No third-party scripts are loaded. There are no advertising networks, analytics providers, social media widgets, or content delivery networks beyond Cloudflare's own edge for the HTML, CSS, JS, and favicon that are served from the same origin.

Why there is no cookie banner

Cookie consent banners are required when a site sets non-essential cookies or loads third-party tracking. Advoke CV sets no cookies and loads no trackers, so there is nothing to consent to. This is a design choice, not a workaround.

See also: Privacy Policy, Data Handling.

© 2025 Advoke CV. All rights reserved.