Skip to content
BeaconStep

Privacy notice

Last updated: 10 October 2026

This notice explains what personal data the BeaconStep app and website use, why, where it is stored, and how long we keep it.

On this page

1. Who is responsible

The controller is DevFIRE WEB SRL, Corvinilor 64, Ap. 1, 440080 Satu Mare, Satu Mare County, Romania.

Contact for privacy questions: privacy@beaconstep.app.

When a company uses BeaconStep for its own team event, that company decides who plays and what the quest contains. For the players’ data inside that quest, the company is the controller and BeaconStep processes the data on its behalf (data processing agreement, Art. 28 GDPR).

2. What we use, and why

Organizers (people who create quests)

  • Email address — to sign you in with a one-time code (no password).
  • Company name, default language, the time you accepted our terms.
  • If you tap Use my location when you pick a start point, the app rounds your position to about 100 m before it uses it to move the map and look up the street name. Your exact position is never sent to us or stored.
  • During a live quest: the messages you send to teams (up to 280 characters), the surprise tasks, hint gifts, warmer / colder signs and cheers you send, and which help requests you marked as done. Players of that team see that “your organizer” sent a hint gift, a warmer / colder sign or a cheer, never your name.
  • If you allow notifications: a push token for this device, so we can tell you when a team asks for help or seems stuck (section 5).
  • If you place printed QR codes: where each code hangs (the position and accuracy of your phone when you scan it there, or no position), the time, and an optional note and photo (section 3).
  • If your quest has a story and a game master: the story (written by the AI or by you), its settings, and what you send to the game master, with an optional idea for a final twist or a meeting point (section 4).
  • For company quests: your company’s logo and main colour, what you hide in the company recap, the state of its secret link (we keep only a fingerprint of it), and when the report was first opened and the report email sent (section 12).
  • Purpose and legal basis: providing the service you asked for (Art. 6(1)(b) GDPR).

Players (people who join a quest)

  • A display name you choose (a nickname is fine), your team, and the time you confirmed you are 16 or older. We do not ask for your birth date, email or phone.
  • An anonymous account id, so the app can remember your quest on this device.
  • Photos you take with the in-app camera for a photo step (never from your gallery), and your answers to answer steps.
  • One location fix each time you send a photo or an answer for a step that has a place (section 3).
  • Your team’s tries, points and hints, and your choice about AI photo checks (yes or no, and when).
  • Your role in the team (a label such as Navigator), the help requests you send (the choice, your team’s step and the time), and your team’s surprise tasks with their tries.
  • During a live game, your live position: shared with the organizer, never stored (section 3).
  • During a game, a live feed of what your team does (for example a photo sent, a try passed or failed, a hint used, a help request, a QR scan, being stuck on a step, the finish), with the first name of the player who did it and the step number, never a place or a position. Only the quest’s organizers see it (sections 3 and 6).
  • If the organizer shows the quest on a big screen (a secret link, for example on a projector), it shows team names, the ranking and short cheers such as “Team Blue got 🔥”, never a player’s name, a photo or a position.
  • For QR steps: which code your team scanned, when, and the result. For “Point at target” steps: one compass direction sent with the location fix, never stored (section 3).
  • If the quest has a game master: the short lines it writes for your team, and your team’s answers to its buttons (which button, when, and who tapped it; only your team sees who). Whether spoken lines are on is stored only on your phone (section 4).
  • On company quests: your choice about your team’s photos in the company recap (yes or no, and when; section 12).
  • If you allow notifications: a push token for this device, so your organizer’s messages, surprise tasks and hint gifts reach you (section 5).
  • Purpose and legal basis: running the quest you joined (Art. 6(1)(b) GDPR; for company events, the company’s legitimate interest, Art. 6(1)(f)). AI photo checks only with the consent of the player who takes the photo (Art. 6(1)(a) GDPR).

Website (beaconstep.app)

  • No cookies, no analytics, no tracking. Our host keeps short technical logs (IP address, time, page) for security, for at most 30 days.
  • If you write to us with the contact form on the home page: see section 10.

Technical logs (app)

  • When the app talks to our servers, our providers keep short technical logs (IP address, time, request) for security and error finding, for a limited time set by the provider.

Support email

  • If you write to us, we keep your message and email address to answer you. Our mailbox is provided by Google Workspace.

