Privacy Policy

1. Who processes the data

Praxis is the controller of account, billing, support, business relationship and website visit data. Full identification is at the end of this page; the data protection contact is privacidade@praxis.lbostuff.tech.

For the data DataVault reads from the sources the customer connects, Praxis is a processor: it processes that data on behalf of the customer, who is the controller, and only to provide the service (GDPR Art. 28). That processing is governed by the Terms of Service and, where one exists, by the data processing agreement (DPA) signed with the customer.

2. What data we process

• Account: name, email, password (stored only as a hash), workspace and role, session and security records (such as multi-factor authentication) and the version of the Terms accepted at sign-up, with the date.
• Service usage: connected sources (with encrypted credentials), quality metrics, issues, suggestions, rules and reports.
• App usage, only if the workspace admin turns it on (it is off by default): which pages and features the workspace uses, with the event name, the page pattern, the plan and the time. It does not include the user, the email, the IP, the browser or any typed text.
• Analysed data: metadata and limited samples from the customer's sources, read in strictly read-only mode. They may contain personal data from the customer's systems.
• Billing: the billing contact and payment method are collected directly by Stripe. Praxis keeps only the Stripe customer and subscription identifiers and the plan status — it never sees the card number.
• Website: what you enter in the diagnostic form (name, email, company, company country, role, sector, size, message, availability and, if you attach it, the maturity test result), which reaches us by email and is recorded in the Praxis CRM (Twenty, from 16 November 2026), and aggregate visit statistics (section 10). When you request a diagnostic, we email you a confirmation of the request.
• Maturity test: it works without an email, and your answers stay in your browser; only the level and the sector, without identifying anyone, go into the aggregate visit statistics (section 10). The share link keeps the answers in the URL fragment (the part after the #), which the browser does not send to the server.
• Email at the end of the test (optional): if you enter it and tick the box to receive the result, we send you the result through Resend (section 4), at most once per address every 24 hours, and we use the address only for that email. The box where you agree to be contacted by Praxis about the result is a separate one and starts unticked. Only with it ticked does the request reach the Praxis team: the email, the result and the context you choose to give (sector, company size, role and the process that hurts most) reach us by email and are recorded in the Praxis CRM (Twenty, from 16 November 2026).
• Business relationship: professional contacts of customers and prospects, opportunities, proposals and contracts, in the same CRM. From DataVault customers, the CRM only receives aggregate usage counts per organisation — never source data or workspace content.

3. Why we use it and on what legal basis

• To provide the service, manage the account and send transactional email (account verification, password recovery, invitations and the alerts, digests and scheduled reports the customer configures) — performance of the contract (GDPR Art. 6(1)(b)).
• To bill paid plans — performance of the contract and compliance with tax obligations (Art. 6(1)(b) and (c)).
• To protect the service: audit trails, logs and error monitoring — legitimate interest in keeping the service and customer data secure (Art. 6(1)(f)).
• To answer a diagnostic request, with a confirmation by email, or the contact request you make at the end of the maturity test — pre-contractual steps at your request (Art. 6(1)(b)).
• To email you the maturity test result when you ask for it — at your request (Art. 6(1)(b)).
• To measure website visits in aggregate, without identifying anyone — legitimate interest (Art. 6(1)(f)).
• To follow up the business relationship with business customers and prospects — recording contacts, opportunities, proposals and contracts and getting back in touch about the request or the service — Praxis's legitimate interest in a business-to-business relationship (Art. 6(1)(f)). You can object to this follow-up at any time by writing to privacidade@praxis.lbostuff.tech; from then on, we stop contacting you for that purpose.

We do not sell data or use it for advertising.

4. Sub-processors

These are the providers that process personal data on behalf of Praxis. The list is generated from the DataVault register — the same one behind the application's Sub-processors page, which also shows each provider's DPA and the announced changes.

A new provider, or a provider leaving, is announced 30 days in advance: admins can subscribe to the email notice in the application and object within that period by writing to privacidade@praxis.lbostuff.tech. During the notice period a new provider receives no data.

5. Artificial intelligence: which data reaches each model provider

AI features send the model provider only what is needed to produce the requested analysis, with row and size limits on every sample. The model providers on the sub-processor list are: Anthropic and Voyage AI.

• Anthropic (Claude models): receives metadata and limited samples for reports, diagnosis, suggestions, signals and the assistant. By default it is the only provider that receives samples of customer data.
• Any other model provider never receives samples as they come from the sources, and may only receive data if it is on the list in section 4, after the 30-day notice.
• Without the customer's authorisation, those providers may only receive metadata — dataset and column names, types, counts and null percentages, never values — and only if they do not train models on the data received and have valid transfer safeguards.
• Samples only reach them anonymised, and only if the workspace admin authorises it: detected emails, phone numbers, tax IDs (NIF/NIPC), IBANs, payment cards, IP addresses and personal names are replaced with placeholders before sending. Automatic anonymisation reduces the risk but is not infallible; that is why a provider that trains models on the data received, or lacks valid transfer safeguards, never receives samples.

Own key and models in the customer's account: if the customer uses their own Anthropic key, or the Claude models in their own AWS (Amazon Bedrock) or Google Cloud (Vertex AI) account, that provider processes the data on the customer's behalf and under the customer's own contract with it — it is not a Praxis sub-processor and is therefore not on the list. In that mode Praxis never replaces the customer's credential with its own, nor diverts AI analyses to other providers.

With AI turned off in the workspace policy, nothing goes to model providers: DataVault uses deterministic heuristics only. All AI-generated content is labelled as such, with the model and provider that produced it (Art. 50 of Regulation (EU) 2024/1689).

6. How long we keep data

• Measurements, profiles and source history: the history window of the subscribed plan (see Pricing); whatever falls outside the window is deleted by a daily purge.
• Account: while it exists; deleted immediately when you ask. In the records that remain, authorship becomes “deleted account”.
• Reports, signals, suggestions and AI feedback: while the workspace exists. Source credentials: while the connection exists.
• Assistant conversations: not stored on the server; they stay in your browser until you close the tab.
• App usage: 90 days. Turning sharing off deletes it at once.
• Audit trail: «A PREENCHER».
• Application logs: «A PREENCHER».
• Database backups: «A PREENCHER». Backups are not edited: deleted data only disappears from them when they expire.
• Website contact requests and business contacts without a contract: «A PREENCHER» after the last contact.
• Billing: for the legal retention period for tax documents.
• Data sent to a sub-processor: according to that provider's retention, under its DPA.

Deleting the workspace permanently erases all customer data — users, connections, measurements and reports — except in backups until they expire.

7. Public links and badges

Nothing in DataVault is public by default. A workspace admin may choose to:

• enable the quality badge and public page of a dataset: they show the score, quality dimensions, columns with their type and the data contract rules — never samples, observed values, credentials or the connection or workspace name. It can be revoked at any time, with immediate effect;
• share a report through a public read-only link, which always expires (7 days by default, 90 days at most). If the report's scope has columns with personal data, the admin must confirm it explicitly and the confirmation is kept in the audit trail. Views are counted without storing the IP address or browser of whoever opens the link.

Whoever enables a share decides who receives the link and is responsible for that disclosure.

8. Access by the Praxis team

The internal Praxis console shows only metadata about each workspace (plan, counts and dates), never customer data.

To provide support, the team requests access to a workspace with a reason and a duration of up to 72 hours, and only gets in if a customer admin approves. Access is read-only, expires on its own at the end of the period and the admin can revoke it earlier. The request, the decision and the first access are recorded in the workspace audit trail.

9. International transfers

DataVault's application, database and backups are in the European Union: Google Cloud, europe-west1 (Belgium), with backups in Google's EU multi-region.

Some personal data may leave the European Economic Area. Platform logs, with the IP address of each request, are kept in Google Cloud Logging in the global location and may be stored outside the EU. The sub-processors in section 4 that process data outside the European Economic Area are: Anthropic, Resend, Stripe, Voyage AI, GitHub, Sentry and Twenty (from 16 November 2026).

Each provider receives the data under the mechanism shown in the “Region and transfer” column in section 4: standard contractual clauses approved by the European Commission (GDPR Art. 46) and, where the provider is certified, the EU-US Data Privacy Framework (Art. 45). The same column shows the mechanism for data coming from the United Kingdom, Switzerland and Brazil, and whether it has been checked against the DPA signed with the provider; while it says “pending”, it is what the provider states in its public DPA. You can request a copy of these safeguards at privacidade@praxis.lbostuff.tech.

10. Cookies and browser storage

The DataVault application does not use advertising or audience-measurement cookies. It keeps in your browser (localStorage) only what it needs to work — the session, language, theme and interface preferences — and the assistant conversation stays in sessionStorage until you close the tab. During an SSO login it uses a technical cookie (dv_sso), HttpOnly, valid for 10 minutes, that ties the flow to the browser that started it. Because they are strictly necessary, these mechanisms do not ask for consent (Art. 5(3) of Directive 2002/58/EC).

This website uses a single cookie, NEXT_LOCALE, which remembers the website language. It is a session cookie, deleted when you close the browser, and it is only set when you change language with the language switcher or open a page in a language other than the one your browser states as preferred (if your browser prefers none of Portuguese, English or Spanish, English counts as its preference, the language the website shows it in; if it states no language at all, the cookie stores the page's language). The customer area keeps the session in localStorage. When enabled, visit statistics use Plausible Analytics (Plausible Insights OÜ, Estonia, EU), which uses no cookies or persistent identifiers and only produces aggregate numbers. Embedded videos (YouTube, privacy-enhanced mode) only load when you press play; from then on Google's privacy policy applies.

11. Your rights

You have the right of access, rectification, erasure, restriction, portability and objection, and to withdraw at any time any consent you have given.

In the application, with no support ticket: an admin exports all workspace data and deletes the workspace (Team → Danger zone); each member deletes their own account. Correcting a name or email is done on request.

Other requests go to privacidade@praxis.lbostuff.tech. We reply without undue delay and within one month of receipt at the latest; for complex requests the period may be extended by two further months, and we will tell you within the first month. Exercising your rights is free, except for manifestly unfounded or excessive requests.

If your data is in the sources of a DataVault customer, that customer is the controller: address your request to them. If the request reaches Praxis, we forward it to the customer without delay.

You may lodge a complaint with the Portuguese data protection authority (CNPD) or with the supervisory authority of your country.

12. Security

Source credentials encrypted before persistence, strictly read-only access to sources, strong password hashing, multi-factor authentication, per-workspace isolation and audit trails. No system is infallible: a personal data breach is notified to the supervisory authority and to data subjects under GDPR Arts. 33 and 34 and, where Praxis acts as processor, to the customer without undue delay: within 48 hours at most, or 24 hours for customers subject to DORA or NIS2 (deadlines of the DPA template, not yet legally reviewed).

13. Changes to this policy

The version in force is shown at the top of the page and the change history lists every version. Relevant changes are announced by email or in the application before they take effect; changes to the sub-processor list follow the 30-day notice in section 4.