Raxni

TRUST IS AN OPERATING SYSTEM

Controls before claims. Evidence before confidence.

Raxni’s launch foundation tracks consent, privacy requests, security events, backups, system health and readiness. Software controls support responsible operations; they do not replace legal or independent security review.

Website boundaries

Public HTTP/HTTPS pages only, robots awareness, private-network blocking, dangerous-port blocking and page-size limits.

Data minimization

Clean searchable text, compressed source archives, hashed request fingerprints and no raw IP storage in launch analytics.

Access control

Authenticated owner controls, workspace ownership checks, CSRF protection, rate limits and database isolation by workspace.

Privacy operations

Versioned consent, export and deletion workflows, identity verification and expiring private export files.

Operational evidence

Queue, scheduler, database, storage, HTTPS and backup readiness checks with incident and restore-test records.

Safe AI behaviour

Verified retrieval, prompt-boundary controls, structured output validation and safe fallback when business facts are missing.

SHARED RESPONSIBILITY

A secure product still needs secure business decisions.

Customers remain responsible for authorized website content, approved domains, lawful visitor notices, agent access, connector permissions and the business policies shown by the assistant.

Before production launch

  • Publish reviewed privacy and service terms
  • Configure a verified owner email channel
  • Add and test a real backup restoration process
  • Configure the chosen AI provider key securely
  • Approve retention periods and escalation rules
  • Complete controlled end-to-end and abuse testing

Report a security concern responsibly.

Do not include passwords, access tokens, full payment details or sensitive customer data in the first message. Share enough information to establish the issue and request a secure follow-up channel.

Contact security →