AddressMask
Skip to content
AddressMask
How it worksYour controlFor businessesSecurityDocs
Open AddressMask
How it worksYour controlFor businessesSecurityDocsOpen AddressMask
Trust center
Privacy noticeTerms of serviceAcceptable useSecurity overviewSubprocessors
Security overview

Security overview

This overview describes the initial release architecture. It is not a certification, penetration-test report, anonymity guarantee, or promise that any system is invulnerable.

Effective
August 30, 2026
Applies to
Initial United States release
Contact
info@newlightai.com
On this pageIdentity and sessionsProtected data and credentialsDisclosure and tenant isolationWebhooks and operationsProvider and availability boundaryReporting a security issue

Identity and sessions

  • Verified passwordless email, Google OIDC, and optional passkeys.
  • Secure, HttpOnly, SameSite cookies backed by revocable server-side sessions.
  • Recent authentication for address reveal, credential changes, deletion, and other sensitive actions.
  • Same-origin defenses for browser mutations and tenant/resource authorization at protected endpoints.

Protected data and credentials

  • Address payloads use versioned envelope encryption with contextual authenticated data. Key material is supplied through protected production configuration and supports active and decrypt-only retired versions.
  • Deterministic lookup uses independent HMAC keys rather than raw address or email columns.
  • API keys and purpose-bound tokens are high-entropy, returned once, and stored only as keyed lookup values. Secrets are prohibited from URLs, logs, analytics, and browser storage.
  • Public masks are random and non-semantic; they do not encode an address, ZIP code, user, coordinate, or timestamp.

Disclosure and tenant isolation

Resolution checks the authenticated resolver, environment, organization, mask and address status, exact purpose, audience, requested field, shipment context where required, token expiry and state, immutable policy version, and active consent. Missing or ambiguous input denies access. Full-address shipping tokens are single-use by default and consumption is transactionally coordinated with the resolution and audit record.

Webhooks and operations

  • Signed webhook events use durable outbox records, fenced leases, bounded retry, and a delivery ledger.
  • Outbound webhook delivery requires HTTPS, re-resolves DNS for each attempt, rejects non-public address ranges, pins the accepted connection, and retains no response body.
  • Redacted structured logs and immutable audit events record IDs and outcome categories, not raw addresses or bearer secrets.
  • Destructive account finalization is a separate production gate and remains disabled without an approved retention-policy version.

Provider and availability boundary

Address validation, email, hosting, and database operations rely on the providers listed on the Subprocessors page. Provider ambiguity or outage never upgrades an address to verified. Required authorization, decryption, database, or resolver failures return no protected address data.

Reporting a security issue

Send a concise report to info@newlightai.com with the affected product area, time, impact, and safe reproduction details. Do not send a raw address, access token, API key, session cookie, encryption key, or other live secret by email. Avoid accessing another person's data or disrupting the service while investigating.

AddressMask

A private address network for the United States. Share an opaque mask, decide what any business is allowed to receive, and take it back whenever you want.

Open AddressMask
ProductHow it worksYour controlFor businessesSecurityFAQ
DevelopersDeveloper docsOpenAPIBusiness workspaceContact
TrustPrivacyTermsAcceptable useSecurity overviewSubprocessors
© 2026 AddressMask · Operated by Newlight Solutions

Designed for verified US addresses. An AddressMask is not a bearer credential or a universal shipping-label address.