// Legal
Last updated: 4 September 2026
What Solana Helper collects, why we collect it, who it goes to, and how to get rid of it. This policy covers the website at solanahelper.com and everything delivered through it. It sits alongside our Terms of Service.
Solana Helper is operated by a sole proprietor in the United States, trading as Solana Helper, who is the data controller for the personal data described here. "We" and "us" mean that operator; "you" means the person using the service.
For anything in this policy, including a request about your own data, write to support@solanahelper.com. If you need the operator's full legal identity to exercise a legal right or to complain to a data protection authority, ask at that address and we'll provide it.
Only what the service needs to do its job. You can read every lesson on the free path without giving us anything at all — no account, no email, no address.
| What | Why | When |
|---|---|---|
| Email address | To identify your account, reset your password, and send you the account and subscription mail described in clause 6. | When you create an account. |
| Password | To sign you in. We do not store your password. We store a scrypt hash of it, which cannot be reversed back into the password you chose. | When you create an account or change it. |
| Your progress | Which lessons and drills you've completed, so your place follows you between devices. Also your quiz answers, if you take it, to pick your starting track. | As you work through the course. |
| Wallet address | Optional. A public Solana address, so the analyzer can grade it and so you don't have to paste it again. See clause 4. | Only when you enter one. |
| Subscription status | Your plan, whether it's active or trialing, when it renews, and a Stripe customer reference — so we know what to unlock. See clause 5. | If you subscribe to Pro. |
| Email delivery records | Which of our account emails have been sent to you, so you don't get the same one twice, plus your unsubscribe preference. | If you have an account. |
| Ad identifiers | No longer collected. Until 4 September 2026 we stored two values the Meta Pixel put in your browser — one identifying the browser, one identifying the ad you clicked — against your account, so a payment made days later could be credited to the ad that earned it. We stopped advertising, so we deleted them and no longer record them. See clause 3. | Never, from 4 September 2026. |
| Lesson reads | A tally of how many times each lesson has been read to the end, and how far into a run of lessons readers get. Aggregate counts only — no cookie, no visitor identifier, and nothing that ties one read to another or to you. See clause 3. | When you finish reading a lesson, with or without an account. |
| IP address | To rate-limit sign-ups, sign-ins, password resets and wallet analyses, so the service can't be hammered by a script. Held in the server's memory only, aged out automatically, and never written to our database. | Transiently, on those requests. |
| Server logs | Ordinary operational logging so we can find faults and abuse. Kept short and not used to build any profile of you. | As you use the site. |
We do not ask for your name, your date of birth, your address, or your phone number, because the service doesn't need them.
There is no ad tracker on this site, and no advertising platform receives anything about you. Until 4 September 2026 we ran paid ads on Facebook and Instagram and measured them with the Meta Pixel. We stopped paying for ads, so on that date we removed the Pixel from every page and switched off the reports our server sent. Nothing about your visit, your account, your subscription or your trading is sent to Meta any more, and nothing has replaced it.
We do still promote the site. We post about it on social media, and those posts link here — which is how a lot of people arrive. That is ordinary marketing and it involves none of your data: the posts live on those platforms, we learn nothing about you from them beyond the fact that somebody followed a link, and nothing on this site reports back to them. What we removed was the tracking, not the promoting, and this clause will keep saying so plainly if that ever changes.
What was sent before then, and what we can and can't undo. While it ran, the Pixel told Meta that a browser had loaded a page here — with the page address, your IP address and your browser's user-agent string — and set a first-party cookie named _fbp. Alongside it we reported four actions: creating a free account, starting checkout, starting a free trial, and subscribing, the last carrying the amount charged. Some of those reports went from our server rather than your browser, and carried your email address as an irreversible cryptographic hash rather than the address itself. None of them ever carried your password, your wallet address, or anything about your trading.
Reports already delivered are with Meta, and we cannot take them back. Meta received them as its own controller, under its own policies rather than ours, and may have joined them to your Facebook or Instagram account. Stopping the tracker prevents new reports; it does not reach back into Meta's records. To do something about what Meta already holds, use the ad settings and off-platform activity controls in your own Meta account — those are the only controls that reach it, and they always were.
On our side we deleted what we had kept. The two ad identifiers described in clause 2 are gone from our database and are no longer recorded for anyone. The _fbp cookie is set by Meta's script in your browser, not by our server, so we cannot delete it from here: if you visited while the Pixel ran, it may sit in your browser until it expires (up to about 90 days) or until you clear cookies for this site. Nothing here reads it any more.
We also use Cloudflare Web Analytics to count page views. It sets no cookies, stores nothing on your device, doesn't fingerprint you, and can't follow you to any other site. It's how we know whether anyone is reading this at all.
And we count lesson reads on our own server. When you reach the end of a lesson, the site tells us which lesson it was and what number it is in your own running total — your fifth, say. That total is kept in your browser, not by us: we receive the bare number and never anything that says which reads belong to the same person. So we can see that a lesson gets read and that somebody got as far as a fifth one, and we cannot reconstruct who read what. There is no cookie and no visitor identifier involved, and none is sent even when you're signed in. It's how we tell a lesson people finish from one they abandon, which page-view counting can't show us because every lesson shares a single web address.
There is no longer an off switch, because there is nothing to switch off. The account menu used to carry an Ad measurement control; it has been removed along with the tracking it governed. If you had already turned it off, that choice is still recorded and would still apply were we ever to run paid ads again. If we do resume, this clause will say so before it starts, not after.
What an ad blocker does now. Nothing here needs one. Blockers still stop Cloudflare's page-view counter, and nothing on this site breaks when they do — the whole free course still works.
What we don't run: no ad tracker of any kind, no Google Analytics, no session recorder, no heatmap tool, no tag manager, and no social login widget. Cloudflare's cookieless page-view counter and the lesson tally described above are the whole of it. We have never built our own cross-site profile of you, and there is now no third party we hand anything to that could.
We never collect a seed phrase, private key, or anything else that controls a wallet. No part of the service will ever legitimately ask for one — treat any message that does, however it appears to be from us, as fraudulent.
We don't sell personal data and we don't rent it, and we don't pass it to anyone for their own marketing.
The analyzer works from a public Solana address. Nothing is signed or connected — we read the same public transaction history any block explorer shows.
To produce the analysis we fetch that address's swap history from a third-party on-chain data provider and cache it on our server, so a second look doesn't re-fetch everything. That cache is keyed to the address, not to you, and exists for any address that gets analyzed whether or not the person analyzing it has an account.
Be aware of what an address is: a Solana address and its full transaction history are public and permanent on a blockchain we don't control. We can delete what we hold, but we cannot delete anything from the chain itself. If you save an address to your account, you connect that public history to your email address in our records — so only save an address you're comfortable associating with your account, and only analyze an address you own or are otherwise entitled to.
Pro subscriptions are processed by Stripe. Your card details go directly to Stripe and never pass through our servers — we never see or store your card number.
From Stripe we keep only what's needed to run your subscription: a customer reference, your plan, its status, and its renewal date. Stripe processes your payment data as its own controller under its privacy policy, which is worth reading if you subscribe.
Two kinds, and they're treated differently:
Mail is delivered through a third-party email provider, which necessarily processes your address in order to deliver it.
If you're in the UK or EU, data protection law requires us to name a legal basis for each use. Ours are:
Only the service providers the product runs on, and only what each one needs:
We may also disclose data if the law requires it, or to establish or defend legal claims. If the business is ever sold or merged, account data may transfer with it — you'd be told before that changed anything about how it's handled.
Within our own team, access is limited to the people who need it to run the service and support you.
We set no cookies at all. The only one we ever set was the Meta Pixel's _fbp; the Pixel was removed on 4 September 2026, and clause 3 explains why a copy set before then may still sit in your browser until it expires. Beyond that the site uses your browser's local storage — data held on your device that we never receive unless you send it. It holds your sign-in token, your lesson progress, the list of lessons you've read, and a wallet address you've entered, which is what lets the free course work fully without an account. That reading list is also the count described in clause 3: it stays on your device, and only its length is ever sent.
Signing out clears the token. Clearing your browser's site data for solanahelper.com removes the rest — along with any progress that was only ever stored locally, so sign in first if you want to keep it.
Passwords are hashed with scrypt. Session and reset tokens are stored only as hashes. Traffic is served over HTTPS. Card data never touches our servers. Sign-up, sign-in, reset and analysis endpoints are rate-limited.
That said, no service can promise perfect security, and we don't. Use a password you don't use anywhere else, and tell us promptly if you think your account has been accessed by someone else.
Depending on where you live, you have some or all of the following rights over your personal data:
You can delete your account yourself, at any time: open the account menu in the header and choose Delete account. It asks for your password, tells you exactly what's about to go, and cancels any active subscription as part of the same step. It takes effect immediately and cannot be undone — your email, your saved wallet address, your progress and your quiz answers are removed from our systems.
For anything else on that list — or if you'd rather we did the deletion for you — email us at support@solanahelper.com from the address on your account. There's no charge, and we'll respond within one month.
If you're in California: we don't sell personal information for money, and as of 4 September 2026 we no longer share it for cross-context behavioral advertising either. The advertising reporting described in clause 3 did count as sharing under the CCPA as amended while it ran; it has been switched off for everyone, so there is nothing left to opt out of. We won't discriminate against you for exercising any right above.
Our service providers may process data outside your country, including in the United States. Where data leaves the UK or EEA, we rely on the safeguards those providers have in place — standard contractual clauses or an adequacy decision. You can ask us for details.
Solana Helper is for adults: you must be 18 or over to use it, and we don't knowingly collect data from anyone under 18. If you believe a child has given us data, tell us and we'll delete it.
If we change this policy we'll update the date at the top. If a change materially affects your rights — a new category of data, or a new recipient — we'll tell you by email or in the service before it takes effect.
Questions about this policy, or a request about your data: support@solanahelper.com.