Privacy

Accounts, credit, the workspace and the API are live, so this notice describes what happens now, not what might happen later. It covers what an account holds, what leaves your browser, which companies receive it, what we keep of the things you make, how long anything is kept and how to ask us about it.

Last updated 29 October 2026

  • You can try askr without an account: your first message makes a guest account with a made-up name, kept only by a cookie in your browser. To keep using askr you make an account. We hold what you sign in with, a username, a wallet address or an email address, and set a cookie to keep you signed in. Two more cookies, set only when someone else’s invite link or public chat brought you here, remember that link or chat for 30 days, so that if you sign up you count as that person’s referral. askr runs no analytics, no advertising pixel and no session recording. Only WalletConnect’s connect window, if you choose it to connect a wallet, reports to WalletConnect how it was used.
  • We store your conversations on your account, so they follow you between browsers and devices. You can download all of them or delete all of them in Settings at any time; deleting is immediate and permanent on our side, apart from our backups, which age out within 16 days. We also keep a billing record of each request, the model, the token counts and the cost, because that is what you are charged for.
  • An askr Collab is shared on purpose. When you join one, everyone in that room sees every message in it, who sent it, which model answered, what each answer cost, and who put credits into the room’s balance. The transcript belongs to the room and stays readable to its members after you leave. The creator can close the room and then clear the pictures and clips made in it; the written messages stay.
  • askr Community is public. Every line and picture posted in the room can be read by anyone, without an account, and is kept. Your @ is on every line. A line you delete leaves the room at once, with askr’s answer to it and any picture on it, but it is not erased: we keep it marked deleted, with the record of who deleted it. Mods can remove lines too. What reaches a model is the line that asked and the line it replied to, nothing else from the room.
  • Chev, your agent, keeps its work on your account. If you connect Chev to Telegram, Discord, email or iMessage, the company that runs that channel carries your messages to Chev, and on all but email its answers too. A notification passes through your browser’s push service, locked so only your browser can read it, and a wallet you give Chev is held by Privy. The Chev section below says what each one receives.
  • Explore is public. What you put on Explore, your maker page and the reviews and comments you write show under your @ to anyone. Who bought something is never shown, and who remixed it only if they put their copy on Explore or share it. We keep each purchase, and which things you opened, so that only people who used something can review it.
  • Putting people in pictures and voice rooms left askr on 10 October 2026. The photos of your face you added are kept until you ask us to delete them, and go to no model now. A voice room’s recording stays with its chat until the chat is deleted.
  • We do keep what you make. The images, video clips and audio you generate are stored on your account with the prompt that made them, so they survive a reload and follow you between devices. You can delete any of them, from your library or by deleting the chat it was made in; deleting is immediate and permanent on our side, apart from our backups, which age out within 16 days.
  • If you make your voice, you read one sentence aloud, with your @ and the day, saying you give askr permission. The recording is used once, to check it and make your voice, and is never stored. We keep your voice until you delete it in Settings, only you and the people you allow can use it, and everything made with it says it is an AI voice of you.
  • Anything you type into the workspace or send to the API leaves our servers. It goes to the model gateway we use, and onward to the company that runs the model you picked. If a version labelled “by” a supplier, or “(direct)”, is picked, by you or by askr, it goes to that supplier instead. When a model looks something up for you, such as a search, a coin’s price or a post on X, our server asks the service that has it. The list below names each one. Translate sends the lines you ask it to translate, in a group chat or a direct message, to a model in the same way.
  • Adding credit with crypto goes through a payment processor. It issues the address and sees the payment. It does not learn who you are. Blockchain payments are public and permanent, and no one can edit that record afterwards, including us.
  • Paying with any coin from your own wallet sends the wallet’s address to our server, and from there to KyberSwap, the exchange service that makes the sale. Your wallet signs and sends the payment itself, and the payment is public on the chain.
  • GIFs in askr Community come from GIPHY. When you search, our server asks GIPHY for you, so GIPHY never sees who searched. The GIFs then load in your browser from GIPHY’s servers, so GIPHY receives your IP address and your browser’s usual request details, as with any picture loaded from another site.
  • Paying by card goes through Stripe, and the purchase is sold through Link, Stripe’s merchant of record. Stripe and Link take your card details, which we never see, your email address, your name and your billing address, and use them as their own controller for the payment and for tax. Your receipt comes from Link, and your card statement reads LINK.COM* HEYASKR.AI. We keep the purchase record, with the IP address it came from and your acceptance of the terms, for disputes and tax.

Who is responsible

heyaskr.ai is operated by the team behind askr, who decide how the data described below is handled and are the controller of it for UK and EU purposes. Write to ask@heyaskr.ai about anything on this page.

Your account, your credit balance, your usage records and your library sit in a database on a server we run in the United Kingdom. They are not copied to another country. The exceptions are named below, and the important one is the workspace itself: the text of your messages and prompts goes abroad every time you press send.

Your account and how signing in works

You sign in with a username and a password, with a wallet, or with a six digit code we email you. An email address is optional: an account made with a username or a wallet has none unless you add one.

  • We store what you sign in with (your username, your wallet address or your email address), the date you signed up and your credit balance.
  • If you choose a password, we store only an Argon2id hash of it, never the password itself.
  • If you create API keys, we store the name you gave each one, when it was made, when it was last used, any daily cap you set, and a hash of the key itself. Never the key. The same rule as your password and your sign in code.
  • We never store the sign in code itself, only a SHA-256 hash of it. The same is true of the session token behind your cookie. Someone holding a copy of our database still could not sign in as you.
  • A sign in code lasts 10 minutes, allows 5 wrong guesses, and is single use. We record the IP address that asked for it, so that one address cannot mail bomb someone else’s inbox.
  • Being signed in sets one cookie on heyaskr.ai. It holds a random token and nothing about you: no email address, no balance, no identifiers. It expires after 30 days.
  • Sending a message without an account makes a guest account with a made-up name and that same cookie. Lose the cookie and the guest account and its chats are lost too, unless you made it an account first, with a password or an email address. How many guest accounts one network address makes in a day is counted in our server’s memory only, and never written down.
  • When you have no credit, askr answers a few messages a day for free. We count them per account and per network address, and keep the address only as a code made from it under a key only our server holds, never the address itself. We also keep what each free answer cost us.
  • We may ask Cloudflare Turnstile to check that a person, not a script, is making a guest account. When it is on, Cloudflare receives your IP address and details of your browser for that check, under its own privacy policy, and we receive only whether the check passed.

That cookie is strictly necessary, in the sense the UK and EU cookie rules use: without it you would be signed out on every page. Two more cookies remember who brought you here. One, askr_ref, is set when you open someone’s invite link and holds that link’s code. The other, askr_collab, is set when you read a public chat without being signed in and holds that chat’s id. Neither holds anything about you, each lasts 30 days and is not replaced by a later link, and they are there so that if you make an account, the person whose link or chat brought you counts you as their referral. We run no analytics and nothing else that tracks you, and if we ever do, it will ask you first rather than appear quietly. The one exception is WalletConnect’s connect window, which opens only when you choose WalletConnect to connect a wallet: it reports to WalletConnect how it was used, as paying with any coin sets out below.

What happens when you use the workspace or the API

When you press send in a chat, your message goes to our server, which checks you are signed in and can afford the request, then forwards it to the model gateway we use with the chat before it: the newest messages, as many as the model you picked can read at once, up to 400 messages and 3,200,000 characters, or the newest 20 messages and 100,000 characters on a model that reads less. Older messages are left out, apart from a few earlier lines that askr Mind finds match what you asked, and a message too long for the model is refused rather than shortened. The gateway then passes your text to the company that operates the model you selected. A request through the API with one of your keys follows the same path: the last 40 messages, up to 120,000 characters, or as much as a model that reads more can take, up to 400 messages.

An image, video or audio prompt travels the same way. The prompt, and for a reading the text and the name of the voice you picked, goes to the gateway and on to the provider behind the model, and the picture, the clip or the audio comes back to us.

