Last updated: October 6, 2026

ATH Community Guidelines, Content Policy, and Cookie Notice

This page holds two documents. Part A is our Community Guidelines and Content Policy. Part B is our Cookie and Technology Notice. Both form part of the ATH Terms of Service. Capitalized terms not defined here have the meaning given in the Terms.

Quebec residents: the French version of this page is available at ath.trade/fr/not yet published. If you are reading the English version, it is because the French version was presented to you first and you chose English.

Part A. Community Guidelines and Content Policy

1. Who we are and what this policy covers

1.1 ATH is operated by ATH, a Florida, United States entity located at Miami, FL 33178 ("we," "us," "our"). You can reach us at [email protected] or through ath.trade.

1.2 This policy applies to everything you post or do on the community side of ATH: posts, comments, reactions, tips, profile information, usernames, and follows. It also applies to how you interact with rankings and leaderboards.

1.3 This policy does not cover the on-chain data we display (trades, prices, holders, wallet history). That data is public on the Solana network. We record it and show it. We do not write it and we cannot edit it.

2. Definitions

"Service" means the ATH website and its API.
"Account" means your profile on the Service, tied to a wallet address, whether you signed in with Google or Apple and received an embedded wallet through Privy or, before October 22, 2026, connected an external wallet.
"Content" means anything you write or upload that other people can see: posts, comments, your username, bio, photo, cover image, and the X and Instagram handles on your profile. Reactions, tips, views, and follows are actions, not Content (Section 8.5).
"Rankings" means any public list or score we compute, including Top profit, Performers, community leaderboards, "Traders to follow," follower counts, reaction counts, and view counts.
"Tip" means a transfer of SOL from one user to another, started from a post (including posts shown on a profile) and signed by the sender in the sender's own wallet.
"Token" means any digital asset on the Solana network that appears on the Service.

3. The basics

3.1 You must be at least 18 years old and at least the age of majority where you live (19 in British Columbia, New Brunswick, Newfoundland and Labrador, Nova Scotia, Northwest Territories, Nunavut, and Yukon). If we learn that an Account belongs to someone under that age, we terminate it and delete the account data we hold, subject to legal retention duties.

3.2 You may use more than one wallet, and each wallet has its own profile. What you may not do is use several wallets or profiles to pretend to be several different people, to react to or tip your own posts, or to get around a restriction (Section 5.10).

3.3 Everything you post is public by default. There are no private posts. Assume that anyone, including people who are not signed in, can read what you write.

3.4 Your wallet is yours. We never hold your funds or your keys. Nothing in this policy lets us move, freeze, or seize anything in your wallet. When we say we may "restrict" or "terminate" an Account, we mean access to the Service, never your on-chain assets.

3.5 Nothing on the Service is financial advice. Not our data, not the Rankings, and not other users' posts. Do your own research.

4. What you can post

We built the community for people who trade and study tokens on Solana. You are welcome to:

Share your trades, positions, and results, including losses.
Post analysis, charts, and opinions about tokens, wallets, and developers.
Ask questions and answer them.
Warn other people about tokens or wallets you think are risky, as long as you are honest about what you know and what you are guessing (see Section 5.13).
Promote a token you are involved with, if you say so (Section 5.9).
Disagree, strongly. Attack ideas, not people.

5. What you cannot post

Content that breaks any rule below may be removed, and your Account may be restricted or terminated (Section 11).

5.1 Fraud and scams

Do not use the Service to deceive anyone out of money or tokens. This includes fake giveaways, fake airdrops, "send X and receive 2X" schemes, fake customer support, wallet-drainer links, rug pulls, honeypots, and any post that promotes a token while hiding facts you know would matter to a buyer (for example, that you or the developer control most of the supply, or that the developer has abandoned the project).

5.2 Coordinated pumps and market manipulation

Do not organize, recruit for, or promote coordinated buying or selling meant to move a price so that insiders can exit on other people. Do not post false or misleading statements about a token, a developer, a wallet, or a listing in order to move a price. Do not post fake "insider" information. Wash trading, spoofing, and similar conduct are prohibited whether or not they are illegal where you live.

5.3 Impersonation

Do not pretend to be another person, project, developer, company, or ATH staff. Do not use a username, display name, photo, or bio that is likely to make people think you are someone you are not. Parody and fan accounts are allowed only if it is obvious from the profile that they are not the real thing. We never ask for your seed phrase, private key, or a "verification" transfer. Anyone who does is not us.

5.4 Doxxing and private information

