Privacy Policy — The Coin Daily

On this page

Public news and videos are free to read and watch. Research Desk and our AI-assistant tools share a subscription. This policy covers both, including account access, billing, optional emails and website measurement.

Who is responsible

The Coin Daily is operated by Novaframe AI Limited, a UK company and the controller of the personal information we use to run these services. Use our contact form for a privacy question or to exercise your rights. Choose Privacy or personal data and include an email address if you would like a reply.

We use Amazon Cognito to authenticate accounts. You can sign in with email and password, or with Google where offered. We receive identity information such as your verified email address, provider identifier and sign-in status. Passwords are handled by the authentication service, not sent to our editorial team.

Google sign-in is for identity and email verification only. It does not give us access to your Gmail, Drive or other Google content, and does not give customers access to our internal Google Cloud resources.

Our account service keeps a member identifier, linked sign-in identities, verified contact information, membership references, preferences and security records. Secure cookies and server-held sessions keep you signed in. Linking a purchase requires verification, not just a matching email typed into a form.

Subscriptions and payments

Stripe processes checkout, subscriptions, invoices and payment methods for paid plans and card trials. It receives the payment and billing details you enter, which can include your name, email and billing address. Our services use customer and subscription identifiers, status, plan, trial and renewal dates, and invoice information to manage access.

We do not store your full card number or card security code in our account database. Manage billing through your account. See Stripe’s privacy policy.

Our account service records a no-card free week and its eligibility separately from paid billing. A free week does not create a Stripe subscription, require card details or charge you. Complimentary access is also recorded separately from paid billing and does not start a Stripe subscription. Creating an account alone does not start a free week, trial or purchase.

Research and AI-assistant requests

Research receives requests for the assets, dates, indicators and groups you select. Our MCP receives the tool requests your assistant sends, such as a ticker, comparison window or search query, and returns the relevant research data or chart.

Connecting the MCP does not give us access to your entire chat history. We receive the tool arguments the assistant sends, not general access to your conversations. Do not include private documents, passwords or sensitive information in a research query. Your assistant provider handles the conversation and returned data under its own terms and privacy policy.

In-product support chat. The Research Desk support panel sends your question, the bounded recent conversation history you provide and the section of Research you are viewing (for example Today, Markets, Cohorts, Tickers or Taxonomy) to our AI model provider, DeepSeek, so it can draft the answer. DeepSeek processing may take place in China. Do not include passwords, payment details, API keys or other secrets in a support question. Answers are drawn from our published support guides and are not a record of your account. DeepSeek processes that request under its own terms: see the DeepSeek privacy policy and the DeepSeek open platform terms of service.

The research tools are read-only. They do not connect to your exchange account, place trades or require your portfolio or holdings. Selecting assets is a research filter, not a request for personalised investment advice.

Limited technical request records help operate and secure the service: time, a pseudonymous account/key reference, tool or method name, outcome and response time. Our dedicated MCP usage log does not include tool arguments or conversation text. Separate hosting and security logs can include IP addresses and requested paths. Short-lived access checks, rate-limit counters and chart evidence references also support the service.

Emails and contact messages

Optional emails. Newsletter and product-update preferences are separate choices in your account. Neither is a condition of paid or complimentary access. Public newsletter signup asks you to confirm your address; account preferences use a verified contact address. We store your email, any optional name, preference and consent records, and relevant delivery, bounce or complaint information.

We operate Listmonk for subscriber management and use AWS Simple Email Service for delivery. Unsubscribe using an email’s link or change your account preferences. This stops the relevant optional messages; it does not cancel your membership. Necessary verification, security and billing communications are separate.

Free-week email and private feedback. If an eligible free week ends without a paid continuation, we may send one service email to the account’s verified address. It explains how to continue with a paid plan and offers an optional private feedback path. Ignoring or declining it does not change your account. The feedback form asks about usefulness and, only after an explicit decision not to continue, what would make the service worth paying for. It asks for your answers and comments, not your AI conversations. Feedback is optional and private.

