Beta privacy status
This is a product privacy summary, not the final legal Privacy Notice. Data controller details, privacy contact, ICO registration status, processor names, transfer safeguards, and retention periods remain pre-launch blockers.
Privacy
Your research workspace should stay private and explainable.
This beta privacy summary explains what TickrScope expects to collect, why the data is needed, which controls users should have, and which privacy details still need operator, legal, and processor confirmation.
Data controller details pending
Before paid public launch, TickrScope needs the final operator or company name, direct privacy contact, postal contact where required, ICO fee/registration position, and the final user complaint route.
Data used to run the service
Account details, workspace membership, Telegram identifiers, watchlists, saved notes, research prompts, generated research cards, alert settings, support tickets, billing references, cookie preferences, and technical security logs may be processed.
Telegram data
Telegram chat IDs, usernames, names, commands, and message text can pass through Telegram before reaching TickrScope. Do not send broker credentials, private keys, full payment details, or other secrets through Telegram.
Onboarding and watchlist data
Experience level, interests, watchlist tickers, and alert preferences can be used to simplify the interface and organise research. They must not be used to decide what you should buy, sell, hold, size, or trade.
Portfolio context is optional
If you provide portfolio context, it is used to organise research and show concentration or evidence gaps. It must not be used to tell you what to buy, sell, hold, size, or trade.
Billing and support data
Stripe customer references, subscription state, webhook events, support messages, bug reports, bad-output reports, and data-rights requests may be kept so the beta can operate and respond to disputes or requests. TickrScope does not store full card numbers or CVV details.
Lawful bases to settle
Contract is likely for core service delivery, legal obligation for records required by law, legitimate interests for security and abuse prevention, and consent for optional analytics or marketing where required. The final lawful-basis map still needs privacy review.
Providers and processors
Hosting, database, Telegram, Stripe, email/support, monitoring, and model providers may process limited data needed to operate the beta. Final processor names, contracts, locations, and data processing agreements must be confirmed.
Telegram transfer risk
Telegram is a platform dependency and data-protection weak point. The beta needs a processor/transfer assessment and a channel-migration plan before wider launch.
AI and automated processing
AI can help summarise pre-checked public sources, but TickrScope must not make solely automated decisions with legal or similarly significant effects. AI outputs need source trails, challenge routes, and DPIA review before broader use.
Retention schedule
Account, billing, research, support, Telegram, security log, consent, and backup retention periods must be defined by purpose, minimised, and matched to deletion/export fulfilment before paid public launch.
Your controls
Users should be able to request access, correction, export, deletion, restriction, objection, portability, and withdrawal of optional consent where applicable. Telegram routes include /privacy, /export, /delete, and /stop.
Security and breach response
Expected controls include TLS, password hashing, tenant isolation, least-privilege admin access, audit logs, backup hygiene, secret scanning, and a breach response plan that can assess ICO notification within 72 hours where required.
Retention and rights
Data should be retained only as long as needed for service delivery, security, support, legal, accounting, and audit purposes. Support routes for /privacy, /export, /delete, and /stop should remain visible during beta.
Pre-launch privacy blockers remain: final legal entity details, privacy contact, ICO registration or fee position, processor list, DPAs, international-transfer position, DPIA, ROPA, retention schedule, breach response plan, SAR/export/delete identity workflow, and privacy notice acknowledgement.
Read the related beta controls: Cookie Policy, Terms, Risk, Acceptable use, and Accessibility.
Reviewed June 2026. Reviewed 8 June 2026. This is a product privacy summary, not a final legal notice.