DocumentMeroveil · Melioratrix LLC

Privacy Policy

How Meroveil handles your data, in plain language. This page matches what the game actually does — if that changes, this page changes with it.

Effective date
2026-11-02
Data controller
Melioratrix LLC (“we”, “us”)
Contact

What we collect

  • Account data: a device identifier and, if you register, your email address. Your display name is visible to other players. The device identifier is a random id the app creates the first time it runs (not an id the operating system gives us, so it cannot be matched to you in another app); it is stored on your device, scrambled with a key built into the app, and sent to us on every guest sign-in, because it is your login for a guest account. So that a guest can get back in after reinstalling the game or on a new phone, the game also saves that guest sign-in (with your player ID and display name, never an email or password) in your phone’s own credential store: the Keychain on iPhone, which iCloud Keychain can sync to your other Apple devices, and Google’s Block Store on Android, which your Google backup can carry to a new phone (end-to-end encrypted when the phone has a screen lock). Apple and Google keep it as part of your device’s own data; it is not sent to anyone else. Deleting your account or linking an email removes it. To keep a guest account for sure, link an email.
  • Network data: our servers see the IP address each connection comes from, as every server on the internet does. We do not store it with your account. To limit abuse (for example repeated sign-in attempts) we keep short-lived counters keyed by a one-way hash of the address, deleted after 30 days without use, and logs can contain IP addresses (see Retention & security).
  • Game data: progress, inventory, scores, guild membership, and messages you send in chat (visible to their recipients).
  • Chat moderation records: the game checks chat messages automatically against a word list that we keep ourselves; no outside service is involved, and no message leaves our servers for it. A message that hits the list may be blocked. When a line is blocked or flagged, we keep an excerpt of it, at most 120 characters, for 30 days for moderation and appeals. If a moderator mutes your chat for a set time or requires you to change your display name (a forced rename, which locks your name for a period), we keep that on your account and send you a notice in the game that states the reason and how to appeal (see the Terms of Service, item 9).
  • Purchases: your purchase history when you buy through the Apple App Store or Google Play. Payment details are processed by Apple and Google — we never see your card. We also store which in-game offers you dismissed, when an offer last appeared, and your offers setting, so we can limit how often offers appear; they are included in your data export and deleted with your account.
  • Analytics: which screens and features you use, and when. Every event carries the app version, the platform (e.g. “Android”), the scene you are on and the app state you are in. Individual events add a small number of details about the thing that happened — for example the campaign node you attempted, how many heroes you summoned in a batch, which tutorial step you reached, or the error message when a sign-in fails. Events also carry a random analytics session id we generate on your device and reuse until the game’s stored data is cleared: it lets us stitch one player’s events together without a name attached, and it is not shared with anyone or used outside Meroveil. This is software we wrote ourselves, running on our own servers.
  • Crash reports: when the game crashes we receive a random install identifier we generate ourselves (not a device identifier — it cannot be linked to you across other apps and it dies when you uninstall), the app version, platform, device model, OS version, graphics chip and total RAM, the error and its stack trace, the screen you were on, and your account id only if you were already signed in. Our own crash reporter, our own servers. We removed the third-party crash SDK this game used to include.
  • Your profile picture, if you choose to set one: see Your profile picture below. Nothing else from your photo library is read or sent.

Your profile picture

Setting a profile picture is optional. If you choose one (open PROFILE from the lobby and tap UPLOAD IMAGE):

  • You pick one image yourself. On Android 13 and later the system photo picker opens; on older Android versions your device’s own image chooser opens instead (this can be a gallery or files app you pick). Either way the game can read only the single image you choose. The game asks for no photo, storage or camera permission and never browses your library.
  • Only a small copy leaves your device. The game crops the image to a square, shrinks it to at most 128 × 128 pixels, and re-encodes it as a new PNG before sending it. The original and its metadata (for example the camera’s location tag) are never uploaded. To read the image the game makes one temporary copy on your device; it is deleted once read, at once if the pick fails, and before your next pick if a pick was interrupted.
  • It is stored for display. We keep that small image with your account, with the time you set it, so other players can see it next to your name (chat, friends, guild and profile views). Players who have blocked you do not see it. Setting a new picture replaces the old one, including in the moderation queue if reports about the old one were still waiting for review.
  • It is moderated. Other players can report a picture. Once two established players report it, it is hidden at once (everyone sees the default picture) until a moderator reviews it, and you are told why. A moderator can restore it or remove it.
  • Moderation evidence. When a moderator removes a reported picture, or you delete your account, while a moderation case about that picture is still open, was decided less than six months ago, or is under a legal hold, we keep a copy as evidence so an appeal can be decided fairly. When you replace a picture, a copy is kept only if such a case was already decided less than six months ago or is under a legal hold. An evidence copy is deleted automatically six months after the case’s decision (or after the decision on an appeal of it, if that is later). While the case is still open the copy is kept until it is decided, and a case open for more than 12 months is flagged to our moderators to decide rather than kept quietly. A legal hold keeps the copy for as long as the hold lasts.
  • It is deleted with your account. Deleting your account deletes the picture and any pending review of it. The only exception is a moderation evidence copy as described above, deleted under the same rules.
  • It is included in your data export.

No third-party SDKs. None.

There is no advertising SDK, no analytics SDK, no crash-reporting SDK, no social SDK and no tracking pixel in Meroveil. We have not integrated a single outside company that receives information about you. We collect no advertising ID, no device fingerprint, no location, no contacts, and no photos other than the one profile picture you choose to upload. We cannot profile you across other apps or sites, because we collect nothing that would let us.

