Privacy Policy

Effective November 4, 2026

Kemisu is run by Hustlebox in Ontario, Canada. This policy explains what we collect, why, who sees it and how long we keep it. We follow Canada’s Personal Information Protection and Electronic Documents Act (PIPEDA).

What we collect

If you have an account

Your email address and password. The password is stored hashed.
Your plan and billing status. Card details go to Stripe and never reach us.
Branding you upload, such as a logo and colours.
Contact details you choose to show on your public event pages and to your guests, such as a name, email, phone or social links.

If you join a room as a guest

The display name you type.
What happens in the game: your card, the squares you mark, who you credit them to, and any win you claim.
A random sign-in code kept in your browser, so you can come back to the room.

If you are a guest at an event

Your email address, and the name, gender and age the account running the event adds for you, if it does.
Your reusable profile: name, gender and year of birth. You can also add an introduction, interests, dislikes, photos, contact details, nationality, religion, profession, company, job title, income, hometown and education level.
At Dating events, optional private preferences about who you would like to meet, and relationship intentions you can choose to share.
Matching picks and the notes you add to them.
Your answer to the event’s consent form, if it has one, and when you gave it.
When you check in at the door.

From everyone

Your IP address and browser signals, used to limit abuse and tell people from bots.

How we use it

To run rooms, events, matching and check-in.
To send the emails the service needs, like invites and sign-in links.
To show an account summaries of its own rooms and events, such as how many people played, came, or came back to one of its earlier events.
To understand how Kemisu is used as a whole, from counts and rates that identify no one.
To bill paid plans.
To keep the service secure.

We do not sell personal information.

Who sees what

Other people in a room see your display name.
People authorised to view you in an event’s matching see your current name and gender. The account running the event decides whether and when they also see your introduction, interests, dislikes and photos, and your nationality, religion, profession, company, job title, income, hometown and education level if you fill them in. By default these stay hidden until the organiser reveals them. Your approximate age is shown only if the organiser also turns on age sharing; it is calculated from your birth year, so they can infer that year. Hiding details later cannot recall what someone has already seen. Dating preferences stay private to you. Relationship intentions are shown only at Dating events, only once details are revealed, and only when you choose to share them.
The account running an event sees its guest list, with the name, gender and age it entered for you, and whether you came to its earlier events. Saving your profile or joining matching at its event shares your details there. Its organiser can then open your current full profile, approximate age and photos, including later changes after the event. This applies to profiles already shared and future shares. It does not grant access to your private dating preferences, picks or notes; relationship intentions appear only at Dating events when you choose to share them. Inviting you, importing a guest record or signing in alone does not grant this profile access. The organiser never sees which other accounts’ events you go to.
When matching closes, your contact details and any note you wrote go to the people your picks reach: someone you both picked, or, in one-way matching, the person you picked or shared back with.
If the event has a consent form, the account running it sees whether you agreed, declined or have not answered yet.
Event pages marked public, and the organiser’s saved name, email, phone and social contacts on them, can be seen by anyone.

Your profile is reused when you follow an invitation to another event, including events run by another account. This does not register you for an event or join its matching. Each event has its own invitation, consent, attendance and matching choices. Updating your profile changes what authorised matching participants and organisers of events where you have shared can see, including your photos. Event guest lists and reports keep the details shared at that event; the separate current profile viewer may show later values. Current values do not establish what you shared at a past event or which other events you attended.

Post-event feedback

An organiser may invite you to give feedback after an event, and may require its submission before you view newly released picks results. You can decline individual rating questions; written answers are optional. We track completion separately so you do not need to submit again.

When anonymous feedback is allowed, it is selected by default. You can choose to attach your name instead. If anonymous responses are not allowed, the form tells you before submission. Identified feedback is shown to the organiser with your name. Anonymous answers have no guest identifier attached, but comments may reveal who wrote them. This is anonymity to the organiser; database administrators may still have access to operational records.

Response counts update during collection. Anonymous answer summaries and comments appear only after guest access closes, and only when at least five anonymous responses exist. We also show an aggregate count of results presentations, separately from feedback. Organisers use feedback to improve their events. We may use aggregated feedback that identifies no one to improve the platform.

Identified feedback can be deleted when your information is erased. We cannot locate an anonymous response for individual withdrawal because it has no identity link. Deleting the event removes its survey data. Otherwise feedback follows the retention policy below.

Service providers

We use these companies to run Kemisu:

Supabase, for the database, sign-in and file storage.
Vercel, for hosting and bot protection.
Stripe, for payments.
Resend, for email.
Cloudflare Turnstile, for the bot check when you sign in or create an account.

Some of them process data outside Canada, including in the United States.

Analytics and ad measurement

On Kemisu’s public pages (the home page, the pages about our products and plans, the FAQ, the Terms, this policy and the events listing) we use Google Analytics, loaded through Google Tag Manager, to understand how people find and use the site, and the Meta Pixel, to measure our ads on Facebook and Instagram. Both set cookies and run for every visitor to those pages. Neither runs on the sign-in page, the dashboard, guest rooms, event pages or emails sent for an event.

They collect your IP address, device and browser identifiers, the pages you visit and whether you arrived from an ad. Meta may link this to your Facebook or Instagram account to measure and show ads, as described in Meta’s privacy policy. To opt out of Google Analytics, use Google’s opt-out add-on. To limit what Meta uses, change your ad settings in Facebook or Instagram.

When you create an account or start a paid plan, our servers also tell Meta, so we can see which ads led to it. We send your email address and account ID in hashed form, with your IP address, browser details and the Meta Pixel’s cookie. We never send anything about guests.

Cookies and browser storage

Accounts stay signed in with cookies. Guests stay in their room or event with a code stored in the browser. We use no advertising or tracking cookies other than the ones above.

How long we keep it

We keep data with no set expiry, so that past rooms and events stay available. You can ask us to delete your information at any time by emailing hello@kemisu.com.

Your rights

You can ask to see the personal information we hold about you, to correct it, or to delete it, and you can withdraw consent where we rely on it. Email hello@kemisu.com. If you are not satisfied with our answer, you can complain to the Office of the Privacy Commissioner of Canada.

Children

Kemisu is not meant for children under 13.

Changes

We will update this policy when what we do changes, and the date above changes with it.

Contact

hello@kemisu.com. See also our Terms of Service.