What we collect through the waitlist form, and what we do with it.

DueNotice is a solo-operated, pre-launch UK project. Full company registration details will appear here before the product goes live; until then, the contact point below reaches the person running it.

• Your email address — so we can tell you when it’s your turn to sign up.
• What you take payments with — so we can prioritise building support for it.
• A one-way hash of your IP address, kept separately and only to stop the form being used to spam that list — never your actual address, and never linked to the email you gave us.

We don’t collect anything else: no name, no company, no tracking cookies, no analytics script on this page. The legal basis is your consent — submitting the form is you asking us to hold this email for this purpose, and you can withdraw that consent at any time (see below).

In our database (Neon, PostgreSQL), hosted in London. We don’t share it with anyone else, and we don’t use a mailing-list or CRM tool that would mean a third party holding a copy.

Up to 24 months from the date you sign up, whichever comes first with you asking us to delete it sooner. This isn’t an aspiration — a scheduled job actually deletes anything older than that on its own, every day, the same way the rest of this product treats a deadline as something code enforces rather than something someone remembers. The IP hash mentioned above is kept for a much shorter 30 days, since it has no purpose beyond that short a window.

Email privacy@duenotice.app to ask what we hold about you, to correct it, or to have it deleted — we’ll act on a deletion request within 30 days. Because a waitlist entry is just an email address and an answer to one question, there is nothing to export in a more useful form than that. You can also complain to the UK’s data protection regulator, the Information Commissioner’s Office, if you think we’ve got this wrong.

DueNotice’s core product keeps an append-only, hash-chained evidence record of the statutory notices it sends on a merchant’s behalf — deliberately built so nothing in it can ever be edited or deleted, which is what makes it useful as evidence. A waitlist signup is the opposite kind of data: ordinary, and ordinarily deletable. It is stored in a completely separate table with no relationship to that chain, is never written to it, and a request to delete your waitlist entry is a plain, complete deletion — not something that has to work around a record designed not to allow one.