Paz StudiosPrivacy policy
This page describes what the Aniimo Companion Overwolf app sends back to us, and why. It applies to the anonymous usage telemetry only. It’s short on purpose — if you finish it and you’re still not sure what leaves your machine, we’ve failed at writing it.
What we collect
The first time it runs, Aniimo Companion generates a random id (a UUID) on your own device. It isn’t linked to your name, your Overwolf account, or anything else — it just lets us tell “one install used the app twelve times” apart from “twelve installs used it once.” Alongside that id, we collect:
- The app version you’re running.
- Launch events: which window opened, the desktop window or the in-game overlay, and whether it was the first launch of the day.
- Feature events: which panel you opened, map or dex, and a coarse action name. Not what you searched for or clicked inside it.
- Error reports: an error message, a stack trace, and roughly where in the app it happened, so we can fix what’s broken.
- The two-letter country your request came from. We get this from Cloudflare, sitting in front of our server; we don’t look it up ourselves.
That’s the complete list. The server enforces it with an allowlist: any field that isn’t one of the above is dropped before it’s ever written down, no matter what the app sends.
What we don’t collect
No name, email address, Overwolf account, or game account. No search terms. No record of which creatures or map markers you look at. And no IP address is ever stored — the table we write events into has no IP column at all.
About IP addresses
Your IP address passes through our server briefly, the way it does for any web request. We use it in memory, for a moment, to rate-limit abuse, so one client can’t flood the endpoint. It is never stored, never logged, and never written to the database.
About error reports
A stack trace can contain a filesystem path, and on Windows that path usually contains your account name. Before an error report is stored, we strip anything that looks like that kind of path, on a best-effort basis. This is a prefix match against common path shapes, not a guarantee: we can’t promise every error report is free of anything personal, and we’re not trying to win an arms race against every possible way a path could show up. It’s a good-faith attempt to keep your Windows username out of our database, not an ironclad filter.
How long we keep it
Honestly: right now, we don’t delete old events automatically. Nothing does that yet, so everything collected so far is still sitting in the database while we build that part. Our intention is to delete individual events after 90 days and keep only aggregate daily totals beyond that. We’ll update this page the day that’s actually in place — not before.
Why we collect it
To see how many people actually use the app, how quickly updates reach them, and what’s breaking. That’s it: none of this telemetry feeds an advertising or analytics network, and nothing here is sold or shared with anyone.
The app itself does display ads, through Overwolf’s own ad SDK — that’s separate from the telemetry described on this page. The ad SDK doesn’t use any of the data listed above, and we don’t control it, so we won’t describe what it does or doesn’t collect. It’s covered by Overwolf’s own privacy policy, not this one.
Turning it off
In the app: Settings → “Share anonymous usage data.”
It’s on by default and clearly labelled; we’re not hiding it in a submenu. Turn it off and collection stops immediately. Anything queued but not yet sent is discarded, not sent late.
Questions
Email [email protected], or drop by the community Discord.