Legal
Privacy policy
Preliminary version, under legal review. Details not yet defined appear as [pending] and will be completed before the final version.
Data controller: legal name AYVU TECNOLOGIA LTDA; CNPJ 10.241.762/0001-33; based in Uruguaiana – RS, Brazil. Contact for requests: hola@fiuit.com.
Who handles the data
For bookings and customer service to end customers, the business decides the purpose and the instructions; Fiuit acts as processor. The business must provide its own identification and its own channel for data subject requests. For user registration, billing and the security of the Fiuit service, the roles and legal bases will be set out in an approved annex.
Data and uses
The product may record contact identification (name, phone number or channel identifiers, email), language, bookings and resources, messages and transcripts, service metadata, and notes and tags entered by the business. Dashboard users have account data, membership of the business workspace and access and change events.
The catalog and the schedule make it possible to provide the requested service; queues and automations may send reminders when enabled. Diagnoses, symptoms or unnecessary data should not be recorded in notes or tags. Limits and legal bases are defined per purpose, not inferred from the mere existence of a field in the product.
AI, audio and channels
The assistant uses tools to look up information and request actions; Fiuit’s core system validates every operation. The necessary messages may go through channel and inference providers, as set out in the approved contract. Sending a message does not authorize the use of the data for any future purpose. When audio is enabled, voice notes from WhatsApp and Telegram and those dictated in the Wagy chat in the panel are transcribed by OpenRouter and the model providers it uses to transcribe (for example, OpenAI). Fiuit asks that the audio not be retained for training (data_collection: deny) and does not store it: it is discarded after transcription and only the text remains. Sensitive clinical use is not enabled. Provider countries and contractual safeguards are [pending].
Shared location and address
When the customer shares their location in the chat and the channel does not include the address text, the server sends only the coordinates (and the language) to Google’s Geocoding API to obtain the address, which only fills empty address fields of the order or the customer after the customer confirms it. No name, phone number or identifiers are sent.
When the customer types the address in the chat (for example, for a service at a destination), the server sends the typed address text (up to 300 characters), the language and the business’s country as a search hint to the same API, to normalize it and obtain the coordinates; again, no name, phone number or identifiers are sent. If the search is ambiguous (several cities) or fails, the address stays exactly as the customer wrote it, without coordinates, and the assistant may ask for the city once. The typed address is only saved to the profile after the customer confirms it, and the customer can undo the save. If that service is not configured on the server, nothing is sent. Google is included in the provider list below.
Access, retention and rights
Access is limited to the business workspace and to authorized roles. The business must restrict operators, verify who is making a request and keep personal data out of logs and public tickets.
Retention periods
| Category | Period and limits |
|---|---|
| Account, configuration and business data | while the account is active. After closure, no automatic deletion within 90 days is implemented; deletion requires a validated request, except for legal obligations. |
| Customers, conversations and messages | while the account is active; the business may request deletion earlier. After closure, no automatic deletion within 90 days is implemented. |
| Attachments and files | 30 days from creation, with the default configuration. The job revokes access and deletes the file; storage failures are retried. |
| Shared location | 30 days from the event, with the default configuration. This does not delete a confirmed address in a profile or order. |
| WebChat for unidentified visitors | 30 days after session expiry, with the default configuration. Cleanup removes sessions and messages; contacts linked to bookings or other channels may remain. |
| Audio | Downloaded bytes are not stored by Fiuit: they remain in memory for the time needed for transcription and are discarded afterwards; only the text remains. Transcripts and references to channel audio follow message retention. OpenRouter is asked not to retain the audio for training (data_collection: deny). |
| Payment and financial records | 5 years as the approved period for tax and accounting obligations; no automatic deletion at the end of this period is implemented. |
| Audit and security records | while the account is active; no automatic deletion is implemented. Retention exceptions must be justified when responding to a request. |
| Backups | according to the recovery window of the Neon plan and configuration. The operator must confirm the effective window; no number of days is confirmed. |
File and location cleanup requires the operator to run the retention process; its production execution has not been confirmed in this version. Automatic periods depend on configuration and job execution; they do not guarantee immediate deletion. Access, correction or deletion requests may be sent to hola@fiuit.com, with a response within 30 days, or to the responsible business. Deletion of all linkable copies still requires validation; we do not promise irreversible anonymization.
Fiuit does not promise irreversible anonymization while identifiers, audit records or backups still allow data to be linked, nor the removal of copies controlled by WhatsApp or other providers without a separate procedure and evidence.
Providers and sub-processors
Services present in the code and deployment documentation; optional services receive data only when configured for the stated purpose. This list does not establish that all integrations are active for every business. Countries and contractual safeguards remain [pending].
| Provider | Purpose |
|---|---|
| Fly.io | API and worker hosting. |
| Tigris | File storage on Fly.io infrastructure, when configured. |
| Neon | Database and backup/PITR recovery. |
| Cloudflare | Website and dashboard hosting (Workers), DNS and Turnstile. |
| Upstash | Redis for queues and temporary controls, via Fly.io. |
| OpenRouter | AI inference and audio transcription (with the model providers it uses, for example OpenAI), when enabled. |
| Mercado Pago | Payment processing, when configured. |
| Meta Platforms | Official WhatsApp and Instagram. |
| Telegram | Messages through the Telegram channel. |
| WAHooks | Unofficial WhatsApp channel, if used by the business. |
| Resend | Transactional email; local log mode sends no email. |
| Geocoding API for coordinates and addresses, when configured, within the limits described above. |
Protection and incidents
Planned measures: isolation per customer (tenant), access control, auditing without unnecessary content, encryption in transit and key custody. Column-level encryption of clinical data and complete deletion are yet to be implemented and validated, and are not proven yet. Incidents are assessed together with the controller; notifications and obligations depend on the applicable rules and the case, with legal advice.
Instagram, WhatsApp and Telegram
When a business connects its professional Instagram account to Fiuit (Meta's Instagram API with Instagram Login), Fiuit processes, on behalf of the business and as the processor described above: the professional account ID, its username, the app-scoped ID of the person writing (IGSID), the text of direct messages (DMs) and conversation metadata (date, time and message ID). We use them only to serve and book: receive the message, reply, check availability and confirm or change a booking. We do not use this data for advertising, sell it, or share it with third parties outside the service, and there is no authorization to train models on it. The account access token is stored with restricted access and used only to send and receive that business's messages. When the business disconnects the account, Fiuit stops receiving and sending messages on that channel.
The same principles apply to WhatsApp (Meta) and Telegram: the chat or phone identifier, the name shown by the channel and the message content are processed for the same purpose of serving and booking.
The applicable providers and periods are listed in the tables above; connecting a channel does not authorize other purposes.
To request deletion of Instagram, WhatsApp or Telegram data, follow the instructions on the Data deletion page.
Notice at the start of a conversation (proposed)
Proposed informational text for the start of a conversation with the assistant. It is not a consent checkbox, does not replace this policy, and is not active yet:
I am this business’s booking assistant. We use your contact details and messages to handle your request. Do not send health information or documents. To ask about your data or speak with a person, request human assistance.