Privacy policy | Beyond Vision

01. In short

We collect only what it takes to make the systems work. We do not sell data, we do not trade it, and we do not use it to build a profile of you.

The short version: beyondvision.dk sets no cookies. OSIS processes participant data on behalf of the school, club or organiser you are registered with — they are the ones in charge. Sailing Log stores your account, your boats, your voyages and the boat's position on our own server in the EU — no longer with Google — and you can delete all of it yourself inside the app.

Who can see your boat and your logbook is controlled by our server, not just by the app. Your profile and your logbook in Sailing Log cannot be read without logging in. Until 10 September 2026 they could be — how that happened is in section 08.

02. Who is responsible

It depends which part of us you are dealing with.

We are the data controller for beyondvision.dk, for enquiries sent to us, for our customer records, for applications through the careers page — and for user accounts in Sailing Log, where we determine the purpose.
Sailing clubs in Sailing Log: When a sailing club uses the Sailing Log club module, the club is the data controller for its members, boats, entries, start lists, race data and results, and we are the club's data processor. Your own Sailing Log account, logbook and boats remain our responsibility. See The club module in section 08.
We are a data processor when a boarding school, club or organiser uses OSIS to process information about their students, members or participants. There they are the data controller, and we act only on their instructions. So if you are a competitor at an event, the organiser is who you should approach — but do write to us and we will point you to the right place.

A data processing agreement is in place with every customer using OSIS commercially and with every sailing club using the Sailing Log club module. The framework is set out in Legal, section 05.

03. The website & cookies

beyondvision.dk sets no cookies. No analytics cookies, no marketing pixels, no Meta Pixel, no Google Analytics. We have checked: there are no cookies in your browser after a visit, and no measurement data about you is passed on.

We do not use information from your visit for advertising either, and we do not resell it.

Google Tag Manager

We should be precise about one thing, though: the site loads Google Tag Manager. That is a container for managing measurement scripts — not an analytics tool in itself. There are currently no active analytics or marketing tags in the container, and as noted, no cookies are set.

But when the script is fetched, your browser contacts Google's servers, and your IP address is technically visible to Google at that moment. We think you should know that, even though nothing is being measured.

If we ever do switch measurement on, a consent solution will go on the site first, and this policy will be updated before it happens. We will not start measuring you quietly.

Technical logging on the server

Our web server keeps — as essentially every web server does — a log of requests: IP address, time, which page was fetched, status code and browser type. It is used for operations, debugging and blocking attacks. The logs are not used to follow individuals, and they are deleted on a rolling basis.

Local storage in your browser

We store one thing locally in your browser: your choice of light or dark theme. It is not a cookie, it is never sent to us, and it cannot be used to recognise you.

Content from others

Google Fonts — the typefaces are fetched from Google's servers, which makes your IP address visible to Google.
Google Calendar — the "book a meeting" button leads to Google's own booking page, where Google's terms and cookies apply.
Google Maps — maps on individual pages are loaded from Google.
The App Store and Google Play — links to the app lead off our site.

If you click through to LinkedIn, Instagram, Facebook or elsewhere, their policies apply, not ours.

04. When you write to us

If you write through the contact form, send an email or call, we process your name, email, phone number, any club name, and whatever you write in the message.

We use it to answer you and to follow up.
If it becomes a customer relationship, the correspondence is kept as part of the file.
If it does not come to anything, we delete the enquiry after 12 months.
Do not put civil registration numbers, health information or passwords in an ordinary email to us. If you need to send something confidential, call us and we will find a secure route.

If you book a meeting through the calendar link, the booking itself takes place at Google, on their terms.

05. Project OSIS

Here we process information on behalf of the customer you are registered with. What is actually collected is the customer's decision — below is what the system is capable of handling.

Module	Typical data
Camp Suite	Name, date of birth, contact details, next of kin, group and room allocation, registrations, activity choices, presence at the lights-out round — and, at the customer's choice, allergies, medication and special needs.
Competition Suite	Competitor name, club, category, start number, marks, points, times and placings. Judges' entries with a timestamp.
LiveSync	The names and results shown on the big screen and in the stream. No collection of its own.
Digital Signage	No personal data as a rule — but the customer's own content may contain names, photos and schedules.
NFC DMS	A card or wristband id linked to a participant, the time of check-in and check-out, and which zones or equipment access was granted to.
Payment Suite	Time, amount, line items and payment reference. Never full card details — those are handled exclusively by SumUp.

