Privacy policy

Updated 12 November 2026.

What you make stays with you

Your plans, layouts, finishes, furniture and pictures are kept in your browser's storage and in the project files you save, never on {app}'s server. We can't see them, so we can't lose, share or sell them.

What we keep about you

For your account: your email address, the language of our emails, the plan you're on, the version of the terms you accepted and when, when the account was made, the day you last signed in (and, after two years without one, the day we warned you), and, if you set one, your password, kept only as a one-way hash. You may add a display name. For each signed-in browser, a session: when it began and was last used. For each AI agent you connect, or key you make for one: the name the agent gave or you gave the key, when it was connected and the day it was last used, its tokens kept only as one-way hashes. For a sign-in link not yet opened: the address it went to. Sign-ups, changes of address or password, connected and disconnected agents, and deletions are noted in an audit log, with the account's number and the time only.

We keep these to give you the account you asked for (a contract, GDPR Article 6.1.b), and the audit log and the request records below to keep the service secure and running (our legitimate interest, Article 6.1.f).

How long

What the server records

For each request: the time, the page or file asked for, the answer's status and how long it took. Not who you are, not your IP address, and nothing you type or search. These records keep the site running and are deleted after 30 days, on the server and in the monitoring that watches it. The rate limits that stop someone guessing passwords remember an IP address or an email address for at most an hour, in memory only.

Which features are used

To decide what {app} offers for free and what for a fee, we count which features are used, in anonymous totals. When you use one (the 3D view, Place on the map, rendered pictures…), the page tells the server its name and nothing else: not your plan, not what you did with it. The server adds one to that day's count for the feature, and one to the number of accounts that used it that day. To count each account once a day, it remembers a code made from your account with a key drawn at random each day, in memory only, and forgets both when the day ends. The counts say nothing about who: we keep them for two years, for our legitimate interest in deciding what to build (Article 6.1.f). No cookie and nothing in your browser's storage serves them, and no other company sees them.

Feedback

If you send a suggestion or a bug report with the Feedback button, we keep what you wrote, whether it's an idea or a bug, the release of {app} and your browser's name and version, with your account, so we can read it, fix what's wrong and answer you by email. Never your plan. We're emailed that a message came, and nothing of it. This is our legitimate interest in improving {app} (Article 6.1.f). A message goes after 12 months, when you delete your account, or sooner if we delete it.

Gifts

If you give to {app} through the links in the help, the gift goes from you to Revolut or from your Bitcoin wallet, under their own terms and policies. Our server knows nothing of it, and a gift is never tied to your account. Revolut shows us the name you choose to show and the amount; a Bitcoin gift, only the amount and the sending address, which the blockchain makes public anyway. We keep these only where Revolut and the wallet keep them, and copy them nowhere.

Cookies

One cookie, set when you sign in, which keeps you signed in. It's needed for the service to work, so we don't ask for consent. No analytics service, no advertising, no tracking, and no other site's scripts or fonts.

Who else sees anything

OVHcloud (France) hosts the server, its database, its backups and the email that sends your sign-in links, in France, as our processor. OVHcloud may involve its own companies in the United Kingdom and Canada to run these services; the EU recognises that both countries protect personal data adequately.

OpenStreetMap. Place on the map asks OpenStreetMap's services straight from your browser: the search and the map's tiles from the OpenStreetMap Foundation, the buildings around from overpass-api.de. They see your IP address and what you search, under their own rules (the Foundation's privacy policy). Our server never sees those requests.

An AI assistant, such as Claude, ChatGPT or Le Chat, if you connect one: it receives what you ask it to read from the plan you have open, in your own account with it and under its own policy. Our server passes those requests along to your page and keeps nothing of them.

Nobody else. We never sell or share your data.

Your rights

You can see, download, correct and delete everything we keep about you yourself, from your account. To object to what we keep for our legitimate interest, ask us to limit it, or anything else, write to privacy@redomus.app: we answer within a month. You can also complain to your data protection authority (in France, the CNIL).

Who is responsible

{app} is run by Khaled ARSALANE, an individual in France, the controller of this data. Write to privacy@redomus.app. If data we keep is ever breached in a way that puts you at risk, we tell the CNIL within 72 hours, and you too.

When this policy changes, its date above changes, and a change that matters is shown when you next sign in.