This document sets out what UDISOFTBOX CONSULTORIA E TECNOLOGIA LTDA ("INGESTIA") commits to in operating INGESTIA.IO: availability, support and service credits. It forms part of the Terms of Use and the SaaS License Agreement.
1. Where the Platform runs
Each customer's data lake (landing zone, Bronze, Silver and Gold layers and load processing) runs on Google Cloud infrastructure, São Paulo region: BigQuery, Cloud Storage and Cloud Run. The application runs in São Paulo, with its metadata database also in Brazil. Suppliers and their regions are listed in the Subprocessor List.
In the own-cloud model, the data lake runs in the customer's own Google Cloud project: the data stays under the customer's account and remains there regardless of INGESTIA.
2. Committed availability
| Plan | Monthly availability |
|---|---|
| Starter | commercially reasonable efforts, no percentage |
| Growth, Business and Scale | 99.5% |
| Enterprise | 99.5% or the percentage set in the contract, whichever is higher |
Availability is the share of minutes in the month (Brasília time) in which the Platform answered the health check. The check runs every minute from a scheduler outside the application's hosting: a minute without an answer counts as an unavailable minute. An outage of the hosting, of the metadata database or of the application itself is therefore counted.
The measurement is public, with daily history, at /status. It is the same series used to calculate credits.
3. Service credits
If availability in a month falls below the commitment, customers on plans with a percentage are entitled to a credit on that month's fee:
| Availability measured in the month | Credit |
|---|---|
| below 99.5% | 10% of the monthly fee |
| below 99.0% | 25% of the monthly fee |
- Credits are capped at 25% of the monthly fee for the affected month and are deducted from the next invoice.
- Requests go through the support channel within 30 days after the end of the month. INGESTIA checks them against the /status series.
- Service credits are the compensation for missed availability, without excluding rights that the law does not allow to be limited.
4. Support
| Channel | When |
|---|---|
| Aiô, the assistant inside the Platform (button on every screen or the ⌘/ shortcut) | 24 hours a day, 7 days a week. It investigates the customer's environment (runs, logs, tables, dashboards), explains and proposes the fix, which the customer confirms |
| Human, at suporte@ingestia.io or on the Support screen (an Aiô conversation that did not solve the problem becomes a ticket automatically, with its context) | 9 a.m. to 6 p.m., Monday to Friday (Brasília time) |
First human response time, counted in support hours from when the ticket is logged:
| Plan | First response |
|---|---|
| Starter | 1 business day |
| Growth | 8 business hours |
| Business | 4 business hours |
| Scale | 2 business hours |
| Enterprise | set in the contract |
Resolution time depends on the nature of the problem: a dashboard adjustment and a failure in a third-party source do not follow the same path. The ticket is tracked on the Support screen until it is closed.
Security requests go to seguranca@ingestia.io and take priority over the ordinary queue.
5. Internal engineering objectives
Beyond the commitment in section 2, operations pursue tighter targets:
| Indicator | Internal target |
|---|---|
| Application availability | 99.9% monthly |
| Pipeline run success | 99.0% monthly |
| Dashboard query latency (p95) | under 8 seconds |
These are engineering targets that guide operations. The contractual commitment is the one in section 2.
6. How the customer follows along
- /status shows the current state and the availability of each day over the last 90 days.
- The
/api/healthendpoint is public and returns 200 when the application and the metadata database respond, or 503 when a required dependency is down. Customers may point their own monitor at it.
7. Maintenance
Planned maintenance that implies unavailability is announced with reasonable notice, in the Platform or through contact channels, and does not count as unavailability when announced at least 48 hours ahead and totalling under 4 hours in the month. Urgent security fixes may be applied without prior notice and are communicated afterwards.
8. What does not count as unavailability
- unavailability of the customer's data sources (database, API, spreadsheet, ERP) or an expired credential on the customer's side;
- unavailability of the AI provider whose key belongs to the customer: that contractual relationship is between the customer and the provider;
- use in breach of the Terms of Use (in particular clause 3.2, prohibited uses) or of the Plan limits;
- suspension for non-payment, order of an authority or security risk;
- maintenance announced under section 7;
- acts of God and force majeure.
9. Enterprise
A higher percentage, shorter response times, a dedicated channel, after-hours support and different credits can be negotiated in an Enterprise contract. When agreed, they prevail over this document.
10. Contact
Support: suporte@ingestia.io · Security: seguranca@ingestia.io · Sales: contato@ingestia.io