1. Controller

Scrupling is responsible for the personal data processed through Scrupling. Contact: [email protected].

2. What we collect and why

Personal data categories
Data	Purpose	Legal basis
Email address and account identifier	Create your account, sign you in, send service and security messages	Contract
Session token (cookie)	Keep you signed in securely	Contract; strictly necessary
Plan, subscription status and payment-provider customer ID	Provide the plan you chose and handle billing	Contract; legal obligations for tax records
Decisions, journal entries, watchlists and PAPER records you create	Provide the workspace features you use	Contract
Preferences you choose: trading style, experience, coins you follow and alert channels	Personalise defaults, such as which coins appear first	Contract
Questions you send to Scrupling AI, its answers and the evidence they cited (your Copilot history)	Answer you, and let you return to an analysis from any screen	Contract
Conditions you add to a decision (Assumption Radar) and your cooldown-lock setting	Re-check them on market data and tell you when one breaks	Contract
The public address of a Hyperliquid account, if you connect one in Connections	Read that account's open positions from Hyperliquid's public data so you can watch them. The address is public; we never receive a key or a signature	Contract
Your token rules and the tokens you watch (their contract addresses)	Check tokens against your rules and email you when a watched token fails one	Contract
Commands you send to our Telegram bot, such as /check	Run the check you asked for and answer in the chat. The message is processed and not stored	Contract
Technical logs (IP address, timestamps, error codes)	Security, abuse prevention and fixing faults	Legitimate interest

We never ask for, and you must never enter, seed phrases, private keys or exchange credentials. We do not sell personal data and we do not use advertising trackers.

3. Service providers

We share data only with providers that help us run Scrupling, under data-processing terms:

Supabase: account authentication and database hosting.
Google sign-in: only if you choose it. Google tells us your email address and that it is verified; we receive no password and no other Google data.
Stripe: payments. Card details go directly to Stripe; we never see or store full card numbers.
Google (Gemini API): AI answers. When you ask a question, we send it with the parts of your own data needed to answer it (for example the decision you are looking at, your Playbook limits and the market data shown). We use the paid API tier, under which Google does not use prompts or responses to improve its products.
Telegram, Discord and your browser's push service (Google, Apple, Mozilla or Microsoft): only if you connect them, to deliver alerts you chose. An alert names your decision and what changed. Telegram and Discord keep messages under their own terms; delete them there, and disconnect in Connections at any time.
Resend: sends our emails (welcome, billing notices, the optional weekly report and invite rewards). It receives your email address and the email itself.
Sentry: error reports, so we can fix faults. Reports hold the type of error, the code location and the page path with ids removed; we strip email addresses, tokens and account ids before anything is sent.
Plausible Analytics: only if you choose "Accept all". It counts page visits without cookies and without identifying you; we send the page address with ids removed and, if you came from another site, that site's name.
Market data sources (CoinMarketCap, Hyperliquid, DefiLlama, FRED, Deribit): our servers read public prices, funding, order books, protocol TVL, release dates and options open interest. Nothing about you is sent to them.
Hyperliquid (your positions): only if you connect an address. Our servers send that public address to Hyperliquid's public API to read its open positions; nothing else about you is sent.
Token data sources (DexScreener, RugCheck, GoPlus and a Solana RPC provider): when you read or watch a token, our servers send the token's contract address to read its public signals. Nothing about you is sent to them.
Upstash (only where we use it): short-lived counters that limit repeated sign-in and AI requests, to prevent abuse.
Microsoft Azure (Germany): hosting the application, technical logs kept for 30 days, and encrypted daily database backups kept for 30 days.
Cloudflare: our domain's DNS, the encrypted connection to your browser and protection against abuse. It sees request details such as your IP address and browser, as any web host does.

Some providers may process data outside your country. Where required, transfers rely on appropriate safeguards such as the EU Standard Contractual Clauses.

4. Retention

We keep account data while your account is open. Decision and journal records are kept as an unchangeable history while your account exists, because that history is the purpose of the feature. After you ask us to delete your account, we delete or anonymize personal data within 30 days, except billing records we must keep by law. Technical logs are kept for a limited period for security. Alert delivery records are deleted after 30 days. Imported trades are kept until you delete the import; the file you upload is never stored. Copilot conversations are kept until you delete them (one at a time or all at once, in Copilot) or delete your account. A connected Hyperliquid address is kept until you disconnect it, and watched tokens until you stop watching them; both go with your account.

7. Security

Data is encrypted in transit. Access is checked on the server for every request and scoped to your own account. No system is perfectly secure; if a breach affects you, we will notify you as the law requires.

8. Changes

We will post updates here and, for material changes, tell you in the product or by email before they apply.