PROTECT → APPROVE → RELEASE → RELOCK → RECOVER

Authority before access.

XAIPT Guard is a protection layer for configured Android app access. When a protected target opens, XAIPT can hold the boundary, require fresh authority, grant bounded access, and relock—while Recovery, Vault and evidence remain separate, understandable product surfaces.

See the real flow →What XAIPT does—and does not do

Current public-launch candidate · Android first · claims remain evidence-bound · release remains gated until physical qualification and Play submission are complete.

Living product stateConfigured is not silently called Protected.

Five clear surfacesHome · Protection · Activity · Vault · You

THE PRODUCT

Protection is a state machine, not a badge.

XAIPT is designed around Authority Before Action and bounded consequence. The visible interface follows the same security truth as the runtime underneath it.

01 · PROTECTION

Configured targets

Choose apps you want XAIPT to observe and protect. Target identity and enforcement health matter; selection alone is not a Protected claim.

02 · AUTHORITY

Fresh approval

A held access request requires the admitted authority path. The current local path uses fresh strong biometric-backed approval rather than a durable “already authenticated” flag.

03 · CONTINUITY

Recovery without pretending

Recovery packages, authority succession and verification remain a separate domain. Recovery does not silently become access approval.

REAL ACCESS FLOW

Open. Hold. Approve. Release. Relock.

The product meaning is simple enough to understand at a glance, while the security contract stays strict underneath.

01Target observed

02HOLD established

03Fresh approval

04Bounded release

05Relock

PROTECTION

A visible boundary before access.

XAIPT’s protection center brings target selection, enforcement readiness, authority requirements and proof status together. It is designed to show what is configured, what is ready, and what still needs proof—without decorative “security percentages.”

Target identityEnforcement healthProtection Proof

VAULT

XAIPT-owned private content.

Vault is a separate protected content surface. It does not claim to secure arbitrary third-party data.

ACTIVITY

Evidence, made readable.

Security events are projected as understandable activity—not raw developer logs or fabricated confidence scores.

RECOVERY

Your way back.

Create, preserve and verify a Recovery Package, then use controlled succession when authority must be replaced.

CLAIM BOUNDARY

What is real now. What remains future authority.

A premium security product earns trust by separating implemented behavior from architecture that has not yet been admitted for public use.

CURRENT PRODUCT

Admitted product surfaces

Configured Android protection targets

Runtime target observation and HOLD

Fresh local strong-biometric approval

Bounded release and relock

Recovery package verification/succession

Vault + Activity + evidence-backed state

NOT A CURRENT PUBLIC CLAIM

Expansion stays clearly separated

Independent / Authority Phone expansion

Maximum multi-factor authority

Provider, bank or payment-network enforcement

Hardware / XAN authority endpoints

Universal AppLock or OS-level control

Any claim not backed by qualified evidence

X ECOSYSTEM

Focused products. Shared discipline.

XAIPT is not presented as “AI everything.” Each product keeps a clear job and boundary.

XAIPT

Protection & authority

XAIPT Guard focuses on protected access, bounded authority, continuity and recovery. Its mission is PROTECT → SURVIVE → RECOVER.

XMECK

Private intelligence workspace

XMECK is the separate private/offline-first intelligence product direction: local and governed model workflows, projects, knowledge and agents. XAIPT remains the protection product; XMECK remains the intelligence product.

GOOGLE PLAY READINESS

Public launch is a gate, not a button.

The website is prepared to become the public policy/support surface, but Play publication remains correctly blocked until the qualified Android artifact and declarations match reality.

Release control board

Bounded HOLD + Recovery physical regressionPending before release admission.

AccessibilityService declaration + disclosure evidenceRequired for the production behavior actually used.

Privacy policy + Data Safety reconciliationMust match the final app, SDKs and backend exactly.

Release signing, AAB, merged-manifest and R8 auditNot performed by this website build.

Store listing, screenshots and reviewer accessPrepared only after final release artifact identity is frozen.

ANDROID FIRST

Protection that says exactly what it means.

XAIPT Guard is moving through controlled physical and release qualification. Public download should activate only when the qualified build, Play declarations and published policies describe the same product.

Privacy Account & data deletion Security disclosure