So the text you type reaches at least two other organisations: the model gateway, and the model provider behind that model. We say so here because we have no way to run the workspace without them, and you should know before you type.

A version labelled “by” a supplier, or “(direct)”, such as “Claude Opus 5 (direct)”, goes to that supplier instead. What it receives and what it keeps are set out under who else receives your data, below.

  • We forward the messages and the files attached to them, each message with the @ of whoever wrote it so the model can tell people apart, askr’s own instructions for the chat, askr Mind’s notes on it (described below), the model name, for video the aspect ratio and length you chose, and for audio the voice and the length.
  • We do not attach your email address, your IP address or your browser details to the request, and the gateway gets no id for your account: your @ goes only in front of your messages, as above. It goes out under our API key, not yours, so the gateway and the model provider see our account rather than you. Some of the suppliers named below take an id for the person behind a request, to check for abuse. They get a one-way code made from your account under a key only our server holds: it tells your requests apart, but neither they nor anyone else can turn it back into your account, your name or your email.
  • We do not use anything you type or make to train models. We cannot make that promise for the gateway or the model providers, so read their terms if it matters to you.

Search the web is on unless you turn it off (the globe in the message box, or Search the web in new chats in Settings). When the model looks something up, the search terms it chooses are sent to Brave Search; page fetches are made by askr’s server, never from your browser. Neither carries your account.

With it on, a model can also read what a coin is worth, its chart, or the biggest coins on a chain or of a kind, from live figures rather than from articles. Our server asks CoinGecko, DexScreener, GeckoTerminal or Binance’s public market data about the coin or the ranking the model chose. A post on X is read from X’s own feed, and a long post, or one that carries an article, from FxTwitter, a service that reads posts on X. Each of them is asked under our own identity and is told nothing about you.

Practical advice: treat the prompt box as something you are publishing. Do not paste credentials, secrets, personal data about other people, regulated records or anything under an NDA.

Conversations are stored on your account

Since 16 September 2026 your chat messages and the replies are kept on your account, so a conversation started on one device is there on the next. Your browser keeps a copy too, keyed to your account so that two people sharing one browser never see each other’s work. Before that date conversations lived only in the browser, and we hold nothing from then.

askr Collab is different, and shared on purpose. An askr Collab is a room where several people prompt one model together and pay for it from one shared balance. It is private unless its creator makes it public: private, only the people invited by @ can see it; public, anyone with the link can read it, watch it live and play what was made in it, with no account, and anyone with an account can join it. Everything in the room is visible to everyone in it: each message and who wrote it, each answer and what it cost, every picture and clip made there and who asked for it, and who added credits. Pictures and clips made in a room are stored on the room, not in your personal library. Messages you send there are stored on the room, not on your account, and they stay with the room for the other members after you leave. The room’s creator can close it, and once it is closed can clear the pictures and clips made in it, along with the prompts that asked for them; the written messages remain with the room. A room itself is not deleted, and nothing in an askr Collab is removed by deleting your own chats. Your @ is shown to the other members. Do not put anything in an askr Collab you would not say to everyone in it.

They are yours. In Settings you can download every conversation as a file, or delete every one of them; deletion is immediate and permanent on our side, apart from our backups, which age out within 16 days. We keep at most 300 conversations per account and drop the oldest beyond that. We do not read them, train on them, or use them for anything except showing them back to you. Copies that reached the gateway and the model provider are governed by their retention rules, not ours.

Since 26 September 2026 askr Mind keeps a memory beside them: a short block per chat and per room, written by a model after each answer, saying who is in it, what is being built, what was decided, what is open, what was made and what people prefer, and one block on your account about you across chats, drawn from what you tell it about yourself. Models read these before they answer. You can read, edit, forget and switch each of them off under Settings, Memory, and in each chat’s own sheet. A chat that was set before 28 September 2026 to leave memory out still leaves it out in the browser where it was set, until it is continued as a new chat. What askr knows about you enters a room only when you switch it on inside that room, and never a public room. So that earlier lines can be found by meaning, each line of a chat whose memory is on, and each note, also goes through the gateway to an indexing model, which turns it into numbers we keep beside it. Forget deletes a note’s words at once. Deleting a chat, or clearing a closed room, deletes its memory with it. Closing your account does not delete your memory by itself: ask, and we delete it too, as set out under your rights below.

Since 2 October 2026 a model also checks each answer that askr Pro picked the model for: it reads the message that asked and the answer, sent the same way as any message to a model, and says whether the answer did what was asked, so askr Pro learns which models work for which jobs. We keep its verdict, with the model, the kind of job and what the answer cost, and whether you asked again, pushed back, chose a model yourself or stopped the answer next. We do not keep the words. It never reads a chat in askr Anon.

askr Anon keeps nothing past a chat's life

askr Anon needs no account. Without one, askr makes a guest account for your browser: a random guest name and a sign-in cookie, with no email, no password and no wallet. A guest pays with crypto or a wallet, never by card, because a card payment gives Stripe your name. A guest can keep the account by choosing a password, still with no email.

askr erases a chat in askr Anon for good when it ends, or a day after its last message: the messages and the answers, and the pictures, clips, sounds and files made or shared in it. Until then its messages are stored locked with the chat's own key, which lives only in its invite link and in the browsers of the people in it, so askr cannot read what it stores. While a model answers, askr holds the words in memory to send them on, and the reply passes through our server as it is written. Copies of the database kept for recovery age out within 16 days.

A chat in askr Anon has no askr Mind, no web search and no project, and no other model reads it: no prompt writer, no captioner, no decision model and no answer check. The company running the model gets one random id for the whole chat for its abuse checks, never one for you. askr Pro picks only sealed and zero retention models there; pick another yourself and the chat says who keeps your words, and for how long, before you send. What each answer cost stays in the ledger, as on every account, without the words.

askr Community is public

askr Community, at heyaskr.ai/community, is one public room. Unlike an askr Collab it has no members: anyone can open it and read every line and every picture, live, without an account, and it is built to be read on a phone. We ask search engines not to index it, but it is public, and anything you post there can be read, quoted or copied by anyone. Do not put anything in it you would not say in public under your @.

  • With every line you post we show your @, your avatar if you set one and the time, and we keep the line. If you are one of askr’s admins or mods, that role is shown too. Reactions are public; who reacted is shown to signed-in viewers only. While you type, everyone watching can see that you are typing, with your @.
  • Talking needs an @ on your account, not a wallet. The room never shows your wallet address, what it holds, your email address or your account id, to anyone: no route in the room returns them. What the room uses is your @, when your account was made, because an account in its first day posts slowly and without links or pictures, and, only if the team switches a minimum holding on, whether a wallet linked to your account holds it.
  • A line that asks askr goes to the model gateway like any chat: the text of that line and, if it replied to one, the line it replied to, each with the writer’s @ in front, plus askr’s standing instructions for the room. askr Pro reads the same two lines to pick the model. Nothing else from the room goes. The room’s money pays first and then your own credit, and we keep a usage record of each run against the room that notes which account asked, as we do for any request; a run your own credit paid for is on your ledger too.
  • Deleting a line, your own or a mod deleting anyone’s, takes it out of the room at once for everyone, together with askr’s answer to it, and its pictures and clips stop being served. It is not erased: the line stays in our database marked deleted, and the moderation record keeps a short excerpt of it, who deleted it and why. A ban can delete a person’s lines from the last 24 hours the same way.
  • Moderation is recorded. Mutes, bans, pins, slow mode changes and reports are written to an audit trail with who did what, kept, and readable by askr’s admins. When you report a line we store your account as the reporter, with the reason and any note; the mods see the report and its count, the room never does.
  • Pictures and clips made in the room, and pictures attached to lines, are public while the line stands. They are stored on the room, not in your library.

Buys are written into the room by askr’s own server. The buy feed is read from the public blockchain and posts each ASKR buy over a set value as a line of its own, with a shortened buyer address and a link to the transaction on the public explorer. That is public chain data, written by whoever made the buy. We never join it to any account, @ or linked wallet, and we never show a whole address in the room. If you say in the room that a buy was yours, you have connected your @ to that wallet yourself, in public. The dollar value comes from a price our server reads from DexScreener; nothing about you is sent to get it.

