MagicProphet

Privacy Policy

1. Controller

The controller within the meaning of the General Data Protection Regulation (GDPR) and other national data protection laws is:

Marius Prehn
Wachthauskoppel 94
23556 Lübeck
Germany

Email: info@magicprophet.com

Full provider information is available in the Legal Notice. We have not appointed an external data protection officer, as we do not exceed the statutory thresholds. For all data protection matters, please contact the email address above.

2. Overview and Legal Basis

We process personal data only insofar as this is necessary for the provision of Magic Prophet. The most important legal bases are:

• Art. 6(1)(b) GDPR (performance of a contract): for all data you provide to use the account, search, watchlists, collections, alerts, or card scan.
• Art. 6(1)(f) GDPR (legitimate interest): for server logs, rate limits, abuse protection, anonymous usage metrics, your ratings of AI features, and improvement of the catalogue data set.
• Art. 6(1)(a) GDPR (consent): for the Patreon link, sending in-app feedback to our public GitHub issues, and optional push and email notifications.
• Art. 6(1)(c) GDPR (legal obligation): insofar as statutory retention obligations apply (e.g. tax/commercial code obligations on the part of the payment provider).

3. Account and Authentication

For registration, we process your email address and a password chosen by you. Sign-in runs through the sign-in service of Amazon Web Services (AWS) in Frankfurt, Germany. Your password is stored there exclusively in hashed form; we never see the password in clear text.

In addition to email and password, the sign-in service stores settings such as your time zone and, if enabled, the secret of your two-factor sign-in. In our database, we additionally store profile preferences such as display name, time zone, currency and language preference, optional push token, and Patreon ID.

Storage location: sign-in and profile data both in Frankfurt, Germany (EU).
Retention period: until your account is deleted.
Third-country transfer: when you sign in with email and password, all sign-in data stays in the EU. In the web app, however, the sign-in components are loaded from Apple's and Google's servers when you open the sign-in screen; these providers receive your IP address and technical browser data even if you then sign in with email and password. For sign-in with Apple or Google, see the paragraph below and Section 13.

Sign in with Apple / Google: instead of a password, you can sign in with your Apple or Google account. Apple Inc. or Google LLC then issue a signed identity token that we verify on our server. From it we take your email address and, on the first sign-up with Apple, optionally your given and family name; we also record which sign-in providers are linked to your account. Beyond this sign-in flow we send no data to Apple or Google, with one exception: when you delete an account linked to Apple in the iOS app or on the web, the app asks you to confirm the deletion with Apple once more, and with the code from that confirmation we revoke your Sign in with Apple authorization for MagicProphet at Apple. Nothing is stored in the process. In the web app, the sign-in components are loaded from Apple's and Google's servers only when you open the sign-in screen, and Apple's also when you open “Delete account” for an account linked to Apple; these providers then receive your IP address and technical browser data (transfer basis: see Section 13).

4. Card Search and AI Processing

When you submit a search query, the search text is processed by AI models that we run via AWS Bedrock. Specifically:

• Query interpretation (language model by Anthropic; if it is unavailable, an openly available language model that AWS runs itself): the search text is sent verbatim to a language model, which derives the search intent, filters and an English version of the query from it. This applies to the signed-in search and to the guest search alike. The backup model was published by OpenAI; OpenAI takes no part in the processing and receives no data.
• Semantic search (model by Cohere): the model turns the (translated) search text into a series of numbers that we use to find cards with a matching meaning.
• All of these models run inside AWS Bedrock on AWS infrastructure in EU regions; the backup model runs in Frankfurt, Germany. According to AWS, inputs and outputs are neither shared with the model providers Anthropic and Cohere or with OpenAI nor used to train models.

Your search text is used only transiently; neither the text nor the intent derived from it is stored, and our server logs record only a hash and the length of the query. One exception: if you rate a search result with thumbs up or down, we store the search query with your rating in your account (see Section 5). Which cards a search returned is counted anonymously (without the query text and without your user ID) for 90 days to improve the catalogue and forecasts. Please do not enter personal data or secrets into search queries.

Retention period: search queries are not stored (transient); a rated search query until your account is deleted.

5. Watchlists, Collections, Alerts, Feedback, Ratings

All content you create is stored in our database, which is operated for us by Neon (Neon, LLC, a Databricks, Inc. company) on AWS infrastructure in Frankfurt, Germany. Linked to your account are:

