Service
Why
What it gets
Role
Where
Passage file
It does not leave the device. The skipper is the controller of that file; DeckVakt is not.
Crew, rota, log, standing orders, boat, waypoints. Seasickness notes stay with the skipper.
Not received
On device
Website host
Serving deckvakt.com
Connection logs: IP address, time, URL
Processor
EU
Web3Forms
Relaying waitlist and contact email to their inbox. No DeckVakt database of addresses.
Email address and the message you send
Processor
US
Umami Cloud
Aggregate stats on marketing pages only. No cookies, no profiles, no advertising. Honours GPC and Do Not Track. Desk and apps do not use it.
Page views, referrer, country, browser. Never crew names, passage files or waitlist addresses.
Processor
US
Sentry, EU region
Faults on the website and desk. Names, boats, ports and share codes stripped before send. Mobile apps do not send crash reports.
Technical fault, version, browser environment
Processor
EU
Apple and Google
App stores, optional one-time contributions, and Apple place lookup if you use it. Location is not used for advertising.
That a contribution completed, not card numbers. A coordinate if you look up a place.
Independent
US
Device-to-device share
Join codes, QR, Bluetooth or local Wi-Fi in the saloon. Not an upload to DeckVakt.
The passage file you choose to hand to another phone
Not received
Local