Skip to content
Kutsio
Suomi

Privacy policy

Updated 9 November 2026

Who is responsible

Kutsio is run by Sävyö, a sole trader registered in Finland, business ID 3555540-1. Sävyö is the controller of the personal data Kutsio needs to run the service. Contact: hello@kutsio.com.

When you book an event, its organiser receives your name, email and booking. The organiser is responsible for how they use them, for example to contact you about the event.

What we collect

From participants:

  • your name and email, and the dates and spaces you book;
  • the language of the page you booked on, for the emails about that booking;
  • what you paid and any refund; card details go to Stripe, never to Kutsio;
  • cancellation requests, your messages in them and the organiser’s answers;
  • email codes, personal booking links and a random identifier of the browser you booked in, all stored as one-way hashes;
  • a one-way hash of your IP address, used to limit abuse.

From everyone who signs in:

  • your name and email; Your bookings shows the bookings made with that email;
  • the language you chose, or that of the page where you last signed in, booked or published, for your account’s emails;
  • what you add to Edit profile: your profile’s address, city and country, About you, photo, website, Instagram, WhatsApp number, Telegram name and contact email. Everyone can open your profile at its address and see these, but never your sign-in email; search engines are asked not to list it.
  • the events you publish. A Public event shows on your page and can appear in search engines and AI assistants. A Private event is left off your page and search engines are asked not to list it, though anyone with its link can still open it.
  • the organisers’ pages you follow. A page shows how many people follow it, never who; you see your own list in Your bookings.

When you book an event while signed in, with your sign-in email, the event’s page shows your name and photo under Going, linking to your profile, while the event has dates ahead. When you book without signing in, the people booked on the event see your first name and the first letter of your last name, with no photo; once you sign in with the email you booked with, the booking is your account’s and shows as above. Ticking “Hide your profile from Going” in Edit profile takes you out of every Going; you then only count in the number of people going. The organiser chooses whether their event shows Going. Anyone sees the number and the pictures or initials of a few of the people going, without names; the names and the whole list only the people booked on the event and its organiser.

When you send a review, anyone who opens the event’s page sees your rating and your words, with your first name and the first letter of your last name. The rating alone shows only as part of the event’s average. The organiser sees your full name and can delete your review. It goes with your booking after 24 months, or with your account when you delete it.

From organisers:

  • your page’s name;
  • the website, Instagram, WhatsApp number, Telegram name and contact email you add to Edit page. Everyone who opens your page sees them;
  • the events, sessions, prices and venues you publish;
  • the identifier and status of your Stripe account; Stripe keeps your identity and bank details;
  • the image you add to your organisation’s page and the posters you add to your events; your browser removes a photo’s details, such as where it was taken, before sending it.

If you continue with Google, Google sends us the email address, name and account ID of your Google account. We use the email address as above and the name only when you haven’t typed one. If you are an organiser and your email is not a Gmail or Google Workspace address, we ask once for a code sent to it, then keep the account ID with your account so that Continue with Google signs you in without a code. Nothing else from your Google account reaches Kutsio.

Why we use it

  • To take and manage bookings, send codes, confirmations, reminders and cancellation notices, and process payments and refunds. This is needed to provide the service you ask for.
  • To email you when a page you follow publishes an event or adds dates. This is needed to provide the service you ask for by following it; every such email has Unfollow, and you can unfollow on the page.
  • To email you after each date of an event whose organiser asks for reviews, asking how it was and showing the next dates. This is our and the organiser’s legitimate interest; you are told of it when you book, every such email has Stop these emails, and pressing it ends them for that organiser. We keep that choice while the organiser’s page stands.
  • To keep Kutsio secure and prevent misuse. This is our legitimate interest.
  • To show your profile, and your name and photo in Going, so people can see who they will meet. This is our legitimate interest; you can object at any time: sign in with the email you booked with and tick “Hide your profile from Going” in Edit profile, or write to us, and we take you out of Going.
  • To keep records of Kutsio’s fees as accounting law requires.

