Kørt Privacy Policy
Last updated 2 November 2026 · Version 1.6 · Dansk udgave
This is an English translation of the Danish privacy policy. If the two versions differ, the Danish version applies.
This privacy policy explains how Kørt processes personal data when you use our app, web app, website and support.
Kørt helps you record your driving, keep a mileage log, keep track of trips and shifts, and calculate and export information about the Danish commuting deduction (befordringsfradrag) and tax-free mileage allowance (kørselsgodtgørelse). Kørt is not affiliated with the Danish Tax Agency (Skattestyrelsen) or any other public authority.
Personal data is any information that can be linked directly or indirectly to a person. In Kørt this includes, among other things, account details, addresses, precise locations, movement patterns and mileage log entries.
1. Who is responsible for your data?
The data controller for the processing described in this privacy policy is:
Birkholm DigitalCVR no. (Danish business registration): 45056635
Kildevej 7, 7870 Roslev, Denmark
Email for personal data matters: kontakt@koert.dk
Website: https://koert.dk
In this policy, “we”, “us” and “our” mean Birkholm Digital.
You can contact us at kontakt@koert.dk if you have questions about how we process personal data or want to exercise your rights.
Where we process data on behalf of a business customer, the allocation of responsibility described below under “Use through a company or employer” applies.
Use through a company or employer
Kørt is currently offered to individuals who keep their own mileage log. We do not offer solutions where a company or employer controls the processing of employees’ data in Kørt.
If we offer this in the future, we will be the data processor for the data we process solely on the company’s documented instructions, and the company will be the data controller. That processing will be covered by a data processing agreement, and we will update this policy before such processing begins.
The allocation of responsibility follows the actual processing. See the Danish Data Protection Agency’s guidance on controller and processor roles (in Danish).
2. What data do we process?
The data we process depends on which features you use.
Account and login
- Email address and an internal user ID.
- When your account was created and changed.
- A secure hash of your password.
- Login and security information, including information used to revoke access from your devices.
- Temporary information for resetting your password.
- If we offer Google sign-in and you choose it: your Google account identifier and email address. Google sign-in is not offered today.
Your password is processed only to create or check the secure hash. It is never stored in readable form.
Profile, home address and vehicle
- Name.
- Home address and its coordinates.
- Municipality, locality and any corrections to how your home address affects the deduction calculation.
- Names of mileage log profiles, type of work and the chosen calculation method.
- The vehicle’s name and type, and its registration number if you enter it.
- Odometer reading at the start and end of the day or shift.
- Your settings and any custom rates.
Trips, shifts and financial information
- Times of trips, stops, breaks and shifts.
- Start and end positions, addresses and place names.
- Distances, durations, route outlines and detailed GPS tracks.
- The trip’s purpose and classification, for example business or private.
- Stops and visits at known places.
- Calculated kilometres, rates, deductions and allowances.
- Earnings, if you record them yourself.
- Your corrections, the previous values and when the correction was made.
- Export choices and information about generated reports.
- Your Danish personal identification number (CPR number), if you enter it yourself for the mileage allowance statement (see section 18).
Subscription
- When your trial period ends and whether the account is exempt from payment.
- The purchase ID at Google Play (purchase token), the name and status of the subscription, when it renews or expires, and whether auto-renewal is on.
- Whether the purchase is a test purchase.
Payment takes place at Google Play. We never receive your card number or other payment details.
Location, steps and movement
- Precise GPS coordinates and the time of each measurement.
- Speed and the accuracy of the GPS measurement.
- Steps in connection with a stop.
- Information that the phone detects movement on foot.
- Derived information about driving, parking, stops, walking and visits.
This data is used to tell driving apart from walking, identify stops and place start and end addresses correctly. When suggesting addresses, the phone’s last known position may be used to rank nearby addresses first.
Support, feedback and technical information
- Messages you send us and any content you attach.
- Contact and account information relevant to your enquiry.
- App version, platform, device information and the screen from which feedback was sent.
- Technical information about the operation of the GPS service and any interruptions.
- Error messages and diagnostic information.
- IP address, time and technical information when your device communicates with our services or the external services we use.
We also keep separate copies of received GPS uploads for troubleshooting for 30 days. They may contain detailed positions and other information from the upload.
3. Where does the data come from?
- From you, when you create an account, enter information, correct trips, export reports or contact us.
- From your phone or browser, when you use location, activity recognition or other features.
- From Google, if Google sign-in is offered and you choose it.
- From public address registers and map and place services.
- From calculations and analysis of your recordings, for example trip classification, visit history and distances.
Our place and address data comes from, among others, the Danish Address Register via Datafordeleren, OpenStreetMap and Google.
4. Why do we process data, and on what legal basis?
We only process the data necessary for the purpose in question.
| Purpose | Data | Legal basis |
|---|---|---|
| Create your account, give access and manage your use of Kørt | Account, login and profile data | GDPR Art. 6(1)(b): performance of our contract with you |
| Keep the mileage log, store trips and shifts, calculate summaries and generate reports | Mileage log, vehicle, address and calculation data | Art. 6(1)(b) |
| Provide the automatic trip recording you turn on | GPS, movement, stop and trip data | Art. 6(1)(b), for processing objectively necessary for the feature |
| Answer questions and help with specific problems | Contact details, messages and relevant account data | Art. 6(1)(b) for help with the service; Art. 6(1)(f) for other enquiries |
| Protect accounts and services against misuse and investigate security incidents | Necessary security and technical data | Art. 6(1)(f): our legitimate interest in secure operation |
| Investigate specific recording errors and keep recordings reliable | Diagnostic data and separate GPS uploads (30 days) | Art. 6(1)(f): our legitimate interest in finding and fixing errors in the recording you use. The copies are used only for troubleshooting and deleted after 30 days |
| Improve shared identification of pickup places and traffic stops | Place data, stops, coordinates and internal user references | Art. 6(1)(f): our and other users’ legitimate interest in more accurate recordings. Other users never see who contributed (see section 7) |
| Manage your subscription and verify the purchase with Google Play | Subscription data and your internal user ID | Art. 6(1)(b) |
| Keep a necessary operational overview | Limited data about accounts, activity, number of trips and kilometres, and the latest trips with purpose and place name when needed for operations and support | Art. 6(1)(f): our legitimate interest in managing and sizing the service |
| Meet a specific legal obligation | The data the obligation requires | Art. 6(1)(c), together with the specific legal provision, for example the Danish Bookkeeping Act for our own accounts |
| Establish, exercise or defend legal claims | Data necessary for the specific claim | Art. 6(1)(f): our legitimate interest in handling legal claims |
We do not use any analytics or tracking technologies for marketing or for statistics about your behaviour.
When we rely on legitimate interests, we weigh our interest against your rights and reasonable expectations. You can object as described in section 15.
We do not sell your personal data, and we do not use your mileage log or location data for targeted advertising.
5. GPS, background tracking and your choices
Kørt records your location during a trip or shift that you start yourself. If background recording is enabled and supported on your device, recording continues while the screen is locked or you use other apps. While recording is active, Android shows a persistent notification.
Automatic tracking. In a regular mileage log (not a courier log) on Android, you can turn on automatic tracking under Settings. The phone’s activity recognition then watches for when you are in a vehicle, and recording starts by itself when you begin driving, even when the app is closed. It stops again when the vehicle has been stationary for 15 minutes and then waits for the next drive. The feature is off until you turn it on, and you can turn it off again in the same place or by removing the physical activity permission. If you have set fixed working hours, automatic tracking only starts within them (with a 30-minute margin), and they are used to suggest whether a trip is business or private. If you log out or switch accounts on the phone, automatic tracking stops so that trips do not end up in another account.
During an active shift, recording may cover the whole period while tracking runs. This may also include private movements if you keep tracking running during a private errand.
You can end recording or use the app’s pause function. When a shift is paused, ongoing GPS recording stops. Data already recorded may still be saved and sent to the server. The app can resume an ongoing recording after a technical interruption or restart so that the recording is not lost.
The app asks for the phone’s permissions for location (including in the background) and physical activity. You can change or remove them at any time in the phone’s settings under Apps → Kørt → Permissions. If you refuse a necessary permission, automatic recording cannot work or works with lower accuracy. Manual entry can still be used.
Location and movement data is processed because it is necessary for the trip recording you start yourself or have turned on automatically (section 4). The phone’s permission dialog is not GDPR consent; it controls whether the app technically has access.
6. Automatic classification and personalisation
Kørt analyses recordings to suggest, among other things:
- Where a trip starts and ends.
- Whether a stop looks like traffic, a pickup, a delivery or a private stop.
- Which place or address a stop relates to.
- Whether information should be checked.
- Whether another vehicle better matches the recorded movement pattern.
The analysis may use position, speed, stop duration, steps, active shift, known places, previous visits and your corrections. Your earlier confirmations may be used to tailor future suggestions. This analysis may constitute profiling because it assesses aspects of your movement and work patterns.
Suggestions and calculations may contain errors, and you can review and correct the recordings. Kørt makes no decisions based solely on automated processing that have legal or similarly significant effects for you. Decisions about your tax, your employment or your entitlement to payment are made by the relevant authority or other responsible party.
See the Danish Data Protection Agency’s guidance on profiling and automated decisions (in Danish).
7. Shared pickup places and shared traffic data
Shared pickup places
Kørt uses a shared register of, among other things, restaurants and pickup places. Places that users save in the pickup place category may be used to supplement the register. This requires information from at least three different users near the same place and agreement from at least two on the place’s name.
A shared place contains only a name, a position and possibly an address. Who contributed is not stored, and other users get no access to your account, your mileage log or the fact that you contributed. Your personal places in the categories home, customer and private are never included.
Shared traffic data
Kørt uses information about traffic stops to recognise places where a stop is probably caused by traffic rather than a delivery or pickup. The information is grouped into small geographic areas and includes position, number of stops and internal user IDs linked to the contributions. The internal IDs are personal data as long as they can be linked to a user. Other users only receive the result, as help for their own trip recording.
The basis for both shared features is our legitimate interest (section 4). Traffic data is kept as long as the area is used in recording. When you delete your account, your ID and your contributions are removed from the traffic data, and areas with no other contributions are deleted. You can object to your contributions by writing to kontakt@koert.dk. You can also opt out of a specific shared place for your own trips in the app.
8. Local storage and offline use
Kørt stores data on your device to support login, settings, ongoing recordings and offline use:
- Login information and access tokens.
- Settings and temporarily stored information.
- GPS points from an ongoing recording.
- Trips waiting to be uploaded, and failed uploads kept so they can be sent again.
When the connection returns, pending data is sent to our server automatically. In the mobile app, login is kept in the phone’s secure storage. In the web app, login is kept in the browser’s local storage.
Deleting the app is not the same as deleting your account with us, and deleting the account does not remove data still on your phone. Uninstall the app to remove all local data from the phone, and log out of the web app to remove the login from the browser.
9. Cookies and similar technologies
Kørt uses no cookies or other technologies for marketing, analysing your behaviour or tracking across services. That is why we show no cookie dialog.
We only use storage on your device that is necessary for the service you have requested:
- Login – the mobile app’s secure storage and the web app’s local storage. Access expires after 7 days without renewal and is removed when you log out.
- Settings, ongoing recording and upload queue – the app’s local storage, until the data has been sent or the app is uninstalled.
The website sets no cookies, and its fonts are hosted on our own server, so nothing is fetched from Google when you visit it.
See the Danish Agency for Digital Government’s and Data Protection Agency’s cookie guidance (in Danish).
10. Who receives data?
Hosting and database
Kørt’s server and database are hosted by Hetzner Online GmbH in Germany. The database, mileage log data and server-generated reports are stored there.
Addresses and public place data
Kørt uses a copy of the Danish Address Register on our own server for Danish address lookups. The copy is updated from Datafordeleren, but your mileage log is not sent to the register provider.
We use Google services for map display in the mobile app, calculating manual routes, calculating individual missing stretches of a recorded track, and supplementary address and place search. Depending on the feature, Google may receive coordinates, start and end points, search text and technical information from the connection, including your IP address. The map in the mobile app is provided by the Google Maps SDK, which may itself collect technical information such as a device identifier, crash and diagnostic data and how you interact with the map. Google may be an independent data controller for parts of the processing. See Google’s data protection terms and Google’s privacy policy.
OpenStreetMap
Kørt uses OpenStreetMap data, most of which is stored on our own server. For external lookups, coordinates, search area and search text may be sent to Nominatim (nominatim.openstreetmap.org, run by the OpenStreetMap Foundation) or to the Overpass services overpass-api.de (Germany) and, as a fallback, overpass.kumi.systems. The web app’s map fetches map tiles directly from OpenStreetMap and thereby passes on your IP address and the map area shown. See the OpenStreetMap Foundation’s privacy policy.
Google Play (payment)
The subscription is bought and paid for in Google Play. At purchase, the app sends your internal user ID to Google so that the purchase belongs to your account. Our server asks Google Play for the purchase status and receives notice from Google when the subscription renews, is cancelled or expires. Google is an independent data controller for the payment. If you delete your account, we ask Google Play to stop the renewal.
Sentry
For technical error reports from the app and server we use Sentry (Functional Software, Inc.), with data stored in Sentry’s EU region in Germany. A report is only sent when an error occurs. The report may contain the error description, app version, platform and technical events leading up to the error. We do not send trips, GPS tracks or addresses as error reports.
Email and support
For password reset emails and forwarding feedback we use Resend (Resend, Inc.). The provider receives the recipient address and the content of the email. For feedback, the content may include your name, email address, your message and technical context.
App updates
The app and its updates are delivered through Expo (650 Industries, Inc.). When the app fetches an update, Expo receives technical information such as IP address, app version and platform – not your trips or your mileage log.
Authorised personnel and authorities
Authorised personnel may get access to the extent necessary for operations, support, troubleshooting, security or handling your rights. We only disclose data to authorities when we are legally required to, and we limit the disclosure to the specific requirement.
We do not give your employer, Wolt, other platforms or the Danish Tax Agency access to your mileage log just because you choose a particular type of work in the app. Data processors that process data on our behalf are covered by a data processing agreement.
11. Transfers outside the EU/EEA
Our server is in the EU. Google, Sentry, Resend and Expo are US companies, so data may be processed or accessed from the United States, even when it is stored in the EU.
Transfers are based on the EU-U.S. Data Privacy Framework where the provider is certified under it, and otherwise on the European Commission’s standard contractual clauses with the necessary supplementary measures. You can contact us for information about the transfers and a copy of the relevant safeguards.
See the Danish Data Protection Agency’s guidance on third-country transfers (in Danish).
12. How long do we keep data?
| Data | Retention |
|---|---|
| Account data | As long as you have an account. Accounts inactive for 5 years are deleted after notice by email. |
| Trips, shifts, profiles, places and calculations | As long as you have an account, so your mileage log can be documented to the Danish tax authorities. You can delete individual trips yourself. |
| GPS tracks and walking segments in the mileage log | Together with the trip they belong to. They are deleted when the trip or the account is deleted. |
| Separate GPS uploads for troubleshooting | 30 days. Clean-up runs at server start and every six hours. |
| Export files on the server | 30 days. The record that an export was made is deleted together with the account. |
| CPR number | Stored only on your phone until you remove it or uninstall the app. An export file containing the CPR number is deleted from the server when you have downloaded it, and otherwise after 30 days at the latest. |
| Correction history | Together with the trip it belongs to. |
| Support and feedback | 12 months after the enquiry. Feedback from the app is deleted automatically; emails are deleted manually. |
| Server logs | Short term. The application’s logs are cleared with every server update and are limited in size; nightly job logs are deleted after 30 days at most. |
| Error reports in Sentry | 90 days by default. |
| Contributions to shared traffic data | As long as the area is used; your ID and contributions are removed when you delete your account. |
| Local recordings and upload queues on the phone | Until they are sent or the app is uninstalled. |
| Database backups | 14 days on the server. In addition, encrypted copies on Google Drive: 7 daily and 5 weekly (36 days at most). The copies are encrypted before they leave the server, and Google does not have the key. |
| Subscription data | As long as you have an account. |
| The server’s automatic backups at Hetzner | Up to 7 days. |
| Data for specific legal claims | Until the case is closed and relevant time limits have expired. |
Archiving a mileage log profile is not the same as deleting it if the profile still has trips.
13. Account deletion and backups
You can delete your account in the app under Settings → About the app → Delete my account, on koert.dk/slet-konto.html, or by writing to kontakt@koert.dk.
Deletion happens immediately and covers the account, profiles, vehicles, places, trips, GPS tracks, shifts, corrections, export files, separate GPS uploads and your contributions to the shared traffic data. Support emails are deleted on request. Shared pickup places contain no information about who contributed and remain.
Deleted data may remain in backups until they expire (36 days at most). Backups are not used for normal operations, and if a backup is restored, we carry out earlier deletions again before the system is put back into use.
Reports you have downloaded or shared yourself are not deleted from the recipient’s system when you delete your account.
14. Security
We protect personal data against unauthorised access, loss and alteration, including through:
- Encrypted connection between app and server via HTTPS.
- Passwords stored as a secure hash.
- Access control and separation of users’ data.
- The option to revoke account access from devices.
- Limits on login attempts and other measures against misuse.
- Two-step login with a one-time code for administrator access.
- Restricted access to the database and backups.
If a security breach is likely to result in a high risk to your rights, we notify you without undue delay. See the Danish Data Protection Agency’s guidance on security breaches (in Danish).
15. Your rights
Access
You can find out whether we process data about you, receive a copy, and get information about, among other things, purposes, recipients and retention.
Rectification
You can have incorrect data corrected and incomplete data completed. You can correct much of the data yourself in the app.
Erasure
You can require data to be erased when the conditions are met. The right is not absolute; a specific legal obligation or legal claim may justify limited continued storage.
Restriction
In certain situations you can have processing restricted, for example while the accuracy of data is being checked.
Objection
When processing is based on legitimate interests, you can object on grounds relating to your particular situation. We will then stop the processing unless we can demonstrate compelling legitimate grounds or the processing is necessary for a legal claim.
Data portability
When the conditions are met, you can receive the data you have provided to us in a structured, commonly used and machine-readable format. In the app you can download it yourself for free under About the app → Download my data. A regular mileage log export is not necessarily a complete answer to a request for access or data portability.
How to exercise your rights
Write to kontakt@koert.dk. We reply without undue delay and within one month of receipt at the latest. For complex requests the deadline may be extended by up to two months; if so, you will be told within the first month. We may ask for information necessary to confirm your identity. Exercising your rights is free, unless the legal conditions for a fee or refusal are met.
See the Danish Data Protection Agency’s overview of your rights (in Danish).
16. Consent
Today, Kørt bases only one processing activity on consent: your CPR number on the mileage allowance statement, if you enter it yourself (section 18). If we introduce another feature that requires consent, we will ask for it separately, and you can withdraw it at any time as easily as you gave it. Withdrawal does not affect the lawfulness of processing before the withdrawal.
Reading or accepting this privacy policy is not in itself consent.
17. What data do you have to provide?
To create an account you must provide an email address and a password. Other data is necessary for certain features:
- Automatic trip recording requires the necessary location permissions.
- Your home address may be necessary for certain deduction calculations.
- Calculations may require vehicle type, dates and distances.
- A complete report may require name, purpose, addresses and odometer readings.
Recording earnings and sending feedback is voluntary.
18. Data about others and special categories of data
A mileage log may contain data about others, for example customer addresses. Only record data necessary for the purpose of the mileage log, and do not enter CPR numbers, health information or other special categories of data in free text and feedback.
Your CPR number on the mileage allowance statement
Under Danish rules, a statement for tax-free mileage allowance must contain the recipient’s name, address and CPR number (Executive Order on travel and transport allowances, section 2). You can therefore enter your CPR number in the app yourself when you export a mileage log with mileage allowance. It is voluntary. Without the number, the statement has a line you can fill in by hand.
- The number is stored only on your phone (in the phone’s secure storage). You can remove it in the app at any time.
- When you make the export, the number is sent encrypted to the server and printed on the front page of the report. It is not stored in our database, and it is not included in error reports.
- The report with the number is deleted from the server as soon as you have downloaded it, and otherwise after 30 days at the latest. During the short time the file is on the server, it may be included in the server’s automatic backup, which is deleted after 7 days at most.
- The number is only included for mileage allowance, not for the commuting deduction or deductions in your own business.
The processing is based on your consent (Danish Data Protection Act section 11(2)(2)), which you give by entering the number yourself and making the export. You can withdraw consent by removing the number in the app.
Location data can reveal private matters, for example visits to a clinic or a religious place. We do not use the data for the purpose of inferring health, religion, political opinion or similar sensitive matters.
19. Age limit
Kørt is designed for recording driving and work-related trips and is intended for people aged 18 and over. If we become aware that an account belongs to someone under 18, we delete it.
20. Exports and sharing you choose yourself
You can export mileage log data to reports containing, among other things, name, addresses, times, purposes, distances, odometer readings and calculated amounts. If you share a report with, for example, an accountant, employer or authority, that recipient receives the data the report contains, and the recipient’s processing is subject to the recipient’s own obligations. Check the report’s content and the recipient before sharing it.
21. Complaints
You can contact us if you are dissatisfied with how we process personal data. You also have the right to complain to the Danish Data Protection Agency (Datatilsynet); you do not have to contact us first.
DatatilsynetCarl Jacobsens Vej 35, 2500 Valby, Denmark
Phone: +45 33 19 32 00
Email: dt@datatilsynet.dk
22. Changes to this policy
We update the policy when our processing changes or when the information needs clarifying. For significant changes, we give clear notice in the app or by email. The date and version at the top show when the policy was last updated.