3. Photos, location, QR codes and compass

Location

When you send a photo or an answer for a step that has a place, the app sends one location fix taken at that moment, with its accuracy. Our server checks it in memory against the step’s place and never stores the coordinates. It keeps only the result (inside the zone: yes or no), the distance to the place in whole metres, and whether the phone marked the location as simulated.

The app asks only for the permission “While using the app”, never “Always”. Outside a live game, it uses your location only while the app is open. For this location check, organizers never see your position or a route; they see only the result and the distance.

Live location during a game

While a game is live, from your team’s start until the game ends for your team, the app shares your phone’s position live with the organizer of that quest, at most every 10 seconds. This also works while your phone is locked, so you can put it away while you walk; your iPhone then shows a blue sign at the top. The organizer sees a dot with your name on a map. Your own team sees one team dot. Other teams never see you.

The position is sent through Supabase Realtime (Frankfurt) and is never stored: it is not written to any table or log, there is no route and no history, and nothing is left after the game. The organizer’s app and dashboard show one dot per player and keep only the last few positions (at most 3 per player, to steady the dot) in memory only.

Sharing stops when the game ends for your team: at the finish, when your time is over, when the organizer ends the quest, or when you leave it. Your phone also stops on its own at your team’s end time, and at the latest 5 minutes after it, even without a network connection. If location or Precise Location is off, the app sends only a “location off” status, without any position. You can turn location off at any time in iPhone Settings; you are then not on the map, and steps at a place cannot be checked.

Purpose and legal basis: running the quest you joined, as for the location check above (Art. 6(1)(b) GDPR; for company events, the company’s legitimate interest, Art. 6(1)(f)).

Photos

Before a photo is stored, our server removes all of its metadata (such as EXIF data, including any GPS position). Photos are kept in a private storage area in Frankfurt, with no public link. Only your own team and the quest’s organizer can see them, through links that work for 5 minutes. On a company quest, people with the company recap link can also see a team’s photos, but only if everyone in the team agreed (section 12). A photo sent from outside the zone is not stored.

Photos can show team mates or other people. Any player can report a photo of their team (for example, when someone in it did not agree to be in it). The organizer sees the report, but not who sent it, and can remove the photo; it is then deleted.

Organizers see all photos of their quest on a photos page, in the app and on the web dashboard, with the team, the step, the time and the result, never a player’s name or position. The live feed in the control room (section 2) shows a small copy of each photo sent, with the first name of the player who sent it. Until the quest data is deleted (section 6), they can download the photos as one ZIP file, sorted by team and step; the ZIP is put together on the organizer’s device and contains no player names and no photo metadata. A downloaded copy stays with the organizer, who is responsible for it (for company quests, the company as controller, section 1); our deletion cannot reach it.

QR codes

Printed QR codes count only when they are scanned with the camera inside the BeaconStep app. The app reads the code on your phone; no camera image is sent or stored. It sends our server only the code from the link and, when the step has a place, one location fix, checked as described above: the coordinates are never stored. Opening a code with the phone’s normal camera only shows a page on beaconstep.app that points to the app; it counts for nothing.

For each scan that counts, our server keeps a record of which team scanned which code, when, and the result: step passed, piece found, decoy found (with the points taken), not near enough, or step not open yet. Scanning a code again after its step is passed, or a piece or decoy the team already found, is not recorded. No player’s position is stored. A scan that passes a step is kept like any other try of the team. The organizer sees the teams’ scans (team, code, time, result), never a position.

Placing the codes (organizers): when an organizer scans a code where it hangs, our server stores where the code hangs (the phone’s position and its accuracy at that moment, or no position when it is placed without a location), the time, and an optional note and an optional photo taken with the in-app camera (metadata removed as for step photos). This is the place of the printed card, not a route. Only the organizers of that company or family space see it, never the players.

Compass and pointing at a target

The compass arrow and “Point at target” steps use your phone’s compass. For the arrow, the direction is used only on your phone and never sent. For a “Point at target” step, when you hold the phone toward the target for 2 seconds, the app sends one averaged direction together with the location fix of that try. Our server compares it in memory with the direction from your position to the target and does not store it; it keeps only the result (yes or no), how many whole degrees the phone was off, and the location result as above.

Hot / cold steps

