Build Emma — Privacy

What we collect is short, so this page is too.

Version 1.0 — 16 September 2026

The short version

• Build Emma the app sends us nothing. No telemetry, no analytics, no account, and your code never comes to us.
• The website has no cookies, no analytics and no tracking.
• When you buy, we receive your name and email address so we can make your licence key and send it to you. That's all.

The app

Your code, your files, your conversations with EMMA and your settings stay on your computer. There is no server of ours that Build Emma talks to.

It only reaches the internet in these cases, and every one of them is a connection between your computer and a service you chose:

• Update checks — on launch, Build Emma asks our public release page on GitHub whether a newer version exists. Nothing about you or your work is included; GitHub sees an ordinary request from your internet address. Turn it off in Settings → Updates.
• Cloud models, if you add a key — if you connect Claude (Anthropic) or OpenAI with your own API key, what you send to that model goes to that company, under their privacy terms. Local models through Ollama never leave your machine.
• Plugins, if you install one — it is downloaded from wherever it is published.
• Sessions, relays and remote development, if you set them up — they connect to the people you approve on your network, or to servers you own.
• Crash reports — kept on your computer. Nothing is sent unless you set a destination yourself in Settings.

Your licence key is checked offline, on your computer.

The website

buildemma.com sets no cookies and runs no analytics. It is hosted by Netlify, which, like any web host, keeps short-lived technical logs of requests (such as internet addresses) to run and protect the service.

When you buy

• Payment is handled by Onelink, powered by Stripe. They process your payment details, billing information and anything needed for tax; we never see your card number. Their privacy policies cover that.
• We receive your name and email address. They are written into your licence key — that is how Build Emma shows whose licence it is — and used to email the key to you.
• The email is sent through Resend, which processes your address and the message to deliver it.
• Our key service runs on Railway. It keeps no database; its short-lived logs record the order number and the email address the key was sent to, so a missing email can be traced.
• If you email us, your message is kept in our inbox (Proton Mail) so we can help.

We don't sell your information, send marketing emails, or share it with anyone except the services above, and only to do what's described here.

How long

We keep purchase records for as long as the law requires for tax and accounting (in the UK, 6 years), and emails for as long as they're useful to support you.

Your rights

Under UK data protection law you can ask to see the information we hold about you, to correct it, or to have it deleted where we're not required to keep it. Email Gregorymoores@proton.me. If you're unhappy with how we've handled your information, you can complain to the Information Commissioner's Office (ico.org.uk).

Who we are

Build Emma is made by Gregory Moore, a sole trader in the United Kingdom, who is responsible for your information (the "controller").

Contact: Gregorymoores@proton.me