ERMAZ Privacy Policy

Who we are. Ermaz LLC, a limited liability company formed in the State of Wyoming, United States, is the controller of the data described in Part 1. You can reach us about anything on this page at privacy@ermaz.app. There is no separate privacy team; that address reaches the operator.

Ermaz LLC manufactures websites from a description of your business, and hosts them. There are two different privacy relationships here, and this policy separates them because the difference decides who is answerable to whom.

Put plainly: if someone fills in the enquiry form on a site Ermaz built for a plumber, those details belong to the plumber's relationship with them. Ermaz delivers and stores that enquiry for the plumber, and does not use it for anything of its own.

Part 1, Data about you, our customer

What we collect

• What you tell us, the description of your business you give in the conversation. It is sent to OpenAI to design your site, and stored so the site can be revised or explained later. Do not put personal data about other people into it; it does not need any.
• Your account, the email address you sign in with, verified through Google or a sign-in link. Sign-in establishes who you are; it does not give us access to your Google account contents.
• Your subscription, an internal reference, what you are entitled to, and when payment events happened. Payments are processed entirely by Paddle, our merchant of record. We never see or store card numbers. Paddle shares your email so we can attach the subscription to your account.
• Operational records, logs of manufacturing runs and requests, including IP address, kept for security, abuse prevention and working out what went wrong.

What we don't do

No advertising, no tracking pixels, no analytics cookies, no profiling, and no selling or sharing of your data with anyone beyond the processors named on this page.

Why we are allowed to hold it, and for how long

• Performance of a contract. Your account email, what you tell us about the business, and your subscription are held because the service you bought cannot run without them.
• Legitimate interests. Operational records, including IP address, are held to keep the service secure, prevent abuse and work out what went wrong. We keep them for 12 months.
• Legal obligation. Billing and tax records are kept for as long as the law requires, which is longer than the rest.
• Retention of account data. We keep your account data while your account is open, and for 12 months after you close it or after your last subscription ends. Then we delete it, apart from the billing records we are required to keep.
• Sign-in codes. An email sign-in code expires 15 minutes after it is sent.

Your rights over data about you

These rights cover the data in Part 1, where Ermaz LLC is the controller. Email privacy@ermaz.app and we will answer within 5 working days. We do not charge for any of them.

• Access. Get a copy of what we hold about you.
• Rectification. Have anything wrong corrected.
• Erasure. Have it deleted, once we no longer need it to run a service you are paying for or to meet tax law.
• Objection. Object to any processing we base on legitimate interests.
• Portability. Receive your data in a standard machine-readable format.
• Restriction. Have processing paused while a dispute about accuracy or grounds is settled.

Export is request-based. Email privacy@ermaz.app and we will send your account, your builds and your enquiries in a standard machine-readable format, normally within 5 working days, at no charge.

Complaints. Tell us first and we will try to put it right. You can also complain to a data protection supervisory authority without going through us. In the EU that is the authority in the country where you live, work, or where the problem happened. In the UK it is the Information Commissioner's Office.

AI and automated replies

Two parts of this service are done by a language model rather than a person.

• Manufacturing. What you tell us about the business is sent to OpenAI to design your site, as set out in Part 1.
• Automated first replies. If you subscribe to Website Care, Ermaz answers inquiries that arrive through your website. The reply is generated by a language model, not written by a person, and it is sent on your behalf under your business name. The message tells the recipient that the reply is automated. The inquiry text and the contact details in it are processed to produce that reply and nothing else. You are the controller of those inquiries and Ermaz is the processor. Cancelling Care stops it.

Part 2, The enquiries your site collects

Our role

When a visitor sends the contact or booking form on your site, Ermaz processes that enquiry only to deliver it to you and keep your copy of it. On this we act on your behalf, as your processor: we do not use enquiries for our own purposes, do not sell them, do not use them to train models, and do not read them except where necessary to run the service or where you ask us to. You are the controller of the people who contact you; Ermaz is the controller only of your own account.

What is collected, and what is not

• The enquiry itself, whatever the visitor types into the form (typically a name, a way to reach them, and their message), plus up to four photographs where the form invites them.
• Your account, the email address you sign in with, and the sites you have made.
• Visitor numbers, not visitors. Your site counts page views with a first-party beacon that sets no cookies, stores nothing on the visitor's device and keeps no IP addresses. There is no profile of any visitor, which is why your site needs no cookie banner. You can switch counting off from your account.
• Cookies. Your finished site sets none. The Ermaz account uses one strictly-necessary session cookie when you sign in; it tracks nobody across sites.

How it is kept separate

Your builds and the enquiries they collect are reachable only by the account that made them. Ownership is checked on the server for every request, so one owner cannot see another's enquiries. Your finished site is static, with no database and no login on it, so there is no shared store of customer records to leak in the first place.

Your obligations as controller

• Have a lawful basis for the enquiries you collect, and tell the people who contact you what happens to their data. Every Ermaz site ships with a privacy notice in the visitor's language for this; keep it accurate to how you actually use enquiries.
• Only ask for what you need. Ermaz builds the form you describe; it does not decide what you should gather.
• Handle requests from those people (access, correction, deletion). Ask us for anything you cannot do yourself and we will help.

Sub-processors

We will tell you before adding a sub-processor that handles your enquiries.

Retention and deletion

• Your enquiries are kept in your records so you can read them again. Photographs attached to an enquiry are kept for 90 days and then removed.
• Export or deletion is request-based. Email privacy@ermaz.app and we will export your account, your builds and your enquiries in a standard machine-readable format, normally within 5 working days, or delete them entirely. Deletion is irreversible.

Where data is held

Your account, your builds and your enquiries are stored on Railway infrastructure in the United States. Ermaz LLC is a Wyoming company and operates from the United States. Your finished site is served from Netlify's content network.

If you or the people in your records are in the UK or EEA, that is an international transfer. Where a transfer mechanism is required, it relies on the Standard Contractual Clauses approved by the European Commission, and the UK Addendum for UK transfers. The same clauses are the basis on which our sub-processors handle transfers. Say so in your own privacy notice, because your users read yours, not ours.

Breaches

If we become aware of a security incident affecting your account or your enquiries, we will tell you without undue delay and with what we know, so you can meet your own notification duties. We would rather report an incident that turns out to be minor than be quiet about one that isn't.

Changes

We'll update this page if our practices change, and tell you about anything significant. Last updated: August 2026.