Privacy note

DoeAsk is built privacy-first — so this note is short, because there isn't much to tell.

The short version

• No cookies. DoeAsk sets none — not even for logging in.
• No third-party tracking. No Google Analytics, ad pixels or social widgets. We keep our own cookie-less usage stats on public business pages only. Scripts and fonts are first-party. (The one outside request is optional map images — see Maps.)
• No personal data in web addresses. We never put your email, phone number, real name or message content in a URL.
• Your messages are end-to-end encrypted. The server only ever moves scrambled text it cannot read.
• Username only. You don't need to give a phone number to use DoeAsk.
• Contact form. If you message us from the website, we receive what you type plus the pages you viewed on that visit. Nothing is sent unless you press Send. Details.

What DoeAsk keeps on your device

Instead of cookies, DoeAsk uses your browser's own first-party storage — it stays on your device and is never sent to a tracking service. That's where it keeps:

• small preferences — your light/dark choice, which tab you were last on, and shops you've saved;
• enough to greet you on the sign-in screen (that an account exists, and your last username);
• your messages, contacts and the encryption keys for this device, held in your browser's encrypted database.

Clearing your browser's site data for doeask.com removes all of it.

What we don't do

• We don't use cookies or any cross-site tracking technology.
• We don't load third-party scripts, fonts, analytics, ad networks or CDNs.
• We don't run ads, and we don't sell or rent your data or your contacts.
• We don't read your private messages — by design, the server can't.

Maps

Some features — like the public business directory (the Bazaar) — can show a map. When a map appears, the map images are loaded from OpenStreetMap, a free, community-run mapping service. To send you those images it sees your device's IP address, the same as any website you open — but we don't pass it your name, your account or your location. This is the only time DoeAsk loads anything from outside doeask.com, and it happens only if you open a map.

Usage analytics

To understand how our public business surfaces are used — shops, listings, channels, communities, the Bazaar and business cards — DoeAsk keeps its own lightweight, cookie-less analytics (think of it as a private, in-house version of Google Analytics). It records which of these public pages are viewed, when, the broad device type, and how a visitor arrived (for example from a channel, the Bazaar, a shared link, or a search). It uses no cookies, and it never stores your IP address — a daily-rotating one-way hash is used only to count unique visitors and can't be traced back to you. This runs only on the public / business tier — never on your private, end-to-end encrypted chats, which the server still cannot read. We use it in aggregate to understand traffic (and to help businesses see their own shop traffic). We don't sell it.

Contact form

If you send us a message from the contact or pricing page, we receive what you type (your name, phone number, email and question) together with a short record of that visit: which doeask.com pages you opened and which links or buttons you tapped, in order, plus the website that sent you here and your broad device type (for example "iPhone, Safari"). That record is kept only in your browser tab while you browse and is sent only if you press Send. Close the tab without sending and it's gone. It uses no cookies and doesn't follow you across visits or other websites.

We use it to answer you faster and in context. Your message is stored in DoeAsk's own system and also delivered to our team's private Telegram group so someone can respond quickly. Those Telegram alerts are not end-to-end encrypted, so please don't put passwords, recovery phrases or private chat content in the form. Email hello@doeask.com to see or delete what you sent.

Your messages

Private chats are end-to-end encrypted on your device before they're sent. The DoeAsk relay stores and forwards only ciphertext — it has no way to read your conversations, your previews or your contact list. Your identifier is a username you choose; no email or phone number is required to message.

Games

Games with friends are the one exception to the encrypted chat: so both phones always see the same board, each move and the board after it are saved on the DoeAsk server, readable by the server, together with who is playing and whose turn it is. The chat itself only carries a short link to the game. Hidden parts of a game stay hidden: ship and army positions are sealed on your phone until the game ends, and card hands are dealt by the server and shown only to the player who holds them. Finished results (and the 3 letters you pick for the leaderboards) are kept for the leaderboards; a game nobody touches for 30 days is deleted.

Email & Google sign-in (optional)

If you add an email or use Continue with Google, we use it only to confirm your account is real and to send you account notices such as your verification code. With Google, we receive your verified email address — never your Google password. Signing in this way does not unlock your encryption: you still set and enter a DoeAsk password, and that password is your key. We don't send marketing email.

Payments

When you share a payment QR or link, people pay straight into your own bank or wallet — DoeAsk isn't a bank and doesn't hold your money or handle the transfer. We don't ask for or store card or bank-login details.

Questions

DoeAsk is made by Imajineer. If you have a privacy question, reach us through the app or at imajineer.io.

This note describes how DoeAsk works today, during its private beta. If anything material changes, we'll update this page. Last updated 8 October 2026.