Privacy Policy

1. Controller

Eyevo is operated by Julian Beck, Theoderichweg 5, 70469 Stuttgart, Germany. Contact: [email protected]. Additional legal information is available in the Impressum.

2. Data on your device

Eyevo uses the camera to recognize trading cards. Live camera frames are processed locally and discarded after recognition. They are not uploaded to Eyevo servers. Photos you choose to scan from your gallery are also read on your device first; only in the cases described in section 3 is part of a photo sent online. Your collections, scan history, preferences, custom values, and portfolio history are stored locally in the app database, and additionally on Eyevo's server if you use Sync & Backup (section 4).

You can export collection and scan data from the app. Deleting the app removes its local data, subject to backups controlled by your device and Apple or Google. Files you deliberately export or share are handled by the destination you choose.

3. Online photo identification

When you scan a card from a photo and the app cannot read it on your device (for example because of glare, a small card number, or a graded slab), the app sends a cropped JPEG of the card area to Eyevo's server, together with the card language you selected and a few candidate card names and numbers the app already found. Eyevo's server forwards the image to OpenAI, whose vision model reports what is printed on the card; the app then matches that against its own catalog. Scanning a sealed product (Eyevo Pro) works the same way with the product area of the photo, without on-device recognition.

Eyevo does not store or log the images. Eyevo asks OpenAI not to store the request. To enforce limits, the request includes the app's random installation identifier and, to confirm Pro, RevenueCat's pseudonymous app-user ID (the Pro result may be cached briefly). The limit counters contain only keyed hashes of the installation identifier and of the network address and are deleted within about two days. Eyevo records technical metrics (image size, response time, whether the card was readable) without the image.

You can turn the online check for cards off in Settings → Scanner → "Check unclear photos online". Sealed products are only identified when you start a sealed scan.

4. Sync & Backup and shared collections

Sync & Backup is optional. If you turn it on, the collections you choose to sync are stored on Eyevo's server, hosted by Cloudflare, so you can restore them and keep your devices in sync. This includes collection and folder names, the cards in them with printing, grade, language, quantities, custom values, and the times of changes, plus random device and pairing identifiers. RevenueCat's pseudonymous app-user ID is used to check that Sync is included in your plan. The data is protected in transit; it is not end-to-end encrypted, because the server merges changes from your devices.

Synced data is kept until you delete it. Deleting a synced collection removes its cards from the server; small deletion markers remain so other devices do not restore it. Pairing attempts and request-limit records are deleted after 24 hours.

If you share a collection link, anyone with the link can view that collection (or a copy of it) on share.eyevotcg.com until you revoke the link. Revoked links and their copies are deleted after 30 days. To delete all synced data, remove your synced collections in the app or contact us.

5. Pseudonymous product analytics

Eyevo uses PostHog's EU service to understand which features work and where users encounter problems. Events can include a random installation identifier, event type, app version/build, platform, feature choices, and public catalogue identifiers such as a card or set ID. Most non-critical events are collected from a stable 10% sample; essential install, scanner, paywall, and purchase-funnel events may be counted for all installations.

Eyevo disables person profiles, automatic screen capture, element capture, and session replay inside the mobile apps. The analytics filter removes user-authored collection names, search queries, URLs, error text, contact fields, local collection IDs, and unapproved cross-system identifiers. Selected attribution, paywall, and purchase-funnel events include RevenueCat's pseudonymous app-user ID so results can be joined between PostHog and RevenueCat; this ID is not a name, email address, or advertising ID.

As with any internet request, PostHog's receiving server sees the IP address of your device while handling the connection. PostHog uses it to derive an approximate location at country and city level, so Eyevo can see in which countries and regions the app is used. The IP address itself is not stored with the events.

Because events from the same installation can still be grouped using a random installation identifier, this data is accurately described as pseudonymous, not completely anonymous.

6. Purchases and subscriptions