We don’t sell personal data or show ads. Apart from the email above, we don’t use it for marketing.

Who else handles it

  • The organiser of the event you book, as described above.
  • Stripe processes payments. For payment data Stripe is a separate controller under its own privacy policy.
  • Google confirms your email when you choose Continue with Google. For your Google account Google is a separate controller under its own privacy policy.
  • Supabase stores our database, organisation images, profile photos and event posters in the EU (Stockholm).
  • Cloudflare Turnstile checks that a person is booking when a network has made many bookings or failed payments in a short time. It then receives your IP address and details of your browser.
  • Vercel runs the website; the server runs in the EU (Stockholm).
  • Resend delivers our emails from servers in the EU (Ireland).
  • Sentry receives reports of errors on the website, in the EU (Frankfurt).
  • PostHog counts visits and steps of booking, in the EU (Frankfurt).
  • Digitransit, a Finnish public transport data service, suggests venues as an organiser types an address.
  • Emails to hello@kutsio.com are forwarded by ImprovMX to our mailbox.

Some of these providers are based in the United States. Where data leaves the EU, it is protected by the EU Standard Contractual Clauses or the EU–US Data Privacy Framework.

How long we keep it

  • Booking details, including names, emails and messages, are deleted 24 months after the booking’s last session.
  • Email codes are valid for 10 minutes. Personal booking links stop working 30 days after the booking’s last date, or after its refund is completed if that is later.
  • A booking that was started but never completed is deleted after 30 days. If a payment was taken for it, it is kept like a completed booking, for 24 months, so the money can be traced and returned.
  • A poster is deleted when the organiser removes or replaces it, or deletes the event.
  • An organisation’s image is deleted when the organiser removes or replaces it, or when their account is deleted.
  • A profile photo is deleted when you remove or replace it, or when your account is deleted.
  • Which pages you follow is kept until you unfollow, or the page or your account is deleted.
  • An email that could not be sent at once is kept, with any booking link in it, for up to a day while we try again, then deleted.
  • An account is kept until its owner deletes it in Edit profile. Its page and events are then hidden at once and deleted once their bookings are, at the latest 24 months after their last date; bookings made with its email stay with their organisers and are deleted as above.
  • Records of Kutsio’s fees are kept as long as Finnish accounting law requires.

Cookies

Kutsio uses only the cookies it needs to work, so there is nothing to accept:

  • a sign-in cookie;
  • a cookie that ties a sign-in code to the browser that asked for it, kept for 30 days;
  • a cookie for the few minutes of signing in with Google;
  • a cookie for an hour after you sign in while creating an event, so the form stays as it was;
  • a cookie that lets the browser you booked in open and manage your booking, kept for one year;
  • a cookie that opens a booking from your personal link in this browser;
  • on events you can pay for, Stripe’s own cookies to prevent fraud.

While you continue with Google from Create event, the form you filled in is kept in your browser until you are back.

While you choose dates on an event page, that browser tab keeps a random key for the places held for you, so they stay yours if the browser loses its cookie. The key is deleted when you close the tab.

There are no analytics or advertising cookies. Pages load no fonts from other companies; the only scripts from them are Stripe’s on events you can pay for, and Cloudflare’s check when it is shown.

To see how many people visit Kutsio and where booking gets stuck, pages tell PostHog the page address without personal links, the site you came from, your type of device and steps such as choosing dates or paying. PostHog counts visitors with a code made from your IP address and browser that changes every day; it stores nothing in your browser, keeps no IP address and gets no name, email or booking.

Kutsio also counts how many times each event page and organiser page is opened each day, and from which site. It keeps only the count and the site’s name, not who opened the page.

Your rights

You can ask to see the personal data we hold about you, correct it, delete it, restrict its use, object to it or get it in a portable form. Write to hello@kutsio.com; we answer within a month.

If you think we handle your data wrongly, you can complain to the Office of the Data Protection Ombudsman in Finland (tietosuoja.fi).

Changes

When we change this policy, we update the date above. We tell organisers about significant changes by email.