Connecting Sign in

← Feed

Privacy

Last updated: October 13, 2026

Aeon is published by Arkhe Technologies Inc. (formerly AO2 Live Solutions Inc.), a company in Alberta, Canada, operating as Aeon Data. This page says what we keep about you, why we keep it, and how to remove it.

What we keep

  • If you sign in: your email address, which plan you are on, the alert rules you set, and the dates you signed in. Nothing else about you.
  • Beside your plan we keep the allowance it bought: how many keys you may hold, how many requests you may make, and whether you may use the data in something you sell. It is kept so that a plan whose numbers move later does not move yours.
  • We also keep where your plan stands: whether you pay by the month or the year, whether it is running, late or ended, and the dates that go with it, such as the day a failed payment has to be fixed by, the day a plan ends or changes, and the day a founding price becomes the regular one. These are what your account page reads to tell you what is happening.
  • Which steps of Get set up on your account page you have done, so the list shows only what is left.
  • When you accept the terms, we keep the date and the version you accepted. If you are on Aeon Business or Aeon Scale, we keep the product name and web address you give us, and whether we have reviewed it.
  • When you ask for a sign-in link, we set a cookie in that browser for one day so that the link signs you in without a click. It holds a random mark, nothing about you.
  • If you sign in with Google, Google tells us your email address and name and nothing else. We keep the email.
  • While you are signing in with Google, we set a cookie in that browser for ten minutes so that the sign in can only be finished by the browser that started it. It holds random marks and the page you were reading, nothing about you.
  • If you close the short strip at the top of the home page, we set a cookie in that browser for 90 days so that it stays closed. It holds the moment you closed it, nothing about you.
  • When you first arrive from a link, we keep a short note of where it came from (such as instagram, google or the name of a newsletter) and the first page you opened, in a cookie named aeon_src, for 30 days. If you make an account in that time, we save the note with it, so we know which places bring readers. It holds nothing about you. Where we ask about cookies, it is set only if you accept.
  • To ask about news and offers only once, a cookie named aeon_news keeps how many pages you have opened here and whether you answered or closed the news banner, for up to a year. It holds nothing about you. Where we ask about cookies, it is set only if you accept.
  • If you say yes to Aeon news and offers by email, on the Terms page, in a box or banner on this site, or on your account page: we keep that you said yes, where you said it, the day and time, and the exact words you agreed to, so we can show what you said yes to. A no, and turning it off later, are kept the same way. Deleting your account takes all of it.
  • If you make an API key: a fingerprint of the key, the first ten characters of it, the name you gave it, when you made it, roughly when it was last used, when you stopped it, and when a plan paused it. We never hold the key itself, so we could not use one or give one away.
  • If you use Aeon through a connected app or an API key: how many questions your account asks each day, the app, and which of our tools or API addresses answered, so we know which data is used most and how much each account uses Aeon. We never keep the questions themselves. If you delete your account, we keep these counts only as totals by day, app and tool, with nothing that ties them to you.
  • If you have a key on Free or Aeon Pro: each day, how many networks and programs used it, and what kinds of programs they were, so we can tell when a key meant for your own use is part of a product other people use. The counts never include the network addresses. If we pause the key or decide its use is fine, we keep the date and the counts that led to it.
  • If you buy Aeon Pro: the customer number and the subscription number Stripe gives us, so that we know which account a payment belongs to and can put the plan back if it ends. We also keep the id, the kind, the arrival time and whether it ended a subscription, for each message Stripe sends us, so that a message sent twice is only acted on once. Those are kept for 90 days. Stripe takes the payment and holds the card. We never see or hold your card.
  • If we send you a free month code: the code, a note of who it is for, and once it is used, which account used it, when, and the Stripe subscription it started.
  • If you turn on push alerts: OneSignal, the service that delivers our emails and push messages, stores a browser token so it can reach that browser. We store which alerts you asked for.
  • If you add an alert destination: its name, the Discord link, Telegram chat or web address it posts to, and a webhook's signing secret, so we can post your alerts there. Removing it, or deleting your account, deletes them.
  • Visits: Google Analytics counts visits, sign-ups, purchases and a few presses, such as opening a card in the Just in strip, with a cookie. We see totals by page, country and where visits came from, not people.
  • Replit, which hosts Aeon, adds its own visit counter to every page; we do not see or use it.
  • Server logs: the network address and pages requested, kept for a short time to keep the site running and safe.

