Privacy and personal information

Who is the data controller?

DinKøreprøve ApS is responsible for processing on this website and in our customer records. Contact us here:

Bookings and payments

We use your name, email address, phone number, language and chosen location, time, instructor, car and services to reserve and deliver your booking. We also keep the booking status, contract terms, your agreement acknowledgements and any request to start before the withdrawal period ends, together with payment and refund references.

This is necessary to enter into and perform the contract (GDPR Article 6(1)(b)). Required accounting records are processed to meet bookkeeping obligations (Article 6(1)(c)). Evidence for a specific dispute is processed for our legitimate interest in establishing or defending a legal claim (Article 6(1)(f)).

Your chosen instructor receives the contact and booking details needed to deliver the service. We send booking emails and reminders. At checkout, Stripe receives your email address, booking reference, service, location and amount. You enter card details directly with Stripe; we do not store your full card number or security code.

You normally provide the information yourself. We also receive payment status from Stripe and service updates from the instructor. We cannot complete a booking without the necessary contact and booking information. We do not book the authority's test on your behalf or retrieve your case from MinKøreprøve.

Instructor reviews

After a paid booking has been marked completed by the instructor or administration, you can give 1–5 stars and write a public comment. We send at most one invitation per booking, no earlier than two hours after the final appointment. Reviewing is voluntary. You can opt out of review emails in My bookings or by contacting us.

We link the review to your booking to verify that you are the customer. The public profile displays the stars, comment and date, but not your name, email or booking reference. Do not include personal information in your comment. You can edit your review or remove it from the profile in My bookings. Removing it clears the comment from the active review and removes its stars from the average.

Both positive and negative reviews count. Administration may hide comments containing personal information, abuse or content unrelated to the driving service. Their stars still count. We record the reason and time of moderation. Contact us if you disagree or need help with deletion. An opt-out is stored as a technical fingerprint of your email address so we can respect it on future bookings too.

Enquiries, withdrawal and complaints

The contact form records your name, email address, message, language and time so we can respond. The withdrawal form records your name, email address, booking reference or agreement description, time and receipt. We use these details to handle your notice and document receipt. You do not need to give a reason for withdrawing.

Contract enquiries are processed under Article 6(1)(b). Legally required records and receipts are processed under Article 6(1)(c). Other enquiries and dispute records are processed under Article 6(1)(f): our legitimate interest in answering enquiries and handling claims. The contact-form checkbox acknowledges this information; it is not consent to marketing.

Do not enter your CPR number, card details, health information or details of criminal offences in forms or the AI chat. We do not request your official decision documents here. If you need to discuss particular circumstances, contact us first without sending the documents.

When you use the AI assistant

The AI assistant is optional. Your question and the recent messages in the conversation are sent through Vercel AI Gateway to OpenAI to generate a reply. The chat cannot access your booking, payment or authority case. We rely on Article 6(1)(f): our legitimate interest in providing the guidance you request. You can use our guides or contact us instead.

Our requests require Vercel's Zero Data Retention and are routed only to OpenAI. Under the Gateway agreement, conversation content must not be retained after processing or used for model training. If that setting cannot be met, the request must fail. Providers may still process technical operational and usage information.

The conversation is displayed in browser memory and is not saved as a customer case in our database. The Clear conversation button removes it from the view. AI provides general guidance and makes no decisions about your driving entitlement or booking.

Instructors and partners

When you register and work with us, we process your login, name, contact information, business and approval details, teaching languages, cars, meeting points, calendar and settlement information. This administers and performs the partnership agreement (Article 6(1)(b)), supports bookkeeping (Article 6(1)(c)) and verifies approval and secure access (Article 6(1)(f)).

Approved, active profiles publicly display your name, profile description, any portrait, teaching languages, cars and meeting points. Bookable times appear in availability searches. Private login and approval details are not displayed in the public profile.

Optional connection to your calendar

Before a booking calendar is marked ready, the connection attempts to create and remove a short fictional control appointment in the past. This requires your explicit approval and contains no personal details, emails or payments. If cleanup cannot be confirmed, transfer stays closed; a retry reuses the same appointment rather than creating more.

As an instructor, you may optionally connect Google or iCloud from your instructor page. You choose which calendars block bookings and where DinKøreprøve bookings are transferred. The Google connection requests access to the calendar list, busy periods and calendars created by our connection. iCloud uses an app-specific password that you create with Apple.

We store connection credentials encrypted on the server together with your choices and permissions. They are not sent to other instructors or customers. The server continues updating after you close the website or sign out; our phone app is not required. We store busy periods to check availability. Reading from the calendar provider may involve processing event details in server memory, but event titles, attendees and private descriptions are not stored in our availability records.