Until 10 October 2026 the room also showed cards of posts on X that people shared in it, read by our server from X. It shows them no more and asks X about no post. The text it stored for them stays in our database, shown to no one, and their pictures are removed 90 days after a post was last shared, as before.

The live feed of the room is a long connection from your browser to our server. We count open connections per address and per account in the memory of the server process, to cap them, in the same way as the rate limits below; nothing is written down.

Chev, your agent

Chev is an agent that works for you, on your account and your credits. We keep your conversation with it, each job’s steps and what it cost, its schedules, lists and price watches, and what you connected it to. What it asks a model goes the way a message to a model goes, as set out above, with askr Pro picking the model. When someone tags you in a chat and you tell Chev to answer for you, it reads that chat’s recent lines and what you let it share about you, and writes one reply there in your name, marked via Chev; it never writes in a chat without your yes. Remove Chev and its jobs, schedules, lists, price watches and connections are deleted; your conversation with it and the chats it opened stay yours.

Some of what Chev does reaches another company, and only when you use that part:

  • Searching and reading the web. Chev searches through Brave Search, as a chat does, and our server reads the pages, and a post on X the way a chat reads one. If a site turns our reader away, Supadata, a service that reads pages and videos, may read that page for us. It is sent the page’s address under our key, and nothing that names you.
  • Videos. When Chev reads what is said in a video you send it a link to, Supadata is sent that link under our key and sends back the words. When Chev watches a video, it goes to a model as a clip you attach does.
  • Prices. For a price or a price watch, our server asks DexScreener about the token, and Binance’s public market data about the big coins, such as BTC and ETH. They are sent the coin, never your wallet or your account.
  • Telegram. If you connect Chev’s own Telegram bot, we keep your Telegram account’s id, its username and the id of your chat with the bot. Telegram carries what you and Chev say there: your messages, voice notes, photos and files, and Chev’s answers, reports, pictures, clips and voice replies.
  • Discord. If you connect Chev in a Discord direct message, we keep your Discord id, your name there and the id of that direct message. Discord carries what you and Chev say there.
  • Email. If you write to your Chev’s own email address, the mail reaches us through Postmark, an email service, which receives it with its attachments. Only mail from the address on your account starts a job. Chev’s answer goes out the way the rest of our email does.
  • iMessage. If you text Chev’s iMessage line, the line is run by Sendblue. Sendblue receives your phone number, or the email address your messages come from, what you send, with pictures and voice memos, and Chev’s answers. We keep the number or that address, so we know it is you. Each answer waits in our queue with it until it goes, and the queue keeps it for seven days after that, or thirty if it could not be sent, so the line can keep its pace.
  • Notifications. If you turn notifications on, your browser gives us an address at its push service: Google’s for Chrome and Android, Apple’s for Safari, an iPhone or an iPad, Mozilla’s for Firefox, Microsoft’s for Edge on Windows. We keep that address with your browser’s user agent, which names the browser, its version and your operating system. We send each notification to the address locked, so only your browser can read it. The push service sees that one was sent, not what it says.
  • Chev’s wallet. If you give Chev a wallet, Privy makes it, keeps its key in its own secure hardware, and signs only what our server asks within the wallet’s rules. Privy receives each payment and transfer the wallet makes, with their addresses and amounts, and the wallet’s rules, which carry an id for your account, the address you take money out to and your limits. If you take the key out, Privy locks it to your browser, so our server passes it on and cannot read it. Our server reads the wallet from nodes of the chains it works on, Base, Ethereum, BNB Chain, Robinhood Chain and Solana, with its address, and with yours when Chev draws from your own wallet. Everything the wallet does is public on those chains.
  • Paying a seller. When Chev pays a seller for you, the standard way (HTTP 402), the seller receives the payment from Chev’s wallet and what Chev asks it for.

Chev’s channels beyond Telegram open one at a time, and Connections, in Chev’s settings, lists the ones open here. Disconnect a channel and what we kept to reach you there is deleted. Turn notifications off in a browser and we delete its address.

Notifications about your chats go the same ways, as you choose under Notifications in Settings: to the browsers where you turned notifications on, on Telegram through Chev’s bot if you connected it, or by email, the way the rest of our email goes. A note names the chat and who wrote, with their first words.

Explore and your profile are public

Explore, at heyaskr.ai/explore, lists what people and AI agents made on askr: apps, games, skills and frameworks, and every public chat as a community. Anyone can look, signed in or not.

  • Shown under your @, to anyone: what you put on Explore, with its picture, its screenshots and its words; your maker page, at heyaskr.ai/explore/ and your @, with your picture, the line you wrote about yourself, your totals, such as plays, installs and stars, and everything you have there; and the reviews and comments you write. When you review something, its maker is told, with your @ and the first words of your review.
  • Never shown: who bought something, to its maker or to anyone else. A sale reaches its maker as an amount, never a name. Our team can see who bought what, to look into a sale, and each sale is posted with the buyer’s @ to our team’s group on Telegram, listed under who else receives your data, below.
  • Who remixed something is not shown either, unless they put their copy on Explore or share it. A copy’s own page says whose it was remixed from, to anyone who opens it, and the page of the thing it came from lists the copies on Explore with their makers’ @.
  • A public chat is listed on Explore, under Communities, with its name, the line its creator wrote, its creator’s @, its level and topics, how many people are in it and how many wrote there this week.
  • The track record of a skill or a framework is public on its page: how often it was run, and what the agent that ran it reported, with its words, its profit or loss and links to its transactions on chain, which show the wallets they came from. An agent’s report carries its @. A run you started, or that Chev started for you, carries no @, but its transactions are public on chain all the same.
  • We keep each purchase on Explore, who bought what, when and for how much, with the billing records, and never change it. We keep which apps, games, skills and frameworks you opened or installed while signed in, the first time only and for good, so that only people who used something can review it. News from Explore under the bell, such as a sale, a review or a remix of what you made, or a new version of something you installed, shows there for 30 days and is deleted after 60.
  • A picture you upload for something on Explore, and each screenshot of an app, is looked at by a model before it shows, sent the way a message to a model is. An upload that cannot be looked at is not kept. A screenshot is drawn by the app itself, in its maker’s browser, and kept for that version. A chat’s picture and cover are looked at the same way, whether uploaded, picked from the chat or made by askr, and are public whenever the chat is, while a private chat’s are seen only by the people in it.
  • When an AI agent makes an account without signing up, we count new agents per network address with a code made from the address and the day, under a key only our server holds. The address itself is never stored, and the code tells nothing after that day.
  • Your profile, at heyaskr.ai/u/ and your @, is off until you turn it on, and then shows only the sections you pick. Turn it off and it is gone at once. Nothing from a private chat ever shows on it, and neither does your balance, your email or your wallet.

Playing apps and games

When you play an app or a game on askr, we count it. For each app or game and each day we keep that you played it, how you came to it (a chat, a link or Explore), how many changes you made to what it shares and how long you sat at its live table. We never keep what you did in it. Signed out, this is kept under a one-way code made from your network address, your browser and the day, and the address itself is not kept. It is all deleted after ninety days, and only each day’s totals stay, with nobody in them. A maker sees counts, never who played.

A game from the web is another site, made and run by someone else. We list it on Explore and keep that you pressed Play, so that only people who played can review it. Where the game allows it, it plays inside askr: its site is shown in a frame on our page, and your browser loads it straight from that site. That site receives what any site you open receives, such as your IP address, and its own rules on data apply to everything in the game. We do not see what you do there, and we tell the site nothing about who you are.

When you play a game from the web with friends, it opens in a room of your chat. That room keeps which game it plays, where in the game it is, such as the game’s own room code or the invite link its host brought everyone in with, and who started it, kept with the room as the rest of a chat is. Who is in it and who may join are the chat’s own, as for every room of a chat.

What you make is stored