The data is used to run the event: registration, group allocation, access, safety, results and settlement. It is not used for anything else, it is not combined with data from other customers, and it is not sold.

The OSIS Competition app (iPhone)

The app is used to follow a competition, vote, play quizzes and — for athletes — register and submit qualification levels. It processes:

Athletes: name, country, club, category, optional photo, favourite trick and Instagram handle (shown on the big screen, in the app and on the audience page), and email (seen only by the organiser and used to log in with a one-time code).
All users: a random ID for the phone, so each phone can only vote and predict once. The ID is not linked to a name or account.
Push notifications: the phone's push token, chosen language and which athletes you follow — only if you allow notifications. Notifications are delivered via Apple's push service (APNs). The token is deleted when you log out or switch competition.
Quiz: the name you enter and your answers.

The app has no ads, no tracking and no third-party analytics. Data is stored on our own server in the EU (cp.beyondvision.dk) and deleted according to section 12. To have your data deleted sooner, write to kontakt@beyondvision.dk.

06. Sensitive data & children

Health, allergies and medication

Camp Suite may hold information about allergies, medication and health. That is sensitive personal data under article 9 of the GDPR, and it is treated accordingly:

It is only visible to the authorised instructor and management team the customer has given access.
It is never shown to other participants, never on information screens and never in exports to third parties.
It is deleted no later than 30 days after the event ends.
The basis for processing — typically parental consent, or the vital interests of the participant — is obtained by the customer, not by us.

Children and young people

A large share of our users are under 18. In Denmark the age at which someone can consent to an online service on their own is 13; for younger children the holder of parental responsibility must give or approve the consent.

If the account was created centrally by a school or club, the institution is responsible for the basis of processing and for informing parents. So if you are a parent and want to know what is held about your child, ask the school or the club — they have access to all of it, and we are happy to help them answer.

07. Photos & video

Our systems can show photos and video on information screens, the big screen and in a livestream — and recordings may afterwards appear on the customer's social media.

It is the organiser or the school who obtains consent and is responsible for having it in place. For minors, the parents must agree.
Consent can always be withdrawn. The material must then be taken down at the first opportunity. A livestream that has already gone out cannot be unseen, but the recording can be removed.
Situational photographs from a public event may in some cases be shown without consent — but that judgement rests with the organiser, and we always recommend asking.
If you do not want to be filmed, tell the organiser before things start. They can flag it in the system.

08. Sailing Log

Sailing Log is a logbook and planning tool for sailors. An account is a person. A boat is an entity of its own, and a person can be on several boats in one of three roles:

Owner — creates the boat and manages its details, visibility, invitation codes and members.
Crew — can record voyages for the boat.
Follower — for example family who just follow along from home. A follower can see the boat's live position and logbook, but cannot record or change anything. A follower account does not collect location.

You join a boat with an invitation code or QR code from the boat's owner. All members of a boat can see the boat's logbook and live position, and every voyage shows who recorded it.

What the app processes

Precise location (GPS): When you record a voyage, your position and route are recorded, so the voyage can be saved in the boat's logbook and shown on the map. Your position is only sent to the server while a voyage is being recorded.
Account details: Your email address and password are used to create your account and to log in. The password is stored only as a bcrypt hash — we cannot see it. We send a confirmation code and a link to your email address to confirm that it belongs to you. To prevent abuse, we count for two days how many codes are sent to an address and from a network — the address is stored only in unrecognisable (hashed) form.
Profile: Your name, an optional phone number, your account type (sailor or follower), and whether you have opted in to our newsletter. Every newsletter has a link so you can unsubscribe with one click — you can also switch it off in the app.
Boat details: Boat name, model, length, home port, visibility, and the boat's members with their roles.
Voyages: Route, times, distance, speed, title and notes — and who recorded the voyage.
Social connections: Friends and friend requests, who you share your logbook with, and competitions you take part in.
Trips and expenses that you record yourself. Only you can see them.
Harbour reviews: Your rating and text. Reviews are public and are shown with the name of your boat (or your name, if you have no boat).
Racing: When your boat takes part in a race, the boat's track and positions during the race.
Technical: A random id for the app installation (it makes sure only one phone at a time records a voyage for the boat), device type and app version, so we can debug. We also store which phone the account is logged in on (model, platform and the app installation id), so an account is only used on one phone at a time, and when the account was last used, so we can help you with support.

