MENDA

Privacy policy

Short version: no accounts, no cookies, no ads — and your AI conversations never leave your browser. Here is the longer version, in plain English.

Who we are

Menda is run by EmTech. If you have a question about this policy or about any data you may have with us, email privacy@menda.help.

What happens when you use Menda AI

When you send a message to Menda AI, it travels from your browser to our API (hosted on Cloudflare), which forwards it to QwenCloud — the service that runs the Qwen model. The reply comes back the same way. QwenCloud is operated by Intelligent Cloud Computing (Singapore) Private Limited, the company named on its own site and legal pages.

What we send is your question and the troubleshooting context that goes with it: the platform you told us about, the problem category, and which questions you have already answered. We do not send your name or your email address — we don't have them — and your IP address is not passed on to QwenCloud either.

Our own API does see your IP address, because every request on the internet carries one — but it is never written down. The moment a request arrives, your IP address is scrambled into a short code using a key that is thrown away and replaced every day. Only that code is stored, and only to count requests, so one person cannot use up the day's allowance for everybody else. The counts expire on their own — about a minute for the per-minute limit, and just over a day for the daily one — and once the day's key is gone, the code cannot be turned back into an address by anyone, including us. The code is never stored alongside your conversation, and your conversation is not stored on our servers at all.

We do not create an account for you, and we do not store your conversation on our servers. Your chat history lives only in your browser's local storage, where you can clear it at any time (see below).

QwenCloud's own documentation says that inputs and outputs are “processed in memory only during the request and are not stored in persistent storage after the response is returned”, and that it “does not retain your inputs and outputs for model training”. It also says metadata such as token counts, timestamps and request IDs is logged for billing and rate limiting. There is one exception in its documentation — conversations sent to its Responses API with storage switched on are kept for 30 days — and it does not apply here: Menda AI uses the chat completions endpoint and never asks for storage.

QwenCloud does not publish where it processes requests, so we are not going to name a country we cannot stand behind. If that matters to you, Guided Diagnosis answers the same kinds of questions and runs entirely in your browser — nothing is sent to us or to anyone else.

Those statements are QwenCloud's rather than ours, and they can change. The links are in the next section so you can check them instead of trusting this summary.

Logging

Your input is never logged. If the AI service returns an error, a short redacted fragment of its reply may appear in our host's operator logs — that is the only content that can end up in a log.

When you answer “Did this fix it?”

At the end of every fix there are two buttons, Yes and No. Pressing one sends us three things: which fix you were reading, your Yes or No, and the date — the day only, not the time. If you press No you can also leave a short note about what happened. That is all. There is no name, no email address and nothing to sign up for.

We ask you not to put personal details in the note, and if any slip in we remove them before the note is saved: links, email addresses, phone numbers, licence or product keys and serial numbers are all replaced with [removed] automatically. Notes are deleted after 12 months. The Yes and No counts are kept, because they are just numbers.

We don't set a cookie for this, store anything on your device, or save your IP address. To stop one person voting on the same fix over and over, your IP address is scrambled into a short code the moment your answer arrives, using a key that is thrown away and replaced every day. The code is only used to notice a repeat vote that same day; it is never saved alongside your answer, and once the key is gone it cannot be worked out again.

Why we collect it at all: a fix that quietly doesn't work is invisible to us otherwise. The Yes and No counts tell us which fixes to rewrite first, and the notes tell us what went wrong.

Services we rely on

Cloudflare

Cloudflare hosts this site (Pages), runs our API (Workers) and stores the “Did this fix it?” answers described above in its database service (D1). We have not enabled log export for this project, so request logs are not retained beyond Cloudflare's standard processing. We also collect anonymous aggregate usage statistics through Cloudflare Web Analytics, which is cookieless and does not track visitors across sites. See the Cloudflare privacy policy.

QwenCloud

The Qwen model that answers Menda AI runs on QwenCloud (qwencloud.com), operated by Intelligent Cloud Computing (Singapore) Private Limited. Your message is processed there to generate the reply. Its data-handling statements are on its own safety page, and its privacy policy and terms are its own, not ours.

What stays on your device

We set no cookies. The site does use eight browser local-storage keys so it can remember you between visits. None of them ever leave your device:

  • Appearance: emtech-theme — dark or light mode.
  • Menda AI session: emtech-ai-settings-v1 (your connection settings), emtech-ai-session-v1 (the current conversation), emtech-ai-history-v1 (past conversations), emtech-ai-feedback-v1 (a rating you gave).
  • Troubleshooter session: emtech-diag-session-v1 (the current diagnosis), emtech-diag-history-v1 (past diagnoses).
  • Progress: emtech-routine-v1 (the monthly routine checklist).

Clearing your browser data removes all of it. Two keys we used to set, emtech-feedback-v1 and emtech-done-v1, are gone: the features that wrote them have been removed, and the site now deletes the leftover keys from your browser on your next visit.

What we don't do

No advertising. No selling or sharing personal data. No tracking pixels, and no analytics scripts that follow you across sites.

Changes to this policy

If anything here changes in a way that affects you, we will update this page and note the date below.

Last updated: October 2026