• Profile: account master data (see Section 3).
• Watchlists: name, description, cards, target prices (USD/EUR), language/condition preference, notes.
• Collections: collection name, contained cards, quantity, condition, foil status, language, capture source.
• Alerts: your alert rules and triggered alerts (trigger reason, before/after values, read status).
• Feedback: your problem reports and feature requests with their status (see Section 9).
• Ratings: when you rate an AI feature with thumbs up or down, your rating, your optional comment and what you rated (for example the search query with its first results, or the card a scan recognised).

Retention period: until you delete the entry yourself or your entire account; feedback and ratings until your account is deleted.
Note: Triggered alerts are deleted automatically after 365 days; scan sessions have no automatic deletion yet (see Section 14). You can delete entries at any time yourself or ask us by email to delete them.

6. Card Scan

The app's card scanner (iOS and Android) reads the card in the camera image:

• Text recognition runs on your device, using Google ML Kit. The image never leaves your device; it is neither uploaded nor stored by us. ML Kit sends Google usage and diagnostic data about the text recognition (such as device model, operating system, app version, processing time, error codes and an identifier), but neither images nor recognised text. According to Google, it uses this data to operate and improve ML Kit and to protect it against misuse. On Android, the recognition model reaches your device through Google Play services.
• To identify the card, we send our server what the app reads in the card's footer (set code, collector number, language) and the lines of text in the image: the first line of each text block, at most 24. These can include other text that happens to be in view, such as the names of other cards. These details appear in our server logs (see Section 11).
• The recognised card (card, printing, confidence) is stored as a scan session in your account.

Retention period: scan sessions are kept until you delete your account or ask us by email to delete them; there is no automatic deletion for them yet. Server logs: 3 months.

7. Push Notifications and Emails

For notifications we process the following data:

• Push notifications: if you are signed in to the iOS or Android app and allow notifications on your device, the app obtains a push token for this device from Expo (USA) and stores it in your account, on every tier. On Android, Expo needs a token from Firebase Cloud Messaging, Google's push service, for this: your device registers with Google to get it. We use no other Firebase service, such as Google Analytics. Which notifications arrive depends on your tier: push notifications, for example about a reached target price, are part of the Orakel and Prophet tiers. To send one, we pass the push payload (card name, trigger reason, title) together with the push token to Expo's push service. Expo acts as a processor and forwards the message to Apple's or Google's push service.
• Emails: sent through the email service of AWS in Frankfurt, Germany. We process the sender address (noreply@magicprophet.com), your recipient address, and the email content (card, price, trigger reason). AWS records whether an email was delivered, for deliverability.

Retention period: push token in our database until your account is deleted; if you sign in on another device and allow notifications there, its token replaces the previous one. Send records in the notification queue at most 7 days; delivery records according to AWS standard retention.

8. Patreon Link (Premium)

For premium memberships we use Patreon (Patreon, Inc., USA) as our payment and membership provider. The data flow during linking is as follows:

• You are redirected to patreon.com and consent there to the transfer of your Patreon identity data to us.
• We receive from Patreon: Patreon ID, email address, email verification status, current membership tier.
• In our database we store your Patreon ID and the derived account tier (free/orakel/prophet).
• Patreon notifies our server of tier changes through a signed message so that your tier stays automatically up to date.

Storage location: Patreon in the USA; derived data in our database in Frankfurt, Germany (EU).
Retention period: until you sever the link. You can sever the link at any time in your profile under "Unlink Patreon", we then remove the Patreon ID and reset your account tier to "free". The actual Patreon account remains untouched and must be managed separately via patreon.com.
Third-country transfer: Patreon servers in the USA, see Section 13.

9. In-App Feedback and GitHub (public!)

Important: when you submit something in the app under "Report a Problem" or "Suggest a Feature", your feedback is automatically created as a public GitHub issue in the repository mariusnop/MagicProphet.com. The form says so right above its submit button. These issues are world-readable via the GitHub search engine.

We publish:
• the category you chose and your text, with your title for a feature request; for a problem report, the first characters of your text form the title,
• for a problem report, also technical context: app version, operating system and its version, screen width, account tier (free/orakel/prophet), language, currency, colour scheme (light/dark) and, if any, the app's most recent error messages.

Your email address, display name, and user ID are not transmitted to GitHub. Nevertheless, you should not enter any personal data or secrets in title and description. By submitting, you give your express consent under Art. 6(1)(a) GDPR to public publication.

