TRUST CENTER / PUBLIC BASELINE

Inspect the controls before you share context.

Implemented controls, delivery rules and evidence not yet available are labelled separately.

← HOME

PUBLIC STATE LEDGERPUBLISHED OPERATING BASELINE

Encrypted intakeBROWSER JWEEncrypted before network submission

Third-party trackers0No advertising or social pixels

App raw-IP persistence0Application layer; upstream controls are separate

Inquiry retention≤ 48 HOURSEncrypted inquiry envelope; application-layer hard deadline

High-impact actionsHUMAN APPROVALAI never holds final authority

Customer content for AI trainingPOLICY: PROHIBITEDExternal AI processing is a separate, approval-gated decision

Availability engineering experienceTARGETS UP TO 99.99%Company-reported historical client work; not a blanket guarantee or default SLA

CONTROL SCOPE / EVIDENCE BASIS

Separate runtime controls, delivery controls and capability evidence.

Public Intake Controls

Browser-side inquiry encryption: ENABLED WHEN INTAKE IS OPENThe browser creates a fixed-size JWE; the public receiver stores ciphertext.RUNTIME + SOURCE VERIFIED
Application raw-IP persistence: 0The application does not persist raw IP or complete user-agent strings; upstream controls are separate.SOURCE / TEST VERIFIED
Inquiry envelope expiry: ≤ 48 HOURSApplication-layer scheduled expiry; independent deletion-test evidence remains pending.RUNTIME CONTROL / TEST PENDING

Project Delivery Controls

Authority and scope: REQUIRED BEFORE WORKTesting and production access require written authority, scope, stop conditions and named decision rights.CONTRACT CONTROL
Customer-boundary delivery: DEFAULT WHERE PRACTICALTechnical work remains in the customer environment wherever the engagement permits.DELIVERY POLICY
AI authority: HUMAN APPROVALCustomer data is not used for model training; high-impact actions remain under human authority.OPERATING POLICY

Service Capability Evidence

Core-team experience: 20+ YEARSArchitecture, SRE/operations and security experience reported for the core team.COMPANY-REPORTED
Availability objectives: TARGETS UP TO 99.99%Historical client work; not a default SLA or guarantee for every system.COMPANY-REPORTED HISTORICAL WORK
Client delivery records: PUBLISHEDCUSTOMER-AUTHORIZED SUMMARYVIEW RECORDS →

OPEN MACHINE-READABLE BASELINE

SIX ZERO CONTROL TARGETS

The scope and evidence behind every zero are visible.

Each figure shows its evidence type and verification status.

0Third-party trackersCODE-AUDITED

0Application raw-IP persistenceCODE-AUDITED

0Customer content used for model trainingOPERATING POLICY

0 TARGETTechnical content in long-term legal archiveCONTRACT CONTROL

0 TARGETPersistent customer secrets after task endVERIFICATION PENDING

0 TARGETExpired complete report copiesDELETION AUDIT PENDING

DATA-GOVERNANCE TRANSPARENCY / 2020–2025

Annual disclosures against defined customer-data controls.

Company-wide records since incorporation in 2020. Counts use the definitions shown in this table. A zero applies only to the defined event and is not a general security guarantee.

YEARCompulsory requests for customer information receivedCustomer information disclosed under compulsory processComplete assessment reports retained past the agreed deletion deadlineCustomer production-data copies retained past the agreed deletion deadlineCustomer content used for model training

2020*00000

202100000

202200000

202300000

202400000

202500000

* 2020 covers the period from incorporation. Retention metrics count copies held beyond the applicable contractual or published deletion deadline; approved temporary processing within an authorized task is excluded.

STANDARD CONTRACT & DELIVERY POLICY

Inquiry retention is enforced by this website runtime. Project deadlines are delivery controls. Technical content is separated from the small legal and transaction record that may need longer retention.

Inquiry not resulting in an engagementAPPLICATION-LAYER EXPIRY ≤ 48 HOURSThe encrypted inquiry envelope and optional reply detail are scheduled for deletion by the deadline; an operator may delete earlier. Independent deletion-test evidence remains pending.

Raw IP and full user-agentAPP DOES NOT PERSISTAbuse controls use short-lived, keyed in-memory identifiers; upstream logs are separate.

Temporary operations-log copiesTASK END / DEADLINE 24 HOURSOnly the minimum fragment needed for the task is copied.

Raw scan filesREPORT CHECK / DEADLINE 72 HOURSValidated findings move to the report; raw artifacts are deleted.

Unavoidable production-data copiesTASK END / DEADLINE 24 HOURSProduction data is not copied unless the task makes it unavoidable.

Final report delivery copyDELIVERY + 7 DAYS / DEADLINE 30 DAYSLong-term custody returns to the customer.

Contract, order, invoice and tax recordsUSUALLY 7 YEARS; LIMITED CASES 10Kept only to the extent required for the transaction and tax record.

Minimum authorization and evidence packageRISK-BASED / UP TO 10 YEARSA contractual ceiling, not a universal legal minimum; separable technical content is excluded.

Actual dispute or investigation materialLEGAL HOLD ONLYScope is limited, reviewed and deleted after the hold ends.

LEGAL AND AUTHORIZATION BOUNDARY

Applicable Japanese requirements include APPI, the Act on Prohibition of Unauthorized Computer Access, FEFTA and external-transmission rules under the Telecommunications Business Act. Before formal work begins, X FUTURO verifies authority, written authorization, scope and stop conditions. Customer eligibility and end use are reviewed before acceptance.

DATA HANDLING NOTICE

Keep legal evidence small. Keep customer technical content out of the archive.

DATA NOTICE / 2026-07-15 / v11

Customer production data and sensitive technical information remain in the customer environment whenever practical. The first inquiry requires only a message with enough context to decide whether a conversation makes sense.

PurposeRespond to the inquiry, evaluate fit, prevent abuse and establish a requested service.

OperatorX Futuro株式会社 (corporation no. 3120001231380), 1-5-15 Hirakawacho, Chiyoda-ku, Tokyo 102-0093, Japan.

CollectionMessage and an optional reply channel or prior receipt. Attachments are not accepted.

LocationThe public inquiry service is hosted on infrastructure in Japan; project processing locations are stated contractually.

Infrastructure logsThe application does not persist raw IP addresses. Load balancer, WAF and hosting logs are separate controls and must be configured to the same minimization policy before production.

AI useCustomer data must not be used to train AI models. Sensitive content must not be sent to an external AI provider without authorization.

DisclosureLimited to contracted processors, a valid legal obligation or the minimum needed to protect rights and systems.

RequestsUse the encrypted inquiry and reference your receipt to request access, correction or deletion where applicable.

Statutory retention, valid compulsory process or a narrowly scoped Legal Hold may override the normal deletion schedule.

ENCRYPTED CONTACT

Start with a short description of the problem.

A short message is enough. Add a phone number, LINE, WhatsApp or email only if you want a reply; a prior receipt may link a follow-up. If you prefer another contact method, describe it in the encrypted message.