Privacy-by-Design

Ship to anyone.
Store nothing.

Replace home addresses in your database with a single ProntoID reference token. Your app fulfils orders without ever seeing—or holding—the recipient's physical location.

GDPR-ready
CCPA-ready
Zero PII stored
The Problem

Physical addresses are a honey pot

Any app that ships physical goods traditionally stores home addresses. That turns your database into a high-value target — and your team into reluctant guardians of some of the most sensitive PII that exists.

Breach Risk

A single SQL injection or misconfigured S3 bucket exposes thousands of home addresses. Residential locations are among the hardest PII to un-expose once leaked.

Compliance Burden

GDPR Article 5 and CCPA both treat physical location as sensitive PII. Storing it triggers data mapping obligations, DPIAs, retention policies, and subject-access-request workflows.

User Friction

Users are increasingly reluctant to hand their home address to yet another third-party app. Abandonment at the shipping-details step is a silent revenue killer.

How It Works

Four steps to zero PII

1

Selection

A user inside your printing app wants to send a photo to a friend. They search by name or scan the recipient's ProntoID QR code.

2

Reference

Instead of typing "123 Maple Street," the app stores only an opaque alphanumeric reference: pid_ref_4f8c2a91e3b7. No postcode. No city. Nothing.

3

Decoupling

Your database table has a recipient_pid column, not an address column. Even if your database is compromised, there is nothing to steal.

4

Secure Fulfilment

At checkout your backend calls the ProntoID Fulfilment API. ProntoID resolves the reference and delivers the shipping label or encrypted address payload directly to your logistics partner — your servers never see it.

Side by Side

Traditional vs ProntoID

Feature Traditional App ProntoID Strategy
Data Stored Plain-text addresses in SQL / NoSQL Opaque alphanumeric reference token only
Breach Impact Thousands of home locations exposed Token is worthless without ProntoID key
Regulatory Scope Full GDPR / CCPA data controller duties Dramatically reduced — PII held by ProntoID
User Visibility Address visible to app admins & devs Address hidden from your platform entirely
Address Updates User must update every app individually Update once in ProntoID — all apps sync
Audit Trail Internal logs with PII embedded Fulfilment logs reference token, never address
DPIA Required? Almost certainly yes Likely no — PII not processed by your app
Security Architecture

Decoupled by design

ProntoID's architecture removes your platform from the PII data path — not as an afterthought, but as its fundamental operating model.

Zero-Knowledge Fulfilment

Your servers facilitate the service without ever processing the underlying address. The resolution happens inside ProntoID's hardened infrastructure and is pushed directly to your logistics partner.

One-Time Encrypted Handshake

Each fulfilment event generates a short-lived, AES-256 encrypted payload delivered directly to your logistics API. Replay attacks are structurally impossible — the token is consumed on use.

Consent-Gated Resolution

Address resolution only succeeds when the ProntoID holder has granted consent to that specific app and fulfilment event. Users can revoke access at any time from their ProntoID dashboard.

Immutable Audit Log

Every resolution attempt — successful or denied — is logged with timestamp, app ID, and fulfilment outcome. No PII appears in the log; you get full accountability without liability.

Single Source of Truth

When a user moves, they update their address once inside ProntoID. Every app holding their reference automatically routes to the new address on the next fulfilment — no stale data, no re-delivery failures.

Privacy-First Brand Signal

Market your app as a platform that structurally cannot leak home addresses. In an era of data scandals, "we never store your address" is a genuine competitive differentiator.

Use Cases

The Printing & Gifting Economy

Any platform that needs to route a physical item to a person without storing their home address is a perfect fit.

Photo Print Services

Users send prints to friends and family. The platform resolves the recipient address at dispatch — never at order creation.

Gift & Flowers Delivery

Senders gift without asking the recipient for their address. The recipient's ProntoID resolves the delivery location at the moment of dispatch.

Marketplace Shipping

P2P marketplaces can route physical items without exposing buyer home addresses to sellers — or storing them in the platform database.

