Galawall

Galawall

Privacy

Galawall is a photo wall for one event. We keep what the event needs for as long as the event lasts, and then we delete it. Guests are never asked to make an account or give a name.

Aktualisiert am 22. September 2026

This page is available in English only for now. The English text is the one that applies.

Who is responsible

Kunn AS (organisation number 937 941 463, Norway) is the data controller for personal data processed through Galawall. Write to support@galawall.com about anything on this page, including the rights below.

The host of an event decides who is invited to it and what is shown on the wall. We act on the host's instructions for the content of their event, and we delete an event on the host's request.

What we collect, and why

Your account, if you make one
Email address, the display name your sign-in provider returns, and an account id. Needed to give you back your event on another device, and to write to you about it. Legal basis: the contract with you.
The event
Its name, date, language, cover and settings, and when it was created. Legal basis: the contract with you.
Photos and videos
What guests upload, the file, its size and the time it arrived. We do not ask a guest for a name, an email address or an account, and we do not read location data out of a photo. Faces in a photo are personal data about the people in it; the host chooses who is invited to upload. Legal basis: the contract with the host, and our legitimate interest in running the wall the guests came to use.
An email address without an account
Optional when an event is created, so an anonymous host can still be told the wall is ready, that the trial is filling up, and that the event is about to close. Stored apart from the event, which is otherwise readable by anyone with the link. Legal basis: the contract with you. Say so at any time and we remove it.
Payment
Stripe takes the card details; we never see or store them. We keep the amount, the currency, the time and Stripe's payment reference, which is what a receipt and our accounts are made of. Legal basis: the contract, and the legal duty to keep accounting records.
Measurement, if you allow it
If you answer yes to the question about measurement, Google Analytics records which pages you open, roughly where in the world and in which language, and which of a handful of product steps you reach. Never a name, an email address, an event key or the name of an event. If you answer no, or are never asked, no identifier is set and nothing about your visit is stored. Legal basis: your consent, which you can take back by clearing this site's data in your browser.
Security and abuse
Counters that limit how often a code can be guessed or an email requested. Where a limit has to be per visitor, the IP address is hashed and only the hash is stored. Server logs and error reports, with keys and codes stripped out before they leave the browser. Legal basis: our legitimate interest in keeping the service standing and other people's events private.

How long we keep it

Deletion means deletion: the photos leave storage and the event leaves the database. Backups roll over on their own schedule and are not searched to restore a deleted event.

  • A trial event and everything in it: 50 photos and 7 days from the day it is created, then deleted.
  • A paid event and everything in it: 365 days from payment, then deleted. We write to you before that day so you can download the originals.
  • An account: until you ask us to delete it. Deleting an account deletes the events tied to it.
  • Payment records: five years after the end of the accounting year, because Norwegian accounting law requires it.
  • Security counters and hashed addresses: days, not months.

Who else touches the data

We use a small number of suppliers, each under a data processing agreement, and none of them may use the data for their own purposes.

  • Some of these companies are established outside the EEA. Transfers rest on the European Commission's standard contractual clauses, and on the EU–US Data Privacy Framework where the supplier is certified under it.
  • We do not sell personal data, and we do not use photos from an event to advertise, train a model or illustrate anything, unless a host has asked us in writing to use theirs.
Google (Firebase)
Database, file storage, sign-in and the servers the site runs on, in the European Union.
Stripe
Payment. Stripe is the controller for the card data it collects, under its own privacy policy.
Mailgun
Sends the emails described above, from European infrastructure.
Google Analytics
Counts visits and a handful of product steps, and only for visitors who have said yes. Web addresses are stripped of everything that could identify an event before they are sent, and Google's advertising features and cross-device signals are switched off. We run no advertising tags.

Your rights

Under the GDPR you may ask for a copy of the personal data we hold about you, ask us to correct it, ask us to delete it, ask us to restrict or stop a particular use, and ask for it in a portable form. Write to support@galawall.com; we answer within a month.

A guest who appears in a photo, or who uploaded one, can ask the host to take it down, or write to us and we will pass it on and act if the host does not.

If you think we have handled your data wrongly, you can complain to the Norwegian Data Protection Authority (Datatilsynet), or to the authority where you live.

Children

Galawall is bought and set up by adults. Children are at weddings and parties, and photos of them will reach the wall; the host is the one who decides who may upload and what stays up, and a parent can ask the host or us to remove a photo.

How we protect it

  • Access to an event is checked on the server on every request, not assumed from a link.
  • The key that identifies a host never travels in a web address that a server, an analytics tool or a log file could record.
  • Everything travels over HTTPS, and files are stored in a bucket that is not publicly listable.
  • Uploads are limited to 25 MB each and are re-encoded on arrival, which strips the metadata a camera writes into a file.

Changes

When this page changes, the date at the top changes with it. If a change matters to events that already exist, we write to the hosts of those events.