What HeyAskr does with your data.

heyaskr.ai is operated by the team behind HeyAskr, 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 and your usage records 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 chat itself: the text of your messages goes abroad every time you press send.

An account is an email address. There is no password, no username and no profile. You type your address, we email you a six digit code, and you type it back.

• We store your email address, the date you signed up and your credit balance.
• 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.

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. That is why there is no cookie banner. We run nothing else that would need one, and if we ever do, it will ask you first rather than appear quietly.

When you press send, your browser posts the conversation so far to our server. Our server checks you are signed in and can afford the request, takes the most recent 20 messages, drops any single message longer than 16,000 characters and any transcript over 32,000, then forwards the rest unchanged to PPQ, the model gateway we use, at api.ppq.ai. PPQ then passes your text to the company that operates the model you selected.

So the text you type reaches at least two other organisations: PPQ, and the model provider behind that model. We name PPQ here because we have no way to run the chat without it, and you should know before you type.

• We forward the messages and the model name. Nothing else.
• We do not attach your email address, your account, your IP address or your browser details to the request. It goes out under our API key, not yours, so PPQ and the model provider see our account rather than you.
• We do not use anything you type to train models. We cannot make that promise for PPQ or the model providers, so read their terms if it matters to you.

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

Having accounts did not change this. We do not keep your messages or the replies. A conversation exists only in the memory of the browser tab you typed it in. Reload the page or close the tab and it is gone. There is no chat history feature, and there is no table of prompts in our database.

This has an honest downside, and it is the same one as before. If you ask us to send you a copy of a past conversation, or to delete one, we cannot, because we never held it. Copies that reached PPQ and the model provider are governed by their retention rules, not ours.

We do 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.

We do not store the prompt, the reply, or anything derived from their content. Token counts are lengths, not text: they say a message was 37 tokens long, not what it said.

Your credit balance is kept as a ledger, an append-only list of every deposit 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.

Credit is bought with cryptocurrency, paid directly to PPQ, the same gateway that runs the models. When you ask to add credit we ask them for an address for that one payment, and show it to you. We tell them an amount and nothing else: not your email address, not your account, not who you are.

That matters for how little they learn. PPQ can see that some invoice was paid. They cannot see whose it was, because the record connecting that invoice to your account is ours and stays here. We are the only party holding both halves.

• We store the asset, the address issued, the amount, the status and the invoice reference. We link it to your account, because that is how your credit reaches you and no one else.
• We never see or hold a card number or a bank detail. There are none in this flow.
• We never hold your wallet, your keys or your seed phrase, and we will never ask for them.
• PPQ are their own controller for what they do 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.

To stop one visitor exhausting the gateway, our server counts requests per IP address: 120 a minute across the site, and 20 a minute for the chat. 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.

The one place an IP address is written down is a sign in request, as described above, so that the code sending emails cannot be pointed at a stranger’s inbox. Ordinary browsing and ordinary chat requests do not record one on our side beyond the server logs below.

Three pages show live cryptocurrency prices: the home page, /pricing and /calculator. On those pages your browser opens a WebSocket directly to data-stream.binance.vision, a public Binance market data endpoint. That connection comes from your device, so Binance can see your IP address, your approximate location from it and the fact that a browser connected. It is a read only price feed: we send nothing about you over it and we receive nothing about you back.

Those same pages also call our own price endpoint once a minute as a fallback. That call is made from our server to Binance, with CoinGecko as a backup, so neither of them sees you on that path. The network fee figures come from public blockchain endpoints called from our server for the same reason.

If you would rather not connect to Binance, the rest of the site does not open that socket. The chat, your wallet, the model catalog, the guides and these legal pages do not.

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. We use it to keep the site up and to debug errors, we do not build profiles from it, and we do not combine it with your account. Logs rotate and are discarded as they age.

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

Sign in codes and receipts are sent through Namecheap Private Email, 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.

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

• PPQ, the model gateway: the text of your chat messages and the model name, with no identifier attached. They also receive your credit payments, again with nothing attached that names you.
• The model provider behind the model you chose, via PPQ: the same text.
• Namecheap Private Email, our mailbox provider: your email address and the messages we send you.
• OVH, our hosting provider: they run the machine everything else sits on.

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.

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

• No passwords. Sign in is a mailed code, so there is no password of yours for us to leak.
• No card numbers, bank details or billing addresses.
• No custody of your wallet, keys or seed phrase.
• No chat history, and no copies of prompts or replies.
• No analytics, no advertising or social pixels, no session recording, no device fingerprinting, and no cookie other than the one that keeps you signed in.
• No uploaded files. The chat accepts text only.
• No name, date of birth, address or identity documents. We do not ask who you are, only where to email you.

• Chat messages on our side: not stored. They exist in your browser tab until you reload or close it.
• Copies received by PPQ and the model provider: kept under their retention rules, which we do not control.
• Your account and email address: while the account exists, then deleted when you ask us to close it.
• Sign in codes: 10 minutes, then expired and cleared.
• Your session: 30 days, or until you sign out.
• 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: alongside the billing records, for the same reason.
• Rate limit counters: seconds, in memory only. Lost entirely on restart.
• Server request logs: rotated and discarded as they age.
• Email: while we handle your request and a reasonable period after, then deleted.

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

• Running your account, taking your deposit and metering what you spend 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.
• Answering your email rests on our legitimate interest in replying to you.

We do not rely on consent for any of it, because the only cookie we set is the one that keeps you signed in and we run no tracking that would need permission.

Your account data stays in the United Kingdom. Two things leave it. PPQ 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. We have not yet put standard contractual clauses in place for those transfers. Until we publish that we have, treat the chat as a service that sends your text abroad, and do not put personal data into it.

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. We reply within 30 days and we do not charge for it.

Now that accounts exist, a request about your account will come back with something in it: your email address, your balance, your deposits and your usage records. A request about chat use will still come back close to empty, because we never held the conversations.

Three honest limits.

• We can close your account and delete your email address. 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 closure is a row of amounts and dates that is no longer attached to your name.
• 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 PPQ 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.

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.

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.