Data is stored on our server so you can reach your logbook across devices.

Who can see what

Visibility is enforced by our server — not just in the app. The server only hands out what each user is entitled to see.

The fleet map: Every logged-in user can see a boat's name, model, length and home port, plus the names of the boat's owners and crew. Followers are only shown to the boat's own members.

Live position: If the boat is public, every logged-in user can see its position. If it is set to friends only, only the boat's members and friends of the boat's owners or crew can see it. The boat's owner chooses the visibility in the app. The position is only sent while a voyage is being recorded; when the voyage is stopped, the boat is shown at its last known position as "In harbour".

Logbook: A boat's logbook can be seen by the boat's members. The voyages you recorded yourself can also be seen by friends you have explicitly shared your logbook with.

Racing: If the race officer makes a race public, the participating boats' names, tracks and positions during the race can be seen without logging in, for example on a big screen. What is shown in a sailing club's races is described under The club module below.

Never: Your email address and phone number are never shown to other users. The leaderboard on beyondvision.dk shows only the boat name, the number of voyages and a total nautical mileage.

Push notifications

If you allow the app to send notifications, you get a push notification when someone sends you a friend request or accepts yours, when a boat you are a member of sets sail, and when a friend sets sail with a boat you are already allowed to see (see Who can see what). You are also notified of news on a boat you are on: a new member (to the owners), an invitation to a race (to owners and crew), or that someone else has stopped the voyage you are recording. So when you start a voyage yourself, the boat's other members and the friends who are allowed to see the boat get a notification with your name and the boat's name.

You can switch each type off in the app under Min Profil → Notifikationer (My Profile → Notifications) — your choice is saved to your account — and you can switch all notifications off in the phone's settings.

To deliver notifications we store a push token for each phone you are logged in on — an address that Apple or Google has issued to the app on that particular phone — together with the platform, app version, language, the app installation's id and a timestamp. The token is deleted when you log out on the phone, when you delete your account, and when Apple or Google reports that it is no longer valid. The notification is sent through the Apple Push Notification service (iPhone) or Google Firebase Cloud Messaging (Android). It contains a title and a short text, for example the boat's name and the person's name, plus technical ids so the app opens in the right place — never your position, your email or your phone number. Apple and Google do not store Sailing Log data for us; they only hold on to the notification until it can be delivered.

Camera and the nearby radar

The camera is used only to scan an invitation QR code when you join a boat. Scanning happens on the phone itself — on Android through Google's code scanner, which runs on the device — and no images are stored or sent. If you save or share a picture of a voyage, that happens from your phone; the picture is not stored with us.

On iPhone you can use the friend radar to find other Sailing Log users close by. It connects the phones directly over Bluetooth/the local network and shows your boat name to the others. If you both say yes, you become friends in the app.

Maps, weather and other data sources

Maps are shown with Apple Maps on iPhone and Google Maps on Android. Sea marks are fetched as map tiles from OpenSeaMap, weather and waves from Open-Meteo, and depth data for the route planner from EMODnet. These lookups are made from a position — your own or the area you are looking at — without any information about who you are; as with any request on the internet, the provider sees the phone's IP address. If you create a share card of a voyage on Android, the map image is fetched from Google Maps based on the voyage's route. AIS vessel data is fetched from aisstream.io by our own server and passed on to the app; your position is not sent to aisstream.io.

We never sell your data to advertisers or other third parties.

The move away from Google Firebase

Sailing Log's data used to be held with Google Firebase. Accounts, boats, voyages and GPS tracks, live positions, friends, shares, trips and expenses, harbour reviews and races now sit on Beyond Vision's own server, operated by our hosting provider Hostnet B.V. in the Netherlands (EU).

