Privacy Policy
Last updated: October 15, 2026
1. Who we are
SIMIA Agenda is an online scheduling platform offered under the SIMIA brand by INTEGRAI ARQUITETURA DE SOLUCOES DIGITAIS LTDA, Brazilian company registration (CNPJ) 60.208.564/0001-46. Our website is agenda.simia.digital. Contact: suporte@simia.digital.
For visitor records, the professional or business responsible for the agenda acts as controller: it defines services, time slots and how booking data are used to manage appointments. SIMIA acts as processor for these records to deliver scheduling services and carry out the account owner's settings. SIMIA acts as controller for data needed to administer your SIMIA account, support and plan purchases. Requests about a booking can be sent to the agenda owner or our support channel.
2. Data we collect
Information you provide includes your name and email address; a password only for accounts using email and password sign-in; optional profile photo and professional description; a visitor’s name and email address, and an optional mobile number when booking; optional booking notes; and your preference for receiving new booking email notifications. We also record the purchased plan, amounts, periods, invoice identifiers and payment status.
Booking records include the service, time, cancellations and rescheduling, the visitor's confirmation, and attendance recorded by the agenda owner, including when and by whom it was recorded. We also record permission to send WhatsApp messages, its date, the version of the notice shown and requests to stop receiving them.
Technical access data: the infrastructure records IP addresses, technical browser information and access and error logs to keep the service operating, protect sessions and diagnose faults. These logs may include the path of the page accessed.
3. How we use your data
We use your data to create and manage your account, check availability and display bookable time slots, and send booking confirmations and reminders to the email address provided for the booking. With the visitor’s permission, these messages can also be sent through the connected WhatsApp number using approved templates. New booking notifications go to your account email according to your profile preference. Plan billing messages use the same address. We process plan purchases and track their payments. We do not sell or rent your personal data. Hosting, email and payment service providers receive only the information needed to deliver their respective services.
Creating your account, providing the agenda and administering your plan require data needed to perform the contracted service. Financial records may also be processed to meet legal obligations and exercise rights concerning transactions. Sending WhatsApp confirmations and reminders depends on the optional permission given when booking. Accepting account terms does not authorize marketing or replace that separate choice.
Sign in with Google
When you sign in or register with Google, we receive your name, email address, Google account identifier and, when available, your profile picture to create or recognize your SIMIA account and authenticate access. The picture is used in your private dashboard; a picture you upload takes priority. It is not automatically published on your booking page. Signing in with Google does not authorize Google Calendar access. Calendar connection requires a separate authorization initiated in the dashboard.
Optional Google Calendar connection
With your permission, SIMIA checks free and busy times and imports the titles, dates and times of events in your primary calendar to display them in your private agenda and avoid booking conflicts. We do not import attendees, descriptions or attachments. Other calendars in the same account are not included. The connected email address is displayed in your dashboard so you can identify the calendar in use.
When a booking is confirmed, SIMIA adds the service and appointment time to Google Calendar. Canceling or rescheduling through SIMIA updates the corresponding Google event. Moving or deleting that event in Google also updates the SIMIA booking when it can be applied without a scheduling conflict. Synchronization runs in the background. SIMIA changes only appointments it created. The customer’s name, phone number and notes remain in SIMIA and are not included in those events.
We securely store your access authorization, connected account details and the records needed to keep bookings synchronized. To display imported events, we retain titles, times, identifiers, recurrence references and update states in private records linked to your account. These events are not treated as customers or bookings and do not trigger patient reminders.
Our use and transfer of information received from Google APIs comply with the Google API Services User Data Policy, including the Limited Use requirements. These data and derived information are not sold, used for advertising, sent to advertising platforms or used to train artificial intelligence models.
You can disconnect your calendar from the Google Calendar section of your dashboard. SIMIA stops accessing your calendar and asks Google to revoke the authorization. You can also remove access through your Google Account connections. Disconnecting does not delete events in Google. Imported copies stop updating and follow the retention criteria below; you can also ask support to delete them.
Deleting your SIMIA account removes active connection data and associated booking records. Protected backups may be retained temporarily for service recovery. To request deletion of specific data, contact suporte@simia.digital. The calendar is not a medical record: do not enter diagnoses, examination results or clinical information in booking notes.
4. WhatsApp messages
When the integration and required templates are configured, confirmations and reminders are sent through the official WhatsApp Business API (Meta Platforms). Booking phone numbers are used solely for communications about that booking, never for marketing without consent. WhatsApp processing follows the WhatsApp Business Platform terms.
Messages share the recipient's number and the content needed for the notice with Meta, such as the name, service, time and booking actions. If a reply is a voice message, it is downloaded from Meta and automatically transcribed by OpenAI, a speech recognition provider, only to understand the scheduling request. SIMIA does not keep the audio; the transcribed text follows the same rules as written messages. Photos, videos and files sent to the number are not opened. When you reply to the connected number, we receive and store the sender's number, message, date and processing states to handle actions and requests to stop messages. Do not send clinical information in these replies. You can request that messages stop by replying that you no longer want to receive them, or request withdrawal through support. Stopping messages does not cancel your booking.
To reduce stored data, we discard the text of new replies when processing finishes with a definite result. Pending messages, messages without a confirmed result and earlier records may remain stored. Metadata needed for processing, such as sender, date and state, remain linked to the account.
Plan payments
Payments take place in Mercado Pago’s checkout. To prepare a charge, we send your account email, the plan, amount and invoice reference. SIMIA records transaction identifiers and results to recognize payment and the purchased period. We do not receive or store your full card number, card security code or Mercado Pago account password.
Your customers’ data, booking notes and information received from Google Calendar are not sent to Mercado Pago for this charge.
Email notifications
Visitors receive confirmation and reminders for their own booking at the email address they provided. Messages include the service, date and time, with the actions offered by the scheduling account owner. Free-text booking notes are excluded from these emails.
New booking notifications go to your account email. You can turn them off in your profile. These messages contain the details needed to identify the booking, without the visitor’s booking notes. Plan invoices, payment updates and essential access or service notices also use your account email.
Email delivery uses Hostinger's service. For delivery, we share the necessary recipient data and the content described above. Free-text booking notes are not sent in this content.
5. Cookies and sessions
We use cookies to maintain your authenticated session and protect forms against unauthorized submissions. The light or dark theme preference is saved in your browser's local storage until you change it or clear site data.
With the same permission, SIMIA sends Meta, through the Conversions API, the account creation, WhatsApp connection and plan payment events, including the amount paid, together with your email and an account identifier converted into an irreversible code (hash), plus the IP, browser and click identifiers recorded at sign-up. These cookies and transmissions are never used on your clients’ booking pages. No data about your clients, bookings or Google Calendar is sent to advertising platforms.
Without permission, or when the browser asks not to be tracked (Do Not Track or Global Privacy Control), none of this is loaded or sent. We only record the source stated in the link itself (UTM parameters and click identifier) to learn which campaigns bring sign-ups. You can change your choice at any time through the “Cookies” link in the home page footer. Withdrawing permission cancels events not yet sent.
On Google sign-in screens, your browser loads that provider's resources needed for login and sends technical information required for the connection, such as its IP address and browser information.
6. Data retention
The following criteria apply unless records are needed for a documented preservation duty, investigation, dispute or processing that remains unresolved:
- Bookings: identifiable records are kept for 24 months after the appointment ends or is cancelled, using the later date. Rescheduled bookings are assessed together; records are not removed while their chain remains in use.
- Administrative notes: free text is removed 30 days after the booking ends.
- Replaced profile photos or photos of deleted accounts: local files no longer linked to an account are removed during periodic cleanup when at least 30 days have passed since their last modification.
- WhatsApp replies: text is discarded when processing has a definite outcome. After 90 days, metadata for completed messages are also reduced. The identifier and dates needed to prevent duplicate messages from executing the same action are retained while the connection exists. Opt-out records remain to prevent further messages.
- Google Calendar copies: past imported events with no booking link are removed after 90 days, or after 30 days of a stable disconnection. Synchronization links and events still in use follow their booking criteria. This does not delete events in your Google calendar.
- Application access records: these are kept for at least six months under Brazil's Internet Civil Framework. Monthly rotation may also retain the current partial month.
- Sign-up source: the source campaign (UTM) stays with the account. Click identifiers, advertising cookies, IP and browser data used for measurement are deleted after 90 days. Each event sent to Meta has its content deleted once receipt is confirmed, or within 7 days.
- SIMIA recovery copies: operational backups follow a 30-day cycle, with restricted access. New automatic copies are encrypted. Before a restored copy returns to service, recorded deletions and data reductions made after that copy are applied again.
Cleanup runs periodically. Data needed to resolve faults, uncertain deliveries, data-subject requests, legal obligations or claims are preserved while that need is documented. These periods do not authorize unnecessary retention.
Canceling a booking or subscription does not delete the account. Without protected financial records, account deletion removes active operational data. With financial history, we register a closure request to separate operational data from transaction records and information needed for legal obligations. Access to invoices and refund requests remains available while the request is handled; its reference is shown in your profile. This procedure does not erase records independently kept by suppliers under their own obligations.
7. Your rights under the LGPD
Under Brazil's General Data Protection Law (Law No. 13,709/2018), you may confirm processing, access your data, correct incomplete or outdated data, request deletion, withdraw consent, request portability and obtain information about sharing. You may also request anonymization, blocking or deletion of unnecessary, excessive or unlawfully processed data.
The account owner can download a JSON file containing account and agenda data from Settings → Export my data. This export includes visitors' information and must only be stored and shared for an appropriate purpose. If you are a visitor, request access to your own data from the agenda owner or suporte@simia.digital. Support also receives correction, deletion, withdrawal and data-sharing information requests. You can petition Brazil's ANPD through its official channels.
8. Security
We protect information during access and storage using secure connections, protected passwords and encrypted Google access authorization.
9. Contact
Questions about this policy: suporte@simia.digital.