Contact messages. Our form sends your message to our private inbox through Formspree. Name and reply email are optional. Include an email if you want a reply, but never send passwords, sign-in links, API keys or full card details. See Formspree’s privacy policy.

Cookies, local storage and measurement

We use different kinds of browser storage:

Account and security: cookies needed for sign-in, session protection and account actions.
Preferences: local storage for your consent choice and, where offered, display preferences or course progress. Browser-only progress is not proof of watching and is not automatically an account record.
Analytics and advertising: Google Analytics, Google Ads, Meta, X and OpenAI advertising measurement. Google tags are configured through Google Tag Manager; the OpenAI measurement pixel is loaded directly by this site only when advertising storage is granted. These systems can measure visits, referral/campaign information, device details, content interactions and promotional-banner performance. Advertising systems can use identifiers for campaign measurement and retargeting. OpenAI’s measurement pixel may use automatic advanced matching: information detected in forms can be normalised and SHA-256 hashed in the browser and included in OpenAI conversion events.
Service diagnostics: After you accept analytics storage, AWS CloudWatch RUM receives page path and title, browser/device details, approximate country and region, load and performance timings, an anonymous browser session identifier and allowlisted campaign labels across public pages and our owned account pages. On the /mcp/ landing page it also receives the full landing-page URL query and its individual parameters, including advertising click identifiers, the browser-supplied referring URL and any query values it contains, plus a per-page-load identifier used to correlate timing records from the same visit. These landing URL values may include information placed in the URL. On account pages the diagnostic record is limited to safe page paths and stage labels such as trial form, claim or signed-in dashboard; timing and performance. It does not include account query strings, referring URLs, email addresses, form values, authentication codes or tokens, Stripe customer/session/subscription identifiers, payment details or other raw financial identifiers. Public pages may also report JavaScript errors and failed same-origin asset paths with query strings removed; account diagnostics use performance telemetry only. On /mcp/, allowlisted behaviour measurements also record scroll-depth milestones, active-section exposures, gallery example changes and screenshot enlargements, monthly/annual selection, C-choice/skip/offer-link actions, sign-in and Academy link clicks, FAQ open/close and lightbox close, with enumerated identifiers and elapsed/foreground timing. These behaviour events do not collect page text, form values, links or arbitrary query values. During the temporary /mcp/ diagnostic, a visitor with no recorded analytics choice is also measured without an acceptance step. In this no-choice mode the same page, query, referrer, timing, browser/device and campaign fields are received with an ephemeral per-page-load context, but no tcd_journey, tcd_consent_pref or RUM session cookie is set and no diagnostic local or session storage is used. This cookie-free mode is not a claim of anonymity: network metadata and the page/query/referrer fields above are still received. The /mcp/ page and shared footer provide Privacy choices with separate Analytics and Advertising controls. Turning off Analytics stops the optional RUM and behaviour diagnostics; turning off Advertising prevents optional advertising measurement and ad identifiers while leaving Analytics measurement available if it remains on. Turn off both records the all-or-nothing rejection; a previously recorded rejection is respected. A domain-wide session cookie (tcd_journey) and the independent enum preference cookies (tcd_consent_analytics, tcd_consent_advertising, with the legacy tcd_consent_pref) support this correlation; the journey cookie contains only an opaque random identifier and is not an authentication or entitlement credential. RUM session cookies are scoped to the instrumented page area (/mcp/ or /account/); no persistent RUM user cookie is set. Signed server callbacks and billing webhooks may add a stage observation with the same journey identifier, but hosted Stripe Checkout and Cognito pages are not instrumented. Turning Analytics off clears the journey and experiment cookie and stops RUM/behaviour and optional GA4 measurement. Turning Advertising off clears the click-attribution and affiliate cookies and stops optional advertising measurement, tags and identifiers, while analytics measurement can continue if Analytics remains on. Turning both off records the all-or-nothing rejection. An advertising-only withdrawal does not stop the analytics journey correlation. These cookies belong to accepted normal whole-funnel measurement and are distinct from the no-choice /mcp/ diagnostic. RUM’s own data is retained for 30 days; our account-owned CloudWatch Logs copy is retained without automatic expiry. These observations are not used for advertising, retargeting or access decisions.
Affiliate attribution: If you allow advertising and arrive through a partner link, Rewardful’s script resolves an anonymous referral identifier and we store it in our own first-party cookie, tcd_ref, for 30 days. It is used only to attribute a subscription to the partner who referred you and contains no personal details.