Bookings are transferred to a separate DinKøreprøve calendar with their time and a generic booking description. We do not transfer the customer's name, contact details or payment information. We only modify events created by this connection. Bookings, changes and cancellations are processed automatically at short intervals; this is not an instantaneous, locked connection to other booking systems.

You may disconnect from calendar settings. This stops new reading and transfer and removes the stored access. Existing calendar copies may remain unless you separately choose to clean them up. You may also revoke access with Google or delete the app-specific password with Apple. If the connection cannot be verified, we withhold new bookings for you until it is ready again. Withdrawal does not change processing of existing booking contracts.

Browser storage and security

The booking form temporarily stores your entered contact information, choices, booking reference and access token in the tab's session storage so you can return to the reservation. It is cleared on confirmed payment or release through the form, and normally when the browser tab's session ends. A browser may restore an earlier session. Close the tab and clear the browser's site data when using a shared device.

My bookings uses your email address to send a personal sign-in link. The link is valid for 15 minutes and can be used once. A cookie then keeps you signed in for up to 8 hours. Sign out to close access on the device. The database stores only hashes of link and session secrets, together with the email address and expiry times. Expired access records are cleaned up when a new sign-in link is requested.

Password sign-in uses necessary Supabase login cookies. Customers may optionally create a password after verifying their email through My bookings. Access is limited to bookings with that verified email. Passwords are managed by Supabase and are not stored in readable form. Our website does not use advertising cookies or visitor analytics, and open and click tracking are disabled in our emails. Stripe uses its own necessary payment and security functions on the checkout page.

Operational providers process technical information such as IP addresses and request data. Our abuse protection uses a daily-changing hash derived from the network address, together with counters and timestamps. Hashing is not the same as anonymisation. Security and administration logs support troubleshooting, accountability and protection against abuse under Article 6(1)(f).

How long do we keep information?

Booking information is kept while the reservation, service, settlement or a related enquiry is being handled. We then assess which details remain necessary for accounting or a specific claim and delete or anonymise the rest. A reservation deadline releases the instructor and car; it is not a personal-data deletion deadline.

Enquiries and withdrawal notices are reviewed when the case and necessary follow-up are complete. Only information still needed for a contract, required records or a specific claim is kept thereafter. Profile information is reviewed when the partnership ends. Security data is assessed according to whether it is still needed for an incident, troubleshooting or accountability.

Accounting material is generally retained for five years from the end of the financial year it relates to. This does not mean every enquiry or chat question must be kept for five years. Evidence for a specific dispute may be retained until the claim and any applicable deadlines are resolved.

Deletion also covers relevant copies in email and message queues. Restricted backups may remain until their normal provider retention expires and must not be used for routine customer processing. Contact us to find out what information we specifically hold about you and why.

Your rights

Contact kontakt@dinkoreprove.dk to request access, correction, deletion, restriction and, where the conditions apply, a copy in a commonly used electronic format (data portability). You may object to processing based on legitimate interests. We assess each request; required accounting records or evidence of claims may be exempt from deletion.

We may ask for the information needed to identify you securely and normally respond within one month. Do not send identity documents unless requested. Where processing relies on consent, you can withdraw it without affecting earlier lawful processing. You may complain to the Danish Data Protection Agency at datatilsynet.dk.

Complain to the Danish Data Protection Agency

Providers, recipients and countries

We use the following providers for the purposes described. They process information relevant to their role:

• Supabase: Database and sign-in. Our database is located in Ireland (EU). Data processing addendum.
• Vercel: Website hosting, server processing, security logs and AI Gateway. Processing may take place in the USA. Data processing addendum.
• Resend: Service and contact emails, including recipient address, content and delivery status. A European sending region does not mean all processing stays in the EU; Resend states that its primary processing is in the USA. Data processing addendum.
• DanDomain / team.blue: Our mailbox for enquiries and replies. Data protection and agreements.
• Stripe: Payments, payment checks and refunds. Stripe Payments Europe, Limited in Ireland is our European payment provider and may also process data in the USA. Stripe acts as an independent controller for some purposes, including required payment checks and fraud prevention. Stripe's privacy policy.
• OpenAI: Processes the questions and answers sent through the optional AI assistant via Vercel AI Gateway. Processing may take place in the USA. See the AI section above for our settings. Gateway data handling.

An EU database location therefore does not mean all information is processed exclusively in the EU. Processing outside the EU/EEA uses the applicable transfer mechanisms in provider agreements, including European Commission Standard Contractual Clauses and any applicable adequacy decisions. The agreements above describe safeguards and subprocessors. Contact us for a copy of the relevant transfer mechanism and information about countries involved in your particular processing.

We also share necessary information with your instructor and, where relevant, an accountant, auditor, adviser or authority when needed for an agreement, a specific claim or a legal obligation. We do not sell your information or use it for advertising profiling.