Privacy

Placeholder. This page describes the maintainer's current intent. It has not been reviewed by a lawyer and may be updated without notice.

What this site collects

This site (the marketing/docs at studioholst.com/vigil) is a static Next.js application served by Vercel. The site itself does not run any analytics, fingerprinting, or tracking code. No accounts. No cookies set by the site itself.

Vercel, as the hosting provider, may collect standard server logs (IP address, user agent, request paths) for operational purposes. See Vercel's privacy policy for their handling.

What Vigil (the tool) collects

Vigil is a self-hostable tool. If you run Vigil yourself, the data it ingests (FFLogs reports, your static's roster, manual prog points, strat configuration) lives on whatever Postgres database you point it at. No data flows back to the maintainer.

If you optionally connect a FFLogs Gold account to Vigil, Vigil stores your OAuth refresh token on your own database so it can fetch private/archived reports on your behalf. That token does not leave your deployment.

Third parties

• FFLogs: when you paste a report link, Vigil queries the FFLogs API. Your queries are subject to FFLogs's own privacy practices.
• XIVAPI: Vigil queries XIVAPI for ability metadata at setup time. This is one-shot data ingestion and doesn't share personal data.
• Vercel: hosts this docs site only.

Your rights

For the docs site: if Vercel's logs contain your IP and you want them purged, see Vercel's support channels. The site maintainer has no direct retention of those logs.

For Vigil itself: if you self-host, you control the data. If a hosted instance ever exists, this section will be updated with the relevant rights and contact paths.

Changes

Material changes will be noted in the changelog. See Contact with questions.