What we use it for

Running the game (accounts, saves, matchmaking, guilds, leaderboards), fixing bugs, balancing content, preventing cheating and fraud, and meeting legal obligations. We do not sell personal data and we do not use it for third-party advertising. There is no cross-app tracking, so Meroveil shows no App Tracking Transparency prompt.

Sharing

We share your personal data with no company, for any purpose. No analytics vendor, no crash vendor, no ad network, no attribution partner, no data broker. Three things deserve to be stated precisely, because “we share with nobody” should mean something exact:

  • Other players see what the game shows them — display names, profile pictures, scores, guild activity, and chat you send. That is the game working, not data sharing with a company.
  • Our infrastructure providers (our server host, our network provider) store and transmit data on our behalf, under contract, on our instructions. They may not use it for their own purposes. That is the relationship a business has with its landlord — they are how our servers exist, not parties we hand your data to.
  • Apple and Google process your payments and distribute the app. If you buy something, the store handles the transaction and tells us it succeeded; we never see your card. This is not optional — it is the only way to sell anything inside an iOS or Android app. Their platforms also report their own aggregate crash statistics to us (Play Console, App Store Connect); we did not install that, it comes with shipping on their stores, and you control it in your device’s own diagnostics settings.

Beyond those two companies, there is nobody else. If that ever changes, we will say so here first.

Your choices

  • Export: download a machine-readable copy of your account’s data yourself. It leaves out other players’ identities, our internal moderation notes and records (it says whether your account is restricted, and when), analytics events and crash reports (kept 30 days), and guild chat lines from guilds you have left; to ask for anything else we hold about you, email . Sign in on the data export page with the email and password you registered in the game, or in the game open PROFILE from the lobby and tap EXPORT DATA. Playing as a guest, or can’t sign in? Email with a one-time support code from PROFILE (or a store order number plus the date and item of a different purchase); we send you the same export. A display name and player ID are never enough on their own, because other players can see them (why we ask this).
  • Delete: in-game, open PROFILE from the lobby and tap Delete Account. It erases your account and game data immediately; the records listed under Retention & security are kept. See how to delete your account for the full steps and an email fallback.
  • EU/UK (GDPR) and California (CCPA/CPRA) players have the rights those laws provide — access, deletion, portability, and objection. Deletion and data export (access and portability) are self-service, as above; for anything else, or if you can’t use them, email and we will respond inside the statutory window.

Children

Meroveil is for adults (18+) and is not directed at children: the game asks for a date of birth before sign-in and does not let younger players in. We do not knowingly collect data from children. If you believe a child is playing, contact us and we will delete the account.

Retention & security

Game data is kept for the life of your account. Some records are deleted on a schedule even while your account exists:

  • battle records after 30 days, the history of changes to your currencies and items after 180 days, and summon records after 400 days;
  • analytics events and crash reports after 30 days (what we keep longer is daily totals per event, which name nobody);
  • flagged chat excerpts after 30 days, unless the line is part of a moderation case; a moderation evidence copy of a profile picture six months after its case’s decision, as described in Your profile picture.

When you delete your account, everything held under it is removed right away: account and login, profile and profile picture, progress, inventory, purchase history, leaderboard entries, world chat and direct messages, and your lines in guild chats, including guilds you have left. Guild records that name you are cleaned up too: your raid entries stay as damage the guild dealt but without your name, and a pending application, the guild’s activity log and an announcement you last edited no longer show who you were.

What we keep after you delete your account, and why. These records are not held under your account, so deletion does not remove them:

  • Moderation records: reports other players made about the account (with the reported message), moderation cases about it (with the display name it had), moderators’ actions and notes, and any ban, all with the account’s id. Reports you made are kept without your id. We keep them to keep other players safe and to decide appeals fairly. We have not yet set a fixed period after which they are deleted: until we do they are kept, and we will state the period here when we set it. A chat mute record is deleted once the mute has ended.
  • Store purchase records: for each purchase, the store’s order reference, the item, when it was bought and the account it was redeemed on; and, if a purchase was moved to another account with RESTORE PURCHASES, a record of that move. We keep them so a purchase cannot be redeemed twice and to handle refunds and payment disputes. We have not yet set a fixed period for these either; until we do they are kept. (A Google Play purchase also has a settlement record for at most four days, until Google confirms it.)
  • Guild records that name you: a guild’s own management history (joins, leaves, promotions; its last 100 entries), a join application still waiting for an answer, a merge proposal you made, the guild raid’s contribution list (replaced when the guild starts its next raid) and the editor of the guild announcement. They belong to the guild and go as its history rolls over; email and we will remove them by hand.
  • Server logs: our server logs can contain your account id, and the logs of our web proxy and game server software can contain the IP address of a connection (for example a refused or failed one); where our own game code needs to tell networks apart in a log, it writes a short scrambled tag instead of the address. Logs stay on our server, are not part of our database backups, and are deleted as the log rolls over (each service keeps at most about 50 MB).
  • Backups: we back up the whole database every night to our storage provider. A deleted account stays in the backups taken before it was deleted. We do not yet delete old backups automatically, so those copies are kept until we do; we will state the period here once automatic deletion runs. Backups are used only to recover the game after a failure and to test that recovery works.

Traffic is encrypted in transit (TLS). Access to production systems is limited and credentialed.

Changes

We’ll post changes here with a new effective date; material changes are also announced in-game.

Questions about this policy? Email . See also our Terms of Service and the support page.