Privacy notice
This notice explains what we do with your personal data when you create a Moorhold account to download Moorhold. It covers account.moorhold.dev and the Moorhold image registry only.
This account is separate from your organisation's Moorhold portal. The portal runs on your organisation's own servers, and your organisation controls the data in it. We never see it.
Who we are
Allotment Technology Ltd is the data controller. We are registered in England and Wales (company number 16925574) and with the Information Commissioner's Office (registration ZC092549).
Contact us about privacy at privacy@moorhold.dev.
What we collect
- Your email address, to identify you, verify you and send you service emails.
- Your name, if you choose to give one.
- Your organisation's name and your role in it.
- Your organisation's country, which we ask for when you create your organisation, so that we can check it against UK sanctions. We keep it with a record of the sanctions declaration you tick: when you ticked it, and which version of its wording you saw.
- Which version of the account terms you accepted, and when.
- Where you plan to run Moorhold. If you choose, the kind of server you will use, the hosting company if you rent one, and which of the steps for getting your server ready you have ticked. We keep this with your account, so it is still there when you sign in on another device. It describes your plans. We never see your server. Before you sign in, this site holds the route from the link you came by in your browser's session storage, so that it can pass it to your account when you do. That copy stays in the tab and goes when you close it. It isn't a cookie.
- Your passkeys. We store only the public part of each passkey, and a label. If your device unlocks a passkey with your fingerprint or face, that stays on your device and we never receive it. We do not use passwords.
- Your access keys. We store an identifier, a label and a one-way hash. We show you the key once and cannot show it again.
- Invitations. A one-way hash of each invitation link, and its expiry.
- Your organisation's plan. If an owner buys Server care, we keep what Paddle tells us about it: that Server care was bought, whether it's paid up, paused or cancelled, when it ends or ended, and Paddle's own reference numbers for the customer and the subscription. We don't keep card or bank details, or the name and address given to Paddle. When your server checks its plan, it sends its access key and its Moorhold version. We record the key's use like any other, and we don't keep the version.
- An enquiry about Hosted, Team or Partner. If you use the form on our site, we keep what you type into it: your email address, the plan you ask about, what you'd use it for, your team size, platform, preferred region and when you'd want to start, and your name, organisation and budget if you give them. We also keep whether you ticked "Contact me about this", which you must do to send the form, whether you ticked "Send me occasional Moorhold product news", and which version of those words you saw. We don't keep your IP address with the enquiry. Our server holds it in memory for up to an hour, to limit how often one network can send the form, and never writes it down. Our server logs, described below, record the request as they record any other page.
- Security records. When a key is used, we record the time and the IP address it came from. We keep the IP address for 30 days. We also keep a log of security events, such as a key being created or a passkey being added. It does not contain your email address or IP address.
- Server logs. Like every website, our servers log each request's IP address, page and browser type. We delete the logs after 30 days. When our front server in Germany shows a holding or outage page, it keeps its own short log of the IP address and the page requested, and deletes it automatically after 30 days.
We do not collect payment details. We use no analytics tools, no advertising and no tracking. The only third-party script is Paddle's checkout, which your browser loads from Paddle only when an owner chooses to upgrade. We set only the cookies that are strictly necessary to keep you signed in and to complete a passkey sign-in. They are not used for anything else.
We count, in total and with no information about who you are, how many times the form is viewed and how many enquiries are sent for each plan.
Why we use it, and our lawful basis
| What we do | Lawful basis |
|---|---|
| Run your account, verify your email, sign you in with passkeys, manage your organisation and its members, approve organisations, automatically or after review, issue and revoke access keys, show you the guide and checklist for the kind of server you chose, and send you service emails | Contract. We do this to provide the service under the account terms that you accept, and to take the steps you ask for before that. |
| Record your organisation's plan from Paddle, and let owners buy, change or cancel Server care | Contract. We do this to provide the plan your organisation chose. |
| Check your organisation's country, and the sanctions declaration you tick when you create your organisation, against UK sanctions | Legal obligation: complying with UK sanctions law. Where it isn't a legal obligation, legitimate interests: not supplying the software where UK sanctions may forbid it. |
| Look up which country a download request comes from, using its IP address, so that we can refuse downloads from some countries because of UK sanctions | Legal obligation: complying with UK sanctions law. Where it isn't a legal obligation, legitimate interests: not supplying the software where UK sanctions may forbid it. We don't keep the country. The request is logged like any other. |
| Keep security records, limit abuse and investigate incidents | Legitimate interests: keeping the service and your keys secure. You can ask us for the balancing test we did. |
| Reply to your enquiry about Hosted, Team or Partner; and, only if you tick the separate box, send you occasional product news | Consent. Replying: your consent, given by ticking "Contact me about this". Occasional product news: your consent, given by the separate tick and withdrawn at any time by writing to privacy@moorhold.dev. |
We approve each new organisation before it can create its first access key, either automatically when its checks pass or after a person at Moorhold reviews it. Only a person refuses an organisation. If we refuse, we tell you, and you can reply to ask us to look again.
If an organisation's keys pull far more than usual, we may refuse its downloads or suspend its keys automatically. If we do, we use only how many download tokens each key asks for each day, kept by key with no IP address or email address. We tell the organisation's owners, and a person at Moorhold looks at it again if an owner asks.
The few people at Moorhold who run the service can see accounts, organisations, their members and their keys (never a key itself), to support you and to act under the account terms: for example to suspend or restore an organisation's downloads, revoke a key, remove a member who has left, or delete an account when you ask. Each such action is recorded with its reason, and we email the people it affects.
We don't send you marketing, except the occasional product news you ask for by ticking the separate box on the interest form.
Who we share it with
We share your data only with the companies that help us run the service, under contracts that protect it:
- Hetzner Online GmbH runs our front server and our backups in Falkenstein, Germany, and our DNS. The front server passes your encrypted connection straight through to our own server without decrypting it.
- Migadu-Mail GmbH, a Swiss email provider whose mail servers are in the EU, sends our emails to you: verification and recovery codes, notices about your account and keys, and replies to enquiries.
- Paddle.com Market Limited, in London, sells Server care for us as our reseller and handles the payment and VAT. An owner who buys gives their name, email address, address and payment details to Paddle directly, in Paddle's checkout, and Paddle's privacy notice covers what Paddle does with them. We send Paddle your organisation's Moorhold reference, so the subscription reaches the right organisation, and Paddle's customer reference when an owner opens Paddle's customer portal from this site. Any owner of the organisation can open that portal. It shows the invoices, billing details and payment card ending of whoever bought Server care.
We do not sell your data or share it with anyone else, unless the law requires us to.
Where it is stored
On our own server in the UK, with our backups in the European Union (Germany), and with Migadu in Switzerland and the EU. If our own server is down for a long time, the service may run temporarily on a Hetzner server in the EU (Germany or Finland). The UK recognises the European Union and Switzerland as providing adequate protection for personal data.
How long we keep it
| Data | How long |
|---|---|
| A sign-up whose email is never verified | 7 days |
| Your account, passkeys, memberships, record of accepting the terms, and the route and ticked steps you chose | Until you delete your account, then removed within 30 days |
| An access key's hash | Until the key is revoked or expires (keys expire after 12 months) |
| A revoked or expired key's record | 30 days |
| The IP address of a key's last use | 30 days |
| Invitations | Until they expire (7 days) |
| Security event log (no email address or IP address) | 12 months |
| Your organisation's plan, with Paddle's references | While the organisation exists; a cancelled subscription's record 30 days after it ends |
| Paddle's notices to us (their reference and type only) | 90 days |
| An enquiry from the interest form | 12 months from the day you send it, then the copy in our database is deleted. If we have started talking, we keep it for as long as the conversation lasts. Emails about an enquiry are deleted 12 months after the last message, unless you become a customer. |
| Server logs | 30 days |
| Backups, including the encrypted nightly copy | 30 days |
Deleted data disappears from backups within 30 days of deletion.
Your rights
You can:
- see the data we hold about you, and download it, from your account page;
- correct your display name from your account page, or ask us to correct your email address;
- delete your account from your account page;
- object to our security records, or ask us to restrict how we use your data;
- ask us for anything else about your data by writing to privacy@moorhold.dev.
We reply within one month. We may ask you to sign in, or to reply from your account's email address, to confirm it is you.
Complaints
If you are unhappy with how we have handled your data, write to privacy@moorhold.dev. We will acknowledge your complaint within 30 days and tell you what we have done about it.
You can also complain to the Information Commissioner's Office: ico.org.uk/make-a-complaint, or 0303 123 1113.
Changes
If we change this notice in a way that matters, we will tell you by email before the change takes effect.