No cookies and no cross-site tracking. DataFastX stores an opaque first-party visitor ID for 30 days by default, or only for the browser session when you choose session-only mode.
5,000 events/month free. No credit card required.
0
Cookies used
0
Cross-site profiles
0
Personal data stored
5K
Free events/month
DataFastX never sets cookies on your visitors' browsers. No first-party cookies, no third-party cookies, no fingerprinting. Period.
The tracker does not set cookies. Whether your site needs consent depends on your jurisdiction, configuration, and the other tools you use.
Events contain page, referrer, UTM, coarse device fields, and a site-scoped random visitor ID rather than a persistent cross-site identity.
DataFastX does not use analytics events to build advertising profiles. Site owners can delete a site from its settings.
A small first-party-friendly script reduces tracking overhead, though blockers and network failures can still prevent events.
DataFastX is designed to minimize collection and uses no cookies by default, but compliance depends on how and where you deploy it. Review your own legal requirements rather than treating a product claim as legal advice.
We do not use cookies or fingerprinting. The default script stores a random, site-scoped ID in first-party browser storage for up to 30 days so a later purchase can match its original visit. Session-only mode removes it when the browser session ends.
It can be blocked. Hosting the script on your own domain may reduce generic third-party blocking, but DataFastX does not promise blocker-proof tracking.
No. We never store IP addresses or any data that could identify individual visitors. Country-level geolocation is derived at the edge and the IP is immediately discarded.
You can minimize collection, but you remain responsible for configuring the product and your site to meet applicable requirements.
DataFastX adds revenue attribution to privacy-conscious analytics. Its storage and attribution model differs from Plausible and Fathom, so compare the implementations and configure session-only mode when that trade-off fits your site.