Privacy Policy

Last updated: 10 July 2026

Praxeum ("Praxeum", "we", "us") is a service operated by Talenture, registered as Talenture.ai with the Netherlands Chamber of Commerce (KvK) under number 42041148, the data controller for this website and the Praxeum application. This policy explains what data Praxeum accesses, how we use and protect it, and the rights you have. Questions or requests:bram@agentlabs.nl.

1. What Praxeum is

Praxeum helps a company turn its own knowledge into verified, human-approved "skills" that its AI agents can execute safely. To do this, a customer connects sources they control — such as Slack, Google Workspace, and Notion — and explicitly scopes which channels, drives, folders, and meeting series Praxeum may read. Praxeum processes this content on the customer's behalf. In relation to a customer's own workspace data, Praxeum acts as a data processor and the customer is the controller; Talenture is the controller for account, billing, and website data.

2. Google user data we access

Where you connect Google Workspace, Praxeum requests the following read-only scopes, limited to what you scope:

Scope	Why we request it
`drive.readonly`	To read the documents in the shared drives and folders you explicitly select, so we can convert procedure-shaped documents (SOPs, runbooks, checklists) into cited draft skills for your team.
`drive.meet.readonly`	To read Google Meet transcripts (which are stored in the meeting organizer's Drive) for the recurring meeting series an organizer chooses to include, so procedures discussed in meetings can be captured as cited draft skills.

We do not request write access to Google data. We never fetch content outside the scopes you select, and unselected drives, folders, and meeting series are never accessed.

Limited Use. Praxeum's use and transfer to any other app of information received from Google APIs will adhere to theGoogle API Services User Data Policy, including the Limited Use requirements. Specifically: we use Google user data only to provide and improve the Praxeum features described above; we do not use it for advertising; we do not sell it; we do not transfer or use it for any other purpose; and humans do not read it except with your permission for support, to comply with law, or as strictly necessary for security. Google user data is never used to train generalized AI/ML models.

3. How we use data

To mine, draft, and serve verified skills within your organization only.
Every skill is drafted with citations to its source and requires human review and approval before use.
We never produce individual employee performance analytics; source scoping is visible to employees by design.
Content you connect is not used to train generalized models. Reviewer edits may tune drafting quality within your own tenant only.

4. How we store and isolate data

Data is logically isolated per customer tenant, enforced in the database (row-level security) as well as in application code.
Personal data and secrets (e.g. API keys, national identifiers) are redacted at ingestion before content is stored or served.
Data is encrypted in transit and at rest by our infrastructure providers.

5. Subprocessors

We use a short, disclosed set of subprocessors to operate the service:

Subprocessor	Purpose
Nango	Source connection auth & sync
WorkOS	Authentication & agent authorization
Anthropic	LLM processing (mining & serving)
OpenAI	Text embeddings
LlamaParse (LlamaIndex)	Document-to-text parsing
Langfuse	LLM observability (redacted payloads)
Sentry	Error monitoring (payloads scrubbed)
Resend	Transactional email
Railway / Supabase	Application hosting & database

6. Retention & deletion

When a source item is deleted or a source is de-scoped, we propagate the removal to derived documents, chunks, and embeddings within a defined window.
On account offboarding we run a full tenant purge across all data and revoke source connections.
You may request erasure of personal data; approved-skill evidence retained for audit is subject to an erasure override on request.

7. Your rights

Depending on your location (including under the EU/UK GDPR), you may have rights to access, correct, delete, restrict, or port your personal data, and to object to processing. To exercise these, contact bram@agentlabs.nl. For workspace data processed on a customer's behalf, requests are directed to that customer as controller and we assist as processor.

8. International transfers

We aim to process data in the EU where possible and use providers offering EU data regions. Where data is transferred outside the EEA, appropriate safeguards (such as Standard Contractual Clauses) apply.

9. Changes

We will update this policy as the service evolves and revise the "last updated" date above.