Kauflist.Back to Kauflist

Privacy

Privacy Policy

How Kauflist handles account, wishlist, and analytics information.

Draft—not ready for merchant review.Add the company environment values listed in .env.example, then obtain professional legal review.

Effective: 8 August 2026

1. Controller

[Required before launch: company legal name], [Required before launch: registered address]. Contact: [Required before launch: privacy contact email].

2. Data we process

We process account identifiers, email address, authentication events, wishlist and product information you submit, support messages, and limited first-party usage events. Kauflist does not currently collect payment information.

3. Purposes and legal bases

We use this information to provide accounts and wishlists, secure the service, answer requests, and understand aggregate product usage. Processing is based on contract performance, legal obligations, legitimate interests in operating a secure service, or consent where required.

4. Service providers

Kauflist uses Supabase for authentication and database hosting and Vercel for application hosting and privacy-conscious web analytics. Their own privacy terms also apply.

5. Retention and security

We keep account and wishlist data while your account is active and for only as long afterwards as required for support, security, accounting, and legal obligations. Access controls, row-level database security, encrypted transport, and restricted administrator access are used to protect information.

6. Your rights

Depending on applicable law, you may request access, correction, deletion, restriction, portability, or object to processing. You may also complain to a competent data-protection authority. Send requests to [Required before launch: privacy contact email].

7. Cookies and local storage

Kauflist uses local storage for local wishlists, session-related browser state, and one random analytics identifier. Essential storage is required for requested functionality. Any future non-essential tracking will require an appropriate consent mechanism before activation.