METRAXIOM Privacy Notice

1. Operator and scope

Andre Jason Watts is the individual operator and seller of the METRAXIOM software service for purposes of this Notice. METRAXIOM is the product and brand name, not a separate legal entity. This Notice applies to the public website and tools, account and workspace services, customer support, subscription administration, and product features that expressly reference it.

The ordinary self-service commercial route is designed for eligible United States professional and business use. A separate written arrangement may include additional privacy or processing terms for another customer class, jurisdiction, data category or deployment.

2. Information categories

METRAXIOM may process account identifiers and authentication events; stated capacity, contracting-party, organization, membership and authorization records; subscription, invoice, customer and payment-status identifiers; physical-instrument identifiers; measurement inputs, methods, results, decisions and evidence records; customer-controlled documents and references; feature acknowledgments and acceptance receipts; support communications; audit events; security and service logs; and limited technical information needed to operate and protect the service.

Payment-card details entered on Stripe-hosted pages are handled by Stripe and are not intended to be stored directly in the METRAXIOM database. Do not put card numbers, passwords, API keys, private keys or other secrets into support email, public contact fields or AI prompts.

3. Sources and purposes

Information is received from users, organization administrators, connected providers the Customer authorizes, Stripe billing events, authentication and hosting services, and the operation of requested features. It is used to authenticate users, enforce tenant and feature boundaries, provide calculation and evidence workflows, preserve provenance, administer plans and billing, prevent duplicate trials, detect abuse, troubleshoot incidents, support customers, maintain availability, enforce agreements, process requests, and satisfy documented legal or contractual obligations.

METRAXIOM does not sell personal information and does not use the general account-agreement acknowledgment as consent to optional promotional email, cross-context behavioral advertising, undisclosed model training or unrelated processing. If optional promotional email is introduced, it requires its own lawful basis and preference control.

4. Customer content and measurement records

Private source files are intended for controlled storage and authorized workspace access. Stored files may be hashed for integrity verification and associated with provenance records. Customers must have sufficient rights and authority for submitted content and must avoid prohibited information. Finalized or released evidence may be intentionally preserved for traceability; a correction normally creates a revision, amendment or superseding record instead of silently rewriting history.

Canceling a subscription does not silently delete measurement records. Account deletion is a separate verified process. Where deletion of an ordinary identifier is appropriate but a controlled record or legal obligation must be retained, access may be restricted and the retained reason documented rather than falsely claiming immediate erasure.

5. Public AI educational guide

When enabled and intentionally submitted, the public Ask METRAXIOM educational guide sends the visitor's question text, a deterministic question-route classification, and limited public instrument-classification context to OpenAI through a server-side API. It does not receive an authenticated workspace, customer source-file bodies, private measurement evidence, live device data or web-search authority. The visitor must complete the displayed per-request acknowledgments before the endpoint will send the question.

The public guide is general education, not human approval or controlled evidence. Do not submit personal records, customer records, confidential or proprietary information, credentials, health information, classified information, controlled government information or export-controlled technical data. The API request uses the configured provider controls, including a no-store application request where supported, but this is not a promise of zero operational, safety, security or legally required provider retention.

6. Private AI, research and external clients

Workspace assistance, retained-record interrogation, Reference Intelligence, customer-connected providers, and OAuth or MCP clients are separate paths. Each enabled path uses only its described task-specific payload and remains subject to authentication, workspace scope, entitlement, provider, rate and feature controls. Enabling one path does not enable another. Declining optional AI does not remove otherwise available non-AI tools.

Private evidence assistance is designed to use bounded tenant-scoped metadata rather than unrestricted database access and to exclude private source-file bodies by default. Reference Intelligence may send an intentional search query to the configured research provider and preserve consulted-source provenance; its ledger is designed to keep a keyed digest rather than the plaintext query. A customer-authorized external client receives only the tool output the customer permits, subject to that client's own provider terms.

7. Service providers and locations

