Privacy — local documentation
Local-version documentation, not a final legal policy. Before launch, the owner must provide the operator, contacts, retention periods and approved terms.
What the application stores
Accounts store names, email addresses, password hashes and profiles. Bookings store dates, guests, prices, statuses and notes. Conversations, guide applications and administrative actions are stored in the database.
Who has access
Public profiles and published tours are visible to visitors. Booking details and conversations are restricted to participants and the administrator. Private guide narratives and other guides’ private points are not published.
Email, files and services
Uploaded photos are stored locally and their URLs are public. The map requests tiles from its provider. Newsletters require consent and confirmation; the unsubscribe link disables the subscription. Contact the operator about data requests once configured.