Skip to content
CCCrisisCore Systems
Privacy and analytics

No ad-tech trackers. No sensitive-data intake by default.

CrisisCore uses analytics only to understand whether public pages are working and which proof or service surfaces are being inspected. The site is not configured for ad retargeting, behavioral advertising, or selling visitor profiles.

Last reviewed: May 21, 2026.

Analytics boundary

Production pages may load Plausible and Vercel Analytics for aggregate page-level signals. Those signals are used to improve the site, not to score visitors.

First-contact boundary

Do not send sensitive personal data, health records, legal facts, credentials, or private user exports in the first note. Send only a product URL, launch stage, and concern.

No-JS resilience

This site remains readable and navigable without JavaScript because trust surfaces should degrade cleanly.

Secure channel needed?

If your product details require a safer intake path, write "secure channel needed" in the first email and keep the initial message minimal.

Direct email: crisiscore.systems@proton.me

Analytics details
Plausible

Plausible is used for aggregate page analytics. It is configured as cookieless analytics; raw IP addresses and raw user-agent data are not stored by Plausible.

Vercel Analytics

Vercel Analytics is used for anonymous page-level traffic signals. It does not use third-party cookies, and the dashboard is not used to identify individual visitors.

Cookies and intake

CrisisCore does not add ad-tech cookies. Analytics run only in production. Contact and intake copy is intentionally minimal so sensitive product or personal data is not collected by default.

Retention and vendors

Analytics retention follows the vendor account settings and vendor policies. The operational boundary is simple: use aggregate site signals, avoid individual visitor scoring, and keep first-contact details out of analytics.