Privacy
This notice says what module.monster stores about you, why it holds it, who else sees it and how long it stays. It is written from what the software actually does, so there is nothing here that the service does not do and nothing it does that is not here.
Who is responsible
module.monster is run by the operator of this service, who decides what is collected here and answers for it. Every request about your data — a question, a correction, a copy of it, or a demand that all of it be deleted — goes to [email protected] and is dealt with by a person.
Last updated 15 August 2026. This describes the service as it is built today. It is a beta and it changes; when what it stores changes, this page changes with it.
What an account holds
Signing up stores one record about you. This is all of it:
- Your email address, stored in lower case. It identifies the account and is what you sign in with.
- A bcrypt hash of your password, never the password itself. The hash cannot be turned back into what you typed, and an account that only signs in with Google has no password stored at all.
- A display name. If you do not give one, the part of your email before the @ is used instead.
- Which of the 16 interface languages you chose, so the portal comes back in it next time.
- How many builds you have left, and whether the account is still active.
- When the account was created, and when it was last used — a timestamp refreshed each time you open your modules.
That is the whole record. There is no phone number, no postal address, no date of birth and no payment card in it, because the portal never asks for any of them.
If you sign in with Google
The Google button is optional, and password sign-in never depends on it. If you use it, you type your Google password on Google's own pages: this service never sees it and never receives it. What comes back is three things — Google's permanent identifier for your account, your email address, and the name on your Google profile.
The identifier is stored so the next sign-in lands in the same account. If that email address already has an account here, the two are linked rather than a second account being made. An address Google has not verified is refused outright, so nobody can take over an account by claiming an email they do not own.
What you write, and where it goes
Describing a module stores that description, every message in the conversation about it, and every reply the agent sends back. Stored beside it is what you picked in the composer: the PrestaShop versions to target, the languages the module should ship in, and whether it has to work on a multistore install.
A reference screenshot you attach is saved as a file on the server in a folder belonging to your account, and its location is included in the text handed to the agent. Only real images are accepted — the check reads the first bytes of the file rather than trusting its name.
Your description and your messages are the input to the build itself. They are sent to Anthropic's API, which is what scopes, writes, tests and documents the module. That is not a side effect of the service, it is how it works: there is no way to have a module built without it.
Server logs and abuse limits
The server writes a line when someone signs up or signs in, including the email address it was for, and a line when something fails. Those lines exist so a fault can be diagnosed and so an attack can be told apart from ordinary use.
Your IP address is used to limit how often sign-in and sign-up can be attempted from one place. It is held in memory for the length of that window — five minutes for sign-in, an hour for sign-up — and is not written to the database.
Why we are allowed to hold it
In plain words, two reasons cover everything above.
- Because you asked for the service. Your account, your descriptions, your conversations and the modules built from them exist because you asked for a module to be built. Without them there is nothing to sign in to and nothing to build.
- Because the service has to stay standing. Hashing passwords, expiring sessions, limiting sign-in attempts and keeping error logs serve the narrow interest of this service not being broken into or knocked over. None of it is used to learn anything about you.
Nothing here is used for advertising, profiling or scoring, and none of it is sold. There is no marketing mail either: the software has no way to send you any, so there is no list to be on and nothing to unsubscribe from.
Cookies
Three cookies, all set by this site for the site to work. There is no advertising cookie, no analytics cookie and no tracking script anywhere on this site, and nothing here is shared with a third party for their own purposes.
ms_session — keeps you signed in
Set when you sign in. It holds a random token rather than anything about you: the record of who is signed in lives on the server, and only a hash of the token is kept there, so a stolen database row cannot be replayed as a cookie. It lasts 30 days, cannot be read by scripts in the page, and is deleted the moment you sign out. Refuse it and every public page still works, but you cannot sign in — there is no other way for the next request to be recognised as yours.
ms_locale — remembers your language
Written when you pick an interface language, and kept for a year. It holds a language code and nothing else. Refuse it and nothing breaks: the language is part of the address of every page, so a link you follow or bookmark stays in its own language, and otherwise the portal falls back to the language your browser asks for.
ms_oauth_state — the Google round trip
Written only if you press the Google button, and gone ten minutes later. It holds a random value that has to come back from Google unchanged, which is what stops a stranger sending you a sign-in link that quietly lands you in their account. Refuse it and Google sign-in cannot finish; signing in with a password is unaffected. It also carries the page you were heading for, so signing in lands you back where you started.
One thing is kept in the browser without being a cookie: an idea typed on the front page before you have an account is held in that tab's own storage so it survives the trip through sign-up, and is thrown away as soon as it has been used.
Who else handles it
Two companies, each for one job:
- Anthropic, whose API runs the agents. Module descriptions and the conversations about them are sent there to be scoped, built, tested and documented. This applies to every module.
- Google, only if you choose to sign in with it, and only for that sign-in. If you never press that button, nothing about you reaches Google from here.
Both are companies based in the United States, so a description sent to be built is processed outside the EEA. Apart from those two, your data stays on the server that runs this service.
How long it is kept
What the software deletes by itself is short and specific:
- A sign-in session expires after 30 days, and its row is deleted the first time it is seen after that. Signing out deletes it at once, and signing out everywhere deletes every session on the account.
- A conversation you opened and never wrote in is deleted, along with the working folder behind it.
Everything else — your account, your modules, your messages, the screenshots you attached and the modules that were built for you — is kept until you ask for it to be removed. This page will not quote a period it does not keep to: no automatic deletion schedule for that data exists in the software today. Delete account, on the account page, removes the account, its drafts and your screenshots whenever you decide to; the modules already built stay, with nothing left tying them to you. Write to [email protected] if you want those gone as well.
What you can ask for
If you are in the EU or the UK, data protection law gives you the rights below, and they are honoured wherever you are:
- Access: a copy of what is held about you, and what each part of it is for.
- Rectification: anything wrong put right. Your name and your interface language you can change yourself, on the account page, at any time.
- Erasure: your account and everything attached to it deleted. Delete account, on the account page, does this yourself — it removes the account, its sessions, its drafts and your screenshots, and cuts every link between you and the modules already built.
- Portability: the data you gave us handed back in a form you can take elsewhere.
- Objection and restriction: an objection to a particular use, which stops it unless the service cannot run without it.
All of them go to the same place. Write to [email protected] from the address on the account, say which one you want, and a person deals with it. There is no form to fill in and nothing about it is automated.
If you are not satisfied with how a request was handled, the law in the EU and the UK also gives you the right to complain to the data protection authority for the country you live in.
A question about any of this, a correction, or a request to delete everything — the same address answers all three.
Email us about your data