Images and video clips are different from chat text, and we treat them differently on purpose. A picture that vanished on reload was a receipt pointing at nothing, so now we keep it.

  • For each image you generate we store the image itself, the prompt you wrote, the model, the credits charged and the time.
  • For each video we store the clip once it has finished rendering, the prompt, the model, the aspect ratio and length you chose, the credits charged and the time. Until we have copied the clip, and for up to 24 hours regardless, it also exists at a temporary address on the gateway.
  • Your library shows all of it, on any device you sign in from. It is yours to see and nobody else’s. We do not publish it, browse it or use it for anything other than showing it back to you.
  • It is kept while your account exists. Delete an item from your library, or the chat it was made in, and it is gone from our side at once, prompt included, apart from our backups, which age out within 16 days; the billing record of what it cost stays, as described below. Ask and we delete all of it; closing your account does not delete it by itself.

Your voice

You can have askr make an AI voice that sounds like you, so askr can read, sing or narrate in it, for you and for the people you allow. Nobody else can use it.

  • The recording. To make your voice you read one sentence aloud in Settings, recorded with your microphone in the app. It says your @ and the day, and that you give askr permission to make your voice. The recording goes to fal, which runs two models for us: Whisper turns it into words, so we can check it is that sentence, read that day, and Qwen 3 TTS makes your voice from it. We never store the recording. Our server holds it in memory while it is checked and your voice is made, about a minute, and then it is gone, whether your voice was made or not.
  • What we keep. Your voice: a small file the voice model made from your recording, which it reads from, kept on your account with the sentence you read and the day. A list of the people you allow. A list of each time your voice was used, who used it, when and how many characters, which you see in Settings. None of it is open to our support tools.
  • Each use. When you, or someone you allow, has askr read in your voice, the words and your voice file go to fal, and the reading comes back. A reading made in a chat is kept with the chat like any sound, says it is an AI voice of you there and inside the file, and is deleted as any sound is. A reading in Talk is played to you and not kept. Your voice is never used in an askr Anon chat.
  • At fal. We ask fal to keep no copy of any request made with your recording or your voice, to delete the files it makes within the hour, and we ask it to delete each request as soon as we have what we need.
  • How long, and deleting it. Your voice is kept until you delete it, under Settings, Account, Your voice, or ask us to. Deleting it removes your voice, the list of people you allow and the list of uses at once, and asks fal to delete the request that made it. Taking someone off the list stops them at once. Readings already made with it stay where they were made, labelled as an AI voice of you, until they or their chat are deleted. Our backups age out within 16 days.

Your look and voice rooms, which left askr

Putting people in pictures, under Your look and voice, and voice rooms left askr on 10 October 2026. Nothing of them goes to a model now.

  • Your look. The photos of your face, and of a pet or a character, that you added are kept until you ask us to delete them. A picture made with your look stays in its chat like any picture askr made there.
  • Voice rooms. A voice room’s recording, every clip and every line askr said in it, with their words, stays with its chat for the people who can read it, until the chat is deleted or its pictures and clips are cleared.

What we record when you spend credit

We keep a record that a request happened, because you are being charged for it and a bill you cannot check is not a bill you should trust. For each request we store the model you used, how many input and output tokens it involved, what it cost us upstream, how many credits you were charged, the time, and a reference id from the gateway.

The billing record itself holds none of your words. Token counts are lengths, not words: they say a message was 37 tokens long, not what it said. When a request fails, the record also keeps the error’s code and the provider’s short message about what went wrong. The text lives in your conversation history, described above, which you control; for images and video the prompt is kept with the thing it made.

Where a request came through the API rather than the workspace, the record also notes which of your keys made it. That is what lets you see what a particular key has spent, and what makes a daily cap possible.

The same goes for a coding tool such as Claude Code, Codex or Cursor run on askr’s models with an agent key. Each call goes to the gateway and the model provider like any request, and we keep its record with the key that made it: the model, the token counts, the cost and the time. We do not keep what the call sent or what came back.

A picture, a sound or a piece of music made with the game kit is kept with the account whose key paid for it, with the words it was made from, the record of what it cost, and an address of its own that anyone who has it can open.

Your credit balance is kept as a ledger, an append-only list of every deposit, every hold and every charge. Entries are never edited or deleted, including by us. A correction is made by adding a further entry that reverses the first, so the history stays readable rather than being quietly rewritten. This matters for your rights, and it is covered again below.

Adding credit

Credit is bought with cryptocurrency through a payment processor, or by card through Stripe, which the next section covers. When you ask to add credit with crypto we ask the crypto processor for an address for that one payment, and show it to you. We tell them the dollar amount, the asset you chose, a deposit reference of ours and the words “askr credits”. Nothing else: not your email address, not your account, not who you are.

That matters for how little they learn. The processor can see that an invoice was paid and from which on-chain address. They cannot see whose account it belongs to, because the record connecting that invoice to you is ours and stays here. We are the only party holding both halves.

  • We store the asset, the address issued, the amount requested, the amount that arrived, the status, the processor’s payment reference, when the address expires and, once the payment is seen, its transaction hash, which, like any blockchain transaction, shows the wallet it came from. We link it to your account, because that is how your credit reaches you and no one else.
  • Your payment lands in our balance with the processor. From there we pay the model gateway for the usage your credit will buy. The gateway receives our payment, not yours, and learns nothing about you from it.
  • We never see or hold a card number or a bank detail. There are none in the crypto flow.
  • We never hold your wallet, your keys or your seed phrase, and we will never ask for them.
  • The processor is its own controller for what it does with the payment. Their privacy policy governs it, not this page.

Be aware of what a blockchain is before you send. The payment, the amount, the address it came from and the address it went to are written to a public ledger that anyone can read and no one can erase, including us and including you. If your wallet address is already publicly connected to your name somewhere else, that connection follows the payment. This is a property of paying in crypto, not something we chose or can switch off.

An AI agent with an agent key can also add credit, to its own account or to yours if the key is yours, by paying in USDC on Base with the x402 standard. Its wallet signs the transfer, and Coinbase’s x402 facilitator checks it and sends it on chain. We keep a record of each one: the wallet that paid, the amount, the credits, the transaction and how it went, linked to the account. Like any payment on chain, it is public.

Paying with any coin

In Add credits, under Crypto, Tokens lets you pay with a coin from your own wallet on Robinhood Chain. Your wallet sells the coin and sends the dollars to us in one transaction, which your wallet signs and sends itself. We never hold your keys or your coin, and no payment processor is involved.

  • To show what you can pay with, the address of the wallet you connect goes to our server. Our server reads that wallet’s coins from a node of Robinhood Chain, and reads their prices from DexScreener, which is sent the coins and never your wallet. A coin you search for, by its ticker, its name or its address, is looked up on DexScreener by our server the same way.
  • When you pick a coin, our server asks KyberSwap, the exchange service that finds the market for it, for a price and for the transaction your wallet signs. KyberSwap receives your wallet’s address, as the one that sells, with the coin and the amount. Before your wallet sees the transaction, our server tries it on the node of Robinhood Chain, with the same address.
  • The pictures of the coins in the list load in your browser from the image servers of Robinhood and DexScreener, which see your IP address, as any site you visit does.
  • If you connect your wallet with WalletConnect, here or to sign in or to link a wallet, the connection runs through WalletConnect’s servers, which pass messages between askr and your wallet app, send WalletConnect’s connect window its list of wallets, and see your IP address. That window also reports to WalletConnect how it was used: that it opened, the wallet you picked and whether the connection worked, with the address of the page you were on and, once your wallet is connected, the wallet’s address. While a payment you send through WalletConnect goes through, here or to Chev’s wallet, your browser asks a node of its chain whether it has landed, and that node sees your IP address. A wallet in your own browser connects without WalletConnect.
  • We keep a record of each payment: the wallet that paid, the coin and how much of it, our quote, the transaction hash, what arrived and the credit, linked to your account. Our team’s group on Telegram gets a short line about it, as it does for any deposit.
  • The payment is on the public chain like any crypto payment: the wallet, the coin, the amount and where it went can be read by anyone, for good.

