PRIVACY

Local browser records

Operator intake, local Operator records, console state, case notes, and related local tools use browser storage on the device you are using. They are not transferred merely because you create or edit them. Browser clearing, private-browsing behavior, device loss, software changes, or the local purge controls can remove them. “Purge Local Record” removes the identified local browser record; Operator-console purge controls remove that console’s local state. These controls do not delete reports you separately volunteered to the report service.

Analytics

Public VeilDaemon pages use Vercel Web Analytics to understand aggregate traffic and page use. VeilDaemon does not intentionally install advertising-network trackers or sell analytics data.

Debrief submissions

When you submit a debrief, VeilDaemon transmits the selected role, Needlepoint, Operator count, best moment, confusing rule or scene, requested improvements, full feedback, and any optional handle or email to api.veildaemon.app. The information is used for product feedback, review, redaction, and—only when separately approved—possible publication of the reviewed public version.

Volunteered anomaly reports

Local anomaly logs remain local unless you choose “Log + Volunteer Copy.” A volunteered copy transmits Operator name and designation, primary Frequency, classification, active Needlepoint, scene, impossible detail, severity, tags, and notes. Do not volunteer sensitive information.

Storage, access, and retention

Submitted debriefs and volunteered anomaly reports are stored through the report service. Production storage uses Upstash Redis when configured; an in-memory fallback may be used in other environments. Access to full submissions is restricted to administrators with the report-review credential. The service retains up to 500 debriefs and 500 anomaly reports; older records may be displaced by that collection limit, and administrators may delete records during review. No fixed time-based deletion schedule is currently established.

Redaction and publication

Private submission does not authorize publication. A debrief can enter the public recovery index only after you generate and approve its redacted version and an administrator separately approves it. Public output excludes the optional handle and email. Volunteered anomaly reports enter private review and are not automatically published.

Correction or deletion requests

To request correction or deletion of a submitted report, email J.Donavon.Love@gmail.com. Include the report ID when available and enough non-sensitive context to locate the record. Local browser records must be corrected or purged on the device where they are stored.

Third-party media and links

The Primary Feed loads a YouTube privacy-enhanced embed only after you open the transmission viewer. YouTube may then receive technical request data under its own policies. External links, storefronts, Discord, GitHub, and other services operate under their own privacy terms.

Contact

Privacy questions: J.Donavon.Love@gmail.com.