Do not post other people's private information: home address, phone number, personal email, government ID, financial information, private messages, or the real-world identity behind a pseudonymous wallet or account, unless that person has already made it public themselves. Linking a wallet address to a person's legal name is doxxing if that person has not done it publicly. Wallet addresses themselves are public. Discussing what a public wallet does is fine.

5.5 Harassment, hate, and threats

Do not threaten, stalk, or harass anyone. Do not post content that attacks people based on race, ethnicity, national origin, religion, sex, gender identity, sexual orientation, disability, or serious illness. This includes hate propaganda and the promotion of genocide. Do not encourage self-harm. Losing money on a trade someone posted about does not entitle you to harass them.

5.6 Spam and automation

Do not post repetitive, off-topic, or bulk content. Do not post the same message across many tokens or threads. Do not use bots, scripts, or paid services to post, comment, react, follow, view, or tip. Do not scrape the Service. Referral links are allowed in your profile and in a post when they are relevant. Posting them everywhere is spam.

If you invite people by email, text, or direct message, you are responsible for complying with anti-spam law where they live (in Canada, CASL). Invite only people you know, one message per person, with your name in it. Do not send bulk or automated invitations.

5.7 Sexual content

Do not post sexually explicit content or nudity. Do not post intimate images of anyone without their consent, including images created or altered by AI. Do not post any sexual content involving minors, real or simulated. We remove it, terminate the Account, preserve the related records as the law requires, and report it to the National Center for Missing & Exploited Children (as U.S. law requires) and to the Canadian Centre for Child Protection through Cybertip.ca (where Canadian law applies), and to police where required.

5.8 Illegal content and activity

Do not post content that is illegal in the United States or Canada or that helps others break the law, including money laundering, sanctions evasion, sale of illegal goods, terrorism, or violent extremism.