Connected apps

You can connect Aeon to Claude or another assistant that supports MCP. When you do, we store the app's name, a hashed token (never the token itself) and when it was last used. The app reads Aeon as you, within what your plan allows, and cannot change anything in your account. Disconnect on your account page ends its access at once.

What we do with it

  • Send you the alerts and sign-in links you asked for, and news and offers only if you said yes to them.
  • Count visits, sign-ups, purchases and a few presses so we know which pages are read, which links bring readers and which parts of a page are used.
  • Count the questions asked through apps and keys, by app and tool, to see which data is used and make Aeon better.
  • Check that keys meant for your own use are not part of a product other people use, and email you before we pause one, unless you have turned those emails off.
  • Keep the site working and stop abuse.

We do not sell, rent or trade your information.

Who else handles it

  • OneSignal delivers email and push messages.
  • Discord and Telegram carry the alerts you send to them, under their own terms.
  • Google counts visits, sign-ups, purchases and a few presses.
  • Replit hosts the site and its database.
  • Stripe takes the payment for the paid plan, on its own pages. If Google Analytics runs in your browser, its random visitor number and the time your visit began go to Stripe with your checkout and come back to us when you pay, so we can count the purchase and the visit it came from.
  • Ticker pages show a price chart from TradingView. When it loads, TradingView receives your IP address, the address of the page and the ticker shown. It sets no cookies. Where we ask about cookies, the chart loads only after you press Show the chart, and we keep that choice for 6 months in a cookie named aeon_chart.
  • The demo video on the account page is served by Amazon Web Services. When you press play, Amazon Web Services receives your IP address. It sets no cookies.

Each works under its own privacy terms. Our servers are in the United States, so your information is stored there.

How long

  • Your email, your alert rules, your alert destinations, your API keys, your Stripe numbers, your Get set up steps and the note of where your first visit came from: until you delete your account.
  • The daily counts of questions: with your account until you delete it, then only as totals with nothing that ties them to you.
  • The daily counts for each key: 30 days. The counts we keep when we pause a key or decide its use is fine: until you delete your account.
  • The request counts for your account's limits, for the current day and month: until a new day or month replaces them, or you delete your account.
  • A free month code and what we keep beside it: as our record of the offer, also after the account that used it is deleted.
  • The messages Stripe sends us: 90 days.
  • Alert history: 90 days.
  • Server logs: 30 days.
  • Visit counts: as Google Analytics keeps them, without your name.

Your choices

  • Every alert email has a one-click unsubscribe link.
  • Delete your account from the account page. We remove your email, your rules, your alert destinations, your API keys and your sessions at once. Only two things stay: the record of a free month code you used, and the counts of your questions, as totals with nothing that ties them to you.
  • Write to us to ask what we hold about you.
  • Turn off the analytics cookies in your browser settings, or choose Reject under Cookie settings; the site works the same.

Cookie settings

If you visit from the European Union, the European Economic Area, the United Kingdom, Switzerland, Gibraltar, Jersey, Guernsey or the Isle of Man, a banner asks before Google Analytics runs, and it runs only if you accept. We decide whether to ask from the country of your internet address, looked up on our server when a page loads; the address is not stored for this. Your answer is kept in a cookie in that browser for 6 months, and "Cookie settings" at the foot of every page lets you change it. The country comes from IP Geolocation by DB-IP, licensed under Creative Commons Attribution 4.0.

Children

Aeon is not for anyone under 18, and we do not knowingly keep information about them.

Changes

When this page changes, the date at the top changes with it.

Contact

hello@aeondata.io. See the Contact page.