25 of 25 free card views left today free views

40/40 searches

Sign in for more

Privacy Policy

How the Holokan website (holokan.com) and the Holokan apps for iPhone, iPad, Mac and Windows handle your data.

Last updated

01Who we are

Holokan is run by iOS Corner (“we”, “us”), which develops and publishes apps for iOS and macOS. iOS Corner is the controller for the personal data described here (company details: Terms of Use, “Who we are”). Contact: info@ioscorner.com.

This policy covers the website at holokan.com, the API it runs on, the Holokan apps for iPhone, iPad, Mac and Windows, and Holokan Pro.

02In short

The essentials
  • No advertising, no ad identifiers, no selling of data, no tracking across other sites.
  • The website sets only cookies it needs to work (and one that remembers your US/EU choice). There are no analytics or advertising cookies, so there is no cookie banner.
  • Visits are counted with Umami on our own server, without cookies and without storing IP addresses.
  • To keep free browsing fair, we count card views and searches per visitor, device or network for 24 hours, then delete the counts.
  • The iPhone, iPad and Mac apps use Google Firebase for anonymous usage events and crash reports, never with your search text, prices, tokens or email. The Windows app sends no usage statistics.
  • An account holds your email address and your collection, until you delete it.
  • Holokan Pro is paid through Stripe; your card details go to Stripe and its company Link, never to us.

03Cookies on holokan.com

Every cookie below is first-party (set by holokan.com, sent only to holokan.com). The ones holding identifiers or tokens are HttpOnly, so no script on the page can read them, SameSite=Lax, and Secure over HTTPS.

CookieWhat it doesLifetimeType
ht_vYour anonymous visitor ID: a random identifier, signed by our server. It lets us count the free card views and searches you have without an account. Set the first time the site loads data for you while you're not signed in.1 yearStrictly necessary
ht_atAccess token for a signed-in session.15 minutesStrictly necessary
ht_rtRefresh token that keeps you signed in. Removed when you sign out.60 daysStrictly necessary
ht_pkceProtects the sign-in step against forgery while you sign in. Sent only to the sign-in addresses.10 minutesStrictly necessary
ht_linkProtects connecting another sign-in method (for example Google next to Apple) to your account while you do it. Sent only to the account-linking addresses.10 minutesStrictly necessary
ht_emailThe step of email sign-in you are on (which emailed code belongs to this browser). Removed once you've entered the code.15 minutesStrictly necessary
ht_td“Remember this browser”: lets your account skip the emailed code here. Set only when you tick the box.30 daysStrictly necessary, set at your request
ht_wd, ht_wd_doneHold your withdrawal form between its steps and show the acknowledgement. Sent only to the withdrawal pages.30 minutesStrictly necessary
marketRemembers whether you chose US or EU prices. Set only when you use the US/EU switch.1 yearFunctional, set at your request

We don't set a language cookie: dates, numbers and currencies follow your browser's language setting. Card images and fonts are served from holokan.com itself, so loading a page doesn't contact the card databases or a font service.

Browser storage. If you build a collection or watchlist without an account, it is kept only in your browser's local storage (holokan.guest.v1) and stays there until you clear it, move it into an account, or discard it. To value it, the website sends the cards, quantities, conditions and prices paid to our API, which calculates the value and stores nothing. When you are signed in, the open tab keeps a working copy of your account's collection in session storage (holokan.account.v1), deleted when the tab closes or you sign out. Neither is a cookie and neither is sent with page requests.

04Visit statistics (Umami)

We count visits to holokan.com with Umami, an open-source analytics tool that we host ourselves on the same server as Holokan (analytics.ioscorner.com). No third party receives this data.

  • No cookies and nothing stored on your device. Umami doesn't follow you across other websites.
  • For each page view the script sends: the page address without its query string, the page title, the referring page, your screen size and your browser's language. On search pages the title is replaced with “Search”, so what you search for is never sent. When you arrive from one of our own ads, the link's campaign tags (utm_…, which name our ad and keyword, not anything you typed) are kept, so we can tell which ads are worth paying for.
  • We also record a few anonymous events: a search was made, a card was opened, a card was added to a collection, the sign-in button was used, the sign-in or cool-down screen was shown, and a shop link was clicked. They carry no search text, prices or anything that identifies you.
  • According to Umami's documentation, it does not store IP addresses. It uses the IP address at the moment of the visit to look up an approximate location (country, region, city) and, together with the browser's user agent and a secret that changes every month, to form a one-way hash so that pages seen in one visit can be grouped.
  • If your browser blocks the script, the site works exactly the same.

