track.easterbunny.cc was designed with your privacy in mind. By using track.easterbunny.cc, you agree to this privacy policy and the data collection policies outlined herein.
In this document, We (“we”) and Our (“our”) refers to the developers of track.easterbunny.cc. You/your (“you”, “your”) refers to you, yourself, your data, etc.
track.easterbunny.cc does not collect personally identifying data, nor collect any data from users directly without consent. However, we do collect anonymous, aggregated analytics for analyzing how and where the tracker is being used so we can improve the user experience and inform decisions when we do testing on the tracker each year. We do so in four different ways - through the Cloudflare CDN, Cloudflare Page Insights, the Geo API, and the Google Maps API.
With user consent, track.easterbunny.cc temporarily collects, but does not store your precise location information through the "Your location accuracy" feature.
Cloudflare:
We collect analytical data through Cloudflare (the CDN provider we use) to determine where and how much the tracker is being used at a country and state level, along with other diagnostic information at about 5-15 minute intervals. This information includes the TLS version used to access the tracker, the user agent used to access the tracker, device type, the ASN of originating traffic, and counts for requests to tracker assets. Using this data, we are able to determine total request & bandwidth counts, see where the tracker is getting used and at what times this usage is occurring.
Cloudflare rotates this data every 30 days, however, we export the data from the 52 hours of peak tracker traffic (2 AM ET Easter Eve to 6 AM ET Day-after-Easter).
Cloudflare Page Insights:
We collect browser performance data from Cloudflare using their Browser Insights feature. On all hits to track.easterbunny.cc, we have injected code that will load Cloudflare Insights' JS Beacon, which should in most cases send back data to Cloudflare regarding page load times and visits. No personally identifiable data is sent back with this feature.
You can opt out of this by blocking loads from the Cloudflare beacon, which most adblockers automatically do.
Geo API:
We run an in-house Geo API to determine a users location in a non-invasive, non-precise manner to determine when the Easter Bunny will arrive at your location, and how far the Easter Bunny is from you. This API is called any time the tracker is loaded to set up these metrics. We use the MaxMind GeoLite2 database for IP location approximation.
We use the logs generated by the Geo API to determine how many hits we've received in a certain period of time, as well as seeing the types of devices that are visiting the tracker by using a browser's user agent. We specifically use the user agent from the Geo API to perform analyses on which devices are using the tracker, including browser type & version, OS type & version when available, and model number when available. This informs our testing decisions. However, we cannot see the IP that a request comes from - only the IP of the Cloudflare server that forwarded the request to the Geo API.
Geo API hits are only logged when the tracker is active past the pre-tracking stage, and is not queried during the countdown phase. When the tracker switches into the pre-tracking stage, a query is made.
Additionally, queries to the Geo API from the tracker are logged at hits between 2 AM ET Easter Eve to 6 AM ET Day-after-Easter to help us analyze tracker performance. Hit counts are saved every minute. We have set up a custom dashboard available to administrators to get a real-time hit count of the tracker, which from the minutely hit counts allows us to determine hits per minute, hits per hour, and our estimated map bill.
Geo API logs are generally speaking rotated every 10 days, with logs getting saved during monthly backups and ongoing backups that purge after about 4 months. The logs during the 52 hour period of highest traffic (2 AM ET Easter Eve to 6 AM ET Day-after-Easter) are saved permanently.
There is the potential for users to be individually identified through a rare user agent that only receives a few hits. However, this is limited to identifying someone with this user agent who visited the tracker at this time, and no further identifying information can be deduced.
You can opt out of the Geo API logging by blocking requests to https://geoapi.easterbunny.cc. However, we ask that you avoid doing this as blocking this request greatly impacts the insights we get from the tracker. Additionally, disabling Geo API requests will disable the arrival time & distance from you metric, and a warning will appear when the tracker is loaded to inform you that the Geo API can't be reached.
Geo API Extended User Agent Hints:
Starting in 2023, numerous Chromium-based browsers are now sending reduced user-agent information in an effort to prevent fingerprinting of users on the internet. We previously relied on data baked into the user agent sent to our server to gather information about device model, OS version, and browser name/version so that we could test against the most popular devices used on the tracker. However, we can no longer gather this information from the user agent of Chromium-based browsers.
As a result of these changes, we have incorporated a change in tracker versions v7 or higher that, on Chromium-based browsers with the navigator.userAgentData property present, automatically sends high entropy data (including device model, bitness, form factor, OS name & version in addition to high-precision browser name/version data) about your browsers environment to the Geo API when the tracker loads. This data also includes your browsers original user agent, in addition to client & server-side timings and the IP of the Cloudflare node that served your request so we can match up the data against our web logs.
Data is securely stored on our servers and will not be distributed to third-parties. This data is only used for diagnostic purposes to collect data on the types of devices using the tracker.
If you would like to disable this feature, please prevent your browser from being able to access the URL https://geoapi.easterbunny.cc/api/v1/uaExtendedData. As mentioned previously, we would appreciate you not disabling this request, as it allows us to cruically gather information about the devices being used to access the tracker.
Google Maps API:
The Google Maps API we use collects some data about the experience of the map aspect of the tracker. In short, we can see the amount of map loads being made to the tracker, in addition to how long those loads took.
You can opt out of Google Maps API logging by blocking the quota service request, which most adblockers already do.
Your location accuracy feature:
Introduced in Version 6.1, users of track.easterbunny.cc can enhance the tracker experience by consenting to the tracker accessing their precise location. Enabling this feature allows the tracker to more accurately estimate when the Easter Bunny will arrive, and improves the accuracy of the distance from you feature.
When this feature is activated, we query your precise location from your device. This precise location is then sent to our servers so we can perform a reverse geocode, sending the results back to the tracker as a confirmation that we got your location correctly. Lastly, your precise location is saved on your device for future use.
When querying our servers, your precise location is not visible to us at any point. We only use your precise location to process the request and do not save any request details, including your precise location. During communication with our server, all data is encrypted and is not visible to any third parties.
The tracker saves your precise location, but only does so locally on your device through local storage. This is the same storage system used for saving other settings of the tracker. We cannot see your precise location at any point when you use this feature. Additionally, when sharing diagnostic data for support purposes, we automatically redact the precise location fields to ensure we cannot see your precise location.
At any time, you can remove your precise location from the tracker by resetting the tracker settings to their defaults. Additionally, you may reset site storage data for track.easterbunny.cc and this will remove precise location information from the tracker.
If you requested a precise location between the release of Version 6.1 and Version 6.1.1 of the tracker, your precise location may have been stored in our server logs, as we used query parameters that attached your precise location. Version 6.1.1 of the tracker now encodes your precise location in the body of the request, improving privacy. However, due to the timing of the release, these logs will not be saved, and all logs during this timeframe will be purged by March 30, 2023. As a reminder, these logs are only visible to our server administrators and are not shared with any third-party.
Third-party privacy policies:
By using the tracker, you agree to the privacy policy of these other businesses.
We're ready to answer any questions, suggestions, or feedback you might have about your privacy on our tracker. You can email us or Tweet at us with your thoughts. Contact information is available on the FAQ page.
Return to the tracker