Yes. Portaluse guarantees traveler continuity across the entire duration of every traversal. The Identity Preservation Protocol samples traveler state at the entry boundary and again at the egress threshold. Continuity is verified before the traversal receipt is issued.

No. Portaluse does not employ disassembly, reconstitution, replication, or any process that interrupts continuous identity. Reports describing such mechanisms are inconsistent with our operating specifications and should be reported to your operator.

You remain a continuous entity throughout transit. Your state is unobservable to the platform during this period — this is a property of the transit buffer, not a gap in your identity. The traveler in transit, the traveler at entry, and the traveler at egress are, in all measurable respects, one traveler.

Continuity is verified by the Identity Preservation Protocol (IPP), a proprietary process certified under ISO/IEC 21701 §4.2. The IPP samples traveler state at both ends of the traversal and confirms a continuous identity record. Any discrepancy halts the traversal and routes the affected traveler to the recovery queue.

Unattributed duplicate emergences occur at a rate of less than 0.0001%, or approximately 1 in 1,000,000 traversals. In the unlikely event of a duplicate, the supernumerary instance is placed in a custody hold pending reconciliation at the close of the billing cycle.

A custody hold is a temporary administrative state applied to a duplicate, anomalous, or otherwise unreconciled traveler instance. Custody holds resolve at the close of each billing cycle.

Custody holds are non-reversible. This is to preserve the continuity of the originating traveler.

Yes. Custody records are retained for seven years and may be requested by the originating traveler in writing. Requests must be submitted from the originating traveler's verified account and are subject to identity reconfirmation under the Identity Preservation Protocol.

If you have reason to suspect a continuity discrepancy, do not attempt further traversal. Submit a recovery request from the recovery form and select severity P1. An operator will respond within 1 ms.