On hot / cold steps, your phone compares its own position with the step’s place, on the phone only, to show a colour and a word and to vibrate (never metres). These positions stay in the phone’s memory for a few seconds and are not sent for this; whether you reached the place is checked by our server with the location check above.

4. Artificial intelligence

BeaconStep uses AI from Google (Gemini via Vertex AI, in an EU region) in four places:

  1. Quest drafts for organizers. Our server looks up public places around the start point in OpenStreetMap data (our own copy for Luxembourg, the Greater Region and Belgium; Geoapify elsewhere), and the AI writes the steps from that list. The organizer can check, edit or regenerate every step before the quest starts. No player data is used for this.
  2. Photo checks. If the player who takes a photo has agreed, the AI checks whether the photo shows what the step asks for and the hand sign of the live check. Without that consent, the organizer checks the photo instead. When the AI is unsure or not available, the organizer decides. After a failed try inside the zone, the team can ask the organizer to review it. In schools, a teacher will always confirm the result.
  3. Photo story captions. After a family quest, the AI writes a short caption per step, from text only (section 11).
  4. Quest story and game master. The AI writes a short story for each quest and, during the game, the short lines of a game master for each team (see below).

The organizer chooses per quest how photos are checked: by the AI, as described above; by the organizer only — then no photo of that quest goes to the AI and the organizer decides every photo; or by the AI with the organizer confirming — the AI suggests a result and the organizer decides every photo. Players never see the suggestion; it is kept with the try for the organizer and deleted with the other quest data. The organizer can change the choice while the quest runs; the change applies to new tries. Answer steps are never checked by the AI: our server compares the answer with the answers the organizer set.

The AI gets only the photo, the step’s check text and place name, the hand sign and the language for its reply — never a player’s name, email, user id or position. Prompts, AI answers and photos are not written to our logs. The app asks the player who takes the photo for consent before the first check; the consent can be withdrawn at any time, and later photos then go to the organizer.

Quest story and game master. When a quest is created, the AI writes its story: a title, a short intro, a mission, an optional character and one short chapter per step. It uses only the quest’s own data (title, language, group, start point, and the steps’ titles, tasks and places), never player data. The organizer can read, edit or rewrite the story, and can switch the game master off for a quest. The quest’s invite page on beaconstep.app and the join screen in the app show a teaser of the story (its title, intro, mission and character, with the quest title, place, length and number of steps) to anyone who has the quest code, and only while the quest is ready or live. To limit misuse of the invite page, our server keeps only a keyed hash of the IP address (never the address itself) and deletes it after 1 day.

During the game, the game master writes short lines (up to 240 characters) for each team: when a step opens, after a try is checked, when the team moves up or seems stuck, and at the end. It only talks about a result; it never makes or changes one. For this the AI gets only the team name, the number and title of the steps already open, the result of the try, the tries left, the ranking (with the name of the team just behind), the story and, from the organizer, an optional idea or meeting point — never a player’s name, a photo, a position, the answers or the hints. The lines are about the task, the place and the game, never about people or how they look. Players answer only with fixed buttons (for example to ask for a clue); the organizer sees the team’s choice, never who tapped it. The organizer sees every line and can pause the game master or mute it for a team. Prompts and AI answers are not written to our logs.

Spoken lines. Sound is off by default. When it is turned on in the app, only the text of a line and its language are sent to Google Cloud Text-to-Speech through its EU endpoint; the audio file is kept with the quest’s photos in Frankfurt and deleted with the quest data (section 6).

5. Where your data is stored

App data is stored and processed in the European Union by these providers:

  • Supabase (database, sign-in, storage of photos and company logos, live updates during a game) — Frankfurt, Germany.
  • Vercel (our API) — Frankfurt, Germany.
  • Google Cloud Vertex AI (photo checks, quest drafts, photo story captions, quest stories and game master lines) — EU region; for spoken game master lines (only when sound is on), Google Cloud Text-to-Speech through its EU endpoint.
  • Bird (sends the sign-in code emails, the next-morning report emails to company organizers, and the contact form messages to our mailbox) — EU.
  • Geoapify (operated by KEPTAGO Ltd, Cyprus, EU), service hosted in the EU (api.geoapify.eu): looks up public places for quest start points outside Luxembourg, the Greater Region and Belgium. We send only the quest start point and search radius, never personal data; the results are public OpenStreetMap places, cached for 7 days.

