Privacy

Who we are and what this covers

Better Things runs a marketplace for small group sessions. When you browse without signing in we learn almost nothing about you personally; this page is about the parts we do keep, who else touches them, and the choices you have.

It covers betterthings.io and our admin portal. It does not cover a session provider's own practices once you are at the session — for example whether they take photographs on the day, which is asked about at booking time.

What we collect, and why it is necessary

Account: your name, email address, and optionally a phone number. The email address is verified by a sign-in link; we do not ask for a password.

Bookings: the answers you give a provider on the booking form, whether you accepted the safety waiver, whether you consent to being photographed, and whether you opted into marketing. These are held because they decide who may attend and what we may do afterwards.

Payments: amounts, currency, and references to the payment Stripe holds — never card details. Refund records also carry the reason a cancellation was made, because a refund with no recorded reason cannot be explained back to you months later.

Photos you upload, for venue listings and session covers.

Nothing else about your browsing. We do not store your IP address or build a page-by-page history of what you read.

If you host or run sessions

Venue details, your application and its status, the dates you are assigned to, participant counts, and payout records. Your display name appears on sessions and listings you are part of — that is what a public profile means here, and it is the one thing a host should decide about deliberately.

Who else sees your data

The host and the provider of a session you join see your name, your contact details if they need them to reach you about that session, and your booking answers. That is a real disclosure to a third party, not to us, and it is why the roster access rules exist in the product.

Our staff see what is needed to run a booking. The admin portal is access-controlled and every change an admin makes to a booking or a setting is written to an audit record with who did it and when.

Nobody else, for marketing purposes, unless you opt in below.

The services we send data to

Each of these processes part of what we hold under our instruction. Where a service's own policy says more, it governs that piece.

Cookies and things stored on your device

Sign-in: two cookies used to keep you logged in and to renew that safely. Necessary — without them there is no session to be in.

Your consent choice, stored on this device so the banner does not ask twice. If you sign in elsewhere, your choice follows you; but the device you declined on stays declined, on purpose.

Drafts: an admin form you started but did not save is kept on that device so a refresh does not destroy your work.

Stripe's own storage, on payment steps only, for fraud detection.

Advertising cookies only if you allow them — see the next section.

Advertising, measurement and your choices

Right now we load no advertising tracker on this site. If you arrive from an ad link we do record the campaign details in that link (and the click identifier) against your account once you sign up, so we can tell which notices actually bring people who book; that record stays with us and is not sent to the advertising platform.

When that changes, it changes with your answer to the banner. Advertising and analytics tags load only after you allow them; if you never answer, they stay off; if an administrator switches consent off, nothing loads regardless of what anyone previously chose. You can change the answer at any time from the banner or the link in its footer.

We also count a few actions inside the product — for instance that someone opened a booking dialog and did not finish it. That is stored against your account, per day, as a count rather than a timeline, and only if you are signed in and have allowed measurement. We do it because a dialog abandoned halfway leaves no other trace anywhere, and without it we cannot tell a confusing form from a busy date.

Marketing emails are opt-in at checkout and every one carries an unsubscribe route.

Links you share

When you share a session, the link points at a preview page that shows the session's public details — title, date, price, area, photo — so that the message reads as a card rather than a bare URL. That page contains only information already public on the session. It never contains participant lists, or anybody who has booked.

Tapping share hands the text to WhatsApp, Instagram, Facebook, X, LinkedIn or your email app from your own device. We do not send anything to those services on your behalf.

Where it is stored and for how long

Singapore, in the asia-southeast1 region.

Booking, payment and refund records are kept while your account exists, and afterwards as long as accounting or safety rules require them — a payment dispute or an injury claim is unanswerable without the record that produced it.

Session photographs are kept according to the consent you gave and the provider's own practice at the session.

Your rights, and how to use them

Under Singapore's Personal Data Protection Act you may ask to see what we hold about you, ask us to correct it, or ask us to stop contacting you. You can correct most of it yourself in your profile.

Account deletion is not something you can do yourself yet — write to us at the address below and a person will do it. We would rather say that plainly than imply a control we have not built.

If something here is unclear or you want to complain about how we handled your data, write to the same address; if we cannot settle it, you may raise it with the Personal Data Protection Commission.

Contact

Data requests, corrections and complaints: notifications@betterthings.io — replace with the dedicated address once one exists (see the note at the top of this page).

Children and vulnerable participants: our forms ask for a guardian's permission where relevant, and we do not market to accounts that indicate a participant is under 18.

If this changes

Material changes get announced in the product and the date at the top of this page changes. The list of services above changes whenever the code starts or stops sending data somewhere, and that change is checked by an automated test rather than remembered by a person.

The services listed above, in one table