TideTrade
ScannerLedgerHow it worksThe Tide RulesPricing
WalletCheck my wallet Sign in Start free

Privacy notice

Last updated: 21 November 2026

This notice explains what personal data TideTrade (“we”, “us”) collects when you use tidetrade.app (“the Service”), why, who else handles it, how long we keep it and what your rights are. It is written to match what the Service actually does today. Where that is still changing, it says so.

1. Who we are

TideTrade, the service at tidetrade.app, is the controller of your personal data: it decides what is collected and why. For anything about your data, write to support@tidetrade.app.

2. The short version

  • We show no ads, set no advertising cookies and do not sell your data.
  • Visits are counted without cookies, by our own server and by Ahrefs Web Analytics. Google Analytics, which does use cookies, runs only if you allow it, and you can change your mind at any time (section 3.9).
  • To give you an account we store your email address, your portfolio, any wallet addresses you choose to save, and how you want to receive alerts.
  • Wallet addresses are public, read-only addresses. We never ask for private keys, seed phrases or exchange logins, and we never hold funds.
  • Payments are handled by Stripe. We never see your card details.
  • If you make your profile public, anyone can see your chosen name and the tide state of the assets you hold. They cannot see quantities, values or wallet addresses.
  • You can delete your data, and your whole account, yourself under Account (section 10).
  • The market data we publish (the scanner, the ledger, the Sunday Tide Reports, the snapshot API, the share images) contains no personal data.

3. What we collect and why

3.1 Your account

You sign in through Clerk, our sign-in provider. Clerk handles your sign-in details: your email address and, if you sign in with a service such as Google, the basic profile it shares (usually your name and picture). The first time you sign in, we ask Clerk for your primary email address and store:

  • an internal account ID and your Clerk user ID
  • your email address
  • your plan (Free or Pro), the date your Pro access runs until, and your Stripe customer and subscription IDs once you subscribe
  • the date you created the account.

We also create an empty portfolio for you and an email alert channel for your sign-in address, so that the Sunday digest reaches you.

If you later change your email address in Clerk’s account panel, tell us too: we do not yet pick up the change automatically, so alerts and the digest would keep going to the old address.

3.2 Your portfolio and wallets

  • Holdings: each asset you add, an optional quantity, whether you added it by hand or from a wallet (and which wallet), and the date it was added.
  • Saved wallets: the blockchain family (EVM, Solana or Bitcoin), the public address, an optional label and when it was last read.
  • Untracked tokens: the symbol and contract address of tokens your saved wallet holds that the Service does not cover, so that we can show you what is not tracked.

3.3 Checking a wallet

When you paste an address into the wallet check, signed in or not, our server sends that public address to public blockchain data services to read its balances (section 6). It sends only the address: not your IP address, your account or anything else about you.

If you do not save the wallet, we do not store the address in our database. Our server keeps the result in memory for up to 10 minutes, so that a shared result link does not call the data services again. The address also appears in the result page’s web address, so anyone you share that link with can see it.

Our usage records (section 3.9) note that a wallet check happened, which blockchain family it was, how many holdings were found and, if you came from a link with campaign tags, those tags. They do not record the address.

3.4 Alerts and the Sunday digest

  • Alert channels: your email address, your Telegram chat ID if you link Telegram, or a webhook address you give us together with the signing secret we generate for it, with your settings for each channel: which assets, which timeframes, entries, exits or both, and whether the channel is on.
  • Delivery records: which flip was sent to which channel and when, so that nobody gets the same alert twice.
  • Digest records: which week’s Sunday digest was sent to your account, and the date you switched the digest off, if you did.
  • Telegram link codes: when you link Telegram, we create a one-time code tied to your account and record when it was created and used. A code works for 24 hours.

To link Telegram you message our bot. Telegram passes us your message and your chat ID. The bot acts only on a link code (and on one set-up command the operator uses) and stores no other message you send it. The open community group runs on Telegram itself: if you join it, Telegram and the other members see your Telegram name and what you post, under Telegram’s own privacy policy. Our bot posts there and does not keep what members write.

