Privacy · Butcher Hero Atlas

Profile and Google sign-in

Without signing in, your profile is stored in the browser on your device. After you sign in, a copy of the profile is saved on the project server. From Google we get your account ID, name and email. Your Google password is never shared with the site. We don't request access to your Google mail or files.

A cloud profile has no automatic deletion date. To delete your account and related data, contact support. Signing out ends the session but doesn't delete the saved profile.

BIN, screenshots and video

BIN files are parsed in server memory and not stored. The site doesn't edit or offer downloads of game BIN files.

Screenshots and videos are recognized right on your device: the file isn't sent to the server. If your device can't manage, the screenshot or only selected video frames are sent to the server. They're recognized on the project server without outside AI services; originals are deleted after processing, reports and check frames after 24 hours. Only the user who uploaded them can see the result. Results aren't applied to your profile without confirmation.

The “Help improve recognition” button sends a screenshot only when you press it. The server rebuilds the image from pixels without file metadata and stores it with your comment, the list of recognized values and your device and browser type. Only the Atlas developer sees this data, to find and fix recognition errors. It's deleted after 30 days.

Feedback

We store the message text, its status and prepared images. Images are shrunk and re-saved without original metadata. Only the sender and the site owner see a message. After it's marked “Processed”, the message and its images are deleted automatically after 90 days.

Statistics and technical data

The visit country is estimated from the IP on the server using a local DB-IP database. Only the country code is stored in statistics, without the IP address. The address isn't sent to any outside geolocation service.

We collect aggregated section visits, device type, browser and referring site. To count unique visitors, a random browser ID is kept in a technical cookie for 90 days. The server stores only its protected hash, with no account name or email. Visits are told apart by a temporary tab ID; repeat openings of a section by the same browser within the chosen period count once. Profile contents, BIN files, messages and uploaded files never go into analytics. Detailed aggregates are kept for 90 days.

Signing in needs a technical session cookie. Settings and the local profile use browser storage. The server may also keep technical error and security logs. Data is never used for ad profiles.

Background bot protection

Google reCAPTCHA v3 protects message sending, file imports and heavy calculations. The check runs in the background, with no typing or picture selection. Google processes technical browser and connection signals needed to detect automated requests; the check may set the technical _GRECAPTCHA cookie. Profile contents, BIN files, message texts, screenshots and videos are never sent to the check service.

The purpose is to protect the site from bots and abuse. More about data processing: Google Cloud Privacy Notice. Access rights, upload limits and CSRF protection are checked separately.

Questions about data

Project support: dimateplive@gmail.com. You can also send a message through the “Feedback” section. In a deletion request, name the Google account the data belongs to; don't send your password.