Maps and place search in the app come from MapTiler AG in Switzerland; this transfer relies on the EU adequacy decision for Switzerland (Art. 45 GDPR). To show a map, the app loads map images from MapTiler, which receives the usual request data (IP address and the map area shown). Place search sends MapTiler the text you type together with the centre of the map, or the position of the pin on the map.

Map and place data © OpenStreetMap contributors, available under the Open Database License.

Place search outside our own data: Powered by Geoapify.

Our support mailbox (Google Workspace) is not limited to the EU.

Push notifications are delivered to your iPhone by the Apple Push Notification service (APNs) of Apple Inc., USA; this service is not limited to the EU. Apple receives the device token and the notification. A notification carries only the quest title and the organizer’s message, or the surprise task title with its points and time, or the call to come to the finish with the meeting point, or that your organizer gifted your team a hint, or, for organizers, the team name with the kind of help and the step, or that a team seems stuck (team name, step number and minutes on it), plus internal ids so the app opens the right screen. It never carries a player’s name or a location. The app asks for permission only when a player joins a quest or an organizer starts one; notifications can be turned off at any time in iPhone Settings.

This website is a set of static pages delivered by Vercel’s global network, so a page may be served from a location near you. It stores nothing about you, except a message you send with the contact form (section 10); Vercel keeps short technical logs as described in section 2.

Purchases of family quests are checked by RevenueCat, Inc., USA (section 11). This transfer relies on the EU-US Data Privacy Framework (Art. 45 GDPR). RevenueCat gets a random id, App Store purchase data and the technical data the app sends with each request (such as IP address, versions, language and App Store country), never your name, email, photos or your phone’s location.

These providers act as our processors under data processing agreements. We do not sell data and we do not share it for advertising.

6. How long we keep it

  • Player names, photos and quest answers: 30 days after the quest ends by default, then deleted by a daily job (so within 31 days). Only anonymous statistics stay (for example “6 teams, 8 steps”). A company can set a different period for its quests; players can ask their organizer which period applies.
  • A photo the organizer removes is deleted at once (at the latest by the next daily job).
  • When an organizer deletes a quest (possible once it is no longer live), its teams, players, photos, answers and results are deleted at once; the photo files at the latest by the next daily job. The anonymous app accounts of its players go with it, unless they play another quest.
  • A quest that is never ended ends by itself 7 days after it went live.
  • Demo quest players: deleted after 1 day.
  • A player can leave a quest and have their data deleted: their name, AI choice, photos and answers are deleted. The team keeps the points already counted; the player’s tries still waiting for the organizer are withdrawn, and their waiting points drop.
  • Organizer accounts: until you delete your account or ask us to. If you are your company’s only organizer, the company and all its quests, players and photos are deleted with it (photos within 24 hours).
  • Family spaces: quest data always 30 days after the quest ends; the space and its quest credits until you delete your account (section 11).
  • In the app: organizers delete their account under Settings › Delete account; players leave a quest and delete their data under Quest menu › Leave quest and delete my data. Players report a photo with Report, and the organizer removes it with Remove photo. You can also write to privacy@beaconstep.app.
  • Organizer messages, help requests, roles and surprise tasks (with their tries and photos) are quest data: they are deleted with the other quest data, as above.
  • Push tokens: until the player leaves the quest or its data is deleted, until the organizer signs out or deletes the account, or until Apple reports that the token is no longer valid.
  • Support emails: as long as needed to answer, then at most 2 years.
  • Contact form messages: 12 months, then deleted (section 10).
  • Location: the coordinates of a location check are never stored; the result and the distance are deleted with the quest data. The live position during a game is never stored at all.
  • QR codes: the scans and the pieces a team found are deleted with the other quest data, as above. Where a code hangs (position, note, photo) is part of the quest: it stays until the code, the quest or the company or family space is deleted.
  • Quest story and game master: the story is part of the quest and stays until the quest or the company or family space is deleted. The game master’s lines, the teams’ answers to its buttons and the audio files of spoken lines are quest data: they are deleted with the other quest data, as above (for demo quests after 1 day).
  • Company reports and recaps: the recap settings, the fingerprint of its link and the record of the report email are quest data: they are deleted with the other quest data, as above (by default 30 days after the quest ends), and the recap page stops then at the latest. The company logo and colour stay until the organizer removes them or the company is deleted (section 12).
  • Live feed: the live feed of a quest, with the hint gifts, warmer / colder signs and cheers sent by organizers, is quest data: it is deleted with the other quest data, as above (for demo quests after 1 day).

