Last updated 20 October 2026.
Bloomprint is a garden design tool. This page says what it stores about you, why, who else sees it, and how long it is kept. It is written from what the software actually does, and when the software changes, this page changes with it.
Who is responsible for your data
Nick Whiteley, trading as Bloomprint, is the controller of the personal data described here. For anything on this page, email privacy@bloomprint.uk.
What we store, and why
| What | Why | Lawful basis |
|---|---|---|
| Your account: your email address, your display name if you set one, and a hashed form of your password (never the password itself). If you sign in with Google, the identifier Google gives your account and the email address it confirms | To let you sign in and to identify your gardens as yours | Contract |
| Whether your email address is confirmed, and when | So that sharing and a second garden reach a real address | Contract |
| Your gardens: the designs you draw, and the named checkpoints you save | This is the service | Contract |
| Sharing: who you have given access to a garden, and at what level | So the people you share with can see it | Contract |
| Your plan and payments: which plan you are on; the payment provider's references for your customer record, subscription and payments; the amounts and dates; and your card's type and last four digits as the provider reports them. Never your card number, which is entered on the provider's own page | To bill you, and to keep the records the law requires | Contract; legal obligation (tax records) |
| Feedback you send, with the page you sent it from | To read it and act on it | Legitimate interests (improving the product) |
| Messages you send to support, from the support page: what you write, and the details we attach so we can answer — your account, your email address and whether it is confirmed, your plan and its state, and the page you came from. They go to our support inbox by email, and we keep a copy like every other email we send | To answer you | Contract; legitimate interests (support) |
| Corrections you suggest on a plant's page: what you suggest and why, your email address if you choose to give one, and the network (IP) address it was sent from | To review the correction and, if you gave an address, to reply; the network address stops one sender flooding the review queue | Legitimate interests (an accurate catalogue, and preventing abuse) |
| The emails we send you: the address each went to, what it was about, when, whether it was sent, and its text — except an email carrying a sign-in or confirmation link, whose text we never keep | So we can answer "did you send me that?", and prove we sent the notices the law requires | Legitimate interests (support); legal obligation (notices about your subscription) |
| The launch list, if you join it: your email address, the page you joined from, and when. Nothing else — not your name, and it is not linked to an account | To send you the one email you asked for, when Bloomprint Pro opens | Consent, which you can withdraw at any time with the link in the email or on the leave page |
| A history of changes to the above | So we can tell what happened and when, and put things right | Legitimate interests (security and accountability) |
| When you last signed in | So administrators can see which accounts are in use | Legitimate interests |
Cookies and your browser
At most three cookies, all strictly necessary, which is why there is no cookie banner. The cookies page lists them, with what your browser stores for the editor.
What we count
Three things, for ourselves, on our own servers:
- which page an account signed up from;
- how many gardens reach a printed sheet;
- how many sheets each account prints.
We also record when making a sheet fails, so that we find out rather than you. No cookie is set in order to count any of it, none of it is shared, and we keep these counts for 13 months.
We also count visits to the pages that are open to anyone: the home page, the plant catalogue,
pricing, the help and legal pages, and the pages for signing up and signing in. That is done
by Vercel Web Analytics, which sets no cookie and does not follow you from
one site to another. It sees the address of the page, where you came from, and broad details
such as your country, browser and device type. We drop anything after a ? in the
address before it is sent. It is never loaded on a page you reach by signing in (your gardens, the editor, your profile), on a link to a plan, or on an email link such as
confirming an address or resetting a password.
Links to a plan
A practice can send a client a link to a plan, which opens without an account. Whoever holds the link can see what the practice chose to send: the plan, the planting schedule and the title block, and the practice's name and logo. They cannot see its notes, its prices or where the garden is. The link shows the plan as it was when it was sent, and the practice can turn it off or replace it whenever it likes.
Opening a link records nothing about the person who opened it. It sets no cookie, counts no visit and tells the practice nothing. The page is not listed by search engines. A practice that shares a client's plan is responsible for sending the link to the right person.
What we do not do
- No advertising or tracking services, and no third-party script other than the page counter described above, which runs on open pages only.
- No visitor profiles, and no record of what you do once you are signed in: not the pages you open, not what you draw.
- No advertising, and no selling or sharing of your data.
- No IP addresses in our request logs, which record the page, the method and the result. There are two exceptions. A brief in-memory count per address slows down anyone trying to guess passwords or flood a form, and is never written anywhere. And a correction you suggest on a plant's page keeps the address it was sent from, as described above.
- Error reports never carry your data. When something breaks, the report we receive is built to exclude passwords, session details, email addresses and the contents of what you sent.
Who else processes it
A small number of suppliers help run the service. They process data on our instructions and for no other purpose.
| Supplier | What for | Where |
|---|---|---|
| Neon | The database your account, gardens and billing records are stored in | UK |
| Vercel | Hosting the site, and storing catalogue photographs | UK |
| Vercel Web Analytics | Counting visits to the pages open to anyone, as described above | USA |
| Postmark | Sending email: password reset links, address confirmation links, sharing notices, billing notices, renewal reminders, and the messages you send to support | USA |
| Only if you choose to sign in with Google. Our support inbox is also hosted by Google Workspace | USA | |
| GitHub | Keeping our nightly backups, which are encrypted before they reach GitHub, with a key GitHub does not hold | USA |
Where a supplier is outside the UK, the transfer is protected by standard contractual clauses and a data processing agreement with that supplier.
How long we keep it
| What | For how long |
|---|---|
| Your account and gardens | Until you ask us to remove them (below) |
| Backups | 90 days, then deleted automatically. A garden you delete is gone from the backups within 90 days |
| Payment records | Six years after the tax year they relate to, as HMRC requires |
| Counts (above) | 13 months |
| The history of changes | Kept as a record, and deliberately not editable by the application — that is what makes it reliable. When we remove your account, we remove the entries that identify you by hand at the same time |
| Feedback | Two years |
| Messages to support | In our support inbox, two years after the conversation ends. Our own copy of the email, 90 days |
| Corrections you suggest | Kept with the correction, including the network address and any email address you gave, as the record of where a change to the catalogue came from. Ask us and we will remove your details from it |
| The emails we send you | Notices the law requires, such as renewal reminders and confirmations of your subscription, six years. Everything else, 13 months. The text of a sign-in or confirmation link is never kept at all |
| The launch list | Until the launch email has gone to everybody on it, then deleted — by us, or automatically 60 days after the last one is sent. The record that the email was sent to your address is erased at the same time |
Your rights
You can ask us for a copy of the personal data we hold about you, to correct it, to delete it, to restrict or object to how we use it, or to have it in a portable form. You can export any of your gardens yourself, from the editor, at any time. You can change your own name and password from your account page.
Deleting your account. There is no self-service delete button yet. Email us and we will remove your account and gardens by hand, within 30 days. We would rather say that plainly than offer a button that does not do what it claims.
We reply to every request within a month.
If you are unhappy
Tell us first, at privacy@bloomprint.uk, and we will look into it and reply within 30 days. You also have the right to complain to the Information Commissioner's Office at any time.