jataíSecurity and LGPD. What protects your data, and what we don't have yet.
In Jataí each brand is isolated in the database itself: every table holding brand data carries its identifier, and row-level security stops a query from seeing another brand. Missing permission is denied, provider credentials are encrypted, audit and consent records cannot be changed, and each contact keeps the source it came from.
Per-brand isolation in the database, permission denied by default, a trail that cannot be erased — and the honest list of what is missing.
One brand can't see another. In the database, not just on screen.
Every table that stores a brand's data has a brand column, and the database enforces row-level security (RLS): each transaction declares the brand it is working in, and a query only returns that brand's rows. The application connects with a database user that cannot turn this rule off. The few tables without a brand — the public company catalog from Brazil's Federal Revenue Service (Receita), invite requests, messages sent through this site — are listed in a test guard, each with its reason.
Identity is per brand too: the same person approached by two brands is two records, and they are never merged. A brand's knowledge base is only searched with the brand as a required parameter, and an automated test checks that a search by brand A never returns a document from brand B.
Missing permission is denied. No one grants what they don't have.
- Every dashboard route that reads or changes data requires a session and a named permission; without it, the response is 403. A test walks through every route and fails any that does not declare its own.
- Role says what a person can do; approval limit says how much, and it lives in that person's membership in the brand. A new operator starts with a zero approval limit.
- Whoever runs the platform is not an owner of the brands because of that. To provide support, they enter a brand read-only, the entry is recorded in the brand's audit log, and editing, approving or exporting does not carry over.
- Passwords are stored as a
scrypthash, never in plain text. The dashboard session is anhttpOnlycookie, which the page JavaScript cannot read.
Encrypted secrets, a trail that cannot be erased.
Provider API keys (language models, email sending) are stored in the database encrypted with AES-256-GCM; the key that opens them does not live in the database. The screen shows whether a credential is usable, never its value.
The audit and consent tables are insert-only: a database trigger refuses to change or delete a row, and the application user does not even have delete permission there. The only door is the complete erasure of a brand that leaves, done through the maintenance connection — because LGPD (Brazil's data protection law) guarantees the right to erasure, and "never delete" cannot become "never able to delete".
Where the data lives.
The application runs on a rented virtual server; the database (PostgreSQL) sits with a separate provider, reachable only from the application server, over an encrypted connection. Email goes out through the sending provider configured for the brand (AraraSend or Resend), and replies are read from the brand's own mailbox.
Language models: who receives what.
To qualify, write and classify replies, Jataí sends the model provider only the excerpt that task needs — the brand profile, what is known about the organization, the reply received. The platform supports eight providers, and the brand chooses which one handles each task: Anthropic (Claude), OpenAI, Google (Gemini), Groq, DeepSeek, Mistral, xAI (Grok) and OpenRouter. These providers process on their own infrastructure, generally outside Brazil.
No model decides the next step of a Rota (sequence) or suppression: that is a deterministic rule. Every AI node has a timeout and a fallback path with no model, and text that cites a fact outside the context does not go out without human review.
LGPD: who is responsible for what.
For the contacts a brand prospects, the brand is the controller of the data and Jataí processes it on the brand's behalf. For the data of people who use the dashboard (name, email, access), Jataí is the controller.
- Source recorded. Every organization and every contact keeps the source it came from — the page, the directory, the imported spreadsheet with its source URL, the public CNPJ database. The question "where did you get my contact?" has an answer.
- Legal basis recorded. Each person's consent, per channel, stores its status and legal basis, in a table that cannot be changed.
- Unsubscribe in every email. The brand's unsubscribe link goes in the footer, and a request to opt out — replied by email or marked by the operator — suppresses the contact for that brand before the next send.
- No purchased lists. Pólen (discovery) does not buy databases or scrape social networks.
Got an email from a brand that uses Jataí and want to know where your contact came from, or ask to be deleted? Write through the contact form, subject "Privacy and data". The message reaches the platform team, who know which brand approached you. Data subject rights and the data protection officer (DPO) are on the LGPD page.
Three things we don't have yet.
Certification.
Jataí has no ISO 27001 and no SOC 2 report. What exists is what this page describes, and the automated tests that check these rules.
Corporate single sign-on.
There is no SSO (SAML or OIDC) and no second factor on the dashboard. Access is by email and password, by invitation.
Region choice.
All brands live in the same database, isolated by row. There is no dedicated database and no choice of where the data lives.
Frequently asked questions
Can another brand on the platform see my leads?
No. Every database query declares the brand, and row-level security only returns that brand's rows. An automated test checks that one brand's search never returns another brand's document.
Does Jataí's team read my data?
Only for support, entering your brand with read-only access. The entry is recorded in the brand's audit log, and editing, approving or exporting is not possible that way.
Is Jataí LGPD-compliant?
The product records the source of each contact, the legal basis and consent, and suppresses anyone who asks to opt out. For the contacts you prospect, your brand is the controller: validate the legal basis of your operation with your legal team.
Where does the text the AI reads go?
To the model provider the brand chose for that task, among the eight the platform supports. Only the excerpt the task needs is sent.