Privacy

• Cloudflare sits in front of every site we run. It sees your IP address, the page you ask for and what your browser sends with the request, as any web host does.
• Our server logs record addresses and pages, to keep the sites running and secure. They are masked and kept for 7 days.
• Your country, from your connection. Cloudflare tells us the country, and the network, your connection comes from. We use it to choose which legal text and prices to show you, and on the pricing pages to spot VPN and data-centre connections, because a price that depends on where you live means nothing if we cannot tell. We do not store it, and it decides nothing that matters: where you live is proved by verification.
• No advertising trackers and no behavioural analytics, on any of our sites.

• Your email address and the page you signed up from.
• To tell you when the product launches. That is the whole purpose.
• The list is copied to our email provider, Resend, to send that message.
• You leave with one click in any email.

• Who you are to us: your email address, and whether you confirmed it; the name you choose to be shown by, and your username; the date of birth you give when you register, to check you are 16 or over; the country you say you live in, and your province or state where tax depends on it; your referral code, and who referred you.
• How you sign in: a password, of which we keep only a one-way hash; passkeys, of which we keep only the public part; an authenticator app's secret, which we need to check its codes, and recovery codes, of which we keep only one-way hashes; and any crypto address you sign in with, and its family (for example EVM or Solana).
• Your sessions. A record of each browser you are signed in on, with its IP address and browser description. You see these on your security page, and support may use them to help you.
• Security events. Sign-ins, refused sign-ins and changes to your account, with the IP address. Shown on your security page.
• Apps you sign in to with your account. When you sign in to one of our apps with your Atheron account, that app receives your account id and the details you agree to share. We record that you agreed.
• Suspension, if it happens: when, and why, so you can read it and appeal.
• Your file in our team portal. Your account, your orders and your linked social accounts appear together, with any moderation history.

Why: to give you an account and keep it secure.

• Your reservation: the packages, the quantities, when, and any creator's code you gave.
• The early-access list. Reserving puts your email address on our early-access list, so we can tell you when the 48-hour early-access sale starts. The list is copied to Resend, which sends that email. If your account has no email address (a crypto sign-in), we ask for one when you reserve and send a link to confirm it before it is used. We use this list only to tell you about the sale you reserved for, and you come off it, at Resend too, when you release your reservation or when early access ends.

• What you bought: packages, quantities, prices and discounts; any creator code you used; your price band and verification level; each tax line (the tax, its rate, what it was charged on, the amount, and our registration number); the total, how you paid and each step of the order.
• Where you were taxed: your country and region, and whether that came from your proof of address or your billing address.
• Your receipt and tax invoice. They carry the name on your identity document if you verified, otherwise the name you chose or your username; the email address for the order; where you live (country and region); and the lines above.
• The emails we send you about each step, and whether they were sent.
• If you used a creator's code, we record which creator it was. They earn a commission on that order, and after launch on up to 12 of your subscription payments. The creator is never told who you are: they see an amount and a date, never a name. Your first coded purchase also earns you community points, if you have linked a community account.
• If you bought through our sales team, we keep the quote you accepted.

Why: to sell you what you ordered, to supply it, and to keep the tax records the law requires.

• Street, city, postal code, region and country.
• We ask for it where tax depends on where you live and nothing you have proved tells us your province, state or region.
• It is also our evidence, for the tax authorities, of where we made the sale.

• Stripe is the seller of a card payment. It sells you the payment through Link, LLC, a Stripe company, as its merchant of record, on its own checkout page. Your name, email, billing address and card or Link details go to Stripe, never to us. Stripe uses them as a controller of its own, under its own privacy policy: to take the payment, work out and collect the tax, run 3D Secure with your bank, screen for fraud, send its receipt, and handle refunds and disputes.
• What Stripe tells us, and we keep: the card's brand, its last four digits and the country it was issued in, whether it was Apple Pay or Google Pay, the amount, the tax Stripe charged and the place it charged it for, the currency you paid in, and Stripe's references for the payment.
• What we give Stripe: your email address, so its page and receipt reach you, our order reference, and what you are buying at what price.
• Why: to know your order is paid and give you access, to keep our records of the sale, and to answer you about it.
• Refunds and disputes of a card payment are Stripe's, as the seller, through Stripe to the card or account that paid.

• What we keep: the address we gave you to pay to, and the memo or tag where the network uses one; the asset, network and amount; the transaction id and its confirmations; the amount in USDC after conversion; and the addresses the payment came from, where the network or Kraken's deposit record shows them.
• A crypto payment is public. Anybody can see the transaction, the sending address and the amount on its network. By linking the transaction to your order, we know that the sending address paid for your order.
• Our payment engine keeps a ledger that cannot be edited, so that every movement of money can be proved later. Clause 9 says what that means for deletion.
• To show you how many confirmations your payment has, our payment engine asks a public network data service about your transaction id (clause 6).

• What you give us: the name on your personal bank account, which must match the name on your identity document; the email address your bank sends e-Transfers to; a Canadian mobile number; and your acceptance of the refund terms shown to you.
• Why: a person on our Finance team enters your name, email and mobile at our bank to send you an Interac money request. The name check is how we make sure the money comes from you and not from somebody else's account.
• The payment notice. When you pay, Interac emails a notice to our payments mailbox, hosted by Microsoft. Our system reads it and records the payer's name, the amount, our reference and Interac's reference; the subject line, with any email address in it cut down to its domain; and whether the notice really came from Interac. It never keeps the body of the message.
• Bank statements. Finance uploads our bank's statements to confirm the money arrived. Each line holds a date, an amount and the bank's own description, which may include the payer's name.
• A payment that does not match an order is held for a person to look at.