Storage location: GitHub servers, USA. Retention period: issues are publicly visible permanently; on request we can close the issue, but a complete deletion is only possible to a limited extent on GitHub's side.

10. Cookies and Local Storage

We do not use any tracking cookies, analytics cookies, or advertising cookies. Only technically necessary storage mechanisms are used:

• Sign-in tokens: so that you stay signed in after login, they are kept in the browser's local storage or in the secure storage of the mobile app. You can remove these tokens at any time via the browser developer tools or the logout button.
• Member since: a local entry with your email address and the date of your first sign-in (used to display account age in the UI). Stored locally only.
• UI preferences: language, theme (light/dark), currency. Stored locally on your device.

No third-party cookies (no Google Analytics, no Mixpanel, no Hotjar, no Facebook Pixel) are set.

For technical stabilisation we collect pseudonymous crash and error reports through Sentry (Sentry Inc., EU region Frankfurt): they contain a hashed user ID and session data (start, duration and whether a session crashed) as well as details of the device, operating system and app version. This processing is based on legitimate interest under Art. 6(1)(f) GDPR and is required to detect and fix programming errors. No personal tracking cookies are set; the diagnostic data contains no search queries, email addresses, or watchlist content. You may object to this processing at any time under Art. 21 GDPR by emailing info@magicprophet.com.

11. Server Logs

When you use our servers, AWS automatically records technical server logs:

• Logs: pseudonymous user ID, the function called, duration and error status. Retention is 3 months for the app's interfaces, 1 month for the other functions and 1 week for internal tooling. The content of requests and responses is not logged, with two exceptions: the details the card scanner sends (see Section 6), and the title of a piece of feedback, which appears publicly on GitHub anyway (see Section 9).
• Performance traces: call path and duration of individual operations. AWS retains them for 30 days.
• IP addresses: temporarily processed for error analysis and abuse protection, but not stored in our application logs.

Legal basis: Art. 6(1)(f) GDPR (legitimate interest in operational security, error analysis, and abuse protection).

12. Third Parties and Sub-Processors

We use the following sub-processors and third-party services:

• Amazon Web Services EMEA SARL (Luxembourg): hosting, sign-in, data storage, email delivery and logs in Frankfurt, Germany; AI processing via AWS Bedrock in EU regions, including an openly available backup language model that AWS runs itself (see Section 4); a worldwide delivery network for the web app and card images, whose locations process your IP address for delivery.
• Neon, LLC (a Databricks, Inc. company, USA): managed database holding profiles, watchlists, collections, alerts, feedback, ratings and scan sessions. The data is stored with AWS in Frankfurt, Germany; Databricks is certified under the EU-US Data Privacy Framework and offers Standard Contractual Clauses.
• Anthropic, PBC and Cohere Inc.: AI models for interpreting search queries and for the semantic search, operated inside AWS Bedrock in EU regions; the model providers receive no data (see Section 4).
• Apple Inc. (USA) and Google LLC (USA): optional sign-in providers (Sign in with Apple, Google Sign-In), see Section 3.
• Google LLC (USA): text recognition for the card scanner with Google ML Kit on your device; Google receives usage and diagnostic data, but neither images nor recognised text (see Section 6).
• Patreon, Inc. (USA): payment and membership platform for premium tiers.
• Expo (650 Industries, Inc., USA): issuing push tokens, push notification relay and delivery of app updates; when the mobile app checks for a new version, Expo receives your IP address, device platform and app version.
• GitHub, Inc. (USA, subsidiary of Microsoft): public issue tracker for in-app feedback.
• Functional Software, Inc. (Sentry) (USA; data stored in the EU region Frankfurt): crash and error tracking. Processes only technical diagnostic data (error traces, operating system, app version, pseudonymous user ID) with no personal content.

A current, complete list of the services in use is also available on the Transparency page in the app.

13. International Data Transfers

Some of the providers named above are based in the USA or process data there (Neon/Databricks, Apple, Google, Patreon, Expo, GitHub, Sentry). Under the GDPR, the USA is considered a third country. Our core infrastructure (AWS) and our database (Neon) are located in the EU (Frankfurt, Germany), AI processing via AWS Bedrock stays in EU regions, and the model providers Anthropic and Cohere receive no data.

For the US transfers, we rely on:
• the EU-US Data Privacy Framework, where the respective provider is certified (GitHub, Google, Databricks/Neon, Sentry),
• Standard Contractual Clauses of the EU Commission (Art. 46(2)(c) GDPR), where the provider offers them (AWS, Databricks/Neon, Sentry),
• your express consent (Art. 49(1)(a) GDPR) or the necessity of the transfer for a service you requested (Art. 49(1)(b) GDPR), where neither applies, in particular for Patreon, Expo, Sign in with Apple and public GitHub issues.

Notice: we recommend that you do not enter sensitive data into search queries, watchlist notes, or feedback.

14. Retention Periods

We store personal data only for as long as necessary to perform the contract or pursue our legitimate interests. Overview:

• Account and profile data: until account deletion.
• Watchlists, collections, alert rules, collection entries: until you delete them yourself or your account is deleted.
• Search queries: not stored (transient); a rated search query until your account is deleted.
• Feedback and ratings: until your account is deleted; for the public GitHub issues see Section 9.
• Card scan images: not stored, the image never leaves your device (see Section 6).
• Triggered alerts: deleted automatically after 365 days.
• Scan sessions: until your account is deleted, or until you ask us by email to delete them.
• Server logs: 3 months for the app's interfaces, otherwise 1 month, internal tooling 1 week.
• Performance traces: 30 days (set by AWS).
• Queues for notifications and price checks: deleted automatically after 7 days.
• Request-limit counters (IP-based): deleted automatically after 24 hours.
• Patreon link data: until you sever the link via "Unlink Patreon".

15. Children and Teenagers

Magic Prophet is not directed at children. Use is permitted from the age of 16; from 13 to 15 only with the consent of a parent or another legal guardian; under 13 not at all (see Terms of Service, Section 2). We do not knowingly collect data from children under 13. If we learn that an account belongs to a child under 13, we delete it together with all associated data. Parents and guardians can reach us for this at info@magicprophet.com.

16. Your Rights under the GDPR

You have the following rights vis-à-vis us:

• Right of access (Art. 15 GDPR): confirmation as to whether we process personal data about you, and a copy of that data.
• Right to rectification (Art. 16 GDPR): correction of inaccurate data.
• Right to erasure (Art. 17 GDPR, "right to be forgotten"): complete deletion of your account and all linked data.
• Right to restriction (Art. 18 GDPR): blocking of processing in certain cases.
• Right to data portability (Art. 20 GDPR): receipt of a machine-readable copy of your data (JSON export).
• Right to object (Art. 21 GDPR): against processing based on legitimate interest.
• Right to withdraw consent (Art. 7(3) GDPR): at any time with effect for the future.

How to exercise these rights:
• Account deletion: via Profile → Delete Account in the app. Alternatively, a short email to info@magicprophet.com is enough; we confirm deletion within 30 days.
• Data export: by email to the address in the Legal Notice, info@magicprophet.com, ideally from the email address of your account. You then receive a machine-readable file (JSON) with your account's data.
• Access, rectification, objection, withdrawal: at any time by email to info@magicprophet.com.

17. Right to Lodge a Complaint with a Supervisory Authority

You have the right to lodge a complaint with a data protection supervisory authority (Art. 77 GDPR). For our seat in Lübeck, the following authority is competent:

Independent State Centre for Data Protection Schleswig-Holstein (ULD)
Holstenstraße 98, 24103 Kiel
Phone: +49 431 988-1200
Email: mail@datenschutzzentrum.de
Web: https://www.datenschutzzentrum.de

You can also contact the supervisory authority of your habitual residence or place of work.

18. Privacy Contact

For all questions, requests, or applications relating to your personal data and this Privacy Policy, the fastest way to reach us is by email:

info@magicprophet.com

We usually confirm receipt within 72 hours and respond to requests under Art. 12 et seq. GDPR within the statutory deadline of one month (extendable up to three months for particularly complex matters).

19. Changes to This Privacy Policy

We may adapt this Privacy Policy to reflect changes in legal requirements, new features, or new sub-processors. The current version is always available here in the app and at magicprophet.com. Material changes, in particular new data categories or new third parties, will be announced at least 30 days in advance by email or in-app banner.

Version date: 13 November 2026.
Last verified against the code: 13 October 2026 (card scan, push notifications, feedback, crash reports, ratings, data export, account deletion and retention periods).