Privacy policy

Lichcards: Card Shop Simulator · Updated 30 September 2026

Your cloud player profile stores game progress, inventory, action receipts and account credential hashes. We use this data to save your shop, prevent duplicate rewards and restore access. Your device keeps an access credential; on iPhone it is stored in Keychain.

This service supports optional Apple In-App Purchases in purchase-enabled iOS builds. Apple handles the purchase confirmation and billing. No advertising, advertising identifiers or tracking SDKs are active. Cloudflare processes requests and hosts the game database. Network information is used for security and abuse limits; application rate-limit identifiers are hashed and expire.

Keep your recovery code private. Anyone with it can recover your shop. You can delete your cloud profile from Settings in the app. Active profile data is removed; infrastructure backups can retain earlier data temporarily. Local solo saves, if any, remain on your device and are separate from the cloud profile.

For access, correction, export, deletion and privacy questions contact info@lichcards.nl. Lichcards uses game data to provide the service you request and limited security data to protect accounts against abuse. You may contact the Dutch data protection authority if you have a privacy complaint.

Retention and security

Game data is kept while your cloud profile exists. Deleting it removes the active profile. A hashed deletion receipt is retained for seven days so a repeated deletion can be confirmed safely. Short-lived abuse counters are removed automatically. Cloudflare recovery backups can retain earlier data for up to 30 days; deleted profiles must not be restored to active service. The game database is hosted in the EU. Cloudflare may process network and security information across its infrastructure under its data protection terms.

The game does not request your real name, email, contacts or location. If you email support, we receive the information you choose to include; never send a recovery code. There is no advertising profiling or sale of player data.

Apple purchase data

When the app prepares purchases or purchase recovery, the game creates a random purchase-account identifier for your Lichcards shop, even if you do not buy anything. When you buy, it passes this identifier to Apple with the transaction. This identifier links the purchase to that shop; it is not your Apple Account email address. Our server verifies the signed transaction and its current status with Apple before delivering diamonds or Astral Collector items and perks. Apple also sends signed transaction-status notifications so refunds and reversals can be reconciled.

Private purchase records include transaction and original-transaction IDs, the product and Apple environment, a hashed shop-purchase binding, granted and revoked diamond amounts, status timestamps and reconciliation counters. While your shop exists, the records link to its player identifier, and a separate record holds the random purchase-account identifier. The records are hosted with the game database on Cloudflare for delivery, purchase restoration, preventing duplicate grants and handling refunds. They are not published in rankings or shared with other players. Hashes and transaction references may still be personal data; we do not describe them as anonymous.

The game server does not store payment-card details or your Apple Account email or password. Signed transaction payloads are processed for verification, not stored in the purchase ledger or application logs. Apple processes transactions under its own privacy policy.

Purchase retention and shop deletion

Deleting your shop removes its active game profile and the separate purchase-account identifier record, and removes the player link from the purchase ledger. Your deleted shop, cards, diamonds and game progress are not restored by purchase restoration. A valid permanent Astral Collector purchase can be restored into one new shop using the same Apple Account only after fresh Apple verification and confirmation that the original shop no longer exists. It cannot be active on multiple shops at once.

Detailed purchase and refund records are retained for 24 months after the purchase or an actual refund, reversal or dispute-resolution event. Routine logins, status checks and Restore purchases do not restart this period. After that, records are deleted or reduced to the minimum proof needed for an ongoing entitlement or to prevent another delivery. A documented unresolved delivery, dispute or specific legal obligation may require a longer, reviewed exception; not all player records are retained for that reason.

For consumable diamonds, a minimal already-delivered record remains while the associated shop exists, so an old transaction cannot grant diamonds again. Deletion immediately removes the player link; any remaining consumable integrity record is deleted within 24 months after shop deletion, unless a documented necessary exception applies. This record does not recreate a deleted shop or refund spent currency.

For a valid permanent Astral Collector entitlement, we keep only the purchase reference, product and verification/refund information needed to deliver and restore that right for as long as the right remains valid. This minimal entitlement proof is not automatically erased after 24 months. It does not contain the deleted shop’s cards or other game progress. Detailed purchase data remains subject to the separate 24-month rule.

The seven-day deletion receipt and the infrastructure-backup window of up to 30 days described above are separate from these purchase-retention rules. Restoring a backup must not reactivate deleted accounts. Support correspondence is retained for 12 months after a case closes, except while an unresolved dispute or a specific legal obligation requires it. Necessary business bookkeeping follows applicable fiscal retention requirements, generally seven years for core records; this is not a seven-year retention rule for all player or purchase-verification data.