7. Children

Company and family quests are for people aged 16 or older; players confirm this when they join. On a family quest, kids under 16 play on an adult’s phone (section 11). School quests for younger pupils will only be offered with parental consent and a teacher in charge.

8. Your rights

You can ask us to access, correct, delete or export your data, to restrict its use, or to object (Art. 15–21 GDPR). Write to privacy@beaconstep.app. Players can also ask their organizer. You can complain to a data protection authority — our lead authority is Romania’s ANSPDCP (dataprotection.ro); you can also contact the authority where you live or work, for example the CNPD in Luxembourg (cnpd.public.lu).

9. Security

Data is encrypted in transit (HTTPS). Every company’s and every family space’s data is kept apart from the others by database rules. Photos can only come from the in-app camera, and QR codes count only when they are scanned in the app. Every check (place, time, photo, answer) runs on our server; the time on your phone and any result sent by the app are never trusted.

10. Contact form

With the “Ask for a demo” form on the home page of beaconstep.app you can write to us.

  • What we receive: your name and email address, your company, school or group (if you give one), who you are writing for (a company, a school, a family or something else), your message (up to 2,000 characters), the language of the page and the time you sent it. No IP address, no cookie.
  • Purpose and legal basis: answering your message and, if you ask for it, showing you a demo and sending you a quote (for a demo or a quote: steps taken at your request before a contract, Art. 6(1)(b) GDPR; for other questions: our legitimate interest in answering the people who write to us, Art. 6(1)(f) GDPR).
  • Where: the message is stored in our database at Supabase in Frankfurt and sent once as an email, through Bird (EU), to our mailbox hello@beaconstep.app (Google Workspace, section 5). You get no copy by email. We keep no other copy and never use your message for newsletters or advertising.
  • Spam protection: the form has a hidden field that people do not see, and our server limits how many messages can come from one connection. For this limit it keeps only a keyed hash of your IP address (never the address itself), apart from your message, and deletes it after 1 day.
  • How long: 12 months after you send it. Then a daily job deletes it from our database, and we delete the email in our mailbox within the same 12 months.

The form needs JavaScript. Without it, write to hello@beaconstep.app; such emails are support emails (section 6).

11. Family quests

With For family & friends in the BeaconStep iPhone app, a private person makes quests for their family and friends in a family space. For family quests, we are the controller of all the data (section 1). The person who made the quest (the host) sees the players’ names, photos and answers in the app, as an organizer does.

Your family space

  • Your email address (to sign you in with a one-time code), your first name (shown only in your family space, never to players), the app language and the time you accepted our terms.
  • Your quests, with their teams, players, photos and answers, as described in sections 2 and 3.
  • A list of your quest credits: your free quest, each purchase and each refund (with Apple’s transaction id), and which quest used which credit. We never get card or bank details: Apple takes the payment.
  • Against company use: for 30 days our server keeps a list of which family quests reached 8 joins (the quest and the date, no names). When a space has had 3 or more such quests within 30 days, it notes this (the number of quests and the date). Nothing is blocked automatically; we may contact you. The note is deleted after 12 months, or with the space.
  • Purpose and legal basis: the family quests you asked for and bought (Art. 6(1)(b) GDPR); the note against company use: our legitimate interest in keeping family quests for private use (Art. 6(1)(f) GDPR).

Purchases through Apple and RevenueCat

You buy quests with an Apple in-app purchase; Apple handles the payment and refunds under its own privacy policy. To check purchases we use RevenueCat, Inc., USA, as our processor. RevenueCat gets a random id for your space, the App Store purchase data for that id (for example the product, transaction, date, price and refunds), and the technical data the app sends with each request (IP address, iOS, app and SDK version, language, App Store country). We turned off device identifiers and diagnostics. RevenueCat never gets your name, email, user id, photos or your phone’s location. The transfer to the USA relies on the EU-US Data Privacy Framework (Art. 45 GDPR). When you delete your account, we ask RevenueCat to delete the data for that id. Only our server decides how many quests you have; it never trusts the app for this.

Photo story