HR Benefits & Perks

Employee gift programmes, work-from-home stipend fulfilment, and recognition packages — HR platforms handle dispatch without needing a home address database.

Book & Subscription Boxes

Subscription box platforms and independent publishers dispatch physical items to verified addresses — no customer address table required.

Corporate Merchandise

Swag and branded merchandise fulfilment for distributed teams — employees register their ProntoID; HR dispatches without maintaining a home address spreadsheet.

fulfilment.js
// Step 1: store only the ProntoID reference at order time
const order = {
  product_id: 'PRINT_A4_GLOSSY',
  recipient_pid: 'pid_ref_4f8c2a91e3b7', // ← no address!
  quantity: 1
};

// Step 2: at dispatch, call the ProntoID Fulfilment API
const label = await prontoid.fulfilment.resolve({
  pid_ref:    order.recipient_pid,
  courier_id: 'dhl_express',
  order_ref:  order.id
});

// Step 3: pass the label to your courier API
await courier.createShipment({ label });

// Your DB never held the address. Done.
Integration

Up and running
in 3 steps

No new UI paradigms. No re-architecting your database schema beyond swapping one column type.

1

API Connection

Add the ProntoID SDK to your project. Point your checkout or shipping flow at the ProntoID Fulfilment API endpoint. A single DPA covers your compliance obligations.

2

Token Exchange

Replace address input fields with a ProntoID Lookup widget — a one-line embed. Users search by name, username, or QR code. Your backend receives and stores the opaque reference.

3

Secure Fulfilment

At dispatch, call prontoid.fulfilment.resolve() with the reference and your courier ID. ProntoID returns a ready-to-use shipping label or encrypted address payload — direct to your logistics partner.

0 bytes
PII stored in your database
AES-256
Encryption on every handshake
< 120ms
Avg. fulfilment resolution time
GDPR · CCPA · eIDAS
Regulatory frameworks covered
Testimonials

Trusted by privacy-first teams

"We removed the address table entirely. Our DPO was delighted — the DPIA scope dropped by half overnight."

J
James P.
CTO, Photo Print Startup

"Users actually trust us more. Saying we structurally cannot store their address resonates in our onboarding."

M
Maria G.
Head of Product, Gift Platform

"ProntoID integration took two days. The SDK is well-documented and the support team answered questions fast."

T
Tom B.
Lead Engineer, E-Commerce Marketplace
FAQ

Common questions

At order time your app stores only the opaque ProntoID reference token — no address data whatsoever. When the order is dispatched, your backend calls the ProntoID Fulfilment API with the reference and your courier ID. ProntoID resolves the address internally and sends a ready-to-use shipping label directly to your logistics API. Your servers are never in the address data path.
Yes. Because your application never receives or stores the physical address, you are not the data controller for that PII. ProntoID acts as the processor under a signed DPA, dramatically reducing your regulatory surface area. In most implementations a formal DPIA is no longer required for the address-handling component.
The user updates their address once inside their ProntoID account. Every application that holds their reference token automatically routes to the new address at the next fulfilment event — no re-entry required, no stale addresses, no re-delivery failures.
Yes. The reference token is permanent and reusable across unlimited fulfilment events. Each individual shipment generates its own short-lived encrypted handshake, so auditability is maintained without ever exposing the underlying address to your systems.
If the recipient does not yet have a ProntoID, your app can send them an invitation link. Once they register and verify their address, the reference resolves normally. During the pending period you can hold the order or offer an alternative fallback flow — our SDK provides status callbacks for both states.
Yes, at any time. Users manage consent grants from their ProntoID dashboard. If consent is revoked, subsequent resolution calls from that app will return a permission-denied response, giving users full control without needing to contact your support team.
Related Services

The broader ProntoID ecosystem

Secure your users.
Protect your business.

Decouple your platform from physical address PII today. Ship to anyone. Store nothing.

Start for Free Contact Sales

No credit card required  ·  Setup in minutes  ·  Cancel anytime