Jev Tracker / Privacy
Privacy, in plain language.
What this publication measures, what it stores in your browser and what email contact shares.
Scope and contact
This notice describes how Jev Tracker handles information when you browse our editorial pages or contact us by email.
The publication does not offer visitor accounts, payments or newsletter signups. The Access Tracker accepts voluntary reports without a login. External websites have their own privacy policies.
Preferences on your device
The appearance selector stores your Dark, Light or System choice in browser local storage under jevpulse-appearance. This preference is not sent to a Jev API and is not an account identifier.
The value has no automatic expiry. Change it with the appearance selector or remove it using your browser’s site-data controls. Clearing site data restores the default appearance. Choosing System follows your device setting; it does not delete the saved choice.
We use Google Analytics, which can store a first-party _ga cookie and related measurement cookies to distinguish visitors and sessions. You can remove these through your browser’s site-data controls.
Page interactions and third-party scripts
Google Analytics receives page-view and default measurement information used to understand audience and site usage. Google's default collection can include session statistics, approximate location, and browser and device information. Jev Tracker does not send account information or a site-defined User ID because the publication has no visitor accounts.
Our custom measurements for source links, access links and section navigation are not currently sent to Google Analytics. Google Analytics may separately measure interactions through its default features.
Google Analytics on the Access Tracker is disabled until automatic form and outbound-link measurement has been reviewed to prevent sending identity fields. Its prepared custom events record only successful submission, update, deletion, opening X sharing and downloading a status image. They do not include display names, X usernames, report IDs, report dates or editing credentials. Opening X sharing does not tell us whether a post was published.
The publication does not currently use advertising, session replay or embedded customer chat. Analytics collection and retention depend on the settings of our Google Analytics property. The tracker moderation page does not load Google Analytics.
Access Tracker reports
When you submit, we store your selected use status, server-recorded creation and update times, publication consent and moderation state in Cloudflare D1. We do not ask when you first used Jev. Editing keeps your original submission date. A report counts anonymously unless excluded for abuse. With your explicit consent, we also store your display name and X username for a public wall. Only approved, consenting successful-use reports appear publicly, with their original report date and a report ID. Names, account ownership and experiences are self-reported, not verified.
A Secure, HttpOnly, SameSite browser cookie named __Secure-jev-report holds a random editing credential for up to one year. Only its hash is stored with your report. It is not an account, and it is never included in share links or analytics events. Clearing browser data or losing the cookie removes your automatic ability to edit or delete the report; contact us if you need help, but we cannot promise to prove ownership without the credential.
You can change your status, withdraw public consent or delete your report in the same browser. Removing consent clears your name and X username from the live report. Changing public information withdraws it from the wall pending review. Deleting removes the live report, its identity fields and associated moderation records. Copies in Cloudflare disaster-recovery backups may remain according to the database’s configured backup retention; deletion from the live database does not immediately erase those backups. Third-party copies of previously public content are outside our control.
Cloudflare Turnstile processes browser and request information to protect submissions. We validate its challenge token before accepting a write. Our rate limiter stores a keyed, rotating hash derived from the request IP, plus short-lived counters. It does not store raw IP addresses in the tracker database, and the hash is not proof of a unique person. Counter records expire and are scheduled for removal within 48 hours. Cloudflare may separately process IP addresses and security logs to run its services.
Moderation actions record the administrator, time, action and reason. Only the protected administrator can access the review interface. Voluntary public data and anonymous reports remain until you delete them or we remove them for operational or abuse reasons; there is no automatic report expiry. Do not submit credentials, API keys, screenshots, sensitive information or another person’s identity.
To show trends, we retain time-stamped changes into and out of successful-use status, linked to your report without duplicating its name or X username. Existing reports are recorded as an opening balance when collection starts, never backdated. Only aggregated daily totals are public. Excluding a report removes its contribution from the displayed history; restoring it may revise that history again. Deleting the report also deletes its linked trend records from the live database. These records otherwise remain for the life of the report; Cloudflare backup retention is separate.
Personal status images are generated in your browser and downloaded to your device, not uploaded to our database. Sharing to X opens a draft under X’s own privacy practices. You decide whether to publish and whether to attach an image.
When you email us
Sending a message shares your email address, any name your mail account supplies, message content, attachments and normal email delivery information. Clicking a mail link alone does not send that message.
Correspondence is used to respond to the request, assess reported issues and maintain the relevant correction record. Email passes through your email service and the receiving mailbox provider; it is not stored in a website submission database.
We cannot currently specify how long messages and backups remain with the receiving email service, or where they are stored. Avoid sending sensitive information. For questions about a message you have sent, contact contact@jevtracker.com.
Hosting, logs and external links
Serving a page necessarily involves request information such as an IP address, requested URL and browser headers. A hosting or security provider may process or log this information to deliver and protect the site.
Cloudflare Workers hosts this site and may process and log request data to deliver and protect it. We have not confirmed the retention periods for Cloudflare logs or Google Analytics data.
Following a source or access link takes you to another service governed by its own practices. Do not send Jev Tracker your credentials for those services.
Questions and data requests
You can ask about information you have sent us, request a correction or request deletion by email. Identify the relevant correspondence and explain your request without including identity documents or additional sensitive data in the initial message.
We assess data requests based on the information we hold and applicable obligations. You can remove browser preferences directly through your device’s site-data controls.
Changes to this notice
Last reviewed September 19, 2026. This notice covers the Access Tracker, Cloudflare hosting and security, Google Analytics and email contact.
We update this notice and its review date when our data practices materially change. Contact us with questions about the information described here.