We don't run trackers.

The honest version

Aplexica's posture, per the zero-telemetry decision applied across all our open-source surfaces, is that we don't run third-party analytics on this site. No Google Analytics, no PostHog, no Mixpanel, no Segment, no Hotjar, no Heap, no Facebook Pixel, no LinkedIn Insight Tag. None of it.

Cookies we do set

Static pages on aplexica.com set no cookies at all. A small number of interactive surfaces set short-lived, first-party cookies for purely functional purposes:

• Form submissions. When You submit the contact or contact-sales form, our backend sets a short-lived first-party cookie to rate-limit duplicate submissions from the same browser. The cookie carries no personal information and expires within an hour.
• CSRF tokens. If You authenticate into a *.aplexica.com subdomain (the customer portal, the docs portal), the relevant subdomain sets the CSRF and session cookies needed for it to function. These are not set on the marketing site.

Why no consent banner

The GDPR cookie-consent obligation applies to non-essential cookies — analytics, advertising, profiling. The cookies above are functional ("strictly necessary") under the ePrivacy directive and do not require a consent banner. We could put one up anyway to be polite, but the obligation to ask consent before we set tracking cookies presumes we set tracking cookies. We do not.

Third-party content

The site embeds no third-party JavaScript. We host our own fonts (IBM Plex Mono, served from the bundle). External documentation and the GitHub repository live at docs.aplexica.com and github.com/aplexica respectively; the cookies set on those properties are governed by their own policies.

Changes

If we ever change this — for example, by adding first-party analytics for the marketing site — we will update this page first and announce the change in our blog. We will not change the posture in privacy@aplexica.com silence.