FleetFeat

Privacy policy

Last updated: June 2026

1. Controller

FleetFeat GmbH i. Gr.
Email: [to follow]

2. Hosting (Vercel)

This website is hosted by Vercel Inc. (USA). Technically necessary data (IP address, time, requested page, user agent) is processed in server logs. Legal basis: Art. 6(1)(f) GDPR (legitimate interest in secure operation). A data processing agreement is in place with Vercel; transfers to the USA are based on EU standard contractual clauses.

3. Quote and waitlist forms

When you request a quote or join the waitlist, we process the data you provide (fleet size, vehicle type, postal code, requested services, email, optional phone) to handle your enquiry. Legal basis: Art. 6(1)(b) GDPR (pre-contractual measures). Data is stored in our database (Supabase) in the EU and never sold to third parties.

4. Email delivery (Resend)

We send confirmation and transactional emails via Resend, which receives your email address for this purpose. Legal basis: Art. 6(1)(b) GDPR.

5. WhatsApp contact (optional)

If you use the WhatsApp chat, data is transferred to WhatsApp Ireland Ltd. / Meta; WhatsApp's privacy policy applies. Use is voluntary — everything can alternatively be handled via the quote form. Legal basis: Art. 6(1)(a) GDPR (consent by actively opening the chat).

6. Cookies & analytics

This website only uses technically necessary cookies (e.g. for platform user login). No analytics or marketing tools are in use. Should this change, we will update this policy and obtain required consent.

7. Platform accounts

For customer and partner accounts we process registration data (name, email, company name, role) and data captured during use (e.g. vehicles, jobs, documents, photo proofs) for contract fulfilment (Art. 6(1)(b) GDPR). Storage location is Supabase (EU).

8. Your rights

You have the right to access, rectification, erasure, restriction of processing, data portability and objection (Art. 15–21 GDPR), and the right to lodge a complaint with a supervisory authority. Contact the email address above.

9. Data protection officer

No data protection officer has been appointed, as the legal thresholds (Art. 37 GDPR, § 38 BDSG) are currently not met. The responsible contact is the controller named above.