Your address.Shared onyour terms.

Your address stays sealed.

A simpler relationship

Share a mask. Decide what comes next.

A participating business asks for the result it needs. Your permission sets the boundary.

  1. 01

    You

    Protect a verified US address. Share your mask and review every request for access.

    Protected
    Vault sealed · AES-256-GCM
  2. 02

    AddressMask

    Checks the permitted recipient, purpose, result and expiry before releasing anything.

    Zero-trust policy
    Policy engine · evaluating
  3. 03

    Participating business

    Uses its supported server integration to receive only the result you authorized.

    Scoped output
    Resolver-bound · single use
How it works

Five steps between a question and your front door.

Each step narrows what can be released. Nothing is assumed, and nothing is inferred.

  1. 01 / 05
    01. STORE

    Your address, sealed

    One verified US address is encrypted and held in your vault. It is never copied into a merchant's database.

  2. 03 / 05
    03. BIND

    Access with a boundary

    A business asks for one result, one purpose, one recipient, with an expiry. You approve it or you do not.

  3. 04 / 05
    04. RELEASE

    Only the permitted answer

    An approved resolver receives exactly what was allowed. Missing or ambiguous authorization is denied, never guessed.

  4. 05 / 05
    05. RECORD

    Every decision accounted for

    The ledger records what was released and to whom, without ever writing the address itself to a log.

Illustrative product model using synthetic data. Each production capability remains independently gated.

Your control

You know who, what, why, and when.

Choose the result a business is allowed to receive, and take it back whenever you want.

Incoming requestrsv_04
  • Shippingfull_delivery_address
AM-23456789ABCDEFGH
ReleasedAllowed

One-time delivery token · expires in 24h

Released to an approved resolver, never to the merchant directly.

AllowedScoped

Illustrative walkthrough using synthetic data. Your protected workspace is separate and never preloads a real address here.

For businesses and developers

Ask for the data your workflow actually needs.

One token, one purpose, one field. Nothing else resolves.

/api/v1 · versioned contract
You askPOST /masks/{mask}/tokens
{
  "policy_id": "b109df71-7e19-4b41-a592-69c8b60bf925",
  "purpose": "POSTAL_ROUTING",
  "audience": { "type": "resolver", "id": "rsv_04" },
  "requested_fields": ["postal_code"],
  "expires_in_seconds": 600
}
You get200 /resolutions
{
  "decision": "ALLOW",
  "result": { "postal_code": "94105" }
}
One field per resolution — maxProperties: 1 in the schema.

Sandbox ≠ production

Separate key material

Signed webhooks

Auditable delivery ledger

Versioned REST

Validated on every call

Privacy starts with the architecture

Access should be explainable before it is allowed.

Holding an identifier is not permission to see where someone lives.

01

Nothing to steal

The mask carries no address.

A mask is a random identifier. It contains no street, ZIP code, coordinates or identity, and the address itself stays encrypted.
02

No reason, no answer

Purpose, recipient, fields, expiry — or denied.

Every request must name a purpose, a recipient, the exact fields and an expiry. A request missing any of them is refused rather than guessed at.
03

Nothing unrecorded

Every decision kept. Never the address.

The ledger records what was released, to whom, and what was refused, without ever writing raw address data to a log.
Clear answers

What a mask is and what it is not.

AddressMask adds a controlled disclosure layer. It does not make the surrounding delivery network disappear.

It is an opaque, shareable identifier mapped to a protected address vault. The identifier itself contains no address information and does not grant permission to reveal an address.

No. A mask is not a bearer credential. When disclosure is enabled, access also requires a purpose-specific, audience-bound, field-scoped, expiring authorization and an approved resolver.

Not directly. An AddressMask is not a postal address or a universal shipping-label value. Shipping requires a separately authorized server-to-server resolution flow; a mask alone never grants access.

No. When the corresponding capability is enabled, a permitted request can return a smaller result such as service-area eligibility, tax jurisdiction, verification status, or postal code.

The product model supports revocable masks, permissions, and unused access tokens. Full-address shipping tokens are designed to be single-use by default.

Address validation is designed for United States addresses only. International addresses are rejected rather than being silently accepted or treated as verified.

Designed for verified US addresses

Take control of your physical identity.

Protect one US address and share an opaque mask instead of copying the source record everywhere.

For verified US addresses and supported integrations