Privacy Policy — Baila App

Last updated: September 24, 2026

1. Introduction

This Privacy Policy describes how Baila Desenvolvimento e Licenciamento de Programas de Computador Customizáveis LTDA (Baila Tecnologia, registered under Tax ID 66.441.518/0001-79, with headquarters at Rua Carijós, 936, Vila Alzira, Santo André/SP, CEP 09180-000), as the data controller, collects, uses, and protects personal data in accordance with Brazil's General Data Protection Law (LGPD — Law no. 13.709/2018).

2. Data Collected

Organizers

  • name
  • email
  • phone
  • business data

Attendees

  • name
  • email
  • event registration data

3. Collection Methods

Data is collected:

  • directly from users
  • during platform use
  • via authorized integrations

4. Purpose of Processing

Data is used to:

  • operate the platform
  • manage events
  • facilitate communication between organizers and attendees
  • comply with legal obligations

5. Payments

Baila App does not collect or store sensitive financial data.

Payments are processed directly by gateways contracted by the organizer.

6. Data Sharing

Data may be shared with:

  • organizers (in the case of attendees)
  • technology providers
  • legal authorities when required

7. Legal Basis

Data processing is based on:

  • contract execution
  • consent
  • compliance with legal obligation

8. Security

Baila App applies technical and organizational measures to protect personal data against:

  • unauthorized access
  • leaks
  • misuse

9. Data Subject Rights

Users may, at any time:

  • access their data
  • request correction
  • request deletion
  • withdraw consent

How to delete your account

10. Data Retention

Data is stored for as long as needed to:

  • fulfill the purposes described
  • meet legal obligations

11. Cookies and similar technologies

On the website and the organizer dashboard, Baila uses cookies and local storage in three categories:

  • Necessary — sign-in, language, cart, referrals and the record of your cookie choice. They work without permission, because the service cannot run without them.
  • Analytics (PostHog and Google Analytics, US) — usage statistics for the site and the dashboard and, in Google Analytics, traffic statistics linked to Google Search and Google ads. Nothing is stored in your browser until you allow it; without permission, browsing is measured by PostHog in aggregate, without cookies and without linking events to you, and nothing is sent to Google. Regardless of that choice, when you are signed in, some account actions (for example, creating an event or completing a purchase) are recorded by our servers and sent to PostHog linked to your account, based on our legitimate interest in measuring and improving the service. You can object through the contact in section 16.
  • Advertising (OpenAI Ads, US) — measuring whether a Baila ad led to a sign-up. Only with your permission, and never when your browser sends the Global Privacy Control signal.

You choose in the cookie notice and can change it anytime from “Cookie settings” in the footer. We keep a record of each choice — date, version of this policy, what was accepted, the IP address and the browser used — to prove consent. That record is kept for as long as it is needed as proof.

The full list, with names and durations, is in the Cookie policy.

12. Mobile App Permissions

The Baila mobile app requests the following permissions:

  • Camera: used solely for scanning QR codes at event check-in. The video stream is not stored.
  • Notifications: for purchase confirmations, event reminders, and reward updates. You can disable these at any time.
  • Internet: to communicate with our servers.

13. On-Device Storage and App Security

Authentication tokens are stored securely using device encryption (Keychain on iOS, Keystore on Android). Ticket data for offline operation is stored in a local database (SQLite) and synchronized with the server when online.

The mobile app does not use third-party analytics services: all of its communication is exclusively with our own servers.

14. Data Retention in the Mobile App

In the mobile app:

  • Account data: retained while the account is active
  • Payment data: not retained on the device after the transaction
  • UTM data: retained for 2 years, then anonymized
  • Offline data (tickets/check-in): synchronized and removed from the device

15. Changes

This Policy may be updated at any time.

16. Contact

To exercise your rights, contact us at: [email protected]