Temporary, during a transition period: The first time an existing user logs in to the new server, the password is checked once against the old Firebase login service (Google Ireland Ltd.) so it can be carried over. After that it is stored only as a bcrypt hash with us, and the Firebase login is no longer used for that account. Until the transition period ends, an older copy of Sailing Log data still sits with Google Firebase in the EU. When the transition is over, the data there is deleted no later than 31 December 2026. After that, Sailing Log uses Firebase only to deliver push notifications to Android — no data is stored there (see Push notifications above). If you use a version of the app older than 7.0, new voyages are still stored with Firebase until you update — they are carried over automatically.

About the period before 10 September 2026. Up to that date, boat profiles and saved voyages could be read through the app's database at the time (Google Firebase) without being logged in. The reason was that the leaderboard and the statistics on beyondvision.dk fetched every user and every voyage directly, so the database was left open for reading.

That was closed on 10 September 2026, and since the move to our own server all access is controlled by the server. We are leaving this description in place because the fault was there. There is nothing to suggest the data was fetched by outsiders, but we cannot rule it out for the period up to 10 September 2026. If you wrote something in your logbook notes during that period that you would not have wanted to share, write to us and we will look at it together.

The club module: sailing clubs, entries and racing

Sailing clubs can use Sailing Log to run their racing: season calendar, entries, entry fees, live tracking, big screen, results and series. Here the club is the data controller for the data about its members, boats, entries and races, and Beyond Vision is the data processor under a data processing agreement with the club. We use the data for nothing other than providing the club module to the club.

The club and its officers: The club's name, logo, colours, home harbour and contact details. For officers: name, email, role (e.g. race officer or judge) and title.
Members and club boats: Who is a member of the club, and the club's boat register: boat name, sail number, boat type and handicap figures (e.g. DH/GPH, LYS or ORC). A boat can be linked to a Sailing Log boat or registered without the app.
Entries: The skipper's name, email and optionally phone number, boat, sail number, class, crew, race number, status (entered, waiting list, withdrawn), check-in on the day, and whether you want your name shown publicly. You can enter in the app or on the web — also without a Sailing Log account.
Race data: Once you have checked in to a race, the app sends the boat's position to the race from 30 minutes before the start until the race is over. The positions are used for live standings, the big screen, automatic finishes and replays. Plus finish times, results, points and any codes (e.g. DNF or DSQ) recorded by the race officer or judge. During the race, competitors do not see each other's positions in the app.
Messages and reminders: Entry confirmation, reminders the day before and an hour before the start, notice of cancellation or postponement and messages from the race officer during the race — by email and/or push notification. Reminders can be switched off in the app under Min Profil → Notifikationer (My Profile → Notifications) or through the link in the email.

Paying entry fees

Entry fees are paid by card, MobilePay, Apple Pay or Google Pay through Stripe. The payment goes straight to the club's own Stripe account — Beyond Vision does not receive the money. Stripe Payments Europe Ltd. (Ireland) processes card details and the payment as an independent data controller under its own terms and its own privacy policy, among other things to prevent fraud and comply with anti-money-laundering rules. If you pay with MobilePay, Vipps MobilePay also processes the payment. We never see card numbers. We only store the payment's amount, status, time, Stripe's reference and the payer's name and email, so the club can see who has paid and can refund on cancellation.

The club's licence for the club module is paid to Beyond Vision through Stripe. Here we are the data controller for the details of the club's contact person and invoices.

What is public