Every digest email carries an unsubscribe link that works without signing in. The link is signed, so nobody can unsubscribe you by guessing it, and the page asks you to confirm, so an email scanner that follows links cannot unsubscribe you either.

3.5 The Sunday Tide Report without an account

You can get the Sunday Tide Report by email without creating an account. We ask you to confirm your address first, with a link we email you that works for 7 days. For each sign-up we store:

  • your email address
  • when you signed up, when we sent the confirmation (and how many we sent that day, to cap them), when you confirmed, and when you unsubscribed
  • a one-time confirmation code (cleared once you confirm) and an unsubscribe code
  • which version of the sign-up wording you agreed to, and which form you used
  • the campaign tags of the link you came from, if any
  • which week’s report we last sent you, and when.

We do not store your IP address or browser details, and we do not track whether you open the email or follow its links. To stop abuse of the form, our server holds the IP addresses of recent sign-ups in memory for one hour (five sign-ups an hour per address); they are never written to disk. A hidden form field catches automated sign-ups, which are discarded.

If you do not confirm within 30 days, we delete the sign-up. If you unsubscribe, we keep your address and the date, so that we never email you again by mistake; the same link turns the report back on, and you can ask us to delete the record. If you also have an account with the same address, you get one report, not two.

3.6 Public profile (optional)

If you set one up, we store your chosen name, whether the profile is public, whether you ticked “I’d like to follow friends’ tides”, and when you last changed these settings. You can clear the name again; clearing it also makes the profile private.

While the profile is public, anyone can open its page and see your chosen name, the date your account was created, and the assets in your portfolio, each with its current tide state and when it last flipped. It never shows quantities, values, wallet addresses, your email address or your history. Search engines and link previews may pick up a public page. After you switch it to private, copies held by browsers or caches can take up to 5 minutes to expire.

3.7 API keys (Pro)

When you create an API key, we show you the full key once. We then keep only its first 11 characters (so that you can tell your keys apart), a one-way hash of the full key, your label, and when the key was created, last used and revoked. Revoked keys stay listed with their revocation date.

3.8 Payments

Pro is sold through Stripe. The checkout page, receipts, invoices and order management are provided by Stripe and its Link service, which acts as seller of record and handles sales tax and VAT. Your card or other payment details, billing address and tax location go to Stripe. We never receive or store them.

When you start a checkout, we create a Stripe customer record holding your email address, our internal account ID and your Clerk user ID. Stripe then tells us when your subscription starts, renews, changes or ends, and we store its status as your plan and the date your Pro access runs until. Stripe handles payment data under its own privacy policy.

Until Pro opens for sale, the checkout runs in Stripe’s test mode and takes no real payment.

3.9 Counting visits and usage

Our own usage records (no cookies). To understand how the Service is used, our server records a small set of events: page views, wallet checks, saved wallets, sign-ups, Sunday Tide Report sign-ups and confirmations, checkouts started, subscriptions started and ended, account deletions, Telegram links, API keys created, webhooks added, and calls to our MCP tools (section 3.10). Each record holds:

  • the event name and time
  • the page path, without the query string
  • the referring website’s host name only (for example google.com), and only when you came from another site
  • campaign tags in the link, if present
  • a few event details, such as whether a checkout was monthly or annual, which MCP tool was called or, for a page view, whether the request carried the headers a real browser sends (presence flags and standard values only), which we use to tell scrapers from people
  • if you are signed in: your account ID
  • if you are not signed in: a pseudonymous visitor code. We make it by hashing a secret value, today’s date, your IP address and your browser’s user-agent string together. The IP address and user-agent are not stored. Because the date is part of the hash, the code changes every day, so we cannot recognise you from one day to the next.

Requests that look automated are not recorded. These records need no script in your browser and store nothing on your device. Only the Service’s administrator can see them.

Ahrefs Web Analytics (no cookies). Every page loads a script from analytics.ahrefs.com to count visits. Ahrefs states that it sets no cookies and stores no personal data; to count a visit the script does send your IP address, browser details and the page address to Ahrefs.

