Privacy Policy

Updated October 4, 2026

Who operates LanaKit

LanaKit is operated by Julian Beck. Contact [email protected] with privacy questions or requests concerning your data. Operator contact details are in the Impressum.

Collections and camera access

The iOS and Android apps store your collections, decks, and downloaded catalog on your device. Camera access supports card recognition. On Android, choosing a photo grants access only to the images you select through the system photo picker. The recognition workflow uses on-device processing. Uncached card artwork and catalog updates require a network connection. Exporting or sharing sends the selected content to the destination you choose.

Local backups and sharing

You can export a backup or share collection files and images through the destination you choose. Full Android backups include collection and deck records, all saved prices and their currencies, scan history, collection value history, and included app settings. Full backups do not offer an option to omit saved prices. When sharing a collection copy file, you can choose whether to include saved prices and their currencies.

A recipient receives an independent copy; later changes or deletion in LanaKit do not update or recall that copy. Backup files remain wherever you save them until you remove them there.

App analytics

The apps use PostHog for product analytics and feature flags when configured for that platform and build. Configured release builds record feature and subscription interactions together with technical app and device context. On Android, analytics requires a configured analytics key. New installations, committed scans, scan limits, paywall views and dismissals, plan selections, purchase starts, and successful purchases are recorded without sampling. App updates and opens, general usage, and other purchase and restore diagnostics are sampled. Android automatic screen capture and session replay are disabled; camera frames and selected photos are not sent to analytics.

Configured Android builds send analytics to PostHog’s EU service. PostHog processes the connection’s IP address and, under the current configuration, can retain the IP address without anonymization and derive approximate location, such as country, region, or city, from it. This is an estimate from the network connection; the Android app does not request GPS or precise device location for analytics.

On iOS, the app can link its analytics identity to its RevenueCat app-user identifier. On Android, selected paywall, purchase, and install-attribution events can include RevenueCat’s anonymous app-user identifier as an event property to understand acquisition and subscription journeys. This Android event property does not replace or merge PostHog identities. Local collection storage does not prevent configured builds from sending analytics.

Android release builds can obtain installation campaign information from Google Play. Selected source, medium, campaign, ad-group, ad, and creative fields, plus click and installation timestamps, are stored locally and sent to PostHog when analytics is configured. Campaign attributes are also shared with RevenueCat to relate acquisition to purchases. Resolved install-attribution events are recorded without sampling. The app does not retain or share the complete referrer string and does not collect the Android advertising identifier for this attribution.

See PostHog’s privacy policy for information about the service.

Subscriptions and purchases

Apple processes App Store purchases and Google processes Google Play purchases. RevenueCat manages subscription status, entitlements, and purchase restoration using app-user and purchase information. LanaKit does not receive your payment card details from either store. See the RevenueCat privacy policy and Apple privacy information, and Google privacy information.

Website analytics and storage

This website uses self-hosted Plausible to measure visits, pages, referrers, broad device and country information, and outbound link clicks. App Store events include the page, language, and download-button placement. We use these statistics to understand which pages lead visitors to the app. The Plausible script does not use tracking cookies.

Interactive checklists can store your selections in this browser’s local storage. Calculator entries are processed in the browser. We do not include checklist selections or calculator entries in our website analytics events. Clear site data in your browser to remove saved checklists.

Network services and external websites

Cloudflare serves the website, card images, and catalog downloads. The app also retrieves pricing references and currency data. Network providers necessarily process connection information such as IP addresses when serving requests.

App Store and marketplace links open external services with their own privacy policies. Some marketplace links may contain affiliate parameters and may earn LanaKit a commission. External providers can process referral information when you follow a link.

Your choices

You can manage camera and notification permissions in device settings, manage subscriptions through the store where you purchased them, and delete local app data by removing the app or clearing its storage. Deleting the app does not cancel a subscription. Android system backup may preserve local app data according to your device backup settings. Optional scan reminder notifications can be disabled in settings. For access or deletion requests concerning service-side information, contact us with enough context to locate the relevant record; do not send payment details or passwords. We will explain any information that must be retained and the applicable next steps.

This policy is currently published in English.