• A refund request: why you asked, when, what for, and what we decided.
• A card refund is made by Stripe, the seller of that payment, to the card or account that paid. Stripe tells us it happened, and how much.
• A crypto refund is paid in USDC to an address you give us, with a memo or tag where the network needs one. Our Finance team adds that address to our withdrawal address book at Kraken, labelled with a random reference, and it is sent from there.
• An e-Transfer refund is sent by e-Transfer to the email address for your e-Transfer order.
• “Withdraw from contract here.” If you use it, we keep the name and email you give, which units you withdrew, and the exact time you pressed it. That time decides whether you were in time. We email you an acknowledgement.

• What we keep: each account's id on its platform, its handle, and the proof that it is yours. For Telegram, we may also keep an invite link made for you alone.
• Why: to give you your roles and perks in our Discord and Telegram; to count people who join through your links, and your points; to show you on the community board, which you can leave; and to apply our community rules.
• Our bots keep moderation records, community points and what they need to protect our spaces from raids, as our community rules describe.

Creators are paid, and some are paid as businesses, so we hold more about them than about anyone else.

• Your application: your page name, the name you are shown by, and a picture from one of your accounts; the social accounts you connect; the countries you say your audience is in; the creator who recruited you, if you name one; your acceptance of the code of conduct; and our decision and the reason for it.
• Proving your accounts. You prove each account by signing in with X, Twitch, Kick, YouTube or Bluesky, and we ask each platform only for read-only access. From the sign-in we receive the account's id, handle, name, picture and creation date. We keep the sign-in tokens, encrypted with a key our database does not hold, so we can read the account again later. If you disconnect an account, its tokens and its readings are deleted, and we ask the platform to revoke our access.
• Readings of your public accounts. We read each proven account's public numbers on a schedule: every 6 hours while your application is open, daily once you are approved, and weekly if you are suspended. A reading holds your followers, the account's age, recent posts and the likes, replies, views or comments on them. It can raise a flag, such as a young account, low engagement or a sudden jump in followers. We use the readings to decide your application and to keep the programme honest (clause 10).
• Your level: your coded sales and the community you brought, over the last 12 months.
• How you are paid. Personally: you verify to Bedrock, and we pay you in the name on your identity document. As a business: Didit checks the business, and we keep its legal name, registration number and country, and the names and roles of its officers and owners, but not documents, ownership percentages, addresses or dates of birth. Didit also asks every director and every owner of 25% or more to verify their own identity, and emails each of them a link. We keep whether you are one of the named officers; where that is unclear, a person decides, and we keep that decision. Your payout: a USDC address and its network, your commissions, your payouts and the name on each payout statement.
• Recruiters. If you name the creator who recruited you, they earn 1% of your coded sales for 12 months. They see each of your sales: the items, the amount it was worth and the time. They do not see who bought.
• Notes our team keeps about you. Our creator reviewers can write notes on your file. They are not shown in your portal, but you can ask us for them like anything else we hold.
• Stream tools. A secret overlay key, of which we keep only a one-way hash, and your overlay settings. If you turn on the chat commands, our bot accounts read the messages in your channel's chat to answer them, and keep neither the messages nor who wrote them. If you turn on your level on stream, viewers can see how close you are to your next level, which with our published thresholds lets them estimate your sales.
• Alerts. A new member or a sale through your code can reach you by Discord or Telegram direct message, or as a browser notification. Each is off until you turn it on, and none names the buyer. For browser notifications, your browser gives us an address on its push service and the keys to encrypt what we send, and we keep those until you turn them off.
• Going live. We ask Twitch, Kick and YouTube on a schedule whether you are live, and you can also press “I'm live”. We then announce it: your name, your stream's title, links to where you are live, and your code, on our Discord and Telegram, our X and Bluesky accounts, and the Live now feed on aton-trading.com, which shows it for 24 hours and then keeps it as history.
• Briefing emails. Off until you ask for them, with an unsubscribe link in each.
• Your public page on aton-trading.com shows the name you are shown by, your page name and your picture, your code, and the public channels you proved and chose to show. It never shows your verified name, email, country, level, money, followers or business.

• Your entry: who entered, and when; an entry code; the country and region you lived in, as proved, when you entered; and your result in the draw.
• Winning. In Canada, the winner must answer a skill-testing question, and we keep the question and your answer. The prize is recorded as an order in your account.
• Our monthly draw. A member who wins it can never enter it again, so we keep a winner's account and a one-way hash of the name and date of birth on their identity document for good.
• The public draw list. So that anybody can check a draw was fair, each draw publishes every entry's code, its rank and its outcome. It does not publish names, and the codes are made with a secret, so nobody can work out which one is yours. The list stays public for 6 months after the draw.
• People who live in Quebec may enter giveaways and the monthly draw. Each draw's official rules list the places it is open in, and are written in French as well as English.

• Account emails; order emails from our orders address, with your receipt and tax invoice, the pre-order terms, the refund policy and the withdrawal form attached; refund and withdrawal acknowledgements; the early-access email; and creator briefings, if you asked for them.
• All go through our email provider, Resend. It sees your address and what each email says.

If you write to us, or send us the form on our partners page, we keep what you send and our reply, to answer you and to keep a record of what was agreed.

We set only the cookies it takes to sign you in and to show you your price. None tracks you, and none needs your consent.

Cloudflare, which protects our sites, may also set a short-lived security cookie of its own to tell people from automated traffic.