05What our server processes

Free views and fair use

Without an account you can open a number of cards and searches per day for free. When our website loads data for you, it tells our API your visitor ID, your IP address and your browser's user-agent string. The API counts each distinct card you open and each distinct search (normalised to lower case) against:

  • your visitor ID (website), device ID (apps) or account, and
  • for visitors and devices without Apple's App Attest, also your network address: the full IPv4 address, or the first 64 bits of an IPv6 address.

Each count stores that identifier or network address, the card number or normalised search term, and the time. Counts run over a rolling 24 hours and are deleted after 25 hours. Short-lived rate-limit counters (to stop floods) are deleted after one day.

Search-engine crawlers

If a request's user agent claims to be Googlebot or Bingbot, we check the IP address's DNS name the way Google and Bing document. The result is cached in memory for up to a day and not written anywhere.

Server logs

Our web server (nginx) writes an access log line for each request: IP address, time, the requested address (which for searches contains the search terms), status, size, the referring page and the browser's user agent. We use it to run and secure the service. The logs are rotated automatically and kept for 14 days. The application's own logs are rotated by size (five files of 10 MB per service).

Prices

When you open a card whose price history we don't have yet, our server may request it from a price provider. Only the card is part of that request, never anything about you.

06The Holokan apps

Without an account, an app gets an anonymous, device-scoped token so it can load prices within the free daily allowance.

  • App Attest. Where the device supports it, the app uses Apple's App Attest: it creates a key in the device's secure hardware and Apple confirms that it belongs to a genuine Holokan app. We store the key's ID and public key, a usage counter and timestamps.
  • Devices without App Attest send a random identifier that the app creates once and keeps in the Keychain. We store it with the IP address it first connected from (so that no single network can create more than 30 new device IDs a day) and timestamps.
  • These device records contain no name, email address or advertising identifier. The first IP address is cleared after 30 days, and a record is deleted once the device hasn't been seen for 90 days. Email us if you'd like yours removed sooner.
  • On the device itself, the app stores your collection, watchlist and cached card data in its own database, and its tokens in the Keychain. Deleting the app removes that local data.

07App analytics and crash reports

The iPhone, iPad and Mac apps (not the website, and not the Windows app) use two Google Firebase services, only in release builds: the App Store apps and the Mac app you download from holokan.com. Development, test and screenshot builds never send anything.

Firebase Analytics

We use Google's “Analytics Core” package, the version without advertising-identifier support. Ad personalisation signals, the vendor-identifier (IDFV) collection and ad-network registration are switched off, and the apps never set a user ID. The apps send exactly these events:

EventWhat it carries
searchWhether the search looked like a card code or a name, and how many results it had. Never the text.
card_viewThe card's catalogue number in Holokan, the game and the market (US or EU).
add_to_collectionThe card's catalogue number, the game, whether it is graded, and the market.
sign_in_wall_shownWhy the sign-in screen appeared (daily limit or account needed) and whether for views or searches.
cooldown_shownWhich screen showed a “cooling down” notice, and a rough wait (under a minute, under ten minutes, longer).

No search text, prices, purchase prices, tokens, email addresses or account IDs are sent; a filter in the app removes anything that looks like an email address, a link, a token or a long identifier before an event leaves the device. Firebase also records some things automatically, such as an app-instance ID, standard events like the first open and the start of a session, device model, OS and app version, language, and an approximate location that Google derives from the IP address.

Firebase Crashlytics

If the app crashes, Crashlytics sends a crash report: the stack trace, device model, OS and app version, the device's state at the time of the crash (such as free memory and disk space) and an installation ID. We use it only to find and fix crashes.

There is currently no switch inside the apps to turn these off. You can object at any time by emailing us (see Your rights).

08Accounts and sync

Accounts are optional: a collection can live in your browser alone (see Browser storage above). You sign in with your email address, a password and a code we email you, or with Sign in with Apple or Google where offered. An account syncs your collection between the apps and the website, enables price alerts and raises the daily limits.

  • From Apple we receive a stable account identifier and your email address. If you choose “Hide My Email”, that is a private relay address that forwards to you. The first time you sign in, Apple may also share your name; we keep it as the account's name.
  • From Google we receive your Google account identifier, email address and name.
  • Email sign-in: we keep your email address and your password as a secure one-way hash (Argon2id), never the password itself. To keep accounts safe we also keep short-lived records of codes sent and wrong codes entered (deleted within two days).
  • What the account holds: your email address, your name if Apple or Google shared it, the sign-in identifier, your display currency and market, your collection (which printing, quantity, condition, grading and certificate number, and, if you enter them, purchase price, date acquired, notes and a for-trade flag), your watchlist, any price alerts, and the daily history of your collection's value. We keep the sign-in token Apple or Google gives us so we can revoke it when you delete your account. Our own refresh tokens are stored only as one-way hashes.
  • Deleting your account: sign in on the website and open Account, then “Delete account”. Or email info@ioscorner.com from the address linked to the account (or tell us the relay address) and we'll delete it for you. Deletion removes everything listed above from our live database at once and revokes Sign in with Apple or Google. Copies in our backups are overwritten within five weeks.
  • On the same Account page you can see which sign-in methods are connected and sign out on every device.
  • Price alert notifications: if you turn on notifications for a browser, that browser's push service (run by Google, Mozilla, Apple or Microsoft, depending on the browser) gives us an address and keys to send alerts to. We store them with your account until you turn notifications off, the push service reports the address gone, or you delete the account. Each notification (the card's name and the price that triggered it) passes through that push service end-to-end encrypted.

09Holokan Pro and payments

Holokan Pro is paid through Stripe. Stripe's company Link is the seller of record: it takes the payment, charges and pays VAT, sends receipts and invoices, and handles refunds and disputes. Your card or other payment details go to Stripe and Link, never to us; their privacy policies apply to that processing.

  • What Stripe tells us to run your plan: your Stripe customer and subscription identifiers, the plan, its status and dates (trial, renewal, end), the amounts paid and refunded, your country, and a fingerprint of the payment method (a code that identifies a card without revealing its number), which we use to allow one free trial per person and payment method.
  • What we keep: the plan and its status, the consent you gave on holokan.com before paying (the text, its version and the time), and the payment service's notifications about your purchase, so Pro is right on every device.
  • Withdrawals: if you use “Withdraw from contract here”, we keep what you submit (name, email address, which purchase, your message), when you sent it and what we did, as proof for both of us.
  • When you delete your account, a running subscription is cancelled first. Purchase records are then kept without your name or email address for seven years, as Dutch bookkeeping law requires.

10Holokan for Mac and Windows

The desktop apps sign in through holokan.com in your browser, and keep their sign-in tokens in the system's secure storage (the Keychain on a Mac, the Windows credential store) on that computer only.

  • Devices: so Holokan Pro can't be shared without limit, an app registers the computer with your account: a name for it (for example “MacBook Pro”), a key the app creates on that computer, the platform and when it was first and last seen. At most five devices count at a time; one unseen for 60 days drops off, and you can remove one in the app. Removing a device or deleting the account deletes its record.
  • Offline Pro: the server gives each device a signed note, valid for up to seven days, saying whether your account has Pro, so the app works without a connection. It holds your account identifier, the device identifier, the plan and dates, nothing else.
  • Updates: the Mac app downloaded from holokan.com checks for new versions with Sparkle, which reads an update list from holokan.com/download/mac/. The Windows app's own updater reads holokan.com/download/windows/latest.json shortly after it starts and then every six hours. Both install an update only after checking our signature on it. Like any web request, these checks show our server your IP address and the app's version, which we use only to run and secure the service.
  • Usage statistics: the Mac app sends the same anonymous Firebase events and crash reports as the iPhone app (see App analytics and crash reports). The Windows app sends none.

11Emails we send

Account emails come from Holokan <no-reply@ioscorner.com>, sent through our email provider IONOS; replies go to info@ioscorner.com. We send only what an account needs: sign-in and confirmation codes, notices when your password or sign-in methods change, Holokan Pro confirmations, and withdrawal acknowledgements. Receipts and invoices come from Link. We never send newsletters or advertising, and we never share your address.

12Links to shops

“Buy at …” buttons open TCGplayer, Cardmarket or eBay. They pass through a short redirect on holokan.com (logged like any request), then the shop's own privacy policy applies. Links to TCGplayer are affiliate links through the Impact network: TCGplayer and Impact may use cookies on their own sites to attribute a purchase to Holokan. See the affiliate disclosure.

13Service providers

ProviderWhat forData involved
IONOS SEHosting the website, API, database and Umami (our virtual server in Frankfurt am Main, Germany).Everything on this page that our server processes.
Stripe (Stripe Payments Europe) and LinkHolokan Pro payments: Link is the seller of record (receipts, invoices, VAT, refunds).Your payment details and billing address (we never see them); the plan and payment status they tell us.
IONOS SE (email)Sending account emails from no-reply@ioscorner.com.Your email address and the message.
AppleSign in with Apple, App Attest, app distribution.Sign-in identity and email; device attestation.
GoogleFirebase Analytics and Crashlytics (apps only); Sign in with Google once available.The app events and crash reports described above; Google sign-in identity and email.
Price and card data sourcesJustTCG, Cardmarket, Scryfall, TCGdex, Lorcast and others (see About).None about you. Our server only asks them for card and price data.

Apple, Google and Stripe may process data outside the EU, for example in the United States. They provide the safeguards the GDPR requires for that, such as the EU–US Data Privacy Framework and the EU's standard contractual clauses.

14How long we keep data

DataKept for
Free-view and search countsDeleted after 25 hours
Rate-limit countersDeleted after 1 day
nginx access logs14 days
Application logsOverwritten as they fill (5 × 10 MB per service)
Sign-in requests and codesDeleted within a day after they expire (they expire within minutes)
Refresh tokens (hashed)60-day lifetime, deleted 7 days after expiry
App device recordsDeleted after 90 days without use; their first IP address is cleared after 30 days
Account and collectionUntil you delete your account
Desktop app devicesUntil removed, or dropped after 60 days unseen; deleted with the account
Purchase records and payment notificationsSeven years (Dutch bookkeeping law); without your name or email once the account is deleted
Withdrawal requestsSeven years, as proof of what was asked and done; an unfinished form is deleted after a day
Database backups7 daily and 4 weekly copies, then overwritten
Website cookiesAs in the cookie table above
Umami visit statisticsOn our server, as aggregated statistics without IP addresses
Firebase AnalyticsEvent-level data for the retention period set in Google Analytics (2 months by default)
Firebase CrashlyticsCrash reports for 90 days

15Legal bases

For people in the EU, the EEA and the UK, we rely on these legal bases under the GDPR:

  • Contract (Art. 6(1)(b)): running your account, syncing your collection, providing Holokan Pro and the service you ask for.
  • Legitimate interests (Art. 6(1)(f)): keeping the service secure and available, preventing abuse and scraping, the fair-use meters, server logs, cookieless visit statistics, and app usage events and crash reports so we can improve and fix the apps. You can object to these at any time.
  • Legal obligations (Art. 6(1)(c)): keeping purchase records for bookkeeping and tax, recording withdrawals, and where another law requires us to keep or disclose data.

The website's cookies are either strictly necessary to provide the service you asked for or set at your request (the market choice). Under the EU's ePrivacy rules (for example, the German TDDDG) such cookies don't need consent, which is why holokan.com shows no cookie banner.

16Your rights

You have the right to access your personal data, to have it corrected or deleted, to restrict its processing, to receive it in a portable format, and to object to processing based on legitimate interests. To use any of these rights, email info@ioscorner.com; we answer within one month. We may ask you to confirm it's you, for example by writing from the address linked to your account.

Most of what we process without an account is tied only to random identifiers, so we may not be able to find it unless you give us the identifier (for example, the device or visitor ID).

You also have the right to complain to a data protection supervisory authority, in particular in the EU or EEA country where you live or work, or where you think an infringement happened.

17Children

Holokan isn't directed at children under 13, and we don't knowingly collect personal data from them. If you think a child has given us personal data, contact us and we'll delete it.

18Security

All traffic uses HTTPS. Website session cookies can't be read by scripts, our refresh tokens are stored only as hashes, secrets stay on the server, and the apps keep their tokens in the Keychain. Database backups are kept on the server with restricted access. No system is perfectly secure, but we work to protect your data and to limit what we keep.

19Changes to this policy

When this policy changes, we update this page and the “Last updated” date at the top. If a change matters for how we use your data, we'll point it out on the website or in the apps.

20Contact

iOS Corner · info@ioscorner.com