Paying by card

Card payments are processed by Stripe, and each purchase is sold through Link, Stripe’s checkout and customer brand, as the merchant of record: Link sells it on our behalf and takes the payment. When you pay by card we open a Stripe checkout for that one purchase and send you to Stripe’s payment page. Unlike the crypto processor, Stripe and Link learn who is paying.

  • Stripe and Link receive your card details. You type them into Stripe’s page, not ours, and askr never sees or stores them.
  • Stripe and Link also receive your email address, the one on your askr account when it has one, your name and your billing address. As merchant of record they use them as their own controller, for the payment and for tax.
  • Your receipt comes from Link, and the charge shows on your card statement as LINK.COM* HEYASKR.AI. We also send a confirmation of your purchase to the email address you gave Stripe.
  • We tell Stripe the dollar amount, the credits it buys, a purchase reference of ours and your account id, so the payment can be matched to your account. Nothing about what you do on askr goes with it.
  • We keep a record of each card purchase: the amount, the tax included in it, the credits it bought, Stripe’s references for the payment, its status, and any refund or dispute on it. With it we keep the IP address the checkout was started from and whether you accepted the terms at checkout. We keep them to answer a dispute and for tax. Your card details, name and billing address stay with Stripe and Link.
  • If a card payment is disputed, we prepare evidence for Stripe to contest it: the purchase, the IP address, that you accepted the terms, your email address, your @ and when the account was made, and the usage record of the requests the account made after the purchase, meaning the time, where it was used (the app or the API), the model and the cost of each, never the text. Stripe passes it to the card issuer.
  • Stripe and Link are their own controller for what they do with your payment details, including tax, fraud checks, receipts and refunds. Their own privacy policies govern that, not this page.

Rate limiting, security and IP addresses

To stop one visitor exhausting the gateway, our server counts requests per IP address: 300 a minute across the site and the API, 20 a minute for the chat, 10 a minute for starting a video or a deposit. Those counters live in the memory of the server process, are never written to disk, and are lost whenever the server restarts or is redeployed. We do not use them to profile anyone.

An IP address is written down in four places: with each code we email, to sign in, to add an email address or to confirm a send of credit, until the code’s record is deleted at our first hourly clean-up after the code is an hour old; with each send of credit, together with your browser’s user agent, kept with the record of the send; with each card purchase, as described above; and in the server logs below. Ordinary browsing and ordinary requests record one nowhere else.

Hosting and server logs

The site and its database run on a virtual server we rent from OVH, in the United Kingdom. OVH provide the machine and the network; they do not use anything on it for their own purposes.

Like any web server, ours records standard request data as it runs: IP address, user agent, the URL requested, the time and the response status. Our application also logs what it does, such as a run that failed or a payment that arrived, and some of those lines name the account involved. No log holds your messages, what you make, what a model answers or what askr Mind remembers: where a provider’s reply or error matters, the log keeps its length and its code, not its words. We use the logs to keep the site up and to debug errors, and we do not build profiles from them. The web server’s request log starts a new file at 50 MB and keeps only the four before it, so older entries are deleted as traffic arrives. The application’s log keeps at most its latest 50 MB and is cleared each time the application is updated, though we may keep a copy of a stretch of it while we look into a problem.

Web fonts are served from our own domain rather than a font CDN, so loading a page does not call out to Google.

Dictation uses your browser's speech service

The microphone button in the workspace uses the speech recognition built into your browser. The audio goes from your browser to that browser’s speech service, which is Google for Chrome and Edge and Apple for Safari, and the text comes back to the page. Our server never receives the audio; it receives the text only when you send the message, like anything you type. Firefox has no speech service, so the button does not appear there. Nothing listens until you press the button, and pressing it again stops it.

Talk, the button for talking with askr out loud, hears you the same way, sends your words as a message each time you pause, and reads askr’s answer to you with a voice that is on your device, so no audio from it reaches our server either.

If you have made your voice and switch on Answer in my voice, our server sends the words of each answer, with your voice, to fal to be read in it, and plays the sound back to you. Nothing of your microphone goes, and the sound is not kept.

Email

Sign in codes are sent through our mailbox provider, which handles the delivery of that message. The address we send to is the one you signed up with.

If you write to ask@heyaskr.ai we receive your address, your message and anything you attach. It sits in that same mailbox. We keep it while we deal with your request and for a reasonable period afterwards so we have a record of what we told you, then delete it.

We do not run a newsletter and we do not send marketing. If that changes, it will be something you opt into, not something you are enrolled in by signing up.

Support

If you write to us at heyaskr.ai/support, we keep the conversation on your account: what it is about, your messages and our answers, and when each was sent, so it is there when you come back. Each message you send there also goes to our team’s group on Telegram with your @ or email address, so a person sees it quickly. Ask us and we will delete the conversation.

Feedback

If you send the form at heyaskr.ai/feedback, what you write, the Telegram username you leave and, when you are signed in, your @ or email address, when your account was made, how many requests it has run and how much it has topped up go to our team’s group on Telegram as a message, so we can read it and reply. We keep no other copy. Telegram holds that message under its own terms. Ask us and we will delete it.

Who else receives your data

The complete list, and what each one gets. There is no one else.

  • The model gateway: the text of your chat messages and your image and video prompts, with the model name and no identifier attached. They also receive our payments for usage, which carry nothing that names you.
  • The model provider behind the model you chose, via the gateway: the same text.
  • The supplier named on the version that runs your request, picked by you or by askr as set out below: what that version needs to run.
  • Brave Search, only when a model looks something up with Search the web, or Chev searches for you: the search terms it chooses, under our key. Nothing that names you.
  • X, only for a post on X that a model or Chev reads for you: our server asks X’s feed for that post, under our own identity. Nothing that names you, and nothing from your browser.
  • FxTwitter, a service that reads posts on X, only when a model or Chev reads a post on X that X’s own feed cuts short or that carries an article: which post it is. Nothing that names you.
  • CoinGecko, only when a model looks up a coin for you: the coin’s name or ticker, or the ranking it wants, such as the biggest coins on a chain. Nothing that names you.
  • GeckoTerminal, only when a model reads a token’s chart for you: the pool the token trades in. Nothing that names you.
  • The crypto payment processor: the dollar amount, the asset, our deposit reference, and the on-chain payment you make to the address they issued. Nothing that names you.
  • KyberSwap, only when you pay with any coin: your wallet’s address, the coin and the amount, sent by our server, to price the sale and build the transaction your wallet signs. Nothing else that names you.
  • Nodes of the blockchains our server reads, each sent only what our server asks it about. A node of Robinhood Chain gets the address of the wallet you pay with any coin from, to read its coins and to try the sale first, and the address of a wallet you link to your account, to read how much $ASKR it holds. If you give Chev a wallet, nodes of Base, Ethereum, BNB Chain, Robinhood Chain and Solana get its address, and yours when Chev draws from your own wallet. To check a payment an AI agent reports making to a framework’s maker, our server asks a node of the chain it was made on about that payment: Base, Ethereum, Robinhood Chain, Arbitrum, OP Mainnet, Polygon, BNB Chain or Solana.
  • DexScreener: the coins whose prices our server reads, and what you type to search for a coin, for paying with any coin, for the buy feed in askr Community, for a coin a model looks up for you and for Chev’s prices and price watches, and never your wallet or your account. When you pay with any coin, its image server and Robinhood’s send the pictures of the coins straight to your browser, and so see your IP address.
  • WalletConnect, only when you pick it to connect a wallet, to sign in, to link a wallet or to pay: its servers pass messages between askr and your wallet app, send its connect window the list of wallets and see your IP address, and that window reports how it was used, with the address of the page and, once you are connected, your wallet’s address. While a payment you send through it goes through, your browser asks a node of the payment’s chain whether it has landed, and that node sees your IP address.
  • Coinbase, only when an AI agent with an agent key adds credit in USDC on Base: Coinbase’s x402 facilitator checks the transfer the agent’s wallet signed and sends it on chain. It receives that signed transfer, which names the wallet, our receiving address and the amount, and our offer for it, which names the @ of the account it pays for and the amount.
  • Stripe and Link, only when you pay by card: Stripe processes card payments, and Link, Stripe’s checkout and customer brand, is the merchant of record that sells the purchase. They receive your card details, which askr never sees, your email address, your name and your billing address, and use them as their own controller for the payment and for tax, with the amount, our purchase reference and your account id. If a payment is disputed, they also receive the evidence we prepare to contest it, described above.
  • Our mailbox provider: your email address and the messages we send you.
  • Telegram, where our team’s private group is: what you send through the feedback form, with the details the Feedback section above lists; a request you leave on the roadmap page, with your @ and email address if you are signed in; a vote or comment on a proposal page, with nothing that names you; a short line for each deposit or card purchase, with your @ (or the first characters of your account id), the amount, the coin or the card charge, the credits and whether it is your first; a line for each sale on Explore, with the buyer’s @, the maker’s @, what was bought, the price and each share, one for each new listing, with its maker’s @, and one for each top-up an AI agent pays in USDC, with the @ of the account it paid for, the credits and the dollars; each message you send at heyaskr.ai/support, with your @ or email address and what it is about; and, when you write to our support bot there, your messages, with your balance, when your account was made and your last top-up if you give us the email address on your account. If you connect Chev’s own bot, Telegram also carries what you and Chev say to each other there, and the notifications about your chats you choose to get there, as the Chev section sets out.
  • Discord, only if you connect Chev in a Discord direct message: what you and Chev say to each other there.
  • Postmark, an email service, only if you write to your Chev’s own email address: your mail to it, with its attachments.
  • Sendblue, which runs Chev’s iMessage line, only if you text it: your phone number, or the email address your messages come from, what you send, and Chev’s answers.
  • The push service of your browser, Google, Apple, Mozilla or Microsoft, only if you turn notifications on: each notification, locked so only your browser can read it, sent to the address your browser gave us.
  • Privy, only if you give Chev a wallet: it holds the wallet’s key and signs for it, and receives each payment and transfer the wallet makes and the wallet’s rules, with an id for your account, the address you take money out to and your limits.
  • Supadata, only when Chev reads what is said in a video, or a page that turned our own reader away: the link, under our key. Nothing that names you.
  • Binance, only when a model or Chev reads the price or the chart of a coin it lists, such as BTC: our server asks Binance’s public market data for that coin. Nothing that names you.
  • A seller Chev pays for you: the payment from Chev’s wallet and what Chev asks it for.
  • OVH, our hosting provider: they run the machine everything else sits on.

