1Who we are and what this covers
evoaxi builds and operates EVO Data Advisor, a virtual data consultant used by companies to plan, audit and decide data architecture.
For the account data of people who use the product, and for visitors to this site, evoaxi is the controller. For the content your organisation sends into an engagement, your organisation decides what to send and why, and evoaxi processes that material under its instructions.
2What data we process
Three sets, with different origins and purposes.
- People who use the product
- Name, email and picture from the account used to sign in, plus a record of what the person does in the system: projects created, engagements opened, deliverables generated, permissions assigned, and security events such as sign-in, second-factor enrolment and policy changes.
- What you send into an engagement
- Database structure (DDL, schema dumps, exports from modelling tools), architecture documents, spreadsheets, specifications, investigation reports and the text of the conversations with the consultant. This is the material the deliverables are produced from.
- Site and product usage
- Aggregate visit and event measurement, with no cookies and no identification of the person, plus the technical records needed to operate the service: model consumption per organisation, failures and the audit trail.
3On personal data inside what you send
EVODA works with the structure of your data, not its contents. To design a model, audit a schema or estimate cost, the structure is enough: table and column names, types, volumes and relationships.
We recommend you do not upload extracts of real personal data. When a sample is unavoidable, prefer anonymised or synthetic data. If personal data does come in, it falls under this policy and your organisation instructions, and you can request deletion at any time.
The privacy classification the product suggests per column is a design recommendation, not a statement of compliance for your operation.
4Who else processes this content
EVODA uses third-party language models to produce the deliverables. The relevant engagement content is sent to those vendors at the moment the answer is generated. None of them receives your credentials, and none is given access to your database.
The vendor choice per organisation is visible inside the product, and switching takes effect from the next engagement onwards.
- Anthropic
- Models used for architecture reasoning, auditing deliverables and quality judgement.
- OpenAI
- Models used as the default engine for the engagement and in supporting roles, when the organisation has not chosen otherwise.
- xAI
- Model used for the counter-check: the adversarial attack and the second opinion, where the value lies in the reviewer coming from a different vendor than the reviewed.
- Infrastructure
- Google Cloud Platform for hosting and database, and a transactional email provider for access links and alerts.
5What we use it for
To provide the service: run the engagement, read the material you uploaded, produce the data model, cost analysis, assessment and execution package, and keep the project memory across engagements.
To operate securely: authenticate, enforce permissions, record the audit trail, measure consumption per organisation and apply cost ceilings.
To improve the product in aggregate, from usage and quality metrics. The content of your engagements is not used to train models.
6Legal bases
Processing of product user data and of uploaded content rests on performance of the contract with your organisation.
Aggregate site measurement and technical operating records rest on the legitimate interest of keeping the service available, secure and correctly sized.
Where personal data appears inside uploaded material, the legal basis is the one your organisation determines as controller of that data.
7Automated decisions
EVODA produces recommendations and assessments with the support of language models. None of them produces legal effects on any person, and none is executed automatically in any environment.
Every deliverable states which checks were performed and which were not. Where a second model disagreed, the disagreement appears in the document itself rather than being resolved silently.
8How long we keep it
Project content stays available while the organisation keeps the account active, because the memory across engagements is what makes the history valuable. The organisation can delete projects and documents at any time.
The audit trail outlives what it describes, on purpose: a record that dies with the object it recorded stops being a trail. It holds what was done, by whom and when, not the content of the material.
Once the account is closed, content is removed within thirty days, except where the law requires retention.
9Security
Each organisation data is separated in the database itself, and isolation between organisations is verified by a test suite that runs on every change.
Sign-in is by emailed link or corporate account, with no password to leak. A second factor is available to anyone and can be required across a whole organisation, alongside inactivity timeout and an IP allowlist.
Permissions are per resource, nobody grants what they do not hold, and every security event enters the audit trail.
10International transfers
The language model vendors and the hosting infrastructure operate outside Brazil, which means the data described above is transferred internationally.
We choose vendors that offer contractual data protection clauses and hold them to processing the material only to provide the service.
11Your rights
You can request confirmation of processing, access, correction, portability, anonymisation and deletion, as well as information about who we share with.
If the request concerns material uploaded by a client organisation, we will forward it to them where the decision is theirs, and immediately do whatever is within our reach.
The channel is contato@evoaxi.com, and we answer within fifteen days.
12Cookies and measurement
This site measures visits in aggregate, with no cookies and without identifying who visits. That is why there is no consent banner here: there is nothing to consent to.
Inside the product we use only the cookie required to keep your session open.
13Changes to this policy
When we change something material, we notify by email and update the date at the top of this page. Continuing to use the service afterwards means accepting the new text.