Privacy

Who we are

CueDuck runs the Boards at cueduck.com and the organiser app that makes them. For anything about your data, email hello@cueduck.com.

What we collect from guests

Nothing that identifies you. Opening a Board needs no account, and the Board stores no profile of you.

Opening a Board never asks for your email address, and organisers can never see who opened their Board.

We count how many phones open each Board in a day, so its organiser can see that it’s being used. It’s a number and nothing else: no name, no account, and no way to tell one phone from another. To count a phone once a day, the Board leaves a note in that phone’s own storage saying it has been counted. That note is never sent to us.

If you star sessions to find them under Mine, that list stays on your phone, in its own storage. It’s never sent to us, organisers never see it, and it’s cleared when the Board closes.

If something breaks on a Board, a short error report goes to Sentry so we can fix it. It says what went wrong and on which kind of page, without your IP address, the Board’s code or anything you typed.

An organiser can add files to a session, such as slides. Opening one sends it to your phone from our storage. We don’t record who opened a file, and organisers can’t see it either. So a session’s files still show when the signal drops, the Board keeps their names in your phone’s own storage; that’s cleared when the Board closes.

What we collect from organisers

Your name and email address, the name of your workspace, and everything you put into your events: schedules, speakers, places and the updates you post. If you sign in with Google, Google tells us your name and email address.

If you add files to sessions, we store them so guests can open them from your Board. A file is deleted when you remove it or its session, when you delete the event, your workspace or your account, and when the Board closes, seven days after the event ends. Each file is checked when it’s added, and a file that’s reported and breaks our rules is taken down.

If you buy Pro, we keep a record of each payment: the amount, the date and Stripe’s reference for it. Stripe takes the payment itself, including your card details, which we never see.

Cookies and tracking

We use cookies to keep organisers signed in. On our public pages and organiser pages, Intercom shows the support chat button and sets cookies to keep a conversation connected on this device. It never loads on guest Boards. We don’t use advertising trackers, and we don’t sell data.

How we measure CueDuck

To learn whether CueDuck works for organisers, we count a few things they do: signing up, creating a workspace, inviting teammates, creating and publishing a Board (and how big it is, like how many sessions and rooms it has), posting updates to it, and buying or cancelling Pro (the plan and the price, never card details). We also count visits to our own pages, like this one and Pricing, and which website or campaign link brought you.

We use PostHog for this, with its data kept in the EU. It sets no cookie and stores nothing on your device. To tell visits apart, PostHog makes a daily code from your IP address and browser type, mixed with a random value it deletes each day, and doesn’t keep your IP address. When you’re signed in, counts are tied to your account by a random ID, never your name or email, and never to what’s in your events. These counts are deleted after a year.

You can turn this off. If your browser sends Global Privacy Control or Do Not Track, we don’t count your visits. You can also stop counting on this device below; that choice is the one thing saved on your device. What you do in an organiser account, such as publishing a Board, is counted on our servers; to object to that, email hello@cueduck.com.

PostHog never runs on Boards, foyer screens, posters or QR codes. The only thing counted there is how many phones open a Board, as described above.

Support chat

Intercom provides chat on our public website and organiser pages. It never runs on guest Boards, foyer screens or Board previews. Where it runs, Intercom receives your browser and device information, IP address and the page address, and the messages you send if you chat. For signed-in organisers, we also send your account ID, name (if set), email address and account creation date, so support knows who is asking. Intercom stores this support data in its US workspace. We do not send your event contents or payment details automatically. You can also email support@cueduck.com.

Who helps us run CueDuck

Our data is stored with Supabase, which also handles organiser sign-in. Resend delivers the sign-in links we send organisers and the emails about their plan. Stripe takes payments for Pro and keeps its own payment records. If you choose Google, Google handles that sign-in. PostHog counts what organisers do, as above. Intercom provides support chat. Sentry, in the EU, receives a report when something breaks in CueDuck, on Boards and foyer screens too: what went wrong and which kind of page it happened on. It doesn’t store IP addresses, and reports carry no names, email addresses, Board codes, links or anything typed into CueDuck. If you use our ideas board, UserJot runs it on its own site. They process data only to provide those services to us.

How long we keep it

After an event finishes, its Board remains available for seven days, then closes. The event itself stays in the organiser’s account.

Payment records are kept for six years after each payment, because UK tax law requires it, even if you delete your account or workspace. They hold no card details.

Your rights

You can ask to see the data we hold about you, to correct it, or to delete it. Email hello@cueduck.com. Organisers can also delete their account, or a whole workspace, themselves in Settings. If you’re unhappy with how we handle your data, you can complain to the Information Commissioner’s Office (ico.org.uk).