Privacy notice

Template notice. Do not collect live data until the controller information, lawful basis, hosting arrangements and retention policy are verified and completed.

This page explains what happens when you submit an introductory meeting request.

Who handles your information?

[Business or individual's legal name, to be configured]
Contact: [Contact email to be configured]

What we collect

Your name, your chosen contact method and either an email address or a telephone number (including country calling code), preferred appointment date and time of day, language, meeting format, selected topic, and any optional note you choose to write. We also store the request time and an internal reference number. To prevent abuse we temporarily process the sender IP address as a secret-keyed digest in hourly rate-limit records, retained for up to 48 hours. We do not ask for account balances, identification documents or sensitive financial information.

Why we use it

Only to review your meeting request, contact you through your selected channel about it and arrange next steps. The intended legal basis is our legitimate interest in answering enquiries you submit voluntarily (GDPR Article 6(1)(f)); the controller should verify this assessment before enabling collection. We do not interpret an enquiry as consent to ongoing promotional messages.

Storage and recipients

For the Firebase deployment, requests are processed by a Google Cloud Function in europe-west3 (Frankfurt, Germany) and stored in Cloud Firestore in the region chosen by the controller. Notifications containing request details are emailed to the controller through a Google Gmail SMTP account. Google Cloud and Gmail are involved in processing the details; Gmail mailbox data may be processed in other countries in accordance with Google’s applicable terms. The controller must identify and verify the Firestore location and any international-transfer arrangements before enabling intake.

How long we keep it

The intended retention period for unconfirmed requests is 90 days. Firestore records include an expiration timestamp. Anti-abuse rate-limit records have a 48-hour expiration timestamp. The operator must either enable Firestore TTL deletion on the expireAt field or manually remove records on schedule. Notification messages in the recipient mailbox must be deleted according to a corresponding retention policy. Other legal obligations, if applicable, must be disclosed by the controller.

Your rights

You can ask to access, correct or delete personal information and exercise other GDPR rights as applicable. Contact the controller above. You may also complain to the Czech Data Protection Authority (ÚOOÚ).