Privacy
How TickrScope handles account, Telegram, research, billing, cookie, and support data during beta.
This Privacy Notice explains how TickrScope collects, uses, protects, shares, retains, and deletes personal data for the current UK beta. It is written for a Telegram-first research product: the service helps users organise watchlists, sources, alerts, and notes, but it does not ask for broker credentials, execute trades, or act as an adviser. This notice is deliberately detailed so users can understand the actual data boundary before using the product.
This notice applies to the TickrScope website, beta signup flow, Telegram bot interactions, support messages, product emails, cookie preferences, and operational logs. It does not replace Telegram's own privacy terms, payment-provider terms, broker terms, exchange terms, or the privacy notices of third-party sources that users choose to open. This is a beta notice and will be updated as the service develops.
TickrScope may collect your name, email address, Telegram user identifier, Telegram username where available, country or region if you provide it, beta access answers, support requests, cancellation requests, privacy requests, and product feedback. If paid plans are offered, TickrScope may also receive billing status, subscription identifiers, invoice status, refund status, and limited payment metadata from the payment provider. TickrScope does not receive full card details, bank credentials, broker passwords, private keys, seed phrases, or account login credentials.
Users may choose to provide tickers, watchlists, alert rules, holdings context, research questions, saved notes, preferred sectors, and examples of decisions they are trying to understand. This information is used to organise research, query market-data and news-data providers, and make alerts more useful; it is not used to assess suitability, affordability, investment objectives, risk tolerance, tax status, or personal financial circumstances. TickrScope does not ask users to provide salary, net worth, debts, dependants, health information, broker credentials, private keys, or formal financial-planning information.
Telegram is a third-party communications channel. Messages, commands, tickers, attachments, and bot interactions may pass through Telegram systems before TickrScope receives them and after TickrScope sends a response. Telegram may process message metadata and content under its own terms and privacy practices. Users should not send private keys, broker credentials, full account statements, sensitive identity documents, or highly confidential information through Telegram. If a safer support route is needed, users should contact TickrScope by email.
TickrScope uses personal data to operate beta access, deliver research cards and alerts, maintain account and consent state, prevent misuse, respond to support requests, process deletion or export requests, operate paid subscriptions where applicable, maintain security, debug product issues, produce aggregated reliability metrics, and keep an audit trail for important user controls. TickrScope does not sell personal data, and the product is not built around advertising profiles or behavioural ad targeting.
TickrScope may rely on hosting, database, email, analytics, logging, payment, Telegram, market-data, news-data, AI, and operational tooling providers. Market-data and news-data providers, including providers such as Twelve Data and APITube, may receive limited ticker, entity, watchlist, query, source, and usage context where needed to retrieve or explain research evidence. Each provider receives only the data needed for its role. TickrScope does not expose support content, payment metadata, broker credentials, private keys, or user identifiers to unnecessary providers.
TickrScope keeps data only as long as needed for product operation, user support, billing records, security, legal record-keeping, audit trails, and abuse prevention. Some data can be deleted quickly when an account is closed; other records may need to be retained for billing, fraud prevention, dispute handling, tax, legal, or security reasons. A deletion request pauses new research processing where required while the request is reviewed, so TickrScope does not keep building new context for a user who has asked to delete their data.
Depending on the circumstances, users may ask for access to personal data, correction, deletion, restriction, portability, objection, consent withdrawal, or information about processing. Requests should be sent to help@tickrscope.co.uk with enough information to identify the account and the request. TickrScope may need to verify the requester before acting. If a request affects service access, saved research, alerts, billing, or audit records, TickrScope will explain the practical effect where possible.
TickrScope uses technical and organisational controls intended to protect user data, including access controls, encrypted transport, limited operational access, logging, and separation of sensitive workflows where feasible. No online service can guarantee perfect security. Users should keep their email and Telegram accounts secure, avoid sharing secrets in chat, report suspicious messages, and contact support promptly if they believe their account, Telegram identity, or TickrScope interaction has been compromised.
