Skip to content
Signedup
  • What it is

    • How it worksThree steps, and what each one takes you.
    • Who uses itThe lists people already keep, department by department.
    • See the formsWhat one of your colleagues actually opens.
    • QuestionsStraight answers on sending, importing and leaving.

    See how it works

  • How it compares

    • What is a preference centre?The category explained, without selling anything.
    • A spreadsheetThe most common alternative, and where its one structural weakness is.
    • An Outlook or Microsoft 365 distribution listAccurate about employment, silent on preference.
    • Mailchimp or another marketing email toolSending tools solve the other half. How the two work together.
    • An intranet formAlready approved and already paid for. Why the list still goes stale.
    • A full internal comms platformWhen a full platform is right, and when it is more than the job requires.

    All comparisons

  • Pricing
  • Practical guides

    • Your first listFrom nothing to a link you can share, in about the time it takes to make a cup of tea. What to call it, what to ask, and when to publish.
    • Getting people to actually sign upA form nobody fills in is a spreadsheet with extra steps. Where to put the link, what to say, and how to reach colleagues who pass a notice board more often than they read an inbox.
    • Keeping a list clean without chasing anyoneEvery list falls out of date - people move team, change site, leave. The answer is not to chase harder; it is to stop being the only person who can make a correction.
    • Do you need consent for internal emails?Employment does not make every internal email lawful, and consent is often the wrong basis to claim. Which messages need what, and the record that settles an argument.
    • How to organise your internal mailing listsMost internal lists are organised by who somebody is, because that is what the directory knows. Nearly everything people actually want is organised by interest, and the gap between the two is where the administration comes from.

    All guides

  • Who it is for
  • How it works
  • Pricing
  • Questions
  • Guides

Cookie notice

Last updated 15 September 2026

Cookies are small files a website asks your browser to keep. Websites can also store or read other information on your device in similar ways. The law requires us to tell you about anything of this kind we use, and to ask your consent unless it is strictly necessary for a service you have asked for.

Signedup uses no cookies for tracking, advertising or profiling, and nothing that needs your consent. Everything described below is strictly necessary, which is why there is no cookie banner. This notice should be read with our privacy notice.

On this website

This website sets no cookies, and our own code stores nothing in your browser. We count visits to our pages using a measurement method that uses no cookies and no other browser storage, and does not identify you. If a page fails, the error report we receive does not rely on cookies either.

Our early access form includes a security check that tells a person from an automated script. It runs only when you come to use the form, reads information about your browser for that purpose alone, and is provided by the company that delivers and protects our websites, which is named on our sub-processors page.

If traffic to our websites looks automated, that company may ask your browser to pass a check and set a short-lived cookie recording that it did, so that you are not asked again straight away. That cookie is used only for security.

In the product

The Signedup application, and the public forms that people use to join a list or update their details, use the following, each of which is strictly necessary.

Sign-in session. When you sign in to a Signedup account, we set a cookie that keeps you signed in. It lasts for up to 30 days and is renewed as you use the product. It cannot be read by scripts on the page and is sent only over encrypted connections.

Form session. When you open the single-use link to a form, we set a cookie named su_form that lets you change your details without signing in. It is signed so that it cannot be altered, is sent only to the form pages, cannot be read by scripts on the page, lasts 30 minutes, and is removed if you delete your record.

Security check. Sign-in and public forms include the same security check described above, for the same purpose.

Payment. When you pay for a plan or manage your billing, you do so on pages provided by our payment provider, Stripe, which sets its own cookies on those pages under its own cookie policy.

Managing cookies

You can block or delete cookies in your browser's settings. Because everything described here is strictly necessary, blocking it will stop sign-in, forms or the security check from working.

Changes to this document

We update this notice whenever we change what we store on your device, and the date at the top shows when it last changed. This version was published on 15 September 2026. Questions about it can be sent to privacy@signedup.io.

Signedup

  • Security
  • Privacy
  • Terms
  • DPA
  • Sub-processors
  • Acceptable use
  • Cookies
  • Contact