TRUST CENTRE · PRIVATE BETA

Your business context should remain under your control.

This page explains what Intendoris stores, when information is shared and which capabilities are intentionally limited during the private beta.

DATA BOUNDARIES

Privacy is part of the workflow.

Security controls are applied on the server, not left to hidden buttons or user-interface assumptions.

01

Private by default

An intent remains inside its workspace until its owner deliberately publishes an anonymised opportunity.

02

Server-side access

Every business record is checked against active organisation membership and role permissions.

03

Controlled sharing

Internal notes and files remain within the sender's organisation; shared items are visible only to conversation participants.

04

Explainable decisions

The current analysis and matching baseline is deterministic, versioned and subject to human confirmation.

WHAT WE STORE

Only product data you create.

  • Account and workspace membership
  • Business intents, requirements and decisions
  • Provider profiles, responses and outcomes
  • Conversation text and uploaded business files
  • Audit records required for accountability
YOUR CONTROLS

See and challenge what is held.

  • Download a machine-readable personal-data export
  • Request reviewed account deletion
  • Choose whether files and notes are shared or internal
  • Confirm inferred intent signals before matching
Open my controls
HONEST PRODUCT BOUNDARIES

What the private beta does not claim.

Intendoris bills its own software subscription through a Merchant of Record. It does not execute provider contracts or transfer money between buyers and providers.

Uploads are type- and size-limited, versioned and prepared for private malware scanning. Public launch stays blocked until the scanner is connected and verified in fail-closed mode.

Workspace invitations and activation messages use the configured transactional email provider, with delivery attempts recorded for support and audit.

The production intent engine uses a structured model when configured and a transparent rules baseline otherwise. Every proposal is schema-validated and requires human confirmation.