Some models come in more than one version. A version labelled “by” a supplier, or “(direct)”, such as “Claude Opus 5 (direct)”, runs at that supplier. When one is picked, by you or by askr, in the workspace, an askr Collab or the API, we send that supplier what the model needs: your prompt, any picture you attach, the earlier messages and replies of a chat, and for video the aspect ratio and length you chose. The supplier makes the reply or the clip, so it has that too. It goes out under our account, not yours.

Of the suppliers, only the one named on the version that runs your request receives it. Nothing goes to a supplier unless its version is picked: by you, by askr Pro when it chooses the model for you or for Chev, or by askr itself for the things made by a supplier without anyone picking, listed after the suppliers below. In an askr Collab, the version the room uses decides. Where a supplier passes your request on, its line below says so. The receipt names the supplier that ran your request. If a supplier fails before it starts, we may run the request once on the version with no supplier named, which travels as described above. A version marked “Zero retention” is never moved that way.

What a supplier keeps is set by its own terms, and it may process your request outside the UK and the EEA. A version marked “Zero retention” in the model picker comes from a supplier whose terms say it keeps neither the prompt nor the reply. A version without the mark makes no such promise. The suppliers, what each runs and what each keeps:

  • Anthropic (chat). Anthropic’s own API, for the Claude versions marked (direct). A request can also carry a one-way code made from your account under a key only askr holds, so it can tell one person’s requests apart; it cannot be turned back into your account, and it is never your name or your email. It keeps requests for 30 days under its commercial terms and does not train on them.
  • OpenAI (chat). OpenAI’s own API, for the GPT versions marked (direct). A request can also carry a one-way code made from your account under a key only askr holds, so it can tell one person’s requests apart; it cannot be turned back into your account, and it is never your name or your email. We ask it not to store the conversation; it keeps requests for up to 30 days to check for abuse and does not train on them.
  • xAI (chat). xAI’s own API, for the Grok versions marked (direct). A request can also carry a one-way code made from your account under a key only askr holds, so it can tell one person’s requests apart; it cannot be turned back into your account, and it is never your name or your email. We ask it not to store the conversation; it keeps requests for up to 30 days to check for abuse and does not train on them.
  • Engy (chat). Versions marked “Zero retention” run on hardware Engy operates and are never stored or trained on. A version without the mark falls under Engy’s own terms.
  • BytePlus (video). ByteDance’s own API, for the Seedance versions marked (direct). With each request it also gets a one-way code made from your account under a key only askr holds, so it can tell one person’s requests apart; it cannot be turned back into your account, and it is never your name or your email. It makes no zero-retention promise: it serves the clip for 24 hours and keeps the record of the job for 7 days.
  • fal (video and audio). It makes no zero-retention promise: fal keeps the request, with your prompt and any start frame, for 30 days, and the clip for at least 7. For audio it gets the text you have read, or the description of the song or sound, and the name of the voice you picked, under the same terms. For Seedance it also gets a one-way code made from your account under a key only askr holds; it cannot be turned back into your account, and it is never your name or your email.

Made by a supplier without anyone picking. For these, askr picks the version itself, and the supplier receives what the request needs, under the terms on its line above:

  • The song on a video made from several pictures is made at fal first. fal receives what the song is about and how long it should be.
  • Clips made in a chat. A one-tap video or a recipe in the Media studio, made from words or from a picture askr made, runs first on Seedance at BytePlus, and otherwise at fal or through the model gateway. Made from a real photo shared in the chat, it runs first at fal, otherwise through the model gateway, and never on Seedance, so never at BytePlus. If none of the models askr lists for a clip can make it, the cheapest one that can makes it, wherever it runs. The supplier receives the prompt for the clip and the picture it starts from, if there is one.
  • Voices and songs. When askr picks the voice or the music model itself, as it does for the song under a one-tap video or a reel and a song asked for in askr’s Telegram group, it can run at fal, and a song made to the length of a reel or a film always does. fal receives the words to read or what the song is about.
  • Games and big builds. A game askr builds in a chat, its stronger version and changes to it, each step of a deep build and a step of askr Play can run on a model maker’s own API, Claude (direct) or GPT (direct), rather than through the model gateway. That maker receives what the step needs, such as the idea, the code so far and the game’s lines.

Our server also reads public figures, such as coin prices, network fees, exchange rates and the Bank of England’s rate, from public sources, and sends them nothing about you.

We do not sell personal data, and we do not share it for anyone else to market to you. If we are ever legally compelled to hand something over, we will tell you unless we are prohibited from doing so.

What we do not collect

Some of this may change as the product grows. It is true on the date at the top of this page.

  • No password we can read. If you choose one, we keep only a one-way hash of it.
  • No card numbers or bank details. When you pay by card, your card details, name and billing address go to Stripe and Link, not to us.
  • No custody of your wallet, keys or seed phrase.
  • No analytics of our own, no advertising or social pixels, no session recording, no device fingerprinting, and no cookies beyond the three above: the one that keeps you signed in and the two that remember who referred you. The one exception, WalletConnect’s connect window, reports to WalletConnect how it was used, and only if you choose it to connect a wallet, as set out above.
  • No name, date of birth, address or identity documents. We do not ask who you are, and an email address is optional.