Do not use the Service if you are in a jurisdiction that the Terms list as restricted (including any country or region under U.S. OFAC or Canadian sanctions), or if you are a sanctioned person as defined in the Terms (which includes persons and entities listed under U.S. OFAC programs and under Canada's Special Economic Measures Act, Justice for Victims of Corrupt Foreign Officials Act, United Nations Act regulations, and Criminal Code listings).

Do not use the Service to offer, sell, or solicit investment in securities, presales, investment pools, or yield products, or to act as a broker or investment adviser, without the registrations or exemptions the law requires.

5.9 Undisclosed paid promotion

If you were paid, given tokens, promised anything, or are part of a token's team when you post about it, say so in the post itself, in plain words, at the start (for example, "Paid promotion," "#ad," or "I'm on the team"). This applies to posts, comments, and profile bios. Your positions are already public on your profile; a disclosure is still required when you have a material connection beyond simply holding the token.

Hiding a paid relationship may also break the law: in the United States under Section 5 of the FTC Act and the FTC's Endorsement Guides, and in Canada under the Competition Act (sections 52 and 74.01) and, in Quebec, the Consumer Protection Act. If the token could be a security, U.S. law (Securities Act section 17(b)) may also require you to state how much you were paid and by whom.

5.10 Manipulation of Rankings, reactions, and views

Do not inflate or deflate any Ranking. Prohibited examples: reacting to your own posts from other wallets or Accounts; tipping your own posts from another wallet; trading reactions or follows with other users ("engagement pods"); buying reactions, follows, or views; refreshing pages or running scripts to add views; wash trading or trading between wallets you control to fake profit; splitting a position across wallets to appear on a leaderboard; and any other scheme whose purpose is to make a number say something that is not true.

5.11 Malware, phishing, and security

Do not post links to malware, wallet drainers, phishing sites, or fake versions of ATH, Privy, or any wallet or exchange. Do not post your own or anyone else's seed phrase or private key. Do not probe, attack, or overload the Service.

5.12 Other people's rights

Do not post content that infringes someone else's copyright, trademark, or other rights. Sections 13 to 15 explain how rights holders can contact us and what happens next.

5.13 False statements about people

Do not post statements of fact about an identifiable person or company that you know, or should know, are false and that damage their reputation. Opinion that is clearly presented as opinion is allowed. When you warn about a token or wallet (Section 4), separate what you know from what you suspect.

5.4 Session storage (cleared when you close the tab)

Key	What it holds	Why
`ath_destino`	The page you were trying to open when you were asked to sign in	Takes you there after you sign in.
`ath_entrada`	The time you last signed in from the home page	Detects a browser that blocks our session cookie, so we can tell you instead of reloading forever.
`ath_puente`	The time we last refreshed your session cookie from a saved session	Prevents a reload loop if the cookie cannot be set.
`ath_puerta`	The time the application last noticed it was open without a session	Prevents a reload loop while it sends you back to the home page.

6. Rankings, leaderboards, and metrics

6.1 Rankings are computed by our systems from public on-chain data and from activity on the Service. They are estimates. They can be wrong, late, or incomplete, and they are not a recommendation to follow or copy anyone.

6.2 We may, at any time and without notice, exclude a wallet, Account, post, or token from any Ranking; recompute a Ranking; change how a Ranking is calculated; or remove a Ranking entirely.

6.3 If we believe a Ranking, reaction count, view count, or follower count has been manipulated (Section 5.10), we may reset it, exclude the Accounts involved, and cancel any benefit obtained through the manipulation, including referral rewards and any Ranking placement.

6.4 Appearing on a Ranking gives you no right to stay on it and no right to compensation.

6.5 Rankings, the profile value chart, and lists such as "Traders to follow" analyze the trading activity of wallets. A wallet is shown next to a username only because its owner connected it to an Account; connecting a wallet is how you turn that link on. You can turn it off at any time by logging out from the account menu (for External Wallets) or emailing support to unlink a Wallet from your profile or by asking us to delete your Account (Section 10.5). The wallet may still appear by address alone, as public on-chain data. Quebec residents: this is the profiling function described in section 8.1 of the Act respecting the protection of personal information in the private sector.

7. Usernames and profiles

7.1 Your username is a revocable license, not property. We may reclaim, change, or disable a username that impersonates someone, infringes a trademark, contains a slur, is misleading (for example, includes "official," "support," or "admin"), or has had no sign-in for 12 months.

7.2 Your profile fields (name, bio, photo, cover image, X and Instagram handles) are Content and follow every rule in Section 5.

7.3 We show your public wallet address, positions, swaps, posts, reactions, followers, and follows on your profile. That is what the Service is for. If you do not want a wallet's activity shown next to a username, do not connect that wallet (see Section 6.5).

8. Your content license to us

8.1 You own your Content. We do not claim ownership of anything you post.

8.2 By posting Content, you grant ATH a worldwide, non-exclusive, royalty-free, transferable license to host, store, cache, reproduce, display, distribute, translate, reformat, excerpt, and adapt it, in any medium now known or later developed. We may sublicense those rights to the service providers that run the Service. The license covers operating, improving, securing, and promoting the Service, subject to Section 8.3.

8.3 This license lets us do ordinary things: show your post in the feed and on token pages, generate previews and thumbnails, include your post in a notification, keep backups, and quote a public post, with attribution to your username, on our own social accounts. We will not use your name, photo, or likeness in advertising or marketing outside the Service without asking you first and getting your separate consent.

8.4 The license for a piece of Content ends when it is deleted: when you delete it from the interface (where the interface offers that), when we delete it at your request (Section 10.5), or when your Account is deleted at your request. Exceptions: (a) copies may remain in backups and logs for up to 30 days; (b) Content that other users have already reproduced (for example, by quoting it) may remain visible in their Content; (c) we may keep copies as needed to comply with law, resolve disputes, and enforce our policies; and (d) data derived from your Content that has been de-identified or anonymized in accordance with applicable law (in Quebec, according to the standards set by regulation), and which we will not try to re-identify, is not deleted.

8.5 Tips, reactions, views, and follows are records of actions, not works of authorship. We keep records of them as described in the Privacy Policy.

8.6 You confirm that you have the rights needed to grant this license and that your Content does not violate this policy or anyone's rights.

8.7 On-chain data is not your Content. Trades, transfers, and balances are public records on the Solana network. We keep our archive of that data indefinitely.

8.8 To the extent permitted by law, you waive, and agree not to assert against ATH and its sublicensees, any moral rights you may have in your Content, including rights of attribution and integrity, for the uses allowed by this Section.

9. Tips between users

9.1 A Tip is a transfer of SOL from your wallet to another user's wallet. You start it from the Service, you review the amount, and you sign it: in your external wallet, or in your embedded wallet, whose key shares are held by you and Privy and are never available to us. We never have authority to sign, and we never accept, hold, or transmit funds. We only broadcast a transaction you have already signed to the Solana network, through our server or through an RPC node your browser talks to directly (Part B, Section 6.4).

9.2 We charge no fee on Tips. You pay the Solana network fee and any priority fee.

9.3 Tips are final. A Tip is an on-chain transaction. It cannot be reversed, refunded, or charged back, by you or by us. Check the recipient before you sign.

9.4 A Tip is a gift. It is not payment for goods or services, it does not buy a place in any Ranking, and it creates no obligation on the recipient or on us. You cannot tip your own posts.

9.5 Tips are public by nature because they are on the blockchain. We show them on the post they relate to and show the total you have received on your profile.

9.6 Do not use Tips to launder money, to pay for manipulation of the Service, to pay for anything illegal, or to solicit payments through impersonation. We never ask for Tips.

9.7 You are responsible for any tax consequences of sending or receiving Tips.

9.8 We may disable tipping for an Account, a post, or the whole Service at any time. We may screen wallet addresses against sanctions lists and may refuse to relay any transaction, including a Tip, that involves an address on such a list or that we reasonably believe is unlawful. Refusing to relay is not freezing or seizing: you keep full control of your wallet and can use any other tool.

10. Reporting Content

10.1 To report Content that breaks this policy, email [email protected] with a link to the Content, the username or wallet involved, and a short description of the problem.

10.2 For copyright claims, use Section 13 (United States) or Section 14 (Canada). For trademark, defamation, privacy, and other claims, use Section 15.

10.3 Do not file knowingly false, repetitive, or abusive reports. Using reports to harass a person you dislike is itself a violation.

10.4 If you believe someone is in immediate danger, contact local emergency services first.

10.5 Deleting your own Content or Account. To delete a post, a comment, or your whole Account, email [email protected]. Include the wallet address on the Account and, for a post or comment, a link to it. We may ask you to confirm the request from that wallet or from the email address on the Account before we act. We act on deletion requests within 30 days, except for records the law requires us to keep (Sections 5.7 and 14.4, and the retention exceptions in the Privacy Policy). The Privacy Policy lists the other ways to send us a request.

11. Moderation: what we may do

11.1 We review Content through user reports, automated tools, and our own checks. We do not review everything before it is posted. We have no obligation to monitor Content. Each user is responsible for what they post; we do not endorse it. Moderation decisions are made in good faith and at our discretion.

11.2 If Content or conduct violates this policy or the Terms, or creates risk for users, third parties, or us, we may, without prior notice:

remove, hide, or label the Content;
hide the Content from the feed, from token pages, or from search;
limit features on an Account (posting, commenting, reacting, tipping, following, the API);
remove an Account or wallet from Rankings and reset counts;
cancel referral rewards obtained by breaking the rules;
refuse to relay a transaction that involves a sanctioned address or that we reasonably believe is unlawful (Section 9.8);
suspend or terminate an Account;
block access from certain networks or devices;
preserve and disclose Content and account records to law enforcement or in response to legal process, as described in the Privacy Policy.

11.3 We take the seriousness of the violation, prior history, and harm into account. Some violations (Sections 5.1, 5.7, and 5.11) lead to immediate termination.

11.4 Termination of an Account does not affect your wallet, your keys, or your on-chain history. It ends your access to the Service.

11.5 When practical, we will tell you which rule was applied. We may not do so when notifying you would compromise an investigation, security, or the safety of others, or when the law prevents it. If a decision to remove Content or restrict an Account was made solely by automated means, we will tell you so when we notify you. On request, we will explain the information and the main factors used, correct any personal information that was wrong, and let you submit observations to a person on our team who can review the decision (Section 12).

11.6 Removed Content may stay in backups and logs for up to 30 days, and longer where the law requires or where we need it for a dispute.

12. Appeals

12.1 If we removed your Content or restricted your Account and you think we got it wrong, email [email protected] within 30 days of our action. Put "Appeal" in the subject line. Include your username, the wallet address on the Account, what was removed or restricted, and why you believe the decision was wrong.

12.2 A person will review the appeal. We aim to answer within 7 days. Our decision ends our internal review process. It does not limit any right you have under applicable law, including consumer protection law in Canada, to bring a claim before a court or a regulator.

12.3 You cannot appeal on behalf of someone else. Repeated appeals of the same decision without new information will not be answered.

12.4 Copyright removals normally use the counter-notice in Section 13; see Section 13.5 if you are outside the United States.

13. Copyright: DMCA notice and counter-notice (United States)

13.1 We respect copyright and expect users to do the same. We respond to notices that comply with the Digital Millennium Copyright Act, 17 U.S.C. § 512.

13.2 Designated agent. Send copyright notices to our designated agent:

Name: ATH Copyright Agent
Address: Miami, FL 33178
Email: [email protected]

13.3 Filing a notice. For a notice to be effective, it must include:

Your physical or electronic signature, or that of a person authorized to act for the copyright owner.
Identification of the copyrighted work you claim is infringed. If several works, a representative list.
Identification of the material you claim is infringing and enough information for us to find it (a link to the post, comment, or profile image).
Your name, mailing address, telephone number, and email address.
A statement that you have a good-faith belief that the use is not authorized by the copyright owner, its agent, or the law.
A statement that the information in the notice is accurate and, under penalty of perjury, that you are the copyright owner or are authorized to act for the owner.

13.4 What we do. When we receive a complete notice, we promptly remove or disable access to the material, and we make a reasonable effort to notify the user who posted it and give them a copy of the notice.

13.5 Counter-notice. If your Content was removed and you believe the removal was a mistake or misidentification, you may send a counter-notice to the designated agent. It must include:

Your physical or electronic signature.
Identification of the material that was removed and where it appeared before removal.
A statement, under penalty of perjury, that you have a good-faith belief that the material was removed as a result of mistake or misidentification.
Your name, address, and telephone number.
A statement that you consent to the jurisdiction of the federal district court for the district where your address is located. If you live outside the United States, consent to any district in which ATH may be found.
A statement that you will accept service of process from the person who filed the original notice or that person's agent.

If you are outside the United States and do not wish to consent to U.S. jurisdiction, you may instead ask us to review the removal under Section 12. We may restore the material at our discretion, but we are not required to.

13.6 After a counter-notice. We forward the counter-notice to the person who filed the original notice. Unless that person tells us within 10 business days that they have filed a court action to restrain the alleged infringement, we will restore the material no earlier than 10 and no later than 14 business days after we received the counter-notice, unless the material independently violates Section 5 or the Terms.

13.7 Misrepresentations. Under 17 U.S.C. § 512(f), anyone who knowingly makes a material misrepresentation in a notice or counter-notice may be liable for damages, including costs and attorneys' fees. Consider talking to a lawyer before filing either one.

13.8 Repeat infringers. We terminate the Accounts of repeat infringers. As a rule, 3 valid notices without a successful counter-notice within 12 months lead to termination. We may terminate sooner in serious cases.

13.9 Notices sent to any address other than the designated agent's may not receive a timely response.

13.10 We accommodate and do not interfere with standard technical measures used by copyright owners to identify or protect their works, as that term is defined in 17 U.S.C. § 512(i).

14. Copyright: notice and notice (Canada)

14.1 For claims under the Copyright Act (Canada), we follow the "notice and notice" regime in sections 41.25 and 41.26 of that Act. It works differently from the DMCA. We forward the notice to the user. We do not remove content solely because a notice was sent.

14.2 What a notice must contain. Send it in writing to [email protected] or to the address in Section 13.2. It must:

State your name and address, and any other details that let you be contacted.
Identify the work or other subject-matter you claim is infringed.
State your interest or right in the copyright of that work.
Specify the location data for the electronic location where the claimed infringement occurred (a link to the post or profile).
Specify the infringement you claim.
Specify the date and time of the claimed infringement.

14.3 What a notice must not contain. Under section 41.25(3), a notice must not contain an offer to settle, a request or demand for payment or for personal information, or a reference or link to any of those. A notice that contains them is not compliant and we will not forward it.

14.4 What we do. When we receive a compliant notice, we (a) forward it electronically, as soon as feasible, to the user who controls the location, and confirm the forwarding to you or tell you why we could not forward it; and (b) keep records that allow the user to be identified for six months from the day we received the notice, or for one year if you start court proceedings about the claimed infringement and tell us before the six months end. We keep these records for that period even if you delete your Account in the meantime; the Privacy Policy lists this as a legal retention exception.

14.5 We do not charge a fee for forwarding a notice. We do not disclose the user's identity to you under this process. That requires a court order.

14.6 Our own policies still apply. If the content also violates Section 5, or if the DMCA process in Section 13 is used, we may remove it on that basis.

15. Trademarks and other rights

15.1 If you believe Content infringes a trademark, violates your right of publicity or privacy, or is defamatory, email [email protected] with a link to the Content, an explanation of the right you claim (including registration numbers where relevant), and your contact details. We review these claims under this policy and applicable law. There is no automatic takedown. We review promptly and may remove Content that appears unlawful, including under Canadian defamation law, after we receive notice.

15.2 Court orders and requests from law enforcement should be sent to [email protected].

15.3 If you live in Quebec, you may ask us to stop disseminating personal information about you, or to de-index a link to it, where its dissemination contravenes the law or a court order, or causes you serious injury to your reputation or privacy that clearly outweighs the public's interest in it (section 28.1 of the Act respecting the protection of personal information in the private sector). Send your request to our Privacy Officer at [email protected] at [email protected]. We answer within 30 days.

16. The former AI assistant and Telegram bot

16.1 We closed our AI assistant ("Peak") and our Telegram alerts bot (@pumppumpz1bot) in October 2026. Neither is part of the Service any more. Anyone who presents a chatbot, a Telegram bot, or a Telegram account as ATH is impersonating us (Section 5). What we keep from the time they ran, and how to ask us to delete it, is explained in the Privacy Policy.

17. Relationship to the Terms and the Privacy Policy

This policy is part of the Terms of Service. If it conflicts with the Terms, the Terms control. How we handle the data you post is described in the Privacy Policy.

18. Changes

We may update this policy. We will change the "Last updated" date. If a change is material, we will give notice as described in Section 4.1 of the Terms. Continued use after the effective date means you accept the change.

19. Contact

ATH Miami, FL 33178 [email protected] ath.trade

Privacy requests: our Privacy Officer at [email protected], Privacy Officer, [email protected], Miami, FL 33178. This person is our person in charge of the protection of personal information under Quebec law and our privacy officer under PIPEDA.

Part B. Cookie and Technology Notice

Last updated: October 6, 2026

1. Summary

Our own servers set one strictly necessary cookie, ath_s, which keeps you signed in for up to 24 hours. Section 4.1 describes it.
We use no advertising cookies, no tracking pixels, no third-party ad networks, and no cross-site tracking.
We keep your preferences, and a copy of your session, in your browser's local storage. Section 5 lists every key.
Our site is served through Cloudflare, which may set strictly necessary security cookies.
We use Cloudflare Web Analytics, which does not use cookies or local storage and does not fingerprint you.
Cloudflare Turnstile may check that you are human when you sign in with Google or Apple (it runs inside Privy's sign-in flow).
Privy (sign-in and embedded wallet) sets its own cookies and storage under its own policy.
Your browser talks directly to some other servers (Solana RPC nodes, SolanaTracker, a QR image service, fonts and scripts). They see your IP address and, where the request is about your wallet, your public wallet address. Section 6.4 lists them.
You can clear all of this from your browser at any time. Section 9 explains how.

2. Definitions

"Cookie" means a small text file a website stores in your browser and that your browser sends back with each request to that site.
"Local storage" (localStorage) means a store in your browser where a website can keep values under named keys. Unlike cookies, those values are not sent to the server automatically. A page's script reads them and decides what to send.
"Strictly necessary" means a cookie or storage item without which the Service, or a security feature of it, does not work.
"Third-party" means set by a company other than ATH, from that company's own domain.

3. What we do not do

We do not set advertising or marketing cookies.
We do not use Google Analytics, Meta Pixel, or any similar tracker.
We do not sell or share your personal information for cross-context behavioral advertising.
We do not fingerprint your device.
We do not use cookies to follow you across other websites.
We do not use IndexedDB. We use sessionStorage only for three short-lived sign-in helpers listed in Section 5.4; nothing in it identifies you.

Because we set no non-essential cookies, we do not show a cookie consent banner. If we ever add a technology that needs your consent, we will ask first and update this notice.

4. Cookies

4.1 Cookies set by our servers

One, and it is strictly necessary:

Cookie	What it holds	Why	Expires
`ath_s`	The same signed session token as `solshark_jwt` (Section 5.1). It is not your private key and cannot move funds.	Tells our server that you are signed in, so it can show you the application instead of the public home page. Set when you sign in; removed when you log out. It is marked HttpOnly (page scripts cannot read it), Secure (sent only over HTTPS) and SameSite=Lax (not sent on requests started by other websites).	24 hours

Our API does not read this cookie: requests to it carry the session token in a header that only our own pages send.

4.2 Cookies set by Cloudflare on our domain

ath.trade is served through Cloudflare, which protects the site from attacks and bots. Cloudflare may set strictly necessary cookies on our domain, such as __cf_bm (bot management, expires after about 30 minutes) and cf_clearance (remembers that you passed a security challenge). They contain no profile of you and are not used for advertising. Cloudflare describes them in its own cookie policy.

5. Local storage: every key we use

The tables below list every key the ATH website writes to your browser's local storage, what it holds, and why. Values stay in your browser until you clear them (Section 9), unless the table says otherwise. Only the ATH website reads these keys. A value leaves your browser only where the table says so.

5.1 Session and wallet

Key	What it holds	Why	Leaves your browser?
`solshark_jwt`	A signed session token issued by our server after you sign in	Keeps you signed in so you do not have to sign a wallet message on every page load. It is not your private key and cannot move funds. Our server stops accepting it 24 hours after it was issued; after that the site asks you to sign in again. Removed when you log out; otherwise the value stays in your browser until you sign in again, when it is replaced.	Yes, sent to our server with your requests
`solshark_jwt_pk`	The public wallet address the session token was issued for	Lets the site notice that you switched wallets and drop the old session. Removed when you log out.	No
`wallet_pk`	The public address of the wallet you connected	Reconnects your wallet on the next visit and loads your positions and profile. Removed when you log out.	Yes, with requests about your wallet
`wallet_provider`	The name of the wallet you used (for example, the embedded wallet)	Knows which wallet to reconnect. Removed when you log out.	No

5.1a Referral

Key	What it holds	Why	Leaves your browser?
`ath_ref`	The username from an invitation link (`ath.trade/r/<username>`) you arrived with	Remembers who invited you so the referral can be credited when we enable referral rewards. Stored once, on your first visit through such a link.	Not yet; see the Fees & Referrals page for how referrals work when enabled.

5.2 Preferences

Key	What it holds	Why
`ss_lang`	`en` or `es`	Interface language
`ss_menu_plegado`	`1` or `0`	Whether the side menu is collapsed
`ss_blur`	`1` or `0`	Whether balances and amounts are blurred on screen
`cur`	`USD` or `SOL`	Currency used to display values
`feed_hidezero`	`1` or `0`	Feed filter (the eye toggle): hide tokens with no pool liquidity and tokens that have dropped to zero
`feed_minliq`	A number	Feed filter: minimum liquidity
`feed_maxdev`	A number	Feed filter: maximum number of tokens the developer launched in the last 24 hours (`0` = no limit)
`chartSrc`	A chart source name	Which chart source is shown on the token page
`cChartType`	A chart type name	Chart type on the token page (for example, candles or line)
`solshark_swap_mode`	Your swap mode setting	Remembers your swap settings between visits
`solshark_slip_bps`	Your slippage tolerance, in basis points	Remembers your swap settings between visits

5.3 Recent items and shortcuts

Key	What it holds	Why
`recentQ`	Your last 8 searches	The "Recently searched" list in the search menu. It has its own "Clear" link.
`recentV`	The last 10 tokens you opened	The "Recently viewed" list in the search menu. It has its own "Clear" link.
`ss_com_recientes`	The last 5 community items you opened	The side rail of the community view, so you can find your way back
`ss_emoji_recientes`	Emojis you used recently	Puts them first in the emoji picker
`rx:` followed by a token address	Which reactions you gave to that token	Shows your reactions as selected when you come back. One key per token you reacted to.

5.4 View counting

Key	What it holds	Why	Leaves your browser?
`ss_cid`	A random string your browser generates the first time the community feed loads, before you interact with the page	Counts a view of a post once per browser per day. It is random, it is not derived from your device, and it is not used for advertising or for tracking you on other sites. It is sent with the list of posts that were on screen; when you are signed in, we attribute the view to your wallet address and ignore this value. It is not rotated: it stays in your browser until you delete it. To turn it off, delete the `ss_cid` key (Section 9.2) or block local storage; the site keeps working and views from your browser are simply not counted. On our server, view records (post, viewer, day) are kept for for as long as the post exists.	Yes, sent to our server with view counts

5.5 Notes on the keys

No key holds your private key, seed phrase, card number, email, or password. Your embedded wallet's key material is managed by Privy (Section 6.1), never by our scripts.
Key names beginning with solshark_ and ss_ carry those prefixes for historical reasons. If we rename them, we will update this table.
The session token is a bearer credential for your account on the Service only. It cannot sign transactions.

6. Third-party services that may set cookies or storage, and servers your browser contacts directly

6.1 Privy (sign in with Google or Apple; embedded wallet)

When you sign in with Google or Apple, the Privy module runs on the page and in a frame from auth.privy.io. Privy stores its own values in local storage under keys that begin with privy: (its session and refresh tokens, connection state, and similar) and may set cookies on its own domain. Privy also handles your embedded wallet's key shares inside secure enclaves; those never touch our storage keys. The Privy module bundles wallet-connection libraries (WalletConnect, Coinbase Wallet) that we have not enabled; they open no connections and write no keys unless enabled. Google and Apple set their own cookies on their sign-in pages. See Privy's privacy policy at privy.io.

6.2 Stripe

Our own code loads no Stripe scripts. We no longer sell plans, so the Service does not send you to a Stripe checkout page. The Privy module bundles a loader for Stripe's fiat on-ramp, which we have not enabled; it does not run.

6.3 Wallet extensions

Since October 22, 2026 the Service no longer connects to wallet extensions. If one is installed in your browser, it sets no cookies for us, and what it stores is governed by its provider.

6.4 Servers your browser contacts directly

Besides our own servers, our pages contact the servers below directly from your browser. Each of them sees your IP address and the request; where the request is about your wallet, it also sees your public wallet address. None of them is used by us to track you. The list is drawn from our content security policy, which names every server our pages are allowed to contact.

Fonts: Google Fonts (fonts.googleapis.com, fonts.gstatic.com). Google states that the Fonts API does not set cookies.
Market data and token logos: SolanaTracker (data.solanatracker.io for data, image.solanatracker.io for token logos).
Solana RPC nodes: to read balances and to send signed transactions, your browser may talk to Solana RPC nodes directly. By default this is api.mainnet-beta.solana.com, operated by the Solana Foundation; our pages are also allowed to contact Helius nodes (helius-rpc.com) and, for the embedded wallet, Privy's RPC (rpc.privy.systems). These servers see the wallet address queried and any signed transaction you send.
Deposit QR code: when you open the Deposit panel, your browser loads a QR image of your wallet address from api.qrserver.com (goQR.me). That server sees your IP address and your public wallet address in the request. We send nothing else.
Cloudflare: static.cloudflareinsights.com (analytics, Section 7) and challenges.cloudflare.com (Turnstile, Section 8).
Privy: auth.privy.io (Section 6.1).

6.5 Telegram bot

We closed our Telegram bot in October 2026. It never set cookies on our domain.

6.6 Where these providers process data

These providers process data outside Canada, mainly in the United States, where it is subject to the laws of that country and may be accessed by its authorities. The Privacy Policy describes the safeguards we use.

7. Cloudflare Web Analytics

We use Cloudflare Web Analytics to see how many people visit, which pages they open, which browsers and countries they come from, and how fast pages load. Cloudflare injects the beacon script into our pages from static.cloudflareinsights.com; our own code does not include it. It does not use cookies or local storage, does not fingerprint the browser, and does not track you across other sites. Cloudflare processes your IP address in the United States to derive your country; the data we see is aggregated, and we do not see individual visitors. Cloudflare's privacy policy describes how it handles the underlying data.

8. Cloudflare Turnstile

Turnstile runs in a frame from challenges.cloudflare.com inside Privy's sign-in flow, when you sign in with Google or Apple, to tell a human from a bot. It may set cookies or storage on Cloudflare's domain, and Cloudflare may set cf_clearance on ours (Section 4.2). Turnstile shows no ads and builds no profile of you. See Cloudflare's privacy policy.

9. How to clear or block

9.1 In the app

Log out. This removes solshark_jwt, solshark_jwt_pk, wallet_pk, and wallet_provider.
In the search menu, "Clear" next to "Recently searched" and "Recently viewed" removes recentQ and recentV.
Language, menu, blur, currency, filters, chart, and swap settings are changed from the interface itself. The key updates when you change the setting.

9.2 In your browser

Every major browser lets you delete a single site's data:

Chrome and Edge: Settings, then Privacy and security, then the site data or cookies section. Search for ath.trade and delete.
Safari on Mac: Safari menu, Settings, Privacy, Manage Website Data. Search for ath.trade and remove.
Safari on iPhone and iPad: Settings, Safari, Advanced, Website Data.
Firefox: Settings, Privacy & Security, Cookies and Site Data, Manage Data.
Developer tools: in the Application (Chrome, Edge) or Storage (Firefox, Safari) panel, open Local Storage for ath.trade to delete individual keys (for example, ss_cid).

9.3 What happens if you clear or block

Clearing local storage signs you out and resets preferences to their defaults. Your wallet, keys, account, posts, and positions are not affected. They live on the network and on our servers, not in your browser.
Blocking local storage entirely: the site still loads, but you cannot stay signed in, preferences reset on every visit, and views from your browser are not counted.
Blocking third-party cookies or frames may break sign-in with Google or Apple (Privy) and Turnstile checks.
Blocking static.cloudflareinsights.com (for example, with an ad blocker) stops analytics and breaks nothing.

10. Do Not Track, Global Privacy Control, and withdrawing consent

We do not track you across sites, so a "Do Not Track" header changes nothing. We honor Global Privacy Control (GPC) signals as an opt-out of the sale or sharing of personal information under California law and the laws of other states that recognize it. Since we do not sell or share personal information for advertising, a GPC signal also changes nothing about how the Service works.

Residents of Canada may withdraw consent to any processing that is not necessary to run the Service by contacting our privacy officer (Section 12). We will explain the consequences of the withdrawal, if any.

11. Changes

We update this notice when we add or remove a key, a cookie, or a service. Check the "Last updated" date. If a change is material, we will give notice as described in Section 4.1 of the Terms. Continued use after the effective date means you accept the change.

12. Contact

[email protected]