Privacy Policy
Draft — not yet in force
This is a working draft, pending review by a lawyer. It describes how Appeye actually operates today, but it is not yet a binding document and has no effective date.
Effective date: none yet — this draft takes effect only once it has been reviewed and published.
Appeye reads publicly published App Store and Google Play reviews and turns them into sentiment, themes, churn signals and comparisons. This page describes what we hold about you — not what we hold about apps.
We have written it against the actual storage, table by table, because a privacy policy that could describe any product tells you nothing. Where we have chosen not to record something, we say so, and you can check it.
1.What we collect, by table
Account and identity
Supabase Auth (auth.users)
Your email address, either a hashed password or an OAuth identity from the provider you signed in with, and timestamps. We never see or store a plaintext password.
user_roles
Whether an account holds admin rights.
Things you create
watchlist
Which apps you track, plus the score, churn level and category rank recorded at the moment you added each one, so we can show you what has changed since.
watchlist_alerts
Alert type, threshold, whether it is enabled, and when it last fired.
notifications
Alerts generated for you: kind, title, body, link and the related app.
ai_reports
Reports you requested, the generated analysis, its cost and status, and — for reports created from 5 September 2026 onwards — the model version, the prompt version, how many reviews were analysed, and the newest review date in that corpus.
comparison_reports, subscribed_apps, report_settings
Comparisons you ran, apps you subscribed to, and your report preferences.
report_share_links
If you share a report: a token, an optional label, an expiry, a revocation flag, a view count and the time it was last viewed.
Billing
subscriptions
Plan, status, Stripe customer and subscription identifiers, billing period, cancellation flag, and which Stripe environment the record belongs to.
payment_events
Webhook records received from Stripe.
We never receive or store card numbers. Card details go directly to Stripe; Appeye holds only Stripe's identifiers.
If you contact us
contact_messages
Your name, email address and message.
newsletter_subscribers
Email address, confirmation and unsubscribe tokens, and confirmation and unsubscribe timestamps. Subscribing is double opt-in: we send a confirmation link first, and every email carries a one-click unsubscribe.
Usage measurement
This is the part worth stating plainly.
search_queries
The search text, how many results it returned, and a yes/no for whether the searcher was signed in. It does not store a user id. Searches cannot be traced back to an account.
card_events
An app id, an event type and a referrer. No user id.
report_events
Report activity, and this one does carry the acting user's id — a report is a paid artefact, so its history has to be attributable.
Most analytics is designed the other way round: usage is tied to a person and payment records are anonymised in aggregate. We do the reverse. Search and browsing behaviour is not linked to you at all; only the paid artefact carries an owner.
2.What we do not collect
- No card numbers.
- No advertising or cross-site tracking cookies.
- No selling or renting of personal data, ever, to anyone.
- No profile built from your searches — searches are not linked to you, so there is nothing to build one from.
3.The review data — whose is it
Appeye analyses reviews published publicly on the Apple App Store and Google Play. Those reviews were written by their authors and published by those platforms. Appeye did not collect them from you and does not claim ownership of them.
We store review text so we can compute sentiment, themes and churn signals, and we quote short extracts in analysis. We do not publish reviewer names or profiles.
To be plain: public review text is not private customer data, and we do not market it as such. If you wrote a review and want an extract removed from Appeye, contact us and we will remove it.
4.How it is used
To run the service, generate the analysis you ask for, send the alerts you enable, take payment, and improve the accuracy of our scoring.
AI reports are generated on request by sending review text and computed metrics to Anthropic's API. That is the only path by which review data leaves our own infrastructure, and it happens only when a report is purchased. The free, rule-based analysis never leaves our systems.
5.Who else processes it
Supabase
Database, authentication and storage. Hosted in the United States (us-east-1).
Stripe
Payments. Card details go to Stripe, not to us.
Anthropic
AI report generation, using Claude models.
Gemini, used only to generate blog cover images. No user data and no review data is sent to it.
Lovable
Application hosting.
We name the region because "we use industry-standard providers" tells a reader nothing. If you are in the EU or UK, note that your data is stored in the United States.
6.How long we keep it
- Account data: until you delete your account.
- Reports and watchlists: until you delete them, or until the account is deleted.
- Newsletter records: until you unsubscribe, after which we keep only the minimum needed to honour that unsubscribe.
- Billing records: for as long as tax and accounting rules require, since they are not ours to delete on request.
- search_queries and card_events: these are not tied to a person, so there is nothing to delete on request. They are kept and used in aggregate.
7.Your rights, and how to use them
You can ask for access to what we hold, correction of anything wrong, an export of your data, deletion of your account and its contents, and you can object to a particular use or withdraw consent you have given.
- Access and export: email info@appeye.ai and we will send a machine-readable export within 30 days, usually much sooner.
- Correction: your email and account details are editable in your account; anything else, email info@appeye.ai.
- Deletion: deleting your account removes your watchlists, alerts, notifications, reports, share links and preferences. Billing records are retained where the law requires. Deletion runs immediately when you use the button in your account; where a request reaches us another way, we complete it within 30 days.
- Newsletter and alerts: unsubscribe from any email in one click, or turn alerts off in your account.
Account deletion is a button in the product, not an email request: sign in, open the account area, go to the Security tab and use “Delete my account”. You confirm by typing your own email address, and the deletion runs immediately.
8.Security, honestly
Every table holding user data has row-level security, so a signed-in account can only read its own rows. Anonymous visitors read a separate sanitised view and hold no privileges on the underlying tables at all. Traffic is encrypted in transit. Passwords are hashed by Supabase Auth and never visible to us.
We hold no security certifications, and we are not going to describe our security as "bank-level" or "military-grade". Both phrases are meaningless. No system is unbreachable; if we ever suffer a breach affecting your data, we will tell affected users directly and promptly.
9.Children, changes and contact
Appeye is a professional research tool. It is not directed at anyone under 16, and we do not knowingly create accounts for them.
If we make a material change to this policy, we will announce it before it takes effect, and the effective date at the top of this page will always show which version is in force.
For privacy questions, data-rights requests, or legal administration connected with this policy, email info@appeye.ai.