Analytics Terms
Terms for using climbrk Analytics: what the snippet captures, privacy-friendly cookies, your domain-ownership responsibility, and honest limits.
What climbrk Analytics is
climbrk Analytics shows how a website is being reached by people, search engines, AI discovery sources, referrals, direct traffic, and detectable crawler/script/pixel activity, from one lightweight snippet you install on a domain you own or manage.
These are traffic and discovery signals captured by the climbrk snippet. They are estimates for understanding reach, not a system of record.
Domain ownership and responsibility
- You confirm you own or manage each domain you connect to an Analytics Property.
- You are responsible for informing your visitors that analytics tracking is used where required by applicable law.
- Only events from your verified domain (or its approved hostnames) are counted as valid traffic. Events from other domains are filtered out.
What we collect
- Page URL and path (query strings are stripped where possible), referrer, and a coarse device/browser family.
- Privacy-friendly first-party cookies used only to count sessions, reduce duplicate visits, and attribute first-touch and last-touch discovery sources.
- A hashed IP and a hashed user-agent. We do not store raw IP addresses for Analytics.
- Detectable crawler/bot activity where the script or pixel is loaded.
What we never collect
climbrk Analytics does not collect form inputs, passwords, payment details, or visitor messages.
It does not perform keystroke logging, session replay, advertising profiling, or cross-site tracking.
Cookies
First-party cookies are used only for de-duplication, sessions, returning-visitor counts, and source attribution. They are not used for advertising or cross-site profiling.
Honest limits
- We report detectable crawler activity and AI/search referral traffic. Not every bot or AI crawler is detectable.
- climbrk does not provide exact chatbot citation counts and does not guarantee rankings or AI citations.
- During unusual traffic spikes, some events may be sampled or filtered to protect Analytics accuracy.
Fair use, data, and control
Plan-based event limits apply. Traffic beyond your plan's clean-event allowance may not be counted.
You can pause an Analytics Property, regenerate its public site ID, delete its collected data, or revoke it at any time from Analytics settings.
For questions about these terms, contact [email protected].