After a family quest, each team sees a photo story in the app: its approved step photos in step order, with a short caption per step. Our AI (Gemini via Vertex AI, in an EU region) writes the captions from text only: the team name and, for each step, its number, title and task. No photo is sent to the AI again, and never a player’s name or a position. Only the team and the host see the story, in the app; there is no public link. Save as image puts the picture together on your phone and saves it there; we never receive it.

How long

  • Family quests always keep their data for 30 days after the quest ends; this period cannot be changed. Then names, photos, answers, story captions and game master lines are deleted, as in section 6.
  • Your family space, first name, email and quest credits: until you delete your account under Settings › Delete account (or ask us to). Quests you have not used yet are deleted with it.

Kids

Kids under 16 play on an adult’s phone, never with their own. Only people aged 16 or older join with their own phone (section 7). Up to 8 phones can join a family quest; a phone that leaves and joins again counts again.

12. Company reports and recap

When a company quest has ended, the company’s owners and admins get a report of it and can share a recap page. Family quests have neither.

Report

The report shows the ranking and, for each team, its score, time, steps done, retries, hints and help requests; for each step, how many teams reached and passed it, the average time and the retries; and how the tries were checked (by the AI, by the organizer, or automatically). It names teams only, never a player, and shows no photos and no positions. It is shown in the app and on the web dashboard; the PDF and the CSV file are made on the organizer’s device. A downloaded copy stays with the organizer, who is responsible for it (section 1); our deletion cannot reach it.

Next-morning email

If nobody from the company has opened the report yet, we send one email at 8:00 (Luxembourg time) on the morning after the quest ended, through Bird (EU, section 5), to each owner and admin of the company. It contains only the quest title and a link to the report, and each email goes to one address only. Once someone has opened the report, no email is sent. Demo quests and quests that no team started get no email.

Recap page and secret link

The organizer can share a recap page of the quest inside the company with a secret link. Anyone who has the link can see the page without signing in, so it should go only to the people it is meant for. The page shows the company’s logo and colour, the quest title, the story’s title and intro, the date and place, the numbers, the podium, highlights (such as the fastest step), up to 3 game master lines per team and, only when allowed (see below), team photos. It names teams only, never a player. The organizer can hide any part, any game master line and any photo, and can turn the link off at any time; it then stops at once. A new link replaces the old one.

A link works for at most 30 days, and never longer than the quest data is kept (section 6). We keep only a fingerprint of the link, not the link itself. The page is not indexed by search engines, sets no cookies and loads no third-party scripts: its text and pictures come only from our servers and our storage in Frankfurt, through picture links that work for 5 minutes. To limit misuse, our server keeps only a keyed hash of the viewer’s IP address (never the address itself) and deletes it after 1 day. People who saw the page may have kept what they saw; our deletion cannot reach such copies.

Photos in the recap

A team’s photos appear in the recap only if every player of that team agreed. When joining a company quest, each player can tick “My team’s photos may appear in the company recap”. It is off by default, and leaving it off changes nothing in the game. Only players who confirmed they are 16 or older can agree; a player under 16 never counts as agreeing. A player can change their mind in the app (in the lobby before the start, or in the Team tab) until the quest data is deleted; as soon as one player of a team turns it off, the team’s photos leave the recap. The app and the dashboard show the organizer only whether everyone in a team agreed, never who did. Only photos of passed steps are used; the organizer can remove any photo from the recap, and a photo that a player reported is not shown until the organizer has checked it. Legal basis: the consent of every player of the team (Art. 6(1)(a) GDPR).

Distance

The report and the recap can show one distance per team. It is an estimate from the places of the steps the team passed: the straight lines from the start to the first of these places and then from place to place, in the order the team passed them. It is not measured from anyone’s position: no player position is used for it, and location coordinates are still never stored (section 3). Only this one number per team is kept, and it is deleted with the quest data.

Company logo and colour

An owner or admin can add the company’s logo and one main colour for the recap page and the report PDF. The app or the browser turns the logo into a PNG image on the organizer’s device before it is sent. Our server removes its metadata and keeps it in our private storage in Frankfurt (section 5); the recap page shows it through links that work for 5 minutes. The logo and colour stay until the organizer removes or replaces them, or until the company is deleted; a removed or replaced logo file is deleted by the next daily job.

13. Changes

If we change this notice, we update the date above and tell organizers by email.