Vercel provides application hosting, deployment, server execution and network delivery. Supabase provides authentication, PostgreSQL database and private object storage; the production database is hosted in a United States region. Stripe provides hosted checkout, subscription billing, invoices, payment-method handling, signed billing events and the customer portal. OpenAI provides server-side inference for each specifically enabled METRAXIOM AI path. Direct customer support currently uses the published Gmail address. A separately configured transactional-email provider is listed only when it is active.

The Subprocessor Register and AI and Data Use notice describe the active paths and their boundaries. Service providers may process information from locations permitted by the applicable service contract and configuration. METRAXIOM does not promise domestic-only processing unless an identified deployment states and verifies that promise.

8. Retention and disposal schedule

Account and workspace data is retained while the account or applicable service remains active and during a reasonable verified exit process. A confirmed account-deletion request identifies the records that can be removed, records that must be restricted or preserved, expected active-system completion, and any backup-aging period. METRAXIOM targets removal of eligible active-system account data within 30 days after completing necessary identity, authority, billing and legal-preservation review; residual backups may age out for up to 90 additional days unless a documented hold applies.

Agreement and covered subscription-consent evidence is retained for at least three years or one year after termination, whichever is longer, and longer only when another documented legal obligation or dispute requires it. Billing and tax evidence is retained for the period required by applicable accounting, payment and tax obligations. Security and abuse logs are ordinarily retained for up to 12 months; incident-related records may be preserved through investigation and required follow-up. Support correspondence is ordinarily retained for up to three years after resolution. Controlled measurement records remain under the Customer's active service and documented exit instructions, subject to legal, safety, audit and dispute-preservation needs.

These periods do not create permission to keep every data item indefinitely. Holds are scoped, access-restricted, reviewed and released when their basis ends. A hash or pseudonymous identifier remains protected where it can still relate to a person. The Data Governance page explains the operational preservation, export, correction and deletion boundaries.

9. Security and access

The architecture uses authenticated access, server-side secrets, tenant boundaries, database grants and row-level policies, scoped storage, signed billing events, immutable or append-only audit records, integrity checks, rate limits, MFA step-up for applicable high-authority actions, and independent release controls. No security program can guarantee prevention of every unauthorized access, loss, outage or misuse. Customers remain responsible for credentials, authorized-user lists, connected-provider accounts and local devices.

10. Cookies, browser storage and analytics

Authentication and security workflows use cookies or browser storage necessary to maintain a signed-in session, preserve requested application state, and protect the service. Public Builder drafts may remain in the visitor's browser until cleared. METRAXIOM does not currently use third-party advertising pixels or session-replay technology. If nonessential analytics, advertising or similar tracking is introduced, this Notice and any required preference mechanism will be updated before activation.

11. Requests, exports and deletion

Privacy, access, export, correction, restriction and deletion requests may be sent to ANDREWATTS23@gmail.com or started from the account-deletion process. Include enough information to locate the account and organization, but do not send passwords, authentication codes, API keys, full payment-card data or unnecessary measurement evidence. We may verify identity, organization authority, request scope and applicable preservation duties before acting.

Available workspace exports and their status labels must not be represented as issued records merely because they can be downloaded. Cancellation, export, privacy requests and account deletion are not conditioned on accepting unrelated new terms or maintaining a paid subscription.

12. Promotional and necessary communications

Optional promotional messages are separate from authentication, account, security, service, billing, trial, renewal, cancellation, legal and support communications that are necessary to operate or administer the relationship. Use the email-preference route to request that optional promotional email stop. A marketing preference does not cancel a subscription, close an account or prevent necessary notices.

13. Children and eligibility

The service is intended for professional and organizational use and is not directed to children. A person creating an account must be at least eighteen years old and legally capable of the applicable agreement. Do not submit children's personal information through public tools or ordinary self-service workspaces.

14. Changes and contact

Material changes to this Notice are versioned and communicated through the service, email or another reasonable method when required. Acceptance of an earlier notice does not fabricate acceptance of an undisclosed replacement. Prior snapshots are retained as needed to show what was presented for earlier activity.

Privacy questions and requests may be sent to ANDREWATTS23@gmail.com. Opening an email application does not prove delivery. The address is displayed for copying, and a request is not confirmed until the sender receives an explicit acknowledgment or other verifiable response.