Our banner still offers an all-or-nothing accept/reject choice, while Privacy choices in the footer provides separate Analytics and Advertising controls. The current tag configuration uses denied defaults in the UK, EEA and Switzerland; defaults elsewhere and the effect of your selection depend on the tag configuration. Your saved choices are passed to the tags on later visits.

Google Consent Mode can send limited cookieless measurement signals when storage is denied. Cookieless does not mean no network information is transmitted. We do not describe these signals as guaranteed anonymous or free of personal data. Serving tags through gtm.thecoindaily.co does not stop Google or advertising platforms being recipients.

To change a saved choice, use Privacy choices in the footer. You do not need to clear cookies or local storage, and using the controls does not sign you out. You can also use Google’s ad settings, Meta’s ad preferences or X’s privacy settings.

Embedded YouTube players and externally hosted images can send requests to their providers. Activating a player brings YouTube’s own data handling into play. Some pages use click-to-load covers; this is not a claim that every third-party asset waits for a click. See Google’s privacy policy.

Why we use personal information

We use account and billing information to enter into and perform our agreement with you. We rely on legitimate interests for proportionate security, abuse prevention and responding to general enquiries, and on legal obligations where records must be retained or disclosed by law. Optional email marketing uses consent. Analytics and advertising storage use consent where required; the actual configuration is described above.

We do not sell personal information or use newsletter subscriber lists for advertising retargeting. This is separate from website advertising tags. Our analysis is not a credit assessment or personalised financial recommendation.

Providers and international processing

Providers include AWS for hosting, authentication, storage and email; Stripe for payments; Rewardful for affiliate referral attribution; Formspree for contact submissions; and Google and advertising platforms for the features described above. Authorised operators can access information needed for support, security and administration. We may disclose information when legally required.

Providers can process information outside the UK. Applicable transfer arrangements depend on the provider and service; contact us for information about safeguards relevant to your data. An assistant you choose also has its own terms. See AWS, Rewardful, Google, OpenAI and Anthropic.

How long information is kept

Retention depends on operating your account, completing the requested service, maintaining security, handling complaints and satisfying accounting or other legal requirements. Verification links and sessions expire; access expiry does not immediately delete every related record.

Private free-week feedback records are retained for 90 days by default from the record’s creation, then expire and are scheduled for deletion through automatic database expiry. Removal is eventual, not immediate. Free-week eligibility, activation history and related audit records are kept separately from feedback content and may be retained longer for eligibility, security and audit purposes.

Necessary billing, dispute, security or suppression records may remain after membership ends or an email opt-out. Unsubscribing stops the relevant optional emails; cancellation ends membership according to its billing terms. Neither action automatically deletes all account records. Ask about a particular record through the contact form.

Your choices and rights

Depending on applicable law, you can request access, correction, erasure, restriction or portability. You can withdraw consent for optional processing without affecting the lawfulness of earlier processing.

You can object to direct marketing at any time. You can also object to processing based on legitimate interests, subject to the applicable legal conditions.

Use your account for preferences and a deletion request, or contact us. A deletion request is recorded for review; it does not immediately erase all records or cancel billing. Cancel renewal in Manage billing if needed. We may verify your identity before acting and respond within applicable legal time limits.

You can complain to the UK Information Commissioner’s Office or your local authority. You do not need to contact us first.

Changes to this policy

We update this page when services or data practices change. The date above identifies the latest revision. Material changes may also be brought to your attention through the service or account communications.