Privacy

Pages and tracking

These pages have no user accounts and do not set application cookies. The record checker and date calculator use same-site forms. No analytics or client-side tracking script runs on these pages. Server logging and aggregate action counts occur as described below.

Record checker inputs and results

The license numbers, dates and format choices you submit are sent in the request body to Millatu and processed to produce the response. They are not saved as a watchlist or copied into application logs, and they are not placed in result URLs. Responses are marked not to be cached or indexed. Readable reports, JSON reports and calendar files you save remain under your control.

The checker reads locally retained, dated source exports; it does not send a lookup request to ABC for each visitor. Names and addresses are excluded from its responses. A separate visit to the official ABC website is handled under that site's practices.

The date calculator uses the dates you choose. Saving a calendar file does not create a Millatu reminder or subscribe you to notifications. If you import the file into a calendar app, that app's settings and privacy practices apply.

Current server logs

The Nginx web server records a project-specific access log. It can include an IP address, ISO-formatted date and time, HTTP method, normalized request path without a query string, protocol, response status, and response size. It does not include the raw referrer or browser user-agent. A coarse request-source category may identify Google, Bing, an internal link, another referring site, or direct/unknown traffic; the referring URL is not saved. A separate error log may contain request details and diagnostic information when a problem occurs.

These Millatu logs are configured for daily rotation, up to 14 rotations, and a maximum archive age of 14 days. The active log is separate from its rotated archives.

Legacy server logs

Before the project-specific logging configuration described above was deployed, Millatu requests used the server's standard shared Nginx logs. Those earlier logs could include an IP address, date and time, full request line including a query string, response status and size, referrer, and browser user-agent. Earlier log files may remain under the server's prior rotation policy while that legacy retention cycle completes.

Why logs may be used

Technical logs may be used to operate the pages, diagnose failures, understand basic traffic volume, and investigate misuse or security events. They are not linked to a Millatu user account because the pages do not have accounts.

Private traffic reports retain aggregate counts for known pages and discard IP addresses and arbitrary request paths. The tools also store daily totals for form openings, submitted checks, completed checks, download requests and generated files, rejected requests, source failures, and date calculations. Rejections use a fixed set of general reasons; record results use general categories such as changed, unchanged, first observation, not found, conflicting data, or unavailable source. Readable reports, JSON reports and calendar files are counted separately.

These totals contain no submitted license numbers or dates, IP addresses, cookies, visitor identifiers, or request bodies. They cannot identify unique people or returning visitors, or establish whether someone saved or used a generated file. Aggregate totals may be retained to compare releases over time.

Providers and email

DigitalOcean hosts the pages and processes network traffic needed to deliver them. If you send email to a millatu.com role address, Porkbun forwards the message and Google processes it in the receiving mailbox.

Millatu does not currently set a separate fixed automatic deletion period for email; messages remain subject to mailbox settings and provider practices.

Contact

A general request may not identify a particular visit because logs are not tied to an account.

Changes

This page will be revised if the site's data practices or providers materially change. The effective date above identifies the current version.