Privacy notice

When you visit this site

Our hosting provider keeps technical logs that include your IP address, so the site stays available and secure. We measure visits with a statistics service that works without cookies and does not build a profile of you. The site sets one cookie, which remembers for a year whether you chose English or Dutch. We use no advertising or tracking cookies.

When you send us a message

The contact form asks for your name, email address and message, and optionally your company, role, business area and timeline. We use this to answer you. The message reaches us through an email delivery service and lives in our business mailbox. We keep enquiries for 24 months after the last contact, unless we start working together.

When you book a call

Booking runs through an external scheduling service. What you enter there is handled under that service's own privacy notice, and we receive the appointment details.

When you register for an event

Registration runs through an external event registration service. We ask for your name, email address, company and job title, and optionally your LinkedIn profile. We use this to run the event: confirming your place, sending practical information, planning seats and catering, and checking you in on the day. We also record which campaign link brought you to the page.

We add registrants to our customer relationship system, so we know who attended. We keep event registrations for 12 months after the event.

Staying in touch

If you tick "keep me posted" when you register, we may email you about future Praxeum events and insights. You can stop this at any time through the link in each email or by writing to us. If you do not tick it, we only contact you about the event you registered for.

Sharing

We do not sell personal data, and sponsors do not receive the list of attendees. We do not pass your details to event co-hosts. The service providers described on this page process data on our behalf and under our instructions. Some of them are based outside the European Union, in the United States and the United Kingdom.

Why we are allowed to do this

We answer your message and handle your registration because you asked us to. We keep logs and measure visits because we have a legitimate interest in a working, secure site. We send marketing email only with your consent, which you can withdraw at any time.

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; Praxeum is the controller for account, billing, and website data.

2. Google user data we access

Where your organization connects Google Workspace, Praxeum requests one read-only Google scope:

What we access. The text content of Google Docs in the selected shared drives and folders, including their unresolved comments (comment text and author); file metadata (title, file type, folder location, last-modified time, link); and each file's sharing permissions (the email addresses and roles of the people it is shared with). For other file types in those locations we store only the title, type, link, and permissions, not the content. We do not access Gmail, Calendar, Contacts, or any Drive location your organization has not selected.

How we use it. Only to provide the user-facing Praxeum features described on this page: drafting cited skills that a person in your organization reviews and approves, answering your team's questions with citations, and enforcing the same access your Google Drive sharing already grants. To draft skills and build search, document text is processed by large language models and embedding models running on Amazon Bedrock in an EU region (see Subprocessors).

How we share it. We do not sell Google user data and do not share it with anyone except the subprocessors listed below, and only as needed to run the service: Nango (stores the Google access token), Amazon Web Services (model processing), Supabase and Railway (storage and hosting). Error and observability tools receive scrubbed or redacted data only.

We do not request write access to Google data. Praxeum never fetches content outside the drives and folders you select. If we add Google Meet transcript import, we will request the separate drive.meet.readonly scope and update this policy first.

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 or fine-tune any AI or ML model. Reviewer edits are stored 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.
• Google OAuth tokens are held by our connection provider (Nango), never in our own database or logs.

5. Subprocessors

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

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. For Google Drive, a file that is deleted, trashed, or moved out of the selected drives and folders is removed from Praxeum, normally within 24 hours.
• You can revoke Praxeum's access to Google data at any time from your Google Account (myaccount.google.com/permissions) or, for your organization, from the Google Admin console. Revoking stops all further reads. To have data that was already read deleted, contact us; we delete it with a full tenant purge.
• 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 legal@praxeum.io. 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.