LGPD · Law 13.709/2018
Privacy Policy
Last updated: [CONFIRM date]
[CONFIRM — this document is a structural template within the mockup. It must be reviewed by a lawyer and completed with the company's real details before launch. No company name, CNPJ, address, email or period below is real.]
1. Data controller
The controller of personal data processed through this site is [CONFIRM registered company name], CNPJ [CONFIRM], registered office at [CONFIRM full address], Florianópolis — Santa Catarina, Brazil.
Privacy contact: [CONFIRM DPO email]. Data Protection Officer: [CONFIRM name or “not applicable”].
2. What we collect and why
| Data | When | Purpose | Legal basis (LGPD art. 7) |
|---|---|---|---|
| Name | Booking / order form | Identify the booking or order | Pre-contractual steps (item V) |
| Phone / WhatsApp | Booking form | Confirm and notify changes | Pre-contractual steps (item V) |
| Date, time, party size | Booking form | Manage the dining room | Pre-contractual steps (item V) |
| Dietary restrictions and allergies | Booking form | Food safety — potentially sensitive data | Consent (item I) |
| Newsletter, if subscribed | Send communications | Consent (item I) | |
| Analytics cookies | Browsing, if permitted | Measure site usage | Consent (item I) |
| Marketing cookies | Browsing, if permitted | Measure campaigns | Consent (item I) |
| Event date | Event enquiry form | To check diary availability and format. It is a fact about somebody’s life, not a lead field: restricted access and no marketing use | Pre-contractual steps (art. 7, V) |
| Estimated guest count | Event enquiry form | To know whether the space takes it, and in what format | Pre-contractual steps (art. 7, V) |
| Budget range | Event enquiry form | To build a proposal that fits. It indicates financial capacity, so it is not exported to a marketing tool and not used for segmentation | Pre-contractual steps (art. 7, V) |
| Event type (wedding, graduation, corporate) | Event enquiry form | To decide format and staffing. It reveals a personal occasion and gets the same care as the date | Pre-contractual steps (art. 7, V) |
| Guest names and contacts on an event list | Event contract, where a list is provided | To organise reception and dietary requirements. It is third-party data handed over by the buyer, and each guest remains a data subject | Performance of a contract (art. 7, V) |
| Deposit, balance and payment details | Event contract | To reconcile payment and issue an invoice. The payment instrument stays with the financial institution | Performance of a contract (art. 7, V) and tax obligation (art. 7, II) |
The notes field on a booking and the guest list for an event usually carry dietary restrictions and allergies. That is sensitive health data under LGPD art. 5, II, and art. 11 requires specific, highlighted consent for a stated purpose — here, preparing and serving the meal safely. It is not there to segment a list or build an ad audience.
3. Cookies
Essential cookies keep the site working and remember your consent choice; they cannot be switched off. Analytics and marketing cookies are off by default and are only enabled if you tick the matching option in the banner. You can revisit your choice at any time by clearing site data in your browser.
| Category | Default | Examples | Retention |
|---|---|---|---|
| Essential | Always on | Consent record (stored in your browser) | [CONFIRM] |
| Analytics | Off | [CONFIRM tool — e.g. Google Analytics 4] | [CONFIRM] |
| Marketing | Off | [CONFIRM tool — e.g. Meta Pixel] | [CONFIRM] |
4. WhatsApp
The buttons on this site open a WhatsApp conversation with a pre-filled message. From the moment you send that message, the processing of your data in that app is also governed by Meta Platforms' privacy policy, over which we have no control.
5. Sharing
We do not sell personal data. We share it only with processors necessary to deliver the service:
- Website hosting — [CONFIRM]
- Analytics tool, if permitted — [CONFIRM]
- WhatsApp / Meta Platforms, when you start the conversation
- Public authorities, where legally required
International transfers: [CONFIRM — likely, if hosting or analytics sit outside Brazil. State the countries and safeguards.]
6. How long we keep it
Contact data and enquiries: [CONFIRM period]. Consent records: [CONFIRM period]. After that, data is deleted or anonymised, unless a legal retention duty applies.
7. Your rights (LGPD art. 18)
At any time, free of charge, you may request:
- confirmation that processing exists;
- access to your data;
- correction of incomplete, inaccurate or out-of-date data;
- anonymisation, blocking or deletion of unnecessary or non-compliant data;
- portability to another provider;
- deletion of data processed on the basis of consent;
- information about who we share your data with;
- information about your right to refuse consent and the consequences;
- withdrawal of consent.
To exercise any of these, write to [CONFIRM email]. We will reply within the statutory period. You may also petition the ANPD, Brazil's data protection authority.
8. Security
We apply technical and administrative measures to protect personal data. [CONFIRM measures — e.g. HTTPS, access control, backups]. In the event of a significant security incident we will notify you and the ANPD under art. 48.
9. Minors
This site is not directed at people under 18 and does not knowingly collect children's data. No image on this site depicts children or minors.
10. Changes
We may update this policy. The date at the top shows the last revision. Material changes will be flagged on the site.
An event enquiry is a dossier
Name, WhatsApp, event type, date, guest count and budget range. Together those six fields describe a private occasion and a financial position — and they sit in an inbox until somebody answers.
So they are restricted to whoever builds the proposal, they are not exported to a marketing tool, a shared spreadsheet or a messaging group, and they do not feed ad segmentation. An enquiry that did not become a contract is deleted within the period stated below [CONFIRM the period].
The date is the delicate part. “Wedding, 14/03, 120 guests” is not a CRM field: it is a fact about somebody’s life, often months before they tell the rest of the world.
Guest lists: third-party data
When an event has a guest list, the buyer hands over other people’s names and, often, their dietary restrictions. Each guest remains a data subject: they can ask for access, correction and deletion directly, and the buyer does not waive those rights on their behalf. The list is used only for the event and deleted afterwards [CONFIRM the period].
Event photography
Photographing a private event inside the venue and posting it afterwards requires specific written permission, separate from the booking contract, stating where the image may appear and for how long. That counts double where minors are present: a child’s image requires the guardians’ consent (LGPD art. 14) and does not go into commercial material without it. [CONFIRM the event photography policy]
No image on this site shows a minor, and none shows a real Zilá event.
Cookies
Everything non-essential is off by default, rejecting is as easy as accepting, and nothing is pre-ticked. No analytics or advertising tool is installed in this mockup. [CONFIRM the script list when the site goes live]
Retention
Event enquiries that did not become an event [CONFIRM]. Table bookings [CONFIRM]. Event contracts, deposits and invoices follow the applicable tax and civil periods [CONFIRM with the accountant]. Dietary restrictions are deleted with the rest of the enquiry.
Deposit, cancellation and rescheduling
The deposit amount, the balance, the cancellation window and the rescheduling rule have to be clear before a client submits an enquiry, or at least flagged as detailed in the proposal. CDC art. 46 says a consumer is not bound by a clause they had no chance to know, and art. 54 requires limiting clauses to be highlighted. [CONFIRM all the terms]
A couvert artistico and a 10% service charge, if any, disclosed up front and as optional [CONFIRM]. Any “from” price has to be genuinely achievable, with the mandatory extras beside it — CDC art. 31 and Decree 5.903/2006.
Who the controller is
Registered name, CNPJ, address, events e-mail and the data officer (DPO) who receives art. 18 requests [CONFIRM all of them]. None of them was invented to fill this page, because none could be read: the only confirmed digital surface is an Instagram profile behind a login wall.
A privacy policy needs a route that works for requesting deletion. An Instagram inbox is not a route: it has no deadline, no record, and it depends on whoever runs the profile seeing the message. A dedicated e-mail address solves it [CONFIRM].
Never invented here: a CNPJ, an alvara, a sanitary licence or an AVCB fire-safety certificate. Venue safety certification is exactly what an events client asks about, and exactly what must not be fabricated. [CONFIRM all of them]