Privacy Policy

When you open a page, your browser sends a single short message to our own server at /api/public/pv saying which page was viewed. That message is stored in our database and used only to produce aggregate reports (top pages, rough geography, how people arrived). Nothing is written to your browser, so clearing your cookies or using private browsing changes nothing.

• Page address: The path you viewed, e.g. /news or /calendar.
• Page title: The title of that page.
• Referring website: Only the domain name that linked to us (e.g. google.com) - never the full URL you came from.
• Campaign tags: If a link includes utm_source, utm_medium or utm_campaign values, those labels are stored so we can tell newsletters, social posts and search apart.
• Approximate location: Country, and for US visitors the state and city supplied by our network provider. This comes from the network edge, not from your device's GPS.
• Device type: Whether the visit came from a phone, tablet or desktop.
• A daily, one-way visit code: A scrambled, irreversible code built from your network address and browser type, mixed with the current date. It lets us count one person visiting five pages as one visitor for a single day, and it cannot be reversed, linked to you, or matched across days.
• Timestamp: The date and time of the pageview.

• No cookies, local storage, fingerprinting or advertising IDs.
• No Google Analytics, Meta Pixel, or any third-party analytics or ad tracker.
• Your raw IP address is never written to our database and never shared.
• No names, emails, accounts or any information that identifies you personally.
• No cross-site tracking, no profiles, and no selling or sharing of data with anyone.

Our traffic measurement uses no cookies at all. The only browser storage this site may use is what's strictly necessary to keep an administrator signed in to the private admin area - that applies to site staff, not to visitors reading the site.

Traffic rows are kept for a maximum of 400 days from the date of the visit, then deleted. Reporting only needs year-over-year comparison, so nothing older is retained. The daily visit code expires by design after 24 hours: after that, past rows can no longer be grouped into visits at all.

Expired rows are purged automatically by a scheduled job that runs daily, so nothing lingers past the window. An administrator can also purge on demand from our internal analytics health screen - either the expired rows, anything older than 90 days, or the entire traffic table.

The data contains no identifiers, so we cannot look up a person by name or email. We can, however, match the daily visit codes your own browser and network produce: use the form below and every stored pageview attributable to this connection over the retention window is deleted immediately. You can also enable your browser's Do Not Track or an ad/analytics blocker - the beacon is a plain request that blockers stop.

Some pages let you submit content, such as a card show for the calendar or a job listing. Those forms store what you type, including a contact email if you provide one, so we can review and publish the entry. Submitter names and emails are never shown publicly. Email us to have a submission or its contact details removed.

Questions, corrections or deletion requests: info@cardindustry.com