Privacy statement
How QuiverLog handles your personal data, in the app and on this website.
- Provider
- 118 Performance (part of Duuriedat Beheer B.V.)
- Address
- Veldhuisweg 4-17, 7955PP IJhorst, The Netherlands
- Chamber of Commerce
- 74022261
- Contact
- info@118performance.com
- Version
- 7 November 2026
Who we are
QuiverLog (the iPhone and iPad app and this website) is offered by 118 Performance (part of Duuriedat Beheer B.V.). Duuriedat Beheer B.V. is the controller for the personal data described here. Questions or requests: info@118performance.com.
QuiverLog has no advertising, no tracking or analytics, and we do not sell or share your data for marketing.
What we process and why
| Data | Purpose | Legal basis (GDPR art. 6) |
|---|---|---|
| Account: email address, name, and with Sign in with Apple an Apple user identifier (and Apple's relay address if you hide your email) | Your account, signing in on the app and this website, sign-in notifications | Contract (b) |
| Your logbook: equipment, sessions, settings and tags, wind and water conditions, spot names and coordinates, notes, ratings, wetsuits, body length and weight if you enter them, your profile photo, and the photos you take of your equipment and settings | Keeping your logbook and syncing it between your devices and this website | Contract (b) |
| Purchase details of equipment (Pro): price and date bought or sold | Only for your own insights (purchase and sale tracking), and only if you enter them. Never shared with third parties. | Contract (b) |
| Device push tokens | Telling your other devices that your logbook changed, so they sync | Contract (b) |
| One-time sign-in codes (stored hashed) and the IP address that asked for them; failed sign-in attempts per IP address | Signing in with email, and stopping misuse | Legitimate interest (f): a secure service |
| Security and mail logs: time, IP address, account id and what happened (sign-ins, refused requests, sent mails), never passwords, codes or tokens | Keeping accounts and the service safe | Legitimate interest (f) |
| Logs to improve QuiverLog: time, account id and what happened with your syncs, uploads and push notifications (for example a refused upload), never the content of your logbook | Only to find faults and improve QuiverLog. You can switch these off in the app under Settings › Privacy › Logs to improve QuiverLog. | Legitimate interest (f), with the right to object |
| Beta test proof: Apple's signed app transaction of a TestFlight build | Giving beta testers Pro for life | Contract (b) |
| Connections (only when you connect a service): the key you paste (stored encrypted, only its last 4 characters shown), when you agreed and for which data, and the gear and sessions fetched from that service, with a record of each fetch | Bringing your gear and sessions from that service into your logbook | Consent (a), per service; withdraw it by disconnecting |
We do not ask for special categories of data. Your body length and weight are optional and only used for your own logbook.
How we use logs
Logs are only used to keep QuiverLog safe and to find faults and improve it. They are not used for profiling, advertising or anything else, and they are not shared.
The logs to improve QuiverLog are on by default. Switch them off in the app under Settings › Privacy › Logs to improve QuiverLog; the server then stops keeping them for your account straight away. Logs that are needed for security, such as sign-ins and refused requests, are always kept, for at most 90 days.
Connections with other services
In the app under Settings › Sync, or on the website under Account › Connections, you can connect a service where you keep gear or sessions, starting with SpeedSurf. QuiverLog then fetches your gear and sessions from it: once a day, when you open the app, and when you tap Sync now. QuiverLog only reads, unless you switch on Send my settings for that connection: then the settings you log in QuiverLog for sessions that came from that service (downhaul, outhaul, the foil's mast and back wing shims, and as extra settings or notes the other settings of that session and the mast, extension and boom used) are sent to it, and nothing else. You can switch that off at any time; what was sent stays with that service, under its privacy terms. Only data the service passes on comes in (for example, rides it got from yet another service only if it shares them).
You connect at the service itself: you sign in there and choose what to share, and you never give QuiverLog your password there. The service gives us a key, which is valid for a limited time. It is checked before it is stored, kept encrypted on our server in the Netherlands and never shown again, nor written to logs. A record of each fetch (time, number of items, errors) is kept 90 days. To run the service we keep totals per day, such as the number of new and deleted accounts and of calls to a service; these say nothing about who. When you disconnect, the key is deleted straight away. The gear and sessions that came in always stay in your logbook as your own: you may have added to them in QuiverLog (settings, photos, notes, merged gear), so disconnecting never deletes them. They are no longer linked to the service and it no longer changes them. We keep only which item at the service became which item in your logbook (its id there), so that connecting again adds nothing twice; this goes when you delete your account. You can also withdraw QuiverLog's access at the service. You can still delete any gear or session yourself, or your whole account. Fetched data is part of your logbook: it is included when you ask for your data or delete your account.
AI assistants
With Pro you can connect an AI assistant of your choice, by agreeing on this website or by giving it a personal key from the app. It then reads your quiver and sessions through our MCP server. If you allow it, it can also log sessions and change their details. Nothing goes to an assistant unless you connect it. What it fetches goes to the service behind that assistant, under that service's own terms and privacy statement: you choose that service, and we have no say in what it does with the data.
We store only a hash of each key and token, the name of the key or the name the assistant gives itself, the address it goes back to, and when it was last used. Purchase prices and photos are not available to assistants. End an assistant's access in the app at any time; signing out on all devices or deleting your account ends them all.
Your location
The app asks for your location only when you tap Use my location (for a session or for Quiver advice), and only while you use the app. The location is used on your device. If you save it with a session, the spot's coordinates become part of your logbook and are synced like the rest of it. You can withdraw the permission at any time in the iPhone or iPad Settings.
Sessions that come in from a connected service get the spot's point from that service, which is the spot itself and not where you rode. When the service doesn't know the spot, a session gets a place on the map from your own sessions at a spot of that name; otherwise the app asks Apple's map service where a spot of that name is. Only the spot name is sent for that, once per name, without your account or other data, under Apple's privacy policy. The place found becomes part of your logbook like any other.
Photos
Photos you add to your equipment and to the settings of a session are synced through our server, so your other devices and this website show them too. They are stored with your logbook on our server in the Netherlands, can only be seen when you are signed in, and are never shared or used for anything else. A photo you remove, or of equipment or a session you delete, is deleted from our server within an hour of your next sync; all of them go when you delete your account. Your profile photo goes along as a small version of at most 400 pixels.
Who else receives data
- Hostnet B.V., the Netherlands (a virtual private server) hosts this website, the database and the mail server, as our processor. Everything on our server is stored in the Netherlands.
- Apple: Sign in with Apple, push notifications (APNs), the App Store and its subscriptions, TestFlight, and with Pro a daily backup file of your logbook in your own iCloud Drive, which only you can reach. Apple processes this under its own privacy policy. We never receive your payment details.
- Open-Meteo (Switzerland): when you get the weather for a session or the wind for Quiver advice, the app sends the spot's coordinates (and for a session the date) to Open-Meteo. No account details are sent.
- OpenStreetMap: the map on this website (the map page and a session's spot) loads its map tiles from OpenStreetMap, which receives your IP address and browser details. Everything else on this website, including its fonts and map code, comes from our own server.
Some of these companies are based outside the European Economic Area or may process data there (Apple in the United States; the OpenStreetMap Foundation in the United Kingdom). Transfers to the United States are covered by the EU-U.S. Data Privacy Framework or the European Commission's standard contractual clauses. Switzerland and the United Kingdom have an adequacy decision of the European Commission.
How long we keep it
- Your account and logbook: until you delete your account. Items you delete are marked deleted so your other devices delete them too.
- Sign-in codes and failed attempts: 24 hours.
- Security, mail and improvement logs: 90 days, then they are deleted automatically.
- Push tokens: until you sign out, the app is removed, or you delete your account.
- Website sign-in: a session cookie, for at most 30 days.
When you delete your account (in the app under Settings, or on this website under Account), we delete it and everything stored with it on our server straight away. Backups of the server are overwritten within the host's backup cycle. Data on your devices and in your own iCloud stays until you delete the app or that data.
Cookies
This website only uses cookies that are needed for it to work: one that keeps you signed in, and a short-lived one during Sign in with Apple. They are not used for tracking, so no consent banner is needed.
Security
All connections use HTTPS. Sign-in codes and session tokens are stored hashed, the website sends strict security headers, and sign-in attempts are limited. Nobody but you and, when needed for support or security, the people who run QuiverLog can see your logbook.
Your rights
Under the GDPR you have the right to access your data, to have it corrected or deleted, to restrict or object to its use, and to receive it in a machine-readable format (data portability). Much of this you can do yourself: see and edit your logbook in the app and on this website, and delete your account at any time. For a copy of all your data (free of charge, also without Pro) or any other request, mail info@118performance.com. We answer within one month.
Where we rely on your consent, such as location access, you can withdraw it at any time. You can also lodge a complaint with the Autoriteit Persoonsgegevens (the Dutch Data Protection Authority) or the authority in your own EU country.
Children
QuiverLog is meant for people of 16 and older. Younger users need permission from a parent or guardian.
Changes
When this statement changes, the new version is published here with a new date. If a change matters for how we use your data, we tell you in the app or by email first.