Purchases are processed by Apple App Store or Google Play. RevenueCat receives a pseudonymous app-user identifier and store subscription information such as product, purchase, trial, renewal, cancellation, refund, entitlement status, and transaction timing so Eyevo can unlock Pro and manage subscriptions. Eyevo does not receive your full payment-card details.

7. Install and advertising attribution

Eyevo uses the Meta and TikTok app-events SDKs to measure whether an advertising campaign produced an installation or later app activity. These providers may process app, device, network, and event metadata under their own privacy terms.

• Meta: The Meta SDK runs for every user and sends events to Meta Platforms Ireland Ltd. for advertising measurement: the app activation (when Eyevo is installed or opened) and store purchase events (trial start, subscription, purchase). On iOS, it also manages Apple's SKAdNetwork attribution. A Meta-generated anonymous app-device ID is passed to RevenueCat so RevenueCat can also deliver subscription lifecycle events to Meta from its servers.
• TikTok: Eyevo permits automatic install, launch, and two-day-retention signals. Automatic in-app-purchase tracking, advertising-ID collection, and enhanced identity postback are disabled.
• Advertising identifiers: On iOS, Eyevo shows Apple's App Tracking Transparency prompt; the Meta SDK receives the advertising identifier (IDFA) only if you allow tracking. On Android, the Meta SDK uses the Android advertising ID (Google Advertising ID), which you can reset or delete in your device settings.

8. Diagnostics and notifications

Firebase Crashlytics may process crash reports, diagnostic details, app/device information, and installation identifiers to help fix stability problems. If you enable push notifications, Firebase Cloud Messaging and Apple Push Notification service or Google Play services process a push token and delivery metadata. Eyevo does not use notification permission to access contacts or messages.

9. Website analytics and advertising pixels

The Eyevo website is separate from the mobile apps. It uses self-hosted Plausible analytics, PostHog EU, the Meta Pixel, and the TikTok Pixel. These tools can process page views, clicks, referral and campaign parameters, browser/device data, cookies or local storage identifiers, and network information. As in the apps, PostHog derives an approximate location (country and city level) from the IP address. Meta and TikTok use their website data for advertising measurement under their own terms.

PostHog website analytics use a persistent 10% sample, while App Store and Play Store click events are counted exactly. For sampled visits that begin on an Eyevo /get campaign page, PostHog session replay may record interactions on the website. Passwords and payment information are not collected through those Eyevo campaign pages.

10. Eyevo in ChatGPT

When you use the Eyevo app inside ChatGPT, ChatGPT sends Eyevo the card questions it needs to answer, for example card names, set names, card IDs, and quantities, together with technical request data: the network address of OpenAI's servers and an anonymous identifier that OpenAI assigns to your ChatGPT account. Eyevo does not receive your name, email address, or chat history, and it does not ask you to sign in.

Eyevo uses the technical request data only to limit how many requests can be made per minute. These counters are kept for about a minute and are not linked to any other Eyevo data, including app analytics. Request logs that our hosting provider Cloudflare keeps for troubleshooting are deleted after the provider's standard retention period.

Card images, prices, and links shown in ChatGPT come from Eyevo's public card catalog. Your use of ChatGPT itself is governed by OpenAI's privacy policy.

11. Referral program ("Invite friends")

With Invite friends, you can share a personal invite link or code and earn bonus scans (see the referral program terms). So that your code is ready and an invite can be accepted right away, the app creates a pseudonymous referral profile on Eyevo's server in the background. For the program, Eyevo processes:

