Privacy policy

1. Who is responsible

The software uses the name DushiDesk and publishes privacy@dushidesk.com as the address for privacy questions. That address is in the code. The product does not store a legal entity, Chamber of Commerce number or business address.

TODO-MIKE: fill in the legal entity, the Chamber of Commerce number, the business address and the data protection officer contact. Also confirm whether privacy@dushidesk.com is the mailbox that is read for this.

2. Data the software processes

Only the data below exists in the software. There is no separate messaging system between guest and host.

Account: name, email address, password as a hash, optional photo URL, language, preferred market, role, linked organisation, and which version of the terms and this policy you accepted, with time and source (email signup or Google).

Session: session token, IP address, browser data (user agent) and expiry. The IP address is also the key for request limits.

Google login: only when Google login is enabled on the server. The software then stores the link and the tokens Google returns, on the server.

Workspace booking: name, email address, date, optional end date, language, notes, group size, names and email addresses of extra guests, price in cents, currency, status and source (website or an internal operator). A check-in code is created for check-in.

Hospitality reservation: name, email address, optional phone number, date, time, number of guests and notes.

Review: name, score, text and optional photo URLs.

Host organisation: name, email, phone, country, and if the host fills them in, the Chamber number, statutory name, address and website. A comparison with public Chamber publications is a risk signal for an admin. The software does not deactivate a host because of it and does not call it verification.

On-site measurement: only after you allow analytics in the cookie notice, and for a signed-in account also in the account choices. Stored are the action type, the listing, the screen (search or detail), the language and the island. No IP address, no visitor id and no guest data.

Cookie choice and account choices: whether you turned on analytics, advertising, newsletter, partner offers, personal recommendations or push notifications. Push notifications have no delivery channel. The choice can be on in the account, but nothing is sent.

Signup to stay informed: the email address is sent by email to info@dushidesk.com. It is not stored in the database.

Photos a host uploads are stored in the workspace-images bucket.

Optional two-factor authentication: a secret and encrypted recovery codes, only if you turn that feature on.

When a host asks for a text proposal, the server sends the listing details to the configured AI service (Google Gemini when GEMINI_API_KEY is set, or a separate Papiamentu service when that URL is set).

Optional location: only after you press ‘Use my location’. The browser gives this page your coordinates. The page chooses a supported country on your device and then forgets the coordinates. They are not sent to the server. Outside those countries, or if you refuse, nothing is stored and your current country stays.

3. Purposes

The software uses this data to create an account, deliver a booking or reservation to the host, send transactional email (verification, password, booking), limit abuse through sessions and request limits, and load analytics or the advertising and chat widget only after consent.

TODO-MIKE: record the legal basis for each purpose. The software does not store a legal basis.

4. Services and recipients

These are the services the code can call. An optional service runs only when its server setting is present.

Supabase provides the Postgres database and storage for listing photos (bucket workspace-images). Sign-in is done by the software itself with Better Auth. Sessions live in the same database, not with a separate Supabase authentication service.

Resend sends transactional email, such as verification, password reset, booking mail and the signup to stay informed.

Vercel hosts the application.

Google: optional login, a server call to Gemini for host text when the key is set, and Google Tag Manager only after you allow analytics and a container id is configured.

The leadbot.maixs.nl chat widget loads only after you allow advertising and the server has an approved policy configuration for that widget.

The host of the listing receives the booking or reservation for that listing, by email and in the host area.

Mollie is not used for a workspace booking. Payment happens on location. The software can call Mollie for an advertising order, and only with a server key and a reviewed advertising policy.

An external Papiamentu text service is called only when a server URL is set for it.

If a host chooses the TheFork widget, the listing loads an iframe from module.lafourchette.com. The TheFork API itself does not make a request in this software. A reservation through that method falls back to email to the host.

The software has no function that sells personal data.

5. Cookies and local storage

Necessary cookies are set without a separate consent, because the site does not work without them.

Better Auth session cookie (better-auth.session_token, with the __Secure- prefix on HTTPS). The code does not set its own lifetime. The cookie expires with the session and is removed on logout.

NEXT_LOCALE stores the language you chose, for one year. It is used on private pages and when a browser opens the homepage. The site does not read the browser language or your IP address for this.

dushidesk-market and dushidesk-market-currency store the country and currency you chose, or the country picked after you press ‘Use my location’, for one year. That button does not store coordinates.

dushidesk-cookie-consent stores your choice for analytics and advertising, for one year, as a cookie and in localStorage under the same name.

Google Tag Manager and the chat widget are not loaded until you turn that choice on. Without an approved policy configuration those choices stay off.

You can reopen the choice through the cookie settings in your account, or by clearing DushiDesk site data in the browser.

6. Security in the software

Traffic uses HTTPS. Passwords are stored as a hash. Logs strip email addresses, tokens and keys. Host keys for AI and TheFork are stored encrypted. This describes the code. It is not a certification.

7. What you can do in the product

In a signed-in account you can download your data as JSON, withdraw consent and close the account. Export and deletion require a login from the last five minutes.

Closing removes login details, sessions and connected apps. Bookings, advertising payments and audit data can remain for an operational review. The result says so, with a request number.

TODO-MIKE: confirm which legal rights apply, including correction and objection. The software has no separate correction form.

8. Retention

No default retention period is set in the software. A category is cleaned up only when the server configuration contains a period for that category. Without that configuration nothing is deleted automatically.

TODO-MIKE: set the retention period per category (account, booking, reservation, review, measurement, logs).

9. Changes to this text

This page shows the text that is in the software. The software does not send an email when this text changes.

TODO-MIKE: decide whether a change is announced by email.

10. Contact

Questions about this text can go to the address the software publishes: privacy@dushidesk.com. General questions go to info@dushidesk.com.

TODO-MIKE: confirm who reads this mailbox and whether there is a data protection officer.

Server configuration

The server configuration names this controller:

WE Group N.V. · privacy@dushidesk.com