Privacy policy

The short version

We collect what it takes to sell you a ticket and get it to you, and what it takes to let an organizer run their events. We do not sell your data, we do not run advertising, and there is no public profile of you on this site. If you want to know what we hold about you, or want it deleted, ask us and we will do it.

What we collect

When you buy a ticket

Your email address, and the name and email of each attendee if the organizer asks for them. Some organizers add questions of their own to the ticket form — those answers go to that organizer, because they are the ones running the event. We also keep a record of the order itself: what you bought, when, for how much, and whether the money arrived.

You do not need an account to buy. If you check out as a guest we hold the order and the email address it was sent to, and nothing else.

When you have an account

Your name and email address, and your notification preferences. If you apply to become an organizer we also collect your business name, a contact phone number, your city, optionally a website, and what you told us about the events you run — an admin reads that to decide on your application.

Payment details

Your card number never reaches us.Payment is completed on the payment provider's own pages — Paystack, Flutterwave or Stripe depending on the event's currency — and what comes back to us is a reference, an amount and whether it succeeded. We cannot see your card, and neither can the organizer.

Automatically, as you browse

Your IP address and browser type, in the ordinary server logs any website keeps. For event pages we also record a page view against the event so its organizer can see how their listing is doing — that record holds a session identifier, a country, a city, a device type and where the visit came from. It is not tied to your name or your account.

Cookies

We use seven, all our own. There are no advertising or third-party tracking cookies on this site, which is why you were shown a short notice rather than asked to accept or reject anything — there is nothing here to opt out of.

• Two session cookies that keep you signed in. They are httpOnly, meaning no script on the page can read them, and they are the reason you do not have to log in on every click.
• A flag saying a session exists, so the page can render the right header before it has asked the server anything.
• Your country, so prices and payment methods make sense where you are. Set from your connection on your first visit, and overridden the moment you pick a different one yourself.
• Which studio you last worked in, for organizers who belong to more than one.
• That you have read the cookie notice, so it is not shown to you again. A cookie is the only way to know that before the page draws.
• A maintenance bypass, which only exists for our own staff and only while the site is down for work. It is never set for a visitor.

Clearing them in your browser signs you out and forgets those preferences. Nothing else breaks.

Other things stored in your browser

Cookies are not the only place a site can keep something, and the rest deserves the same list. We use your browser's own storage — never sent to us unless you act on it — to hold a checkout while you are filling it in, to show your ticket again on the confirmation page if you reload it, to remember which notifications you have read, and to keep an organizer's seat-map edits from being lost to a stray refresh.

All of it is first-party, none of it identifies you to anybody else, and clearing your browser data removes it.

What your browser loads from elsewhere

Almost nothing. Our fonts are served from this site rather than a font network, so your visit is not announced to one. Images come from our media host. There are no analytics scripts, no tag managers and no advertising pixels anywhere on this site.

The one exception is the map on an event page, which is an OpenStreetMap frame. It loads only once you scroll to it, and we ask your browser not to tell it which page you came from. If you would rather it did not load at all, the address is written out beside it.

Who else sees it

The organizer of an event you bought from sees the order and the attendee details for it — they have to, to let you in and to deal with you if something changes. They do not see your payment details, and they do not see anything about orders you placed with anybody else.

Our payment providers see what they need to take the payment. Our email provider sees the address a ticket or receipt is being sent to.

Nobody else. We do not sell your information, we do not share it for advertising, and there is no advertising network on this site to share it with.

Emails we send

Some are not optional, and should not be: your tickets, your receipt, and the outcome of a refund request. You have paid for those, and turning them off would mean not getting what you bought.

Everything else is yours to switch off in notification settings, per kind and per channel — including the emails organizers send to people who bought tickets to their events.

What organizers publish

An organizer's business name, description, logo and website link appear on the events they list, alongside a link to everything else they have on sale. That is the point of it — a buyer deciding whether to trust a listing is entitled to know who is behind it.

There is no separate organizer profile page, and no public profile of any kind for buyers. Nothing you do as a buyer — what you looked at, what you bought, what you asked to be refunded — is visible to anybody but you and the organizer whose event it was.

How long we keep it

Orders, tickets and payment records are kept as long as we have to for accounting and for settling disputes. Account details are kept while your account exists. Contact messages sent through the contact form are not stored at all — they are emailed to our support address and the reply happens there.

Getting your data, or having it removed

Write to support@allevents.test.luday.se from the address on your account and tell us what you want. We will tell you what we hold, correct it, or delete it.

There are two honest limits on deletion. Records we are required to keep for accounting — an order that took money — cannot simply be erased, and removed data may sit in backups for a period before those are rotated out. Everything else goes.

Other sites

Event descriptions and organizer pages can link elsewhere, and payment happens on the provider's own site. This policy covers what we do; once you follow a link, the policy of the site you land on applies.

Changes

We may update this policy. When we do, the version on this page is the one that applies, so it is worth a look if you have not read it in a while.

Questions about any of this? Get in touch.