Google Analytics (cookies, only if you allow it). On your first visit a card asks whether we may count visits with Google Analytics. Until you choose “Allow”, nothing is loaded from Google and no analytics cookie is set. If you allow it, your browser loads Google’s tag script, served through Google Tag Manager, which sets two cookies holding a random identifier and sends Google the pages you open, the site you came from, your browser and device details and your IP address. Google’s standard measurements are on, so it also records how far down a page you scroll, which outside links and downloads you click, and when you start or submit a form on the site, though not what you type into it. The container carries Google Analytics and nothing else; if we ever add another tool to it, this notice will say so first. We use it for totals only: which pages are read and where visitors come from. The advertising settings in Google’s consent controls stay off whatever you choose, and we do not use the data for advertising.

You can change your answer at any time with “Analytics choice” in the footer of every page. Choosing “No thanks” stops the measurement and removes the two cookies. Your answer is kept in your browser, not on our server, and we ask again after six months. If your browser sends a Global Privacy Control signal, we treat that as “No thanks” and do not ask.

3.10 Server logs, the API and the MCP server

Our web server keeps no access log, so it does not record visitors’ IP addresses. The application’s own log, on our server, records operational events such as a payment notification arriving (with the Stripe subscription ID and our internal account ID), account deletions (with our internal account ID), fetches by search crawlers and AI assistants’ fetchers, and error messages. It is deleted after 30 days.

The free snapshot API and the MCP server (the tools an AI assistant can call) serve market data only. To limit how often one client may call them, our server holds each client’s IP address in memory for up to a minute; it is never written down. A call to an MCP tool is also a usage record (section 3.9) with the tool’s name, never what you asked it. If you use TideTrade through an assistant such as Claude or ChatGPT, the request reaches us from that provider’s servers, so we see the provider’s address, not yours; what you type into the assistant is covered by the provider’s own privacy notice. Calls to the keyed API update the key’s last-used time (section 3.7).

3.11 When you contact us

If you email us, we keep your message and our reply to deal with your request.

3.12 What we do not collect

We do not collect special category data, and we make no automated decisions with legal or similarly significant effects on you. The tide states come from a published rule applied to market prices, not from profiling you.

4. Cookies and similar storage

We set no advertising cookies. The only analytics cookies are Google’s, and only after you allow them (section 3.9).

WhatSet byWhyType
__session, __client_uat and similarClerk, our sign-in providerKeep you signed in and protect the sign-inNeeded for sign-in
__clerk_db_jwtClerkPart of the sign-in while it runs on Clerk’s development set-up. It is set on a browser’s first visit, signed in or not (see below), and goes when we move to the production set-upNeeded for sign-in
One session-storage entry on the sign-in pageTideTradeRetries a failed sign-in once, then removes itselfNeeded for sign-in
tt-analytics-consent (local storage)TideTradeRemembers your answer to the analytics question for six months. It stays in your browser and is not sent to usNeeded to respect your choice
_ga and _ga_KPF22V2JHHGoogle Analytics, only after you choose “Allow”Hold a random identifier so that Google can count visits. They last up to two years; most browsers shorten that to about 13 monthsAnalytics, with your consent
Cookies on the Stripe checkout and billing pagesStripePayment and fraud preventionStripe’s own policy applies

Clerk’s sign-in component loads from Clerk’s servers on the sign-in, sign-up and account pages, and on every page once you are signed in; on other pages, for visitors who are not signed in, it does not load. Until we move to Clerk’s production set-up, however, a browser’s first visit to any page is redirected once through Clerk’s domain and back, so Clerk receives your IP address and browser details on that first visit even if you never sign in.

Fonts, charts and images are served from our own server. Apart from Clerk, Ahrefs and, with your consent, Google Analytics, no third-party script runs on our pages. Links to other sites, such as the chart link on asset pages or our Telegram, Bluesky, Medium, Paragraph and Linktree pages, take you to services with their own privacy policies.

5. Our lawful bases

Where the UK GDPR or the EU GDPR applies, we rely on these bases (Article 6):