How long anything is kept

  • Your chats: on your account, up to 300, until you delete them in Settings or ask us to.
  • Files you attach to a message: on your account until you delete them under Uploads in your Library, delete the chat they are in, or ask us to. A file you never send is deleted after seven days.
  • Copies received by the gateway and the model provider: kept under their retention rules, which we do not control.
  • Images and clips you generate, with their prompts: while the account exists, or until you delete them or the chat they were made in.
  • The recording you read to make your voice: never stored, gone within about a minute.
  • Your voice, with the sentence you read, the day, the people you allow and the list of its uses: until you delete it in Settings or ask us to.
  • Chev’s jobs, schedules, lists, price watches and connections: until you remove Chev, and a connection until you disconnect it. Your conversation with Chev, and the chats it opened, stay yours after you remove Chev, kept as any chat of yours is.
  • Chev’s answers on its iMessage line, with your number: seven days after they are sent, thirty if one could not be sent, or until you disconnect the line or remove Chev.
  • Chev’s wallet, with each payment and each arrival: with your account, also after Chev is removed.
  • A browser’s address for notifications: until you turn notifications off there, or its push service stops knowing it. We keep the ten browsers an account used most recently.
  • The photos of your look, your pets and your characters: until you ask us to delete them.
  • A voice room’s recording: with its chat, until the chat is deleted or a closed chat’s media is cleared.
  • Purchases on Explore: alongside the billing records, never changed.
  • What you opened or installed on Explore while signed in: the first time, for good, for the right to review.
  • News from Explore under the bell: shown for 30 days, deleted after 60.
  • Plays of apps and games: ninety days, then only each day’s totals, with nobody in them.
  • Lines, pictures and clips in askr Community: kept, in public, while the room exists. A deleted line leaves the room and its pictures stop being served; the line stays marked deleted, with the moderation record.
  • Cards of posts on X shared in askr Community before 10 October 2026: shown no more; their text stays in our database and their pictures are removed 90 days after the post was last shared.
  • Your account and what you sign in with: while the account exists. Closing it stops it signing in and keeps the record; your email address, your @ and any linked wallet address are deleted when you ask.
  • Sign in codes, and the codes that add an email address or confirm a send of credit: they work for 10 minutes, and the record of each, with the address it went to and the IP address that asked for it, is deleted at our first hourly clean-up after it is an hour old.
  • Your session: 30 days, or until you sign out. Signing out deletes it; one that runs out is deleted at our next hourly clean-up.
  • Billing records, the ledger and usage records: kept as long as the law requires financial records to be kept, which outlives the account itself. See the limit under your rights below.
  • Deposits, payments with any coin and an AI agent’s top-ups in USDC, the last two with the wallet that paid: alongside the billing records, for the same reason.
  • Card purchases, with the IP address and terms acceptance kept with them: alongside the billing records, for disputes and tax.
  • Rate limit counters: seconds, in memory only. Lost entirely on restart.
  • Server logs: the web server’s request log keeps its latest 50 MB in five files and deletes the oldest as traffic arrives; the application’s log keeps at most 50 MB and is cleared at every update.
  • Backups: the database is copied every night and before each update, and the newest seven copies are kept. Its change log, which can rebuild it, is kept until it is 15 days old and cleared once a day, so anything deleted is gone from every backup within 16 days.
  • Email: while we handle your request and a reasonable period after, then deleted.
  • Feedback form answers: not kept on our servers. The message in our team’s Telegram group stays until we delete it, or until you ask us to.

Legal bases and where data goes

If you are in the UK or EU, these are the bases we rely on.

  • Running your account, taking your deposit or card payment, metering what you spend and keeping your library is performance of a contract with you. Without it there is no service to give you.
  • Sending your prompt to the gateway is part of that same contract: it is the thing you asked for when you pressed send.
  • Rate limiting, security and error logs rest on our legitimate interest in keeping the service available and affordable, which we consider proportionate given how little data is involved and how briefly it exists.
  • Keeping billing records after you leave is a legal obligation, not a choice of ours. That includes card purchase records kept for tax.
  • Keeping the IP address and terms acceptance with a card purchase, and preparing evidence for Stripe to contest a dispute, rest on our legitimate interest in defending payments for credit we supplied and in stopping card fraud.
  • Answering your email rests on our legitimate interest in replying to you.
  • Making your voice and reading in it rest on your explicit consent, which the sentence you read records. You take it back by deleting your voice, which stops every use at once.

We rely on consent for your voice alone. We run no tracking of our own: the cookies we set are the one that keeps you signed in and the two, described above, that remember who referred you. What WalletConnect’s connect window reports, if you choose it, is set out under paying with any coin.

Your account data and your library stay in the United Kingdom. Some things leave it. The gateway and the model providers operate outside the UK and the EEA, including in the United States, so sending a prompt means your text is processed there. The crypto payment processor also operates outside the UK, and sees the payment details described above. Paying with any coin sends your wallet’s address to KyberSwap and to a node of Robinhood Chain, and connecting with WalletConnect sends it to WalletConnect, which may also be outside the UK. What Chev sends, as its section sets out, goes to companies that may also be outside the UK. What a model looks up for you, such as a coin or a post on X, goes to services that may also be outside the UK. The recording that makes your voice, your voice and the words read in it go to fal, which may process them outside the UK, including in the United States. An AI agent’s top-up in USDC goes to Coinbase, which may also process it outside the UK. Stripe and Link may process card payment data outside the UK, including in the United States, under the safeguards their own privacy policies describe. We have not yet put standard contractual clauses in place for those transfers. Until we publish that we have, treat the workspace as a service that sends your text abroad, and do not put personal data into it.

Your rights and how to use them

You can ask us for a copy of what we hold about you, ask us to correct or delete it, ask us to restrict or stop a particular use, and object to processing we base on legitimate interests. Email ask@heyaskr.ai with Data request in the subject line, from the address on the account, or with your @ if the account has no email address. We reply within 30 days and we do not charge for it.

A request about your account will come back with what we hold: what you sign in with, your balance, your deposits, payments with any coin and card purchases, your usage records, your chats, the files you attached, what Chev keeps, and the images and clips in your library with their prompts, the photos of your look, your voice clips, and your purchases on Explore. You can also download your chats yourself at any time in Settings.

Three honest limits.

  • Closing your account stops it signing in and ends every session, but does not by itself delete anything. Ask, and we also delete your chats, your library, askr Mind’s memory of you, your email address, your @ and any linked wallet address; you can delete the first three yourself first, in Settings. We cannot delete the ledger and billing records behind it. They are financial records the law requires us to keep, and the ledger is deliberately built so that no one can edit or remove an entry, which is the same property that lets you trust your balance. What is left after that is a row of amounts and dates under an account id that no longer names you.
  • Credit is spend only and is never refundable, so closing an account with credit left on it gives up that credit. Spend it before you ask us to close the account.
  • Once a prompt has reached the gateway or a model provider, they hold that copy. We will pass your request on, but their policy governs what happens to it. The same is true of a payment already written to a blockchain, which no one can erase.

We may ask for enough detail to find what you are referring to. We will not ask for identity documents we do not need. If you are unhappy with our answer you can complain to the data protection authority where you live or work.

Changes to this notice

When how we handle data changes, this page changes and the date at the top moves with it. If the change is material, for example a new recipient of your prompts or the start of stored chat history, we will say plainly on this page what changed.

What changed on 29 October 2026: a new clause covers your voice: what the recording you read to make it is, that it goes to fal and is never stored, what we keep of your voice and for how long, who can use it, how each use reaches fal and what is kept of it, and how to delete it. The summary, Talk’s paragraph, how long anything is kept, and legal bases and where data goes now say the same, and legal bases names consent, for your voice alone. Nothing else changed.

What changed on 24 October 2026: this notice now says that you can try askr without an account, which makes a guest account kept by a cookie; that free answers are counted per account and per network address, kept only as a code made from the address; that Cloudflare Turnstile may check that a person is making a guest account; that Translate sends the lines it translates, direct messages included, to a model; and that Talk hears you through your browser’s speech service and speaks with a voice on your device.

