WriteMyAIPromptFree, no sign-up

Privacy

WriteMyAIPrompt has no accounts, no cookies, and no third-party tracking. The prompt builder runs entirely in your browser, so what you type is never sent anywhere. Two things do leave your device, both described in full below: an optional AI polish you have to press a button for, and a handful of anonymous counters that contain no identifier and no part of your prompt.

The prompt builder

The compiler is a program that runs on your device. Your task, context, constraints and examples are never transmitted to this site’s server, because there is no server-side component involved in building a prompt. You can disconnect from the internet and the builder keeps working.

AI polish sends your prompt to DeepSeek

The optional Polish with AI button is the one feature that transmits your prompt off your device. When you press it, the compiled prompt is sent to DeepSeek, a third-party AI provider, which rewrites the wording and sends it back. Do not use it for anything confidential.

There are two routes, and which one you use changes who sees what:

  • The free daily allowancepasses your prompt through this site’s server to reach DeepSeek. The prompt text is held in memory for the duration of the request and is never written to disk, never logged, and never stored.
  • Your own DeepSeek keymeans your browser talks to DeepSeek directly. Neither your key nor your prompt touches this site’s server at all. The key is stored only in your browser and you can remove it at any time.

DeepSeek handles that data under its own privacy policy, which this site does not control.

If your prompt contains a web address, the builder offers to read that page and use it as context. This is off unless you tick the box. When you do, this site’s server requests the page — so the site you named sees a request from this server, not from you — and the text is passed to DeepSeek along with your prompt. The page is never stored, and the server refuses any address that is not publicly reachable.

How the free allowance is counted

To stop one visitor exhausting the shared allowance, the server counts requests per day. It stores a salted, truncated hash of your IP address alongside a number — never the address itself, and never anything about the prompt. Those counters are deleted after two days. The hash uses a per-installation salt, so it cannot be matched against anything outside this site.

What is stored in your browser

Two things, both in local storage, both only on your device, and neither ever transmitted to this site: your last twenty prompts, so you can return to them, and your DeepSeek API key if you chose to add one. Clearing your browser data removes both, and the builder has a Clear all button for the history.

Share links encode a prompt into the part of the URL after the #. Browsers never send that fragment to the server, so a shared prompt is readable by whoever holds the link and by nobody else — including this site.

Analytics and cookies

No cookies, no fingerprinting, no advertising, no social embeds, and nothing loaded from a third-party domain. There is no cookie banner because there is nothing to consent to.

There is one thing worth describing precisely. The builder and the improver — the two pages that run code at all — send a small number of counters so it is possible to tell which models people target and roughly how their prompts score. What is sent is a short list of fixed labels such as model.claude or score.65-84.

What is not sent: your prompt, any part of it, your IP address, your browser, or any identifier at all. Two visits from you are indistinguishable from visits by two different people, and the server discards anything not on a fixed list of permitted labels. The result is a daily tally of numbers and nothing else. Every other page on this site sends nothing whatsoever.

The web server also keeps ordinary access logs, as every web server does.

Questions about any of this are answered in more technical detail on how it works.