Data Collection

Hardal is a first-party, server-side analytics and data platform. Unlike a third-party tracking pixel, our collector runs as part of your own website or app, on your own domain. What gets collected is data about your visitors and customers, shaped by your implementation, sent to Hardal on your behalf. This page explains exactly what that includes.

Standard analytics data

For every page view and event, we capture:

Page URL: protocol, hostname, and pathname
Referrer: the referring domain
UTM parameters: source, medium, campaign, content, if present
Device and browser: user agent, viewport and screen dimensions
Locale: country and language, derived from the browser's timezone and locale settings, not from your IP address
Session data: a session is considered to end after 30 minutes of inactivity
Custom events: whatever events and properties your own implementation sends us (e.g. add_to_cart, purchase), through our Web, Shopify, mobile, or API SDKs

Identity across devices and platforms

By default, Hardal assigns each visitor a first-party identifier stored via a cookie on your domain, never a third-party cookie. This is what lets you see one customer profile instead of duplicate users when someone moves between your web, iOS, and Android surfaces.

A cookieless configuration is also available if you'd rather not set any cookie at all. This is what we run in production for customers like Bilyoner, who moved to cookieless first-party analytics with one unified profile per user across web and mobile.

IP addresses

IP addresses are used transiently for geolocation and abuse/fraud prevention. We don't store them in raw form beyond that processing, unless you've explicitly configured a destination that requires it (for example, an ad platform's server-side conversion API).

Data you choose to send us

If your own implementation forwards customer identifiers (typically a hashed email or phone number, to power destinations like Meta Conversions API, Google Enhanced Conversions, or the TikTok Events API), that data flows through Hardal because you sent it, not because we collected it independently. We don't read emails, phone numbers, or other personal data out of your site's forms or checkout on our own.

What we never do

No third-party cookies
No cross-site tracking or fingerprinting across domains or customers
No selling or sharing data across our customers' accounts
No combining one customer's data with another's

Export and retention

Your data stays queryable in your own workspace. You can connect it to Looker Studio, Tableau, Power BI, or Hex, or query the underlying database directly. Retention follows your plan's settings.

Who controls what's collected

You, as our customer, are the Data Controller and decide what's captured through your tracking implementation; Hardal is the Data Processor executing that configuration. See GDPR & KVKK Compliance for the full breakdown of that relationship.

For developers

Full setup guides and API references live at docs.usehardal.com.