Amped.Bio Privacy Policy
Last updated: October 17, 2026
This policy explains what personal information Amped.Bio collects, why, who receives it, and the choices you have. It applies to creators, fans and anyone who visits an Amped.Bio page.
1. Who we are and what this policy covers
Oneiro N.A., Inc., doing business as Amplify Digital, Boston, Massachusetts ("Amplify Digital", "Amped.Bio", "we") runs amped.bio. We decide how the personal information described here is used, except where a section says the creator decides.
This policy covers:
- The Amped.Bio editor, account and wallet, including USDC on Base and Buy USDC through Coinbase
- Public creator pages at amped.bio/handle and the public site (home page, pools, blog and developer docs)
- Sign in with Amped.Bio, when you use your account to sign in to another app
- The Amped.Bio bot on Telegram, when you link your Telegram account
- Emails we send you
It does not cover the creator's own tools on their page, or apps you connect through Sign in with Amped.Bio. Those follow their own privacy policies.
Contact: privacy@amped.bio. We have not appointed a data protection officer or an EU or UK representative, as neither is required for us today.
2. Information you give us
When you create an account and build your page, we collect:
- Account: name, email address, password (stored only as a one way hash), and whether your email is verified.
- Google sign in: if you sign in with Google, the identifiers and tokens Google returns so we can keep you signed in.
- Security: two factor settings and backup codes (stored protected), and a record of each signed in session with its IP address and browser details.
- Your page: handle, bio, photo, blocks, links, theme and anything else you publish. Your page is public by design.
- Uploads: images and files you upload, stored with our storage provider.
- X import: if you import from X, the profile details you choose to bring in.
- Browser check: a proof of work check on sign up and sign in to stop automated abuse. It runs on our own service and sets no cookies.
- Messages to us: what you send to support.
If you verify your identity with Authbase, we receive your verification status and badge, and only the attributes you choose to share with Amped.Bio: your name as checked on your ID, whether you are over 18, your gender and your country. We never receive your date of birth. Only you can see those shared attributes unless you choose to show one. You can show each attribute on your own, while you are verified, by turning it on in your page's RNS ID block. Anyone who views your page or your RNS name can then see it. Others see only your verification status, and only where you choose to show it, plus the attributes you turned on.
3. Wallets, tREVO and on chain activity
Your Amped.Bio wallet is created through Web3Auth, which receives the sign in details it needs to secure your wallet key. We store your wallet address with your account.
When you send tREVO, stake in a pool, claim rewards, create a pool, register or transfer a name, or refer someone, we record the transaction details with your account: amounts, addresses, pool, transaction ID and time. Referrals record who referred whom.
Blockchain records are public and permanent. Transactions on the Revolution Network, including your wallet address and amounts, can be seen by anyone and cannot be changed or deleted by us. Pool pages and unlisted pool detail pages show public contract data for a pool, including its creator and totals.
ndau conversion. If you convert ndau, we store your ndau address, REVO address, amounts, the signatures and validation key you provide, the document hash of the terms you accepted, the status and any transaction ID. We keep these as the record of your request.
Testnet only. Pool rewards come from the network, vary, and are not guaranteed.
USDC on Base. Your wallet can also hold USDC on Base, using the same wallet address. When you send USDC, you sign the transfer in your wallet and Coinbase's server wallet submits it for us and pays the network fee. We record each send with your account: amount, sending and receiving addresses, status, transaction ID and time. We also record USDC that reaches or leaves your address, and who on Amped.Bio sent or received it. Transactions on Base, including your wallet address and amounts, are public and permanent.
Address screening. Before a send, and when you first use USDC, we check the receiving address and your own address against sanctions and risk lists, using Circle and the Chainalysis sanctions oracle. We send only the wallet address. If an address is refused, we keep the address, the vendor's reference and the time.
Buy USDC through Coinbase. Coinbase sells you the USDC and delivers it to your wallet. Amped.Bio never receives your card or bank details and charges nothing. When you buy, we send Coinbase your wallet address, your IP address, the amount, your region, and a random reference we made for you instead of your account ID or email. If you pay with Apple Pay or Google Pay, Coinbase asks for your phone number and email and verifies you inside its own window on our page, under Coinbase's privacy policy. We do not receive those details. Coinbase gives us a sign in token so you can skip that step next time; we store it encrypted for 60 days. We record each purchase: way to pay, amount, Coinbase's price and fees, status, Coinbase's order number and the transaction ID. Coinbase's own privacy policy covers what Coinbase collects.
4. Visitors to creator pages and the public site
We measure visits so creators can see how their page performs and so we can run and improve Amped.Bio. A consent card on each creator page lets you choose Accept all, Reject all or Choose. You can change your choice at any time from Privacy choices at the bottom of the page.
Amped.Bio visit counting (always, no cookies)
On every visit we record the page, the links you tap, how long the page was visible, the site or campaign that sent you, your approximate country and city, and your device type, operating system and browser. We do not store your IP address. To count distinct visitors we make a one way code from your network address, browser details, the creator's page and a secret that changes every day. It cannot be reversed or used to recognise you on another day or another creator's page. Known bots are dropped. Creators viewing their own page while signed in are not counted.
Google Analytics (always, cookies only with your permission)
We use Google Analytics, run by Google, on creator pages, the public site and the editor. Until you choose, it runs in Consent Mode: it sends page views, device information and your approximate location, which Google works out from your IP address, and it sets no cookies. If you choose Accept all or allow Return visits on a creator page, Google Analytics also sets cookies to recognise return visits for up to 24 months. In the editor it always runs without cookies. We do not use Google Analytics on Sign in with Amped.Bio pages.
Return visits (only with your permission)
If you allow Return visits, we also save a random Amped.Bio ID in your browser so creators can see returning visitors. It is coded per creator, so creators cannot link your visits across different creators' pages. If you are signed in to Amped.Bio, we record your account with the visit. Creators see only totals, never which account visited. Withdrawing your permission deletes the ID and the Google Analytics cookies from your browser.
If your browser sends a Global Privacy Control signal, we treat it as a refusal of creator tags.
Summaries for creators
A creator can ask for a written summary of their page statistics. To write it, we send Anthropic, our AI provider, that page's totals for the period and the period before, top sources, devices, visitor counts and up to 10 link names. No visitor level data is sent.
5. Creator tags on creator pages (only with your permission)
Some creators connect their own Google Analytics, Meta (Facebook and Instagram) or TikTok to their page. The consent card names the creator and each service they use. These tags load only if you choose Accept all or allow Ads and analytics by that creator. They set their own cookies and receive your IP address and device information, and use it under their own privacy policies: Google, Meta, TikTok.
If the creator also connected Meta Conversions API or TikTok Events API, we send the same page view or link click from our servers, including your IP address and browser details, only if you allowed that creator's tags. We do not store your IP address for this.
Your choice is saved per creator. The creator decides which tools to connect and how to use the data, so the creator is responsible for it. For the server side events, Amplify Digital sends the data on the creator's instructions and does not use it for its own purposes.
6. Sign in with Amped.Bio
When you sign in to another app with Amped.Bio, the consent screen names the app and lists what it will receive. We share only what you allow, for example your name and picture, your wallet address, or your email address. We keep a record of which apps you allowed, what they can access and when.
You can remove an app at any time in Account settings, under Connected apps. Removing it ends its access at once. Access tokens it already holds stop working within 15 minutes. What the app did with your information before that follows the app's own privacy policy.
Some Amped.Bio apps may skip the consent screen. They still appear in Connected apps.
If you register an app as a developer, we store the app's name, website, redirect addresses and credentials.
Telegram
You can link your Telegram account in Account settings, under Connected apps. Linking uses Telegram's own sign in. We receive your Telegram user ID, your name, your username if you have one, and a link to your profile photo. We never receive your phone number, your contacts or your other chats. We store your username, name and photo link encrypted.
We use the link to deliver updates from creators you follow to your Telegram, but only after you turn Get creator updates on Telegram on. Each time you turn it on or off we record the choice, when you made it and the policy version, with no IP address. Sending /stop to the bot turns it off for every creator.
A creator never sees your Telegram username unless you turn on Let creators see my Telegram username. A creator who shows the Telegram mark on their page never shows their username either.
When you message a creator through Amped.Bio, or a creator replies to you, we store the messages and show them in both inboxes on Amped.Bio. When the other side linked Telegram, the Amped.Bio bot also delivers a copy there. We do not read conversations unless one side reports one; then our staff read that conversation to review the report. We keep messages for 12 months after the last message in a conversation, then delete them.
Unlink at any time under Connected apps. Unlinking stops all Telegram delivery at once and deletes the link. Your messages stay in your Amped.Bio inbox. Telegram's own privacy policy covers how Telegram handles your messages.
7. How we use information and why
We do not sell your personal information. We do not use it for our own advertising.
| Use | Information | Legal basis (EU and UK) |
|---|---|---|
| Provide your account, page, wallet and pools | Account, page, wallet and transaction data | Contract |
| Keep accounts secure and stop abuse | Sessions, IP address, browser check, two factor | Legitimate interests |
| Send account emails (verify, reset, security notices) | Email address | Contract |
| Count visits for creators and measure the site | Cookieless visit data, Google Analytics in Consent Mode | Legitimate interests |
| Show returning visitors | Random ID, Google Analytics cookies | Consent |
| Creator tags and server side events | IP address, device, page events | Consent |
| Sign in with Amped.Bio | What you allow on the consent screen | Consent and contract |
| Link Telegram and deliver what you asked for there | Telegram user ID, name, username, photo link | Contract |
| Creator updates on Telegram | Telegram user ID and your delivery choice | Consent |
| Messages between fans and creators, and reports on them | Message text, who sent it and when, reports | Contract, legitimate interests for reports |
| ndau conversion records | Addresses, amounts, signatures, terms hash | Contract and legal obligation |
| Send and receive USDC, show your activity | Wallet address, amounts, addresses, transaction IDs | Contract |
| Buy USDC through Coinbase | Wallet address, IP address, amount, region, random reference, Coinbase's order record, the encrypted Coinbase token | Contract |
| Screen addresses against sanctions and risk lists | Wallet addresses, the vendor's result | Legal obligation and legitimate interests |
| Written summaries for creators | Page totals, top sources, devices, visitor counts and up to 10 link names | Legitimate interests |
| Meet legal duties and handle disputes | Any of the above as needed | Legal obligation, legitimate interests |
8. Who we share information with
| Recipient | What they receive | Why |
|---|---|---|
| netcup (Germany) | All service data: servers, MariaDB database and Redis cache | Host Amped.Bio |
| Amazon Web Services (AWS S3) | Uploaded images and files | Store uploads |
| SMTP2GO | Your email address and the message | Send account emails from noreply@amped.bio |
| Web3Auth | Sign in details needed for your wallet key | Create and secure your wallet |
| Sign in with Google data; Google Analytics measurements, and cookies with permission | Sign in; site measurement | |
| Anthropic | Page totals, top sources, devices, visitor counts and up to 10 link names | Write creator summaries |
| Authbase | Your verification request | Identity badge, if you choose it |
| Creator tools (Google Analytics, Meta, TikTok) | Visit events, IP address and device, with permission per creator | The creator's own analytics and ads |
| Apps you connect with Sign in with Amped.Bio | What you allow on the consent screen | Sign you in to that app |
| Coinbase (United States) | For Buy USDC: your wallet address, IP address, amount, region and a random reference. For USDC sends: the transfer you signed, which Coinbase submits | Sell and deliver USDC; submit your sends and pay the network fee |
| Circle (United States) | Wallet addresses to screen | Sanctions and risk screening |
| Chainalysis (sanctions oracle on Base) | Wallet addresses, checked on chain | Sanctions screening |
| Telegram (United Arab Emirates and other locations) | Your Telegram user ID and the messages the bot sends you | Deliver what you asked for on Telegram |
| The public, the Revolution Network and Base | Your public page, handle, wallet address, transactions, pools and the verification status you choose to show | Public by design |
| Authorities, advisers, a buyer of the business | What the law requires or a transaction needs | Legal duties, rights, a sale or merger |
Creators see totals for their own page. They do not see your IP address, your Amped.Bio account, or your browser ID.
9. Storage on your device
Creator pages and the public site set nothing in your browser until you choose, except where a line below says otherwise.
| Name | Type | Set by | Purpose | Set when | Lifetime |
|---|---|---|---|---|---|
amped_consent_v2 |
Local storage | Amped.Bio | Remembers your privacy choices | You make a choice | 24 months |
amped_vid |
Local storage | Amped.Bio | Random ID for return visits | You allow Return visits | 24 months or until withdrawn |
amped_sid |
Session storage | Amped.Bio | Groups events in one visit | You allow Return visits | Until the tab closes |
amped_message_intent, amped_tg_link_prefs |
Session storage | Amped.Bio | Returns you to the creator you chose to message, with the Telegram choices you ticked | You tap Message me on Telegram | Until you return, or the tab closes |
_ga, _ga_SK6H61G3S1 |
Cookies | Google, for Amped.Bio | Recognise return visits in Google Analytics | You choose Accept all or allow Return visits | 24 months or until withdrawn |
| Referral cookie | Cookie | Amped.Bio | Credits the creator if you sign up from their page | You tap Claim your own Amped.Bio | 30 days |
| Sign in session cookies | Cookies | Amped.Bio | Keep you signed in | You sign in | Until you sign out, or 7 days after you last use Amped.Bio |
| Creator tag cookies (Google, Meta, TikTok) | Cookies | Each provider, for the creator | The creator's own analytics and ads | You allow that creator's tags | Set by each provider |
| Wallet key share | Local storage | Web3Auth | Keep your wallet available on this device | You use your wallet | Set by Web3Auth |
10. How long we keep information
| Information | How long |
|---|---|
| Account, page and uploads | While your account is open, then deleted within 30 days of closing it, except what the law requires us to keep |
| Sign in sessions | Until the session ends or expires |
| Visit events | 25 months, then deleted or combined into totals |
| Consent records (what you chose, when, policy version; no IP address) | 5 years |
| Browser ID and Google Analytics cookies | Up to 24 months, or until you withdraw |
| Wallet and transaction records, including USDC sends, USDC transfers and Buy USDC purchases | While your account is open, and 5 years after it closes, for disputes and legal duties |
| Coinbase sign in token (Apple Pay and Google Pay) | 60 days, or until your account closes |
| Refused address screenings | 5 years |
| ndau conversion records | 7 years after the request |
| Connected app records | Until you remove the app, then 30 days |
| Telegram link | Until you unlink or close your account |
| Telegram link and delivery choice history (no IP address) | 5 years |
| Messages between fans and creators | 12 months after the last message in the conversation |
| Support messages | 2 years |
On chain records on the Revolution Network and Base are permanent. We cannot delete them.
11. Your choices and rights
Choices you can make now:
- Change your privacy choices on any creator page from Privacy choices. Reject all is as easy as Accept all.
- Edit or remove your page content and uploads in the editor.
- Remove connected apps in Account settings, under Connected apps.
- Turn on two factor sign in.
- Close your account by writing to privacy@amped.bio from the email on your account.
Your rights. Depending on where you live, you can ask to access, correct, delete or export your information, object to or limit how we use it, and withdraw consent at any time. Withdrawing consent does not affect what we did before. In some US states you can also opt out of the sale or sharing of personal information and of targeted advertising. We honor Global Privacy Control signals as that opt out. We will not treat you differently for using your rights.
To use a right, write to privacy@amped.bio. We may need to confirm it is you. We answer within one month, or sooner where your local law sets a shorter time. If you are in the EU or UK, you can also complain to your data protection authority.
We cannot change or delete records on the blockchain, including your wallet address and transactions.
12. Transfers, security, children and changes
International transfers. Our providers may process information outside your country, including in the United States and Germany. Where EU or UK law applies, we rely on the EU US Data Privacy Framework and its UK extension where a provider is certified, and otherwise on Standard Contractual Clauses with the UK addendum.
Security. Passwords are stored as one way hashes. Creator Meta and TikTok tokens and Coinbase sign in tokens are encrypted at rest and never sent to any browser. Access to personal information is limited to staff who need it. No system is perfectly secure.
Children. You must be 18 or older to create an Amped.Bio account, because accounts include a wallet and tokens. We do not knowingly collect information from anyone under 18. If you believe someone under 18 has an account, write to us and we will delete it.
Changes. We will post changes here and update the date at the top. For material changes to how visitors are measured, the consent card asks every visitor again.