In this document, We (“we”) and Our ("our") refers to the team running track.orthodoxbunny.cc. You/your (“you”, “your”) refers to you, yourself, your data, etc.
track.orthodoxbunny.cc does not collect, and cannot collect any personally identifying information. However, we do collect anonymous, aggregated analytics to improve the tracker experience, and gain analysis on the usage of our tracker.
We collect analytical data through Cloudflare (the CDN provider that we use), and logs generated by requests to the Geo API (used for the estimated arrival time feature).
In short, through the Geo API and Cloudflare, we can generally see:
How much our tracker is being used in a given timeframe (request count, data transferred, unique visitors)
Where and how our tracker is being accessed (browser/device type, country, referrer, etc)
How Cloudflare is performing to enhance the speed of our tracker
Our analytics methodology ensures that you cannot be tracked across the web. We only use privacy-respecting methods to collect analytical data.
We don’t sell any tracker data to third parties, because we don’t have any third parties to sell data to.
The methods we use to approximate your location to generate the Easter Bunny’s estimated arrival time are privacy-friendly, and do not use any invasive techniques to do so.
Lastly, track.orthodoxbunny.cc is tracker-free. We're not explicitly ad-free as we continue to search for ad solutions. Although some browser extensions may identify our CDN providers as trackers, we do not intentionally put trackers on our website (such as Google Analytics, Facebook share buttons).
How we collect data
Anonymized analytics are collected via Cloudflare and the Geo API access logs. These two collection methods allow us to gain good insight into site analytics and usage, and we use both methods extensively for different purposes.
How we use Cloudflare to collect data
track.orthodoxbunny.cc is proxied behind Cloudflare, a global CDN used by millions of websites to enhance loading times and performance. It’s a crucial asset to us, given it takes an enormous load off of our web servers during tracking, and allows us to scale up the tracker for unexpected traffic.
Cloudflare collects a wide variety of data that gives us insights into how our tracker is performing. These analytics are what we call a “birds-eye view”, they allow us to see general use, but we cannot pinpoint specific users in this analytical data. We use this data to gather insight on where our tracker is being used, and how we can improve the tracking experience, along with making region-specific engagements and improvements.
Cloudflare analytics data is rotated every 30 days. However, we regularly save some analytics data during the course of tracking for future reference.
How we use the Geo API logs to collect data
Since version 4, we’ve been using an in-house “Geo API” to serve the approximate location of users based on their IP address. Because we have custom Cloudflare rules so that 100% of requests to the Geo API are uncached and are forwarded to our origin server, requests to the Geo API will fall under our origin server’s logging system.
In short, the Geo API logs the user agent of each request, which can include information about your browser type/version, your system type/version, and your device model only during tracking. The Geo API is not requested on the countdown page.
There is the potential for you to be identified in the Geo API logs by your user agent if it is extremely rare/uncommon. If this is the case, you would be identified by your device model, system type/version, and browser type/version.
We used this system in version 4 to get the total number of true hits to our tracker, as the Geo API is requested once on tracker load, and we plan on doing so again this year.
We also used the Geo API logs to get in-depth data about browsers & browser versions being used, so we could focus efforts on maintaining compatibility. We plan on doing this again for v5.
Our origin server logs are rotated every 10 days. However, we plan on saving the request log during tracking, as we did with version 4. We also generate a local GoAccess report to visualize the log data.
If you don’t want the Geo API to collect information about you, you can block requests to geoapi.easterbunny.cc in your browser. Note that doing this will disable the estimated arrival time feature.
Other tidbits of information
We use the MaxMind GeoLite2 database for IP location approximation. At this time, you cannot opt out (or opt back in) your IP to return a geolocation, as the last opportunity to do so was before 6:00 PM EDT on March 29, 2021.
We make extensive use of the user agent that your browser reports across the website. Spoofing your user-agent may cause some issues.
We’re Tor friendly! You shouldn’t see any captchas or other verification methods when using Tor (if you do, let us know). We’re planning to make a .onion URL for v6 and onward.
Our servers are located outside of the US, so they aren’t subject to the Patriot Act.
Privacy Policies of third-party services we use
We use these third parties provided by other businesses to run the tracker. If you want to know more about their privacy policies, we’ve included some links below.