INGESTIA uses the vendors below to operate the Platform. When they process Customer Data, these vendors may act as sub-processors. For their own billing or account data, some may act as independent controllers, in accordance with their terms and the law.
| Vendor | Service and purpose | Main location | Data involved |
|---|---|---|---|
| Google Cloud | BigQuery, Cloud Storage and Cloud Run for the datalake, the landing area and processing | São Paulo, Brazil | Business data, files, schemas, queries and technical logs |
| Vercel | Application hosting and execution | São Paulo, Brazil (execution); static files on a global delivery network | Request metadata, account, usage and logs |
| Vercel AI Gateway | Routing of the Platform's AI calls to the model | United States | Schema, metadata, column names, question text, business context and samples of rows with values |
| Anthropic | AI model served through the Gateway for the Platform's features | United States | The same content as the row above |
| OpenAI | Model behind the Platform's help assistant | United States | Support question, attachments sent and audio transcription |
| AI provider chosen by the customer | When the environment has its own AI key registered, that key serves the AI features. Provider chosen among Anthropic, OpenAI and Google | United States | The same AI content. The contractual relationship and retention are between the customer and the provider |
| Neon | Metadata PostgreSQL | Brazil (São Paulo) | Account, organization, billing, pipelines, configuration, encrypted credentials, audit trail and the SQL executed |
| Upstash (Vercel KV) | Usage-limit counters and abuse protection | Outside Brazil — instance region defined by the provider | Key derived from the IP address, no content |
| Asaas | Billing and payment (Pix, bank slip and card) | Brazil | Identification, tax ID, e-mail and billing data |
| Resend | Transactional e-mail | United States | Name, e-mail, message content and attachments — including the report PDF, with business figures |
| Google (OAuth) | Social login ("Sign in with Google"). Authentication is our own; the identity is stored in the metadata database | United States | Name, e-mail and Google account identifier |
udiApps (api.udiapps.com) | Master account of the ecosystem: usage metering, support tickets, audit trail and prospect records | Brazil | Account identifier, name, e-mail, tax ID, phone and the audited action |
| WhatsApp (Meta), through the udiApps hub | WhatsApp notifications and support, when requested | Brazil (hub); Meta processes globally | Phone number and message content |
| Meta (Pixel and Conversions API) | Campaign measurement and remarketing on the public pages. Only with advertising consent | United States | Hashed e-mail and phone, IP address, user agent and advertising cookies |
| Google (Analytics, Tag Manager and Ads) | Audience and campaign measurement on the public pages. Only with consent | United States | Browser identifiers, pages visited and funnel events |
| Microsoft Clarity | Session recording and heatmaps on the public pages. Only with analytics consent | United States | Mouse movements, clicks, scrolling and pages visited |
| Trafegix | Campaign attribution on the public pages. Only with consent | Outside Brazil — region defined by the vendor | Funnel events and page visited |
The vendors in the last three categories — advertising, audience and session recording — receive no data at all until active consent is given in the cookie banner. Without advertising consent, no browser identifier and no contact data, hashed or otherwise, is sent to them.
Safeguards
- Business data in BigQuery/GCS, heavy extraction in Cloud Run and the execution of the application stay in the São Paulo, Brazil region.
- International transfers take place under the hypotheses of art. 33 of the LGPD applicable to each case — performance of the contract, as regards infrastructure; consent, as regards audience, session recording and advertising. The incorporation of the standard contractual clauses of Resolution CD/ANPD No. 19/2024 into supplier contracts is under way and, once done, will be in full and without modification.
- INGESTIA requires contractual commitments on confidentiality, security, purpose limitation and cooperation compatible with the service.
- Source credentials stored in the metadata database are encrypted with AES-256-GCM before storage.
- What is sent to the AI provider includes samples of rows with cell values — today up to 50 (fifty) per panel or query. The Privacy Policy describes the exact content and the controls available; this cap is never raised by configuration, only lowered.
Changes
New material subprocessors will be announced by e-mail, in the dashboard or on this page at least 15 days in advance, except for an urgent replacement necessary for security or continuity. The customer may submit a reasoned objection through privacidade@ingestia.io, in accordance with the DPA.