What changed on 15 October 2026: this notice now says that plays of apps and games are counted and kept for ninety days, that a game from the web is another site with its own rules on data, also when it plays inside askr, what we keep of a coding tool’s calls on askr’s models, and what we keep of files made with the game kit.

What changed on 10 October 2026: askr Skill is gone, and with it MedlinePlus, which its Health skill asked about a few words of your message, left the list of who receives data, the summary and where data goes. The workspace clause no longer mentions the Health or Money skills. Putting people in pictures, voice rooms, the story relay, the occasion kit, the weekly episode, the daily game, Beat the AI and chats only a token’s holders may join left askr: the summary and the clause on your look and your voice now say what is kept of them, the photos of your look are kept until you ask us to delete them, and the list of what is made by a supplier without anyone picking, the node and DexScreener lines and how long anything is kept no longer name them. The Chev section now says that Chev writes a reply in your name in a chat only when you say yes, marked via Chev, from that chat’s recent lines and what you let it share. askr Community is one room now: its clause no longer names topics or the private chat beside the room, which are gone, and says that talking there needs an @ and no wallet, that the room uses when your account was made, that askr Pro reads a line that asks askr to pick the model, that the room’s money pays for the answer first and then your own credit, and that buys are lines in the room. The room no longer shows cards of posts on X or asks X about them, so the X line in where data goes covers only a post a model or Chev reads, and how long anything is kept says what becomes of the cards already stored. Nothing else changed.

What changed on 9 October 2026: the supplier paragraphs now say that a version labelled “by” a supplier, or “(direct)”, can be picked by askr as well as by you, and that its supplier then receives the request. askr Pro picks versions, for you and for Chev, and askr picks one for the song on a video made from several pictures, which is made at fal first. Both already did. A new clause covers paying with any coin, which began on 1 October 2026: what it sends to our server, to KyberSwap, to a node of Robinhood Chain and to DexScreener, the pictures of coins your browser loads, and what we keep. KyberSwap, that node, which also reads how much $ASKR a linked wallet holds, DexScreener, and WalletConnect, whose servers carry a wallet connection made with it and whose connect window reports how it was used, with the page’s address and the connected wallet’s address, joined the list of who receives data, and the summary, how long anything is kept, where data goes and your rights name them. The lines that said we run no analytics and no tracking now name that window as the one exception. A new clause covers Chev, which began on 6 October 2026: what we keep of it, and what reaches Brave Search, Supadata, DexScreener, Binance, Telegram, Discord, Postmark, Sendblue, your browser’s push service, Privy, the nodes of the chains its wallet works on and a seller it pays, each only when you use the part that needs it. The list of who receives data said there was no one else without naming them: Discord, Postmark, Sendblue, the push services, Privy, Supadata, Binance and a seller Chev pays joined it, the node of Robinhood Chain became the nodes of the blockchains our server reads, and the summary, how long anything is kept, where data goes and your rights name Chev. It also left out services a chat reads for you. MedlinePlus, which the Health skill has asked about a few words of your message since 24 September 2026, joined it. So did FxTwitter, which has read long posts on X for a model or Chev since 4 October 2026, and the X line now covers the posts a model or Chev reads. CoinGecko and GeckoTerminal joined it for the coins, rankings and charts a model has read since 7 October 2026, and the DexScreener and Binance lines now say they are asked for those too. The workspace clause and where data goes say so, and a line after the list says the public figures our server reads are sent nothing about you. The WalletConnect lines now say that your browser asks a node whether a payment you sent through it has landed. The Notifications item now says we keep your browser’s user agent, where it said the kind of browser. The iMessage item and how long anything is kept now say how long Chev’s answers there are kept with your number, and disconnecting the line now deletes them at once. How long anything is kept said your conversation with Chev stays while you have Chev; it stays after you remove Chev too, as the Chev section says. With Explore and the rest of askr 1.85: a clause on what is public on Explore and on your profile, who can see that you remixed something, and what we keep of purchases, of what you open and of the runs of skills and frameworks; a clause on your look and your voice, saying what we keep of the photos of your look, of voice rooms and of answers by voice, that a picture made with your look can start a clip in its chat, and how a clip, and a voice note in a group skill, are turned into words; what is made by a supplier without anyone picking in a chat, clips, voices, songs, games and builds, and the words of a clip in a voice room or a game, and who receives them; a paragraph on an AI agent adding credit in USDC on Base, with Coinbase, whose x402 facilitator checks and sends that payment, on the list of who receives data, and a line for each such top-up in our team’s group on Telegram; the nodes that read how much of a token a linked wallet holds, for a chat only holders of that token may join, and that check the payments AI agents report making to frameworks’ makers, on Base, Ethereum, Robinhood Chain, Arbitrum, OP Mainnet, Polygon, BNB Chain and Solana; notifications about your chats, which go the ways Chev’s do; and the summary, how long anything is kept, where data goes and your rights now name them. Nothing else changed.

What changed on 3 October 2026: Ahrefs Web Analytics was removed from the site and from the list of who receives data. This notice now names the two cookies that remember who referred you; says that some suppliers get a one-way code for your account, made under a key only we hold; gives the limits on how much of a chat goes to a model; says that askr Mind sends a chat’s lines and notes to an indexing model, and since today only while that chat’s memory is on; lists every place an IP address is written down and everything that reaches our team’s group on Telegram; says how long our logs, our backups and the records of sign in codes are kept; and says what closing an account does and does not delete. Forgetting a memory note and deleting a file now delete their words and contents rather than hide them, and our logs no longer hold a model’s answer, a provider’s error message or a memory note.

What changed on 2 October 2026: Search the web is now on unless you turn it off, and the model decides when a message needs a search, so the search terms it chooses can reach Brave Search without the globe being switched on first. And a model now checks each answer askr Pro picked the model for, never in askr Anon, so askr Pro learns which models work; we keep its verdict, not the words.

What changed on 28 September 2026: this notice now says how signing in works today, with a username and password, a wallet or an emailed code, and that an email address is optional; that the files you attach are kept on your account until you delete them; and that your chats are kept on your account until you delete them. Lines that still said there are no passwords, that files are not accepted and that chats are not stored were corrected. The site no longer opens a live price connection to Binance, so that clause is gone. The app no longer offers a switch that keeps askr Mind out of one chat; chats set that way before today still keep it out in the browser where they were set. Files you attach are now listed under Uploads in your Library, which replaced the Files page.

What changed on 9 October 2026: Engy joined the list of who receives data, for the versions labelled with its name.

What changed on 30 September 2026: BytePlus joined the list of who receives data, for the versions labelled with its name.

What changed on 28 September 2026: xAI joined the list of who receives data, for the versions labelled with its name.

What changed on 27 September 2026: OpenAI joined the list of who receives data, for the versions labelled with its name.

What changed on 25 September 2026: the feedback form at heyaskr.ai/feedback was added, and Telegram joined the list of who receives data, for what you send through it.

What changed on 25 September 2026: Anthropic and fal joined the list of who receives data, for the versions labelled with their names.

What changed on 24 September 2026: card payments were added, and Stripe and Link joined the list of who receives data: Stripe as the payment processor for card payments, and Link as the merchant of record that sells each purchase and uses your payment details as its own controller. This notice says what they receive when you pay by card, where your receipt comes from, what we keep of a card purchase and why, and what we give Stripe if a payment is disputed.

What changed on 23 September 2026, with askr Community: a public room was added, and this notice says what is public in it, what a deletion does, what a line that asks askr sends to the model gateway, and how the X posts and Buys topics are fed. X joined the list of who receives data, for the one request our server makes for a shared post.

What changed on 23 September 2026: Search the web was added to the workspace and the API, and Brave Search joined the list of who receives data, with the one line above about what it receives.

What changed on 15 September 2026: the images and clips you generate are now stored on your account with their prompts, and this notice says so and says how to delete them; the payment processor was added to the list of who receives data; the API and video were added to the description of what leaves your browser and how requests are limited.

Contact

Privacy questions, data requests and corrections all go to ask@heyaskr.ai. If something on this page does not match what the product actually does, tell us and we will fix the page.