ingestia.ioingestia.io
Trust

Security and privacy without fine print

Where the data lives, who can reach it, how it is audited and what the LGPD requires — and, at the end of the page, the list of capabilities with the usage condition of each one.

Operations

Commitment in writing, measurement in the open

The platform runs on Google Cloud infrastructure in São Paulo, with a 99.5% SLA and credits, availability measured in public and support at any hour.

  • Google Cloud, São Paulo region

    Datalake and processing on BigQuery, Cloud Storage and Cloud Run, in Brazil. Physical and network controls are the provider's, certified ISO 27001 and SOC 2.

  • 99.5% SLA with credits

    From Growth upwards, monthly availability is a contractual commitment. If it falls short, the monthly fee is credited up to 25%.

  • Public status

    A scheduler outside our hosting checks the platform every minute. The history of each day is open at /status.

  • Aiô 24 hours, 7 days

    The assistant investigates your environment and proposes the fix at any hour. Human support answers from 9 a.m. to 6 p.m., within 2 business hours on Scale.

  • Your data stays with you

    With your own cloud, the datalake runs in your company's Google Cloud project. Layers are standard SQL and export is open: nothing is locked into the platform.

  • LGPD and data agreement

    Data processing agreement (DPA), subprocessor list with each one's region, and the data protection officer's channel.

Security and governance

Security and isolation at every layer

  • Data in the São Paulo region

    Processing and storage in Brazil.

  • Per-user access control

    Each person sees only what they need.

  • Granular permissions

    Control over sources, datasets, dashboards and queries.

  • Sensitive data governance

    Features that support LGPD (Brazil's data protection law) best practices and PII tagging.

  • Service Accounts

    Secure consumption by machines and integrations.

  • Controlled APIs and webhooks

    Read-only, scoped and auditable access.

  • Per-customer separation

    Each company's data is kept isolated, with one dataset and one bucket per tenant.

  • Your own cloud (BYOC)

    On Business and Scale, the datalake can run in your company's cloud.

Each company's data is isolated per customer, with its own datasets and landing area and cloud permissions per table, validated on the real infrastructure.

Capabilities

What the platform does, feature by feature

Each feature with its usage condition. The list comes from the same source the product checks to enable a feature — there is no marketing version of it.