Skip to content
AXIS / Data GovernancePublic interface · inquiry data boundary

Privacy should be explicit before trust is requested.

This notice describes the current public AXIS TELESIS website and contact inquiry flow. It is written to match the system that is actually deployed, not future product capabilities.

Document control

AXIS TELESIS / Privacy notice
Scope
Public website + inquiry flow
Private workspace
Separate / in development
Delivery claim
Fail closed if unconfigured
Last updated
19 Aug 2026

TELESIS / Inquiry data path

Data boundary

Where submitted information goes. The clauses below govern; this figure summarises them.

Figure · inquiry data boundary

Nodes A — E

Public interface

A

Contact form submission

The identity, context, introduction and consent fields you complete.

AXIS delivery path

Fail closed if unconfigured

  1. B

    Inquiry record

    The submitted inquiry is recorded in the AXIS inquiry database before delivery is attempted.

  2. C

    AXIS infrastructure

    The contact endpoint sends the submitted inquiry through AXIS infrastructure.

  3. D

    Delivery provider

    The configured email delivery provider.

  4. E

    Destination inbox

    The destination inbox selected for AXIS inquiries.

Private workspace

Separate / in development

Clauses 01 — 06

Governance ledger

Current public handling rules only.

01

Information you submit

When you use the contact form, AXIS receives the name, email address, interest type, and message you provide. The form also uses a hidden anti-spam field that legitimate visitors do not interact with.

02

Why it is used

Submitted information is used to review your inquiry, determine the appropriate response, and communicate with you about that inquiry. The public contact form is not an investment application and does not itself create an advisory, client, partnership, or employment relationship.

03

How it is delivered

In production, the contact endpoint sends the submitted inquiry through AXIS infrastructure to the configured email delivery provider and the destination inbox selected for AXIS inquiries. If the required production delivery configuration is missing, the site returns an error rather than representing the inquiry as delivered.

04

Retention and access

This public website does not publish a fixed retention period for contact inquiries because the operational retention schedule has not yet been finalized. AXIS should retain inquiry information only for legitimate operational, security, legal, or record-keeping purposes and should remove it when it is no longer required for those purposes.

05

Requests about your information

If you need to ask about information previously submitted through this website, use the contact form and clearly identify the request. AXIS will review identity, legal, security, and record-keeping requirements before acting on a request involving personal information.

06

Future services

Authenticated AXIS workspaces, analytics, financial data integrations, evidence storage, or other future services may require separate or expanded privacy disclosures. This notice should be updated before those capabilities are made publicly available.