Privacy policy

Last updated 15 August 2026

Who is responsible

Vireldan Idle is made and operated by an independent developer based in the Netherlands. For any question about your data, or to exercise any of the rights described below, write to legal@vireldanidle.com.

The short version

• You can play without giving us an email address, a name, or any personal detail.
• There is no analytics SDK, no advertising SDK, and no third-party tracking in the app.
• This website counts visits with software we run on our own server. It sets no cookies and sends nothing to anyone else.
• We do not sell, rent, or share your data with advertisers or data brokers.
• Signing in is optional, and exists only so your progress survives losing your device.

This website

To know which pages are worth writing and which are not, we count visits to vireldanidle.com using Umami, an open-source analytics tool running on our own server in the Netherlands. It is not Google Analytics and it is not a third-party service: the data goes nowhere except the machine that serves this page.

For each visit it records exactly this and nothing else:

• The page you viewed, its title, and the site that linked you here
• Browser, operating system, and device type (for example: Chrome, Mac OS, laptop)
• Screen size and language
• Approximate location derived from your IP address: country, region, and city. City level is as precise as it gets, and it comes from the network you are on rather than from your device.
• How quickly the page loaded, so we know which pages are slow

It sets no cookies and stores nothing on your device. Your IP address is used to derive that location and to build a one-way hash, then discarded. The IP itself is never written down. The hash is rebuilt daily from a rotating value, so the same person looks like a different visitor tomorrow, and it includes this site's identifier, so it is meaningless anywhere else. Session replay, which some analytics tools use to record what you do on a page, is switched off.

The practical consequence: we can see that fifty people read the codex yesterday and that most arrived from Reddit. We cannot see that you personally came back this week, and there is no profile of you, because there is nothing to build one from.

Because none of this identifies you, there is no consent banner to click. If you would rather not be counted at all, any tracker blocker or a browser "do not track" setting will stop it, and the site works exactly the same either way.

Playing anonymously

When you first open Vireldan Idle, the game creates an account for you automatically and gives it a generated handle. No email address, real name, phone number, or contact detail is requested or stored at this point. That account is identified by a token held in your device's secure storage.

The consequence is worth stating plainly: an anonymous account is tied to that token alone. If you delete the app or lose the device, we have no way to recognise you and the character cannot be recovered. Attaching a sign-in method is how you prevent that.

If you choose to sign in

You may optionally attach your account to Google, to Apple, or to an email address and password. This is the only reason we ever hold identifying information, and the only data stored is what is needed to recognise you again:

• Google or Apple. The identifier that provider issues for you, and the email address associated with it. We never receive or store your password for those accounts, and we request no access to your contacts, files, calendar, or social graph.
• Email and password. Your email address, and your password stored only as an argon2id hash. The password itself is never written down in a form that we or anyone else can read back.

Game data

Because Vireldan Idle is a server-authoritative game, your progress lives on our server rather than on your phone. That record includes your handle, your skill levels and experience, your inventory and equipment, your current activity, and your history of combat and dungeon results. Where the game shows you another player, for example an opponent in the arena or a member of your guild, their handle is stored alongside the result of that encounter.

Your handle is visible to other players. Nothing else in the list above is, and your email address is never shown to another player.

What you write

Two parts of the game let you write freely, and both are stored on our server rather than only on your phone.

• Guild chat. Messages are kept so the conversation is still there when other members of your guild open the game, and so that a reported message can be looked at. They are visible to members of that guild, and to us. Guild leadership can remove them, and any member can report one.
• Feedback you send us. If you use the feedback form in the game, what you wrote is stored along with your handle so we can act on it and, where it warrants a reply, answer you.

Both are used to run the game and to keep it civil. Neither is used for advertising, analysed for profiling, or shared with anyone else. Please avoid putting anything in either that you would rather we did not hold, and see the terms for what is and is not allowed in chat.

Notifications

If you turn on notifications, the app registers a push token with Apple and sends it to our server so we can tell you when an activity finishes or your attention is needed. The token identifies the installation, not you. Turning notifications off in your device settings stops the messages, and you can ask us to delete the stored token at any time.

Device motion

The night sky in Starcalling tilts as you move your phone. That effect reads your device's motion sensor while the screen is open and uses the values purely to animate what you are looking at. Motion data is never transmitted off your device and never stored.

Technical logs

Like any server on the internet, ours keeps operational logs of the requests it receives so that faults can be diagnosed and abuse can be stopped. These may include your IP address, the time of the request, and which endpoint was called. They are used for running and securing the service, and for nothing else.

Where your data is held, and who else touches it

Game data is stored in a Postgres database on servers we rent from Hetzner Online GmbH. Push notifications are delivered through Apple's Push Notification service and Expo's push service. If you sign in with Google or Apple, that sign-in is handled by them. Those providers act as processors for the specific function described, and none of them receive your game data for their own purposes.

How long we keep it

Your account and its game data are kept for as long as the account exists, because that record is the saved game. Ask us to delete it and it is gone, along with any email address and push token attached to it. Operational logs are short-lived and rotate out on their own.

Your rights

If you are in the European Union or the United Kingdom, the GDPR gives you the right to see what we hold about you, to have it corrected, to have it deleted, to receive a copy in a portable form, and to object to a particular use of it. You can exercise any of these by writing to legal@vireldanidle.com. We will not charge you for it and we will not ask you why. These rights are available to everyone who plays, wherever you live.

Children

Vireldan Idle is not directed at children under 13, and we do not knowingly collect data from them. If you believe a child has created an account, write to us and we will remove it.

Beta testing

While the game is distributed through TestFlight, Apple provides us with aggregate information about beta installs, sessions, and crashes, and shows us the email address you used to accept the beta invitation. Apple's handling of that data is governed by its own privacy policy. Any crash report or feedback you choose to send through TestFlight comes to us with whatever you wrote in it, so please leave out anything you would rather we did not see.

Changes to this policy

If this policy changes in a way that affects what we collect or what we do with it, the date at the top will change and the new version will be published here before the change takes effect.