Public races (the club's default) can be seen without logging in: on the club's page, the entry list, the public live page, the big screen, the replay, the results and series pages, shareable result cards and a widget on the club's own website. They show boat name, sail number, boat type, class, race number, crew count, the boat's position and track during the race and results and points — and the skipper's name, but only if you have agreed to show it and the club shows names.

Never public: email, phone number, crew names, payments and officers' notes.

Private races: The club can make a race private. It can then only be seen by the club's officers and members and by owners, crew and followers of the boats entered. The club can also delay the public positions or hide the replay.

How long, and your rights

Guests' contact details (email and phone) are deleted automatically 12 months after the event. Payments are kept for 5 years under the Danish Bookkeeping Act. Results, start lists and tracks are kept for as long as the club uses them, and deleted if the club asks or closes its account. The raw positions from a race are deleted no later than 400 days after the race, once the track has been saved. To access, correct or delete data from a race, contact the club — or write to us and we will help the club answer.

The club module has a demo club with made-up boats and names. If you make your own copy of the demo club to try it, the copy is deleted automatically after 14 days.

Delete it all yourself

You can permanently delete your account at any time from within the app's settings — in line with the guidelines for both the App Store and Google Play. The deletion covers your profile and account details, friendships and requests, logbook shares, trips and expenses, harbour reviews and competitions you created.

Boats where you are the last owner or crew member are deleted with all their voyages and positions — even if followers remain.
On boats you share with others, your voyages stay with the boat, but without your name; they are shown as recorded by a "former member". If you were the last owner, the longest-standing crew member takes over ownership.
If you leave a boat as the last owner or crew member, the boat is deleted with all its voyages. The app asks you first.

A deletion may remain in the server's nightly backup for up to 14 days, until that backup expires.

09. Legal basis

We only process data where there is a legal basis for it. Here is which:

Purpose	Basis
Providing Sailing Log to you as a user	Performance of a contract — article 6(1)(b)
Showing the boat's position to other users while you record a voyage	Consent — you choose to record, and the boat's owner controls visibility in the app — article 6(1)(a)
Carrying your password over from Firebase at first login (temporary)	Performance of a contract — article 6(1)(b)
Answering your enquiry	Legitimate interest in being able to reply — article 6(1)(f)
Running and securing our systems, debugging, blocking attacks	Legitimate interest — article 6(1)(f)
Processing participant data in OSIS	The customer's basis. We act on instructions — article 28
Members, entries, race data and results in the Sailing Log club module	The club's basis (typically the agreement with you to take part, and the club's legitimate interest in publishing results). We act on the club's instructions — article 28
Sending the boat's position during a club race after you check in	Consent — you choose to check in and race with the app — article 6(1)(a)
Licences and invoices for sailing clubs	Performance of a contract with the club and the Danish Bookkeeping Act — article 6(1)(b) and (c)
Health data in Camp Suite	The customer's consent or vital interests — article 9(2)(a) or (c)
Bookkeeping of sales and invoices	Legal obligation, the Danish Bookkeeping Act — article 6(1)(c)
Processing an application from the careers page	Your consent — article 6(1)(a)
Newsletter to business customers and to Sailing Log users who have opted in	Consent under the Danish Marketing Practices Act — article 6(1)(a)
Service messages by email to Sailing Log users — only important information about the service or your account (e.g. changed terms, security, required updates), never marketing	Performance of the agreement about your account — article 6(1)(b)

Where the basis is consent, you can always withdraw it. That does not affect the lawfulness of what happened before you did.

10. Who receives the data

We do not sell, rent or trade personal data. It is shared only with those necessary to run the service:

Recipient	What they do	Where
Google Ireland Ltd. (Firebase)	Parts of OSIS. For Sailing Log temporarily: checking the password at an existing user's first login to the new server, and an older copy of data that is deleted no later than 31 December 2026. After that, Sailing Log uses Firebase only for push notifications (next row)	EU (europe-west1)
Google Ireland Ltd. (Firebase Cloud Messaging)	Delivery of push notifications in Sailing Log on Android (the content: a title and a short text, e.g. a boat name and a person's name). No data is stored in Firebase	EU/USA — Google may process outside the EU under SCCs, see section 11
Google Ireland Ltd. (Maps, Fonts, Tag Manager)	Maps, typefaces and the tag container on the website; maps and share cards in the Android app	EU/global CDN
Apple (Apple Maps)	Maps in the iPhone app	Their own terms
Apple (Apple Push Notification service, APNs)	Delivery of push notifications in Sailing Log on iPhone (the content: a title and a short text, e.g. a boat name and a person's name)	USA — under SCCs, see section 11
Open-Meteo, OpenSeaMap, EMODnet	Weather, sea marks and depth data for Sailing Log. They receive only a position or a map area and the phone's IP address — not who you are	Their own terms
SumUp	Payment acquiring in Payment Suite. Receives card data directly — we never see it	EU
Stripe Payments Europe Ltd.	Entry fees in the Sailing Log club module (on the club's own Stripe account) and clubs' licence payments. Independent data controller for payment processing. Receives card data directly — we never see it	Ireland (EU); Stripe may transfer to the US under SCCs and the EU-US Data Privacy Framework
The sailing club	When you enter a sailing club's race, the club's officers receive your entry details, payment status and race data — it is the club's system, and the club is the data controller	—
Hostnet B.V. (our hosting provider)	Operation of the server that runs beyondvision.dk, its APIs, and Sailing Log's database and backups	Netherlands (EU)
Our email provider	Sending and receiving email on @beyondvision.dk	EU
Apple / Google Play	Distribution of the app plus purchases and subscriptions	Their own terms

Data may also be disclosed if an authority or a court requires it. If that happens, we tell the person affected, unless we are prohibited from doing so.

If you are taking part in an event, the organiser naturally has access too — it is their system, and they are the data controller.

If we change or add a sub-processor, customers are given at least 30 days' notice. See Legal, section 05.

11. Server location

All data processed by Beyond Vision and our systems sits on servers physically located within the EU/EEA. Sailing Log's data sits on Beyond Vision's own server with our hosting provider Hostnet B.V. in the Netherlands (EU) — the same server that runs beyondvision.dk. During the transition period an older copy also sits with Google Firebase in the EU (europe-west1), which is deleted no later than 31 December 2026.

Push notifications, however, go through Apple (iPhone) and Google Firebase Cloud Messaging (Android), so the notification's title and text and the phone's push token may be processed outside the EU, including in the USA. This takes place on the basis of the European Commission's standard contractual clauses (SCCs) in Apple's and Google's terms. Apart from the notification itself, until it is delivered, no Sailing Log data is stored with them.

Should a transfer to a third country exceptionally become necessary — for example support from a provider outside the EU — it takes place only on the basis of the European Commission's standard contractual clauses (SCCs), supplemented by a specific risk assessment.

All communication between app, screen and server is encrypted in transit with HTTPS/TLS.

12. How long we keep it

We do not keep data longer than the purpose requires. The periods here are the same as in Legal, section 05:

Type	Deleted
Event data in OSIS (registrations, groups, results)	No later than 12 months after the event
Health data in Camp Suite	No later than 30 days after the event
Access and check-in logs (NFC)	No later than 90 days after the event
Sailing Log account, boats, voyages and positions	When you delete the account or the boat yourself in the app (see section 08)
Push tokens in Sailing Log	When you log out on the phone or delete the account, or when Apple/Google reports the token as invalid
Sending history for emails in Sailing Log (which newsletters and service messages you received, and when)	Until the account is deleted — your email address is then removed from the history
Guests' contact details in a sailing club's entries (email, phone)	12 months after the event
Results, start lists and tracks in the club module	For as long as the club uses them, or when the club asks. Raw positions from a race no later than 400 days after the race
Entry fee payments (amount, name, email, Stripe reference)	5 years plus the current financial year (the Danish Bookkeeping Act)
Your own copies of the demo club	After 14 days
Nightly backups of Sailing Log's database	After 14 days
Sailing Log data with Google Firebase (from before the move)	No later than 31 December 2026
Enquiries that do not come to anything	After 12 months
Applications through the careers page	After 12 months, or whenever you ask
Customer and contract documents	5 years after the end of the relationship
Bookkeeping and transaction data	5 years plus the current financial year (the Danish Bookkeeping Act)
Server logs	On a rolling basis, no later than 90 days
Backups	Rotate and are overwritten no later than 90 days

That also means a deletion may sit in a backup a little longer, until that backup expires. We never restore deleted data from a backup without good reason.

13. Security

All traffic is encrypted with HTTPS/TLS.
Sailing Log passwords are stored only as bcrypt hashes, never in plain text.
Sailing Log's nightly backups are kept on the same server, with restricted access.
Access is granted on a least-privilege basis and is personal. Administrator access is protected with two-factor authentication.
Access to production data is logged and reviewed if misuse is suspected.
Backups are taken continuously, and restoration is tested.
Everyone with access — including helpers and volunteers at events — is bound by confidentiality and signs a confidentiality agreement.
Devices used for development and operations are disk-encrypted and passcode-locked.

If something does go wrong: If we identify a personal data breach, we notify the controlling customer without undue delay and no later than 24 hours after we become aware of it. If we are the controller ourselves and there is a high risk to you, you are told directly — and we report to the Danish Data Protection Agency within 72 hours.

If you have found a security hole, we would very much like to hear about it. The procedure is under Responsible Disclosure.

14. Applications

If you apply to join through the careers page, we process what you write yourself: name, email, any phone number, age and where you live, what you would like to do, how much time you have, any links you send, and your two free-text answers.

The basis is your consent, which you give by ticking the box in the form.
The application is read by the owner. It is not shared with anyone else and is not used for anything other than assessing your enquiry.
We keep it for up to 12 months, so we can come back to you if something turns up that fits. If you want it deleted sooner, just write to sebastian@beyondvision.dk and it is gone.
Do not put a civil registration number, health information or anything else sensitive in the application. We do not need it.
If you are under 18, your parents need to agree before we take it further.

15. Your rights

Under the GDPR you have the right to:

Access — to be told what data we hold about you, and get a copy.
Rectification — to have anything incorrect put right.
Erasure — to be forgotten, where we are not obliged to keep the data.
Restriction — to have processing paused while a disagreement is resolved.
Data portability — to receive your data in a machine-readable format.
Objection — to object to processing based on legitimate interest.
Withdrawal of consent — at any time, at no cost.

How to do it

Sailing Log: most of it you can handle yourself inside the app — edit your profile, or delete the account and everything with it.
Racing in a sailing club: contact the club, which is the data controller for entries, race data and results. We will help the club answer.
OSIS: contact your school, club or organiser. They are the data controller and hold the access. We will help them answer.
Everything else: write to kontakt@beyondvision.dk or through the contact page.

We reply within one month. If the matter is complicated, we can extend that by two months — and we will tell you along the way. We may ask you to identify yourself if we are unsure who you are; that is for your own protection.

16. Complaints & changes

Complaints

If you are unhappy with how we handle your data, please write to us first — we will put it right if we can. You always have the right to complain to:

Datatilsynet (the Danish Data Protection Agency)
Carl Jacobsens Vej 35, 2500 Valby, Denmark
Phone +45 33 19 32 00 · datatilsynet.dk

Changes to this policy

We update the policy when the systems or the law change. The date at the top shows when it was last amended. Material changes are notified to active customers by email at least 30 days in advance, and to Sailing Log users through a message in the app.

Version 3.4 — 20 October 2026. The Sailing Log club module: sailing clubs are data controllers for members, entries, race data and results, and we are the data processor; what is processed on entry and during races; entry fees via Stripe on the club's own account with Stripe as an independent data controller; what is public on the live page, big screen and results pages; retention periods and the demo club.

Version 3.3 — 11 October 2026. Section on the OSIS Competition app (iPhone): what data the app processes for athletes and other users, push notifications via Apple (APNs), quizzes, and that the data is stored on our own server in the EU.

Version 3.2 — 8 October 2026. Service messages by email to Sailing Log users (legal basis), one-click unsubscribe from the newsletter, and how long the sending history is kept.

Version 3.1 — 7 October 2026. Push notifications in Sailing Log: when they are sent and how to switch them off; push tokens per phone and when they are deleted. Apple (APNs) and Google Firebase Cloud Messaging added as recipients, including processing outside the EU on the basis of SCCs. After 31 December 2026 Firebase is used only to deliver push notifications to Android; the older copy of data is still deleted by that date. Confirmation of your email address, one phone per account and the time of last use (for support).

Version 3.0 — 6 October 2026. Sailing Log has moved from Google Firebase to Beyond Vision's own server in the EU; passwords are stored as bcrypt hashes; temporary login transition via Firebase and a date for deleting the Firebase data. New boat model with owners, crew and followers. Visibility is now enforced by the server, and positions are only sent during a recorded voyage. Sections on camera/QR scanning, the nearby radar, map and data sources, deletion of accounts and boats, backups (14 days), and updated recipients and retention periods.

Version 2.0 — 10 September 2026. Expanded from 6 to 16 sections: clarification about Google Tag Manager and server logs, an overview per OSIS module, legal bases, recipients and sub-processors, retention periods, data breaches, applications through the careers page, plus rights and how to complain.

Version 1.0 — August 2026. First edition.

See also Legal, Terms of use and Sales and refunds.