• a random invite code and your referral profile. The app keeps the key to this profile in the iOS Keychain or Android Block Store, so the profile can be restored when you reinstall Eyevo on the same Apple or Google account;
• a random installation ID, the platform (iOS or Android), and the app version;
• proof that the app is a new installation: on iOS, Apple's signed App Store transaction information, such as the date you originally downloaded Eyevo; on Android, the app's first-install time and, if you came via an invite link from Google Play, the invite code passed on by the Google Play Install Referrer;
• which invite you accepted, how it reached the app (link, Google Play, pasted or typed code), and who invited you, stored only as pseudonymous profile IDs. Eyevo never shows names; inviters only see counts, such as how many friends have accepted or qualified;
• after you accept an invite, the number of your live scans and the days on which you scanned (no card data and no photos);
• your bonus-scan balance (bonus scans granted and used);
• RevenueCat's pseudonymous app-user ID (section 6); after you accept an invite, RevenueCat also stores a marker that you joined through an invite;
• a pseudonymous analytics ID (PostHog, section 5) to measure how the program performs. Referral events are counted for all installations and never contain invite codes or links.

On iOS, Eyevo may also use Apple's DeviceCheck service, which stores a single yes/no flag for your iPhone on Apple's servers, without your identity, recording that the device has already received a friend gift in Eyevo or one of our other card apps. Eyevo keeps the temporary DeviceCheck token for at most 14 days after you accept an invite and ignores flags older than 12 months. To limit abuse, request counters per network address and per profile contain only keyed hashes and are deleted after one hour. The invite page (invite.eyevotcg.com) counts page views and button taps in PostHog EU using a random ID in your browser's local storage; it sets no cookies and does not send the invite code to analytics.

Eyevo processes this data to run the program, grant rewards, and prevent abuse. The legal basis is the performance of the service you request (Art. 6(1)(b) GDPR) and our legitimate interest in preventing abuse of the program (Art. 6(1)(f) GDPR).

The referral data is stored on Eyevo's server, hosted by Cloudflare, and kept as long as your referral profile exists. You can delete it at any time in the app under Settings → Invite friends → Delete referral data. This deletes your referral profile, your invite code, the invite you accepted, your scan counts, and any bonus scans you have left. Invites that friends accepted from you are kept as anonymous records, without any link to you, to prevent abuse.

12. Service providers, purpose, and retention

Eyevo uses Apple, Google/Firebase, RevenueCat, PostHog, Meta, TikTok, Cloudflare, OpenAI (online photo identification only), and other hosting/network providers to provide app functionality, sync, the referral program, subscriptions, diagnostics, analytics, notifications, security, and campaign measurement. Data may be processed outside your country using the safeguards offered by the relevant provider.

Eyevo keeps provider-side data only as long as reasonably needed for these purposes, legal obligations, fraud prevention, and dispute handling, subject to each provider's retention controls. Local app data remains until you delete it or uninstall the app. Eyevo does not sell camera images or collection contents.

13. Age and children's privacy

Eyevo does not ask for a birth date and does not use an age gate. The iOS age rating describes content suitability; the intended Google Play audience starts at age 13. Eyevo is a general-audience card utility and is not primarily directed to children under 13.

Eyevo does not knowingly request personal information from children under 13. Where local law requires parental permission for a younger user, a parent or guardian must supervise the use. If you believe a child has provided personal information, contact us so it can be investigated and deleted where possible.

14. Your choices and rights

• You can deny or revoke camera, photo, notification, and (on iOS) tracking permissions in system settings, and reset or delete your Android advertising ID.
• You can turn off the online photo check in Settings → Scanner, turn off Sync & Backup, delete synced collections, revoke shared collection links, and delete your referral data (Settings → Invite friends → Delete referral data) in the app.
• You can export supported collection data in the app and delete local data by removing the app.
• You can use browser privacy controls to restrict cookies, local storage, and advertising pixels on the website.
• Depending on your location, you may request access, correction, deletion, restriction, objection, or portability for personal data Eyevo can identify.
• You may complain to a competent data-protection authority.

Requests can be sent to [email protected]. Because Eyevo does not require an account and deliberately avoids direct identity fields in product analytics, it may not be possible to connect an analytics record to you without additional information from your device.

15. Changes

This policy may be updated when Eyevo's products, providers, or legal obligations change. The current version and update date are published on this page.