Skip to main content

Privacy Policy

Last updated: 10 October 2026 · Effective: 10 October 2026

Contents

  1. Summary
  2. No backend
  3. What we collect
  4. Where your data lives
  5. Third parties
  6. Your controls
  7. Children
  8. Changes to this policy
  9. Contact

1. Summary

Advoke CV is a fully static website. It has no backend, no database, and no user accounts. Everything you type into the resume editor stays in your own browser and is never transmitted to any server operated by Advoke CV or by any third party.

2. No backend

Advoke CV is delivered to your browser as static HTML, CSS, JavaScript, fonts, and JSON files. When you interact with the site, all work happens inside your browser. The resume editor does not send your content anywhere, and there is no server that could receive it even if it tried.

This is a deliberate architectural choice. It means Advoke CV cannot lose your resume because of a server outage, cannot be breached to expose your resume, and cannot monetise your resume content by selling it or analysing it.

3. What we collect

Advoke CV itself does not collect any personal information. Specifically:

  • We do not collect your name, email address, phone number, or any other personal detail you enter into the editor. Those details live only in your browser's local storage.
  • We do not use third-party analytics that receive resume content. The site loads no analytics script that inspects what you type.
  • We do not use advertising networks. There are no advertising scripts on any page.
  • We do not use cookies for tracking. Any cookies set by your browser are the browser's own and are not controlled by Advoke CV.

4. Where your data lives

When you save a draft in the Advoke CV editor, the draft is written to one of two browser storage mechanisms:

  • IndexedDB — the primary storage mechanism. Drafts are written to a database named advoke-cv inside your browser's own storage for the domain.
  • localStorage — a fallback used when IndexedDB is unavailable, for example in some private browsing modes. This storage has a smaller size limit.

Because drafts are stored locally, they are tied to the specific browser and device you use. They do not sync between devices, and they are not visible on any other browser or profile.

Storage lifetime

Drafts remain in your browser until you delete them, clear your browser's site data, or use the Clear Local Data control inside the editor. Some browsers may evict local storage under heavy memory pressure; we recommend exporting your resume as a JSON file periodically if the content is important to you.

No cloud backup

Advoke CV does not provide cloud backup. The JSON export feature in the editor produces a portable backup file that you can store anywhere you control.

5. Third parties

Advoke CV loads a small number of assets from the same origin as the site. No third-party scripts, fonts, or analytics run on the site. The following external libraries are bundled locally inside the repository and served from the same origin:

  • pdf-lib (MIT License) — used to generate PDF files in the browser.
  • fontkit (MIT License) — used to embed fonts into generated PDF files.

These libraries run entirely inside your browser and do not transmit data anywhere.

6. Your controls

You can exercise full control over your data at any time:

  • Export your resume as a PDF, as plain text, or as a JSON backup from the editor's Export dialog.
  • Delete individual drafts from the drafts panel in the editor.
  • Clear all local data from the editor's settings. This action requires an explicit confirmation and removes every draft and setting stored by Advoke CV in your browser.
  • Clear browser site data through your browser's own settings. This removes Advoke CV data along with any other site data for this domain.

7. Children

Advoke CV is not directed at children under thirteen. Because the site collects no personal information, it does not knowingly collect information from any age group.

8. Changes to this policy

If the privacy practices of Advoke CV change, this page will be updated and the "Last updated" date at the top will change. Material changes will be summarised at the top of the page.

9. Contact

If you have questions about this policy, you can open an issue in the Advoke CV repository. Because Advoke CV has no backend, it does not maintain a support ticketing system or an email inbox that stores user data.