Privacy policy.

This page covers two separate topics: how this website handles your connection, and how the VITA CLI handles your CV files and AI calls. They have different data flows and different parties involved.

Last updated: 19 September 2026.

---

This website

Analytics

No analytics service is installed on this website. There is no tracking code, no visitor-counting pixel, and no third-party scripts that collect usage data. If that changes in the future, this page will be updated before the service is enabled.

Hosting

When published at the official VITA CV subdomain, this static site is served through Render. Each HTTP request you make is processed by Render's infrastructure. Render's own privacy policy and terms of service describe how Render handles data. The site owner does not run a separate visitor log for this website. Render may process and retain request data in its own infrastructure; we do not claim those logs are absent.

Forms, accounts, and uploads

There are no forms, accounts, logins, or file uploads on this website. The site does not ask you to enter CV details or store your interactions in an application database.

Downloads

The starter ZIP and sample PDF are served as static files from Render's CDN. No download event is tracked by this site. Render may log the request as part of its normal infrastructure operation.

Contact and issue reporting

Report website documentation or CLI issues in the public VITA CV issue tracker. Prefix website reports with “Website:” so they are easy to identify. Issues are public, so remove CV content, API keys, and other personal details from logs before posting. GitHub's own privacy policy governs anything you submit there.

---

The VITA CV command-line tool

The VITA CLI is a Python tool you install and run locally. Its data behavior depends on which commands you use and which options you choose. The sections below describe each data flow plainly.

Local project operations

The following VITA commands work with local project files and do not contact a VITA server:

• vita init — creates project configuration in .vita/ and initializes Git.
• vita new, vita status, vita diff — branch management and comparison against a stored base.
• vita build — calls latexmk on your local LaTeX installation to produce a PDF. Your TeX distribution may fetch a missing package, depending on its settings.
• vita analyze, vita adapt, vita review without --auto — generate a prompt file at .vita/current_prompt.md. VITA makes no AI provider call in this mode; the file remains local until you choose to share it.
• Ordinary local Git commits and diffs do not send your CV to a remote host. A push, including one started by vita save, does.

Automatic AI — when data leaves your machine

When you run an AI command with --auto, VITA sends a prompt and relevant context to the external AI provider you have configured. That can include your main.tex, job.md, and a previous analysis report used for adaptation. Examples:

• vita analyze --auto --provider <name>
• vita adapt --auto --provider <name>
• vita run --auto

VITA does not intentionally add unrelated project files or your local .vita/.env file to the AI prompt. For API-based providers, the configured API key is sent to that provider for authentication. The provider you choose receives and processes the request under its own privacy policy and terms. Review its terms before sending a real CV.

Automatic adaptation can overwrite main.tex. Commit a clean baseline before running --auto, then review git diff and the rebuilt PDF before committing or sharing the result.

Manual prompt sharing

When you run vita analyze or vita adapt without --auto, VITA writes a prompt to .vita/current_prompt.md on your machine. If you then copy that file's contents into an AI assistant — a browser chat, an API call, or any other tool — you are sharing those contents with that service. That sharing is your choice and is governed by that service's terms.

Remote Git repositories

Pushing your CV project to a remote Git host (GitHub, GitLab, or any other service) makes the committed content available under that host's terms. A normal local edit or build does not push. The explicit vita save command stages, commits, and pushes changes to a configured remote, so inspect git status and your remote before using it. Git ignore rules do not remove files already committed.

Credentials and API keys

VITA's key management commands store credentials in the local .vita/.env file. VITA does not send them to a VITA server; an API key is sent to its chosen provider when authenticating an AI call. The starter's .gitignore excludes .vita/ from Git. Check your own project's ignore rules before committing or pushing.