Retention rules and necessary exceptions are reviewed at least annually. For questions, correction or a deletion request concerning retained purchase records, contact info@lichcards.nl. Do not send your recovery code, account password or payment-card details.

World rankings and optional guilds

The current app explains before signup that new cloud shops start in the world ranking under a generated Collector alias, with zero points. Older app versions create private shops. Existing shops keep their current ranking visibility. You can hide your ranking from your profile; if you belong to a guild, leave it first. If raid mode is active, disable it after the 24-hour participation commitment before hiding your ranking. Joining or creating a guild makes your profile public again.

While your profile is public, other players can see your chosen nickname (or generated collector name), public player identifier, verified scores and guild membership. Choose a nickname without personal or contact details. We do not publish your credentials, recovery code or private inventory. Guild names and emblems are preset choices; there is no player chat.

Deleting your account removes your public player entry and membership. Previously earned anonymous guild totals remain for the other members; empty guilds close. Weekly claims, name-change timestamps and membership cooldowns are kept in your private game profile to prevent abuse. Hiding your ranking does not erase these private game records.

Player names and reports

Use the flag next to a player to hide or report an inappropriate nickname. Hiding replaces the name with a collector number in your community views; it does not remove the player or change scores. Hidden player IDs are stored in your profile and can be unhidden there. Reports contain the reporter and target player IDs, reported name, time and review status. They are private and available to the operator for moderation. Names that violate our friendly-name rules may be reset. Reports are deleted after 90 days, or when either associated account is deleted. Contact info@lichcards.nl for support, moderation or privacy questions; never share your recovery code.

Blocking players

Block player is separate from hiding or reporting a nickname. It prevents new shop visits, appreciations, card gifts and raids between the two shops and hides the nickname in collector lists. Previous activity, already-completed transfers, scores and guild membership are not erased.

The server privately stores the blocking player identifier, blocked player identifier and time of the block. These records enforce interaction limits and let you manage your own block list in your profile. Other players cannot view your block list or a list of people who blocked them. A block remains until you remove it or either shop account is deleted. Unblocking removes only your own block; the other player may still block interactions.

Collector neighbourhood and optional shop sharing

Listed profiles can appear in rankings for unique cards discovered, completed sets, verified active weekly shop sales, beginner weekly points and guild contribution. These rankings publish aggregate counts, not your full collection. New ranking categories are populated from trusted game progress when a player next plays.

Shop visits and collection matching require a separate, explicit sharing choice, off by default even for already-listed players. When enabled, visitors can view your current shop layout, selected decorations, shelf stock, staff appearance and cards displayed for sale. Your chosen wish list and spare-card offer list can be matched with other opted-in collectors. Account credentials, balances, undisclosed collection cards and private settings are never included. Disabling sharing withdraws these public views and matching lists; hiding your ranking also disables sharing.

One daily shop appreciation stores sender and recipient player IDs and the UTC day. Visitors see the total appreciation count, not the list of senders. Guild card requests show the requesting member, requested card and expiry to current guild members. A donation transfers one eligible normal spare card, with a private per-card history and daily limit; there is no free-text chat, cash trading or real-money value. Requests expire after 24 hours and are removed from storage within seven days after expiry. Leaving a guild removes your requests. Account deletion removes associated requests, appreciations and public projections; already-transferred cards remain with their new owners, without publishing the deleted player’s identity.

Optional shop raids and guild territories

Raid participation is a separate opt-in, off by default. Eligible participating shops can be challenged using their selected defence deck. A successful raid can transfer a limited amount of saved game cash between participants; cards, inventory, gems and real money are never taken. Players see a public collector name and potential loot, not the other shop’s private balance or full collection. Participation commitments, daily limits and recovery shields are stored privately to enforce fair rules. Starting an attack gives up the attacker’s recovery shield.

Raid records contain the participating player IDs, match identifier, times, outcome and transferred game cash. Private recent raid history is shown to the two participants and is retained for up to 30 days after expiry. Guild territory battles store the player, guild, week, territory and server-verified score; weekly guild totals are public. Territory attempts, personal contributions and reward claims are retained for up to 90 days. Hiding or reporting names works through the same collector profile controls. Account deletion removes associated individual records; cash already transferred remains with its recipient, and anonymous guild totals remain for existing guild members.