Privacy Policy
Last updated: 1 June 2026 | EmaView
1. Overview
EmaView is operated by Anance Intelligence Ltd (SC880824) and runs at emaview.com. We are committed to protecting your privacy. This policy explains what data we collect, how we use it, and what we do not do.
2. What We Collect
We collect only the data necessary to provide the EmaView service. Specifically:
- Your email address, used for account authentication and password recovery. Stored securely in Supabase.
- Your subscription tier (Free or Pro) and purchase history. Stored in Supabase.
- Your paper trading journal, including simulated trades, positions, and performance metrics. Stored in Supabase.
- Your learning progress, including lesson completion, quiz results, and concept mastery scores. Stored in Supabase.
- Your app preferences (theme, EMA settings, SL/TP mode). Synced between localStorage and Supabase.
- Signal interaction data (which signals you acted on and what decision you made). Stored in Supabase.
We do not store payment card details. All payment processing is handled entirely by Stripe.
3. What Is Stored Locally
EmaView stores the following in your browser's localStorage:
- Supabase authentication tokens (session management).
- Your app preferences (theme, EMA settings, trading mode). These are also synced to your Supabase account when signed in.
- Your Telegram bot token and chat ID, if you configure Telegram alerts. These credentials are stored only in your browser and are never transmitted to EmaView servers.
- Onboarding and tour completion flags, so the app can remember where you are in setup.
This is first-party browser storage processed locally on your device. It is not a third-party service and is not shared with anyone. Your Supabase authentication session is cleared from localStorage when you sign out. Your preferences and onboarding flags remain on your device until you clear your browser storage.
4. Third-Party Services
EmaView connects to the following third-party services:
- Supabase: hosts your account data (email, tier, learning progress, paper trades, preferences). Supabase's privacy policy applies.
- Stripe: handles all payments. Stripe's own privacy policy applies to your purchase and payment data. No card details are stored on EmaView servers.
- Anthropic API: powers the AI tutor feature. Your signal data (asset, price, EMA values, decision) is sent to Anthropic for feedback generation. No personal data (name, email) is sent. Anthropic's privacy policy applies.
- CoinAPI: our source for live and historical market data (prices and candles for the chart and the multi-coin scanner). All market data is fetched server-side through EmaView's own API routes and cached, so your browser never connects to CoinAPI directly. The data is read-only and public. We do not send your account details or anything that identifies you by name or email to CoinAPI.
- Telegram Bot API: only if you configure alerts. Your bot token goes directly from your browser to Telegram. EmaView has no access to it.
- Plausible Analytics: privacy-focused, cookie-free, aggregate-only website analytics. It measures page views in aggregate. No personal data is collected and no tracking cookies are set. Plausible's privacy policy applies.
- PostHog: product analytics, hosted in the EU. PostHog is cookie-free and records only a small set of named product events, covering app opens, onboarding, lessons and quizzes, tutor use, paper trades, signal views, upgrade prompts, and checkout starts. Automatic capture and session recording are switched off. Signed-in users are identified by their Supabase user reference only; no name, email, or other personal data is sent, and your identity is reset when you sign out. PostHog is disabled entirely when no analytics key is configured. PostHog's privacy policy applies.
- Vercel: hosts the EmaView application. Vercel may process server logs containing IP addresses and request metadata. Vercel's privacy policy applies.
5. Cookies and Local Storage
EmaView does not set tracking cookies. Plausible Analytics is cookie-free, and PostHog stores only a pseudonymous product-analytics identifier in localStorage rather than in a cookie (your Supabase user reference once signed in). Your browser stores Supabase authentication tokens in localStorage for session management, and these are cleared when you sign out. These are functional tokens required for the app to work, not used for advertising or cross-site tracking.
6. Data Retention and Deletion
Your account data is retained for as long as your account is active. You can export all your data at any time using the "Export My Data" feature in the app.
You can delete your account through the app settings. Deletion follows a 30-day grace period: when you request deletion, your account is immediately locked and scheduled for permanent removal 30 days later. If you change your mind, simply log back in within those 30 days and your account is restored in full. If you do nothing, after 30 days we permanently delete your account credentials, learning progress, paper trading history, concept mastery, and AI tutor history.
One exception applies. We are required by UK law to keep records of financial transactions for a statutory period (around six years). After your account is deleted, your payment records are retained in pseudonymised form: the link to your identity is removed (your user reference and Stripe customer reference are erased), and only the transaction details required for accounting and tax compliance are kept.
7. Your Rights (GDPR)
If you are in the UK or EU, you have the right to access, correct, export, and delete your personal data. EmaView provides self-service tools for data export and account deletion. For any requests you cannot complete through the app, contact us at the email below.
8. Children
EmaView is not intended for users under the age of 18. We do not knowingly collect data from minors.
9. Changes to This Policy
We may update this policy from time to time. The date at the top of this page will reflect the latest version. Continued use of EmaView after any change constitutes acceptance of the updated policy.