PurposeLawful basis
Creating and running your account, portfolio, saved wallets, alerts, API keys and the Sunday digestContract: providing the service you signed up for
Running a wallet check you ask forContract, or steps you ask for before one; for visitors who are not signed in, our legitimate interest in answering the request you made
Publishing your public profileContract: you asked us to publish it, and you can switch it off at any time
Taking payment and managing your planContract
Our own usage records, Ahrefs’ visit counts, rate limits, security, server logs and backupsLegitimate interests: running a reliable, secure service and understanding which pages help people, with records kept minimal (section 3.9)
Counting visits with Google AnalyticsConsent: it runs only if you choose “Allow”, and you can withdraw at any time under “Analytics choice” in the footer
Sending the Sunday Tide Report to someone without an accountConsent: you confirm by email, and every report carries a link to withdraw
Keeping the address of someone who unsubscribed, so we never email them againLegitimate interests: respecting the objection
Answering your emailsLegitimate interests, or contract when it concerns your subscription
Keeping records the law requires, such as tax and accounting recordsLegal obligation

6. Who we share data with

We share personal data only with the providers below, and only what each needs. Where a provider acts for us, it does so under its data-processing terms.

ProviderWhat they do for usPersonal data they handleWhere
Clerk, Inc.Sign-in and sessionsEmail address, sign-in method details, session and device information, IP addressUnited States
Neon (managed Postgres)Our databaseEverything in section 3 except payment detailsFrankfurt, Germany (AWS eu-central-1). Neon is a US company
Hetzner Online GmbHOur server: the website, alert sending and nightly backupsEverything in section 3, and the backups (section 8)Nuremberg, Germany
Stripe, with its Link servicePayments, as seller of record (section 3.8)Email address, our account identifiers, payment and billing detailsUnited States and the countries where Stripe operates
ResendSends alert, confirmation and report emails, through Amazon SESYour email address and the email’s contentUnited States
TelegramDelivers alerts to Telegram if you link itYour chat ID and the alert text. Telegram is an independent provider; its own privacy policy covers your Telegram accountTelegram’s own infrastructure
AhrefsCounts page views without cookies (section 3.9)IP address, browser details and the page address, at the moment of the visitAhrefs is a Singapore company
Google (Google Analytics)Counts visits, only if you allow it (section 3.9)A random identifier in a cookie, the pages you open, the site you came from, browser and device details, and your IP address at the moment of the visitGoogle Ireland Limited or Google LLC; the United States and other countries where Google operates
ntfy.shSends operational alerts to the operator’s phoneOperational messages about the service’s own jobs, written to hold no customer dataNot applicable

Blockchain data services. When you check or re-sync a wallet, our server sends the public address, and nothing else, to Etherscan (Ethereum, Arbitrum, Polygon), public nodes for Base, BNB Chain and Optimism, Hyperliquid (EVM addresses), the Solana public node, and Blockstream or mempool.space (Bitcoin). These are independent services, and the address is already public on its blockchain.

Webhooks. If you add a webhook, we send your alerts to the address you chose, which is your own service or one you picked; what happens to them there is between you and it. The one test we send on adding carries no personal data.

AI assistants. If you add TideTrade to an assistant (section 3.10), the assistant’s provider is your provider, not ours; we receive only the tool calls it makes.

Others. We may share data with professional advisers, or where the law requires it, for example under a court order. We will tell you unless the law stops us. Our source code is held by GitHub, which holds no customer data.

7. International transfers

Our database and server are in Germany. Some providers in section 6 are outside the United Kingdom and the European Economic Area, mainly in the United States. Where personal data goes to them, the transfer relies on an adequacy decision that covers the provider (such as the EU-US Data Privacy Framework and its UK extension, where the provider is certified) or on the standard contractual clauses in the provider’s data-processing terms.

8. How long we keep data

DataKept for
Account, portfolio, wallets, alert settings, profileWhile your account exists. Deleted at once when you delete the account (section 10)
Wallet check results you do not saveUp to 10 minutes, in server memory only
Rate-limit records (IP addresses for the API, the MCP server and the sign-up form)Up to one hour, in server memory only
Usage records13 months, then deleted
Alert delivery and digest records12 months
Telegram link codes30 days
Sunday Tide Report sign-ups without an accountNot confirmed: deleted after 30 days. Confirmed: until you unsubscribe. Unsubscribed: the address and the date are kept so that we never email you again by mistake; ask us and we will delete them
Revoked API key records12 months after revocation
Stripe identifiers and your planWhile your account exists. Stripe keeps its own records under its policies
Server application logs30 days
Database backupsA nightly backup on our server; the newest 14 are kept, so deleted data leaves them within 14 days. An occasional copy is also kept off the server for disaster recovery. Those copies are not on the 14-day cycle: ask us if you want your data removed from them
Your analytics choice and Google’s cookiesIn your browser: the choice for six months, the cookies until you choose “No thanks”, clear them, or they expire
Emails you send usFor as long as it takes to deal with your request, and afterwards only where we need a record of it

A daily job deletes records once they pass these periods.

9. Your rights

If you are in the United Kingdom or the European Economic Area, and in many other places, data protection law gives you the right to:

  • access the personal data we hold about you
  • correct data that is wrong
  • erase your data
  • restrict how we use it
  • object to our use based on legitimate interests, and at any time to direct marketing
  • portability: receive data you gave us in a machine-readable format
  • withdraw consent where we rely on it, such as the analytics choice and the Sunday Tide Report.

To use any of these rights, email support@tidetrade.app from the address you sign in with. We will reply within one month. Some requests may take up to two months more if they are complex, and we will tell you if that happens. Using your rights is free.

If you are unhappy with how we handle your data, please tell us first. You can also complain to your data protection authority: in the United Kingdom, the Information Commissioner’s Office (ico.org.uk); in the European Economic Area, the authority of the country where you live.

10. Deleting your data and your account

You can do these yourself today, under Account:

  • Portfolio: remove any holding, or remove a saved wallet. Removing a wallet deletes its address, its untracked-token list and the holdings imported from it.
  • Alerts: switch off or remove an alert channel, including a linked Telegram chat, and switch the Sunday digest off (or use the unsubscribe link in any digest email; no sign-in needed).
  • API: revoke a key.
  • Profile: switch your public profile to private, or clear the name.
  • Billing: cancel your subscription in the billing portal.
  • Analytics: choose “No thanks” under “Analytics choice” in the footer; no account is needed.

Deleting your whole account. Go to Account, then “Delete my account”, and type “delete” to confirm. In one step we cancel any active Pro subscription, so that you are not charged again; delete your Clerk sign-in account; and delete your account, portfolio, wallets, alert channels, API keys, profile, and delivery and digest records from our database.

Please use that button rather than deleting your sign-in from Clerk’s own “Manage account” panel: at present a deletion made there does not reach us, and your TideTrade data would stay until you email us. We keep only what the law requires, such as billing records, which are held by Stripe. Your usage records stay, but are no longer linked to you. Deleted data leaves our server’s backups within 14 days (section 8). If you cannot sign in, email support@tidetrade.app from your sign-in address and we will do it for you within one month.

11. Security

All traffic to the Service is encrypted (HTTPS with HSTS). The database connection is encrypted and the server’s certificate is verified. API keys are stored only as one-way hashes. Our server allows key-based administrator access only, and its backups are readable only by the server’s administrator. No system is perfectly secure. If we have a breach that puts your rights at risk, we will tell you and the regulator as the law requires.

12. Children

The Service is not for anyone under 18, and we do not knowingly collect data about children.

13. Changes to this notice

If we change this notice in a way that matters, we will change the date at the top and, if you have an account, email you before the change takes effect.

14. Contact

TideTrade · support@tidetrade.app

ScannerLedgerHow it worksThe Tide RulesPricing

Decision support, not financial advice. TideTrade shows the mechanical state of a published trend rule — Rule v1, Supertrend(10, 3) — on historical prices. It does not know your situation, it will be wrong often in sideways markets, and past states do not predict future prices. You decide; your money never leaves your hands.

Full disclaimer · Terms · Privacy · About · Contact · How it works · Guides · Pricing · Community · Sunday Tide Report · Report archive · The study · Status · API · Writing · · Market data from Kraken, Coinbase, Yahoo Finance.

Analytics: your choice

TideTrade can count visits with Google Analytics, which sets cookies.

It loads only if you allow it; the site works the same either way. You can change this in the footer. More in the privacy notice.