Privacy Policy
This policy explains what data is processed when you use animica.org and the first-party services linked from it, why, for how long, and what choices you have. It is written to be specific rather than generic: if something is not listed here, we do not do it.
Effective date: 2026-09-09. Supersedes all earlier versions.
1. Who we are and scope
"Animica", "we" and "us" refer to the maintainers of the Animica open-source project, who operate
this website and the hosted services listed in section 6. This policy covers animica.org and
those services. It does not cover third-party websites we link to, independent node operators,
mining pools run by others, exchanges, or forks of our software. The software itself (node,
wallets, SDKs) ships with telemetry disabled by default; its opt-in telemetry
behaviour is described in docs/legal/PRIVACY.md in the repository and summarised in
section 7.
2. Data we collect on this website
2.1 Server access logs
Like almost every web server, ours records a line for each request: the requesting IP address, the time, the URL requested, the HTTP status, the referring page if your browser sends one, and the user-agent string. We use these logs to keep the site up, to block abusive traffic, and to understand which pages are read. We do not combine them with any other data to identify you.
2.2 No analytics script is loaded
This site does not currently load Google Analytics, Plausible, PostHog, or any other analytics or session-recording script. The site's source code contains optional, opt-in adapters for Plausible and PostHog, but they are not enabled in the published build. If that changes, this policy will be updated before any such script is served, and the adapters are written to honour the Do Not Track and Global Privacy Control signals.
2.3 Web fonts
Pages load the IBM Plex Mono and Space Grotesk typefaces from Google Fonts
(fonts.googleapis.com and fonts.gstatic.com). When your browser fetches
those files, Google receives your IP address and the usual request headers. Google's handling of
that data is described in its
privacy policy.
2.4 Browser storage
We use a small amount of browser-local storage for convenience, never for tracking: for example,
sessionStorage remembers that you dismissed the advertising banner on the home page
for the rest of that tab's session. This data never leaves your browser, and we do not set
first-party cookies for identification.
3. Advertising and paid referrals
3.1 Adcash
We display advertisements served by Adcash (Adcash OÜ, Estonia) through its Auto-Tag unit. Auto-Tag means Adcash — not this site — chooses which ad format to show on a given page view, which can include a display banner, an in-page notification, a full-screen interstitial or a pop-under window. As with any embedded third-party ad resource, Adcash receives your IP address, user agent and request headers when the tag loads, and uses cookies, pixel tags and similar identifiers to select ads, cap how often you see the same ad and measure ad performance. Adcash's own terms and privacy information are at adcash.com/legal.
This site does not currently operate a consent management platform, so no
consent prompt is shown before the Adcash tag loads and we cannot promise you that the ads
you are served are non-personalised. If you are in the European Economic Area, the United
Kingdom or Switzerland and do not want this processing, block third-party scripts and cookies
for acscdn.com in your browser, or use an ad blocker — the site works normally
without the tag. We will publish an update here if a consent prompt is added.
The tag is present across animica.org, including the Thronebound game and Thronebound Realms.
It is not loaded on animica.dev/health, which sets a content security policy that
blocks third-party scripts outright.
We previously served ads through Google AdSense, removed on 2026-09-01, and then a Coinzilla site-verification tag, removed on 2026-09-05. Neither is present any more and no Google or Coinzilla advertising cookie is set by this site. Thronebound's optional "watch a video for gems" rewarded ads relied on the Google tag and remain switched off: Adcash Auto-Tag has no rewarded-video interface, so no reward is offered in exchange for viewing an ad.
3.2 A-Ads
The home page includes a single, clearly labelled "Sponsored" banner served in an iframe by
A-Ads (acceptable.a-ads.com). The banner can be closed, and that choice is kept for
the session. A-Ads describes its unit as cookieless; its own policy is at
a-ads.com/privacy-policy.
As with any embedded third-party resource, A-Ads receives your IP address and request headers
when the iframe loads.
3.3 Affiliate links
Some pages carry links to other companies’ shops, always labelled “Sponsored” and marked rel="sponsored nofollow". They are served through CJ Affiliate (Commission Junction), and we earn a commission if you buy something after following one. As of 2026-09-09 the only such link is in the Thronebound Realms gem shop.
We send CJ nothing about you. The link is an ordinary link; nothing is transmitted unless you click it. If you do, CJ receives your IP address and browser user agent and sets its own cookie so that the advertiser can attribute a later purchase to us. That processing is CJ’s and the advertiser’s, under their own policies (cj.com privacy policy); blocking third-party cookies, or simply not clicking, prevents it entirely.
We keep a count of how many times each advertiser’s link was clicked, per day. It is a bare number, with no account, session, IP address or timestamp attached to it, and exists only so we can tell a link nobody clicks apart from one that never appeared. Clicking a sponsored link never changes anything in a game or grants any in-game reward — rewarding affiliate clicks would be fraud against the advertiser.
3.4 Moving quote requests (Near)
The neighbourhood search at animica.org and its city guides at /moving-to/<city> can show a form offering quotes from moving companies. It is shown only after you tell us you are moving — we ask, and we never infer it from your behaviour — and using it is entirely optional. Nothing on this site requires it.
The form has two steps, and they are different in what they collect. The first step asks only about the move itself: the places you are moving from and to, the date, the size of the move, and the first three digits of your phone number. We send those details, and nothing else, to MoveAdvisor to ask whether any mover covers that route. No name, email address or full phone number is sent at this step, and if no mover covers the route we say so and never ask you for them.
Only if you then choose to continue, and tick the consent box, do we ask for your name, email address and phone number. Submitting that form sends those details, together with the move details above, your IP address and browser user agent, and the page you were on, to MoveAdvisor, who pass them to licensed moving companies so that those companies can contact you by phone, text message and email about your move. MoveAdvisor’s own privacy policy is at moveadvisor.com/privacy, and requests to delete or access what they hold need to go to them as well as to us.
We are paid for this. MoveAdvisor pays us for each lead their network accepts. That is how the search and the city guides stay free to use. It has no effect on which neighbourhoods a search returns or on any number published on this site — the measurements come from OpenStreetMap data and are computed before any of this is shown.
We keep our own record of each submission so we can check their monthly report: the date, where the move was from and to, its size, the identifier and price they returned, and a one-way hash of your email address and phone number. We do not keep a copy of your name, email address or phone number. The legal basis is your consent, which you give by ticking the box, and you can withdraw it by contacting us — though once a lead has been passed to a moving company we cannot recall it, and you would need to ask them and MoveAdvisor directly.
4. Data processed by our blockchain services
4.1 Public RPC (rpc.animica.org)
The JSON-RPC endpoint logs the requesting IP address, the RPC method name, the response code and
the request duration. It does not persist request bodies beyond what is needed to serve the call.
Transactions you submit through tx.sendRawTransaction are, by design, broadcast to
the peer-to-peer network and recorded permanently on the public ledger, together with the sending
address, recipient, amount and fee. An IP address in our logs is not linked to an on-chain address
unless you submit a transaction from that IP, in which case the two appear in the same log line
for the retention period below.
4.2 Block explorer (explorer.animica.org)
The explorer is a read-only view of public chain data. Its web server and API log requests in the same way as this site (section 2.1), including the addresses and transaction hashes you search for, because they are part of the URL.
4.3 Mining pool (pool.animica.org)
To pay miners, the pool must record the payout address you connect with, the IP address of each stratum connection, share submissions, and payout transactions. The pool's public statistics pages show aggregate hashrate and, for a given payout address, that address's worker statistics; they do not show IP addresses.
4.4 Wallet apps
The browser-based web wallet at wallet.animica.org was discontinued on 2026-07-11 and now serves a notice only; it never held keys. The wallet apps we publish (browser extension, desktop, mobile) are non-custodial: keys are generated and used on your device and are never sent to us. They make RPC calls on your behalf, so the RPC logging in 4.1 applies to those calls.
4.5 AI API and developer services
animica.dev, console.animica.org and pay.animica.dev have their own account-based terms and notices shown at sign-up or on first use, because they process API keys, prompts and payment records that this site does not. This policy does not replace them.
5. Retention
| Data | Retention | Purpose |
|---|---|---|
| Web server access logs | Up to 30 days | Security monitoring, abuse prevention, capacity planning |
| RPC / explorer / pool request logs | Up to 30 days raw; aggregates up to 180 days | Rate limiting, abuse prevention, performance statistics |
| Crash and error reports (opt-in only) | Up to 90 days | Stability of first-party software |
| Email correspondence | As long as needed to handle the request | Support, security disclosure, legal obligations |
| Moving quote submissions | Up to 24 months, hashed contact details only | Checking the referral partner’s monthly report against our own record |
| Affiliate link click counts | 90 days | A per-advertiser daily total with no identifiers, to check the network’s own report |
| Blockchain data | Indefinitely, by design | Public ledger; cannot be altered or deleted |
Logs may be kept longer in the specific case of an ongoing security investigation or a legal obligation, and only for as long as that reason exists.
6. Services covered by this policy
animica.org, rpc.animica.org, explorer.animica.org, pool.animica.org and academy.animica.org. Services with their own notices are listed in 4.5.
7. Software telemetry (opt-in)
The animica package, the wallets and the SDKs send no telemetry unless you turn it
on (ANIMICA_TELEMETRY=1, --telemetry=on, or a wallet's Settings → Privacy
toggle). When enabled, the data is limited to version, platform, feature flags, timings and error
counts. It never includes private keys, mnemonics, wallet addresses, transaction bodies, clipboard
contents or precise location. Details are in docs/legal/PRIVACY.md.
8. Legal basis and international transfers
Where the GDPR or UK GDPR applies, we rely on our legitimate interest in running secure, reliable services for access logging and abuse prevention, and on your consent for personalised advertising and for any opt-in telemetry. Our servers and those of the third parties named above may be located outside your country; Google's (Fonts), Adcash's and A-Ads' transfer mechanisms are described in their own policies.
9. Your rights
Depending on where you live, you may have the right to access, correct, delete or restrict the processing of personal data, to object to processing based on legitimate interest, to data portability, and to lodge a complaint with a supervisory authority. Because the only personal data we ordinarily hold is an IP address in a rotating log, we can usually act on a request only if you tell us the IP address and approximate times involved. Data recorded on the blockchain cannot be deleted by anyone, including us.
10. Children
This site is not directed at children under 16 and we do not knowingly collect data from them.
11. Third-party links
We link to GitHub, PyPI, NonKYC, X and other sites. Their privacy practices are their own. A link is not an endorsement and does not make us responsible for that site's data handling.
12. Changes
We will update this page when our practices change and revise the effective date at the top. If a change materially expands what we collect (for example, enabling an analytics script), we will note it here before it takes effect.
13. Contact
Privacy questions and requests: privacy@animica.org. General contact: contact@animica.org. Security issues: security@animica.org (see Security).
Sources
docs/legal/PRIVACY.md · website/src/layouts/BaseLayout.astro (fonts) · website/src/components/AdBanner.astro · website/src/utils/analytics.ts (opt-in adapters, not enabled) · Google partner-sites policy