Frequently asked questions

No. Yegonota does not set any cookies in your visitors' browsers. Not for tracking, not for sessions, not for anything. Your visitors will never see a cookie consent banner because of Yegonota.

The tracking script is served from a separate subdomain (script.yegonota.com) rather than the main yegonota.com domain. This means browser cookie isolation rules prevent any cookies from the main domain from being attached to tracking requests — even if they existed, which they don't.

No. We never store IP addresses, names, email addresses, or any other information that could identify an individual visitor. We only store anonymous, aggregated data — page URLs, timestamps, screen sizes, browser families, and country codes.

When a visitor loads a page, their browser automatically sends a network request to our server. We combine four pieces of information from that request: the network address, browser type, screen size, and the current 6-hour time window. These are run through a one-way mathematical function. The result is a temporary code that:

• Cannot be reversed to recover any of the original values
• Is stored only on our servers to group pageviews into visits
• Is never placed in the visitor's browser
• Resets every 6 hours automatically
• Is never shared with anyone

If two people visit your site from the same network at the same time using the same browser and screen size, they may be counted as one visitor. This is a known limitation of privacy-safe tracking — the tradeoff for never storing personal data. We believe it is the right tradeoff for protecting your visitors' privacy.

When your visitors load a page with Yegonota installed, their browser sends a network request to our server — as it does with any third-party script. We use the network address from that request to estimate visits and look up the approximate country, then discard it immediately. We never store it, never log it, and never share it. We only save the 2-letter country code (for example: NL, DE, US) using a local database (MaxMind GeoLite2). Country detection is approximate — we cannot determine a city or address.

Add one line of code to your website:

<script src="https://script.yegonota.com/track.js?v=1.0.0"
        data-site="YOUR_SITE_ID" defer></script>

You get your site ID when you register a site in the dashboard. That is all. No configuration needed.

For every page visit: the page URL, timestamp, screen width, browser family, operating system family, approximate country, and UTM parameters if present.

For clicks and scroll events: outbound link clicks, download clicks, and email link clicks are tracked automatically. Button clicks are opt-in only — a button is only tracked if it has a data-ye-event attribute (see the getting started guide). Scroll depth per page is also tracked automatically.

See the Events page for the full details on how each event type works.

We do not track individual visitors, sessions across sites, mouse movements, form inputs, keystrokes, or any personal information. We do not build visitor profiles. We do not sell data.

Yegonota compares your current period's data with the previous period and generates plain-language summaries. For example: "61 people visited your site this period — down 24% on last period." All insights are generated by rules, not by AI. The output is predictable and consistent.

If you downgrade from Pro or Premium to Starter, data older than 60 days is deleted at your next billing cycle. If you cancel entirely, your data is deleted within 30 days. You can export your data at any time on Pro and Premium plans before cancelling.

• Starter: 60 days
• Pro: 2 years
• Premium: unlimited

Yes, on Pro and Premium plans. Go to your Sites page and click the export button. You will receive a CSV file with your pageview and event data.

Yes. The tracking script automatically detects navigation events in SPAs and records them as pageviews. No extra configuration needed.

No. The script is under 2KB, loads with defer so it never blocks page rendering, and fails silently if it cannot reach the server. It has no effect on your Core Web Vitals.