Separate
Keep PII away from the broad software estate that does not need to hold it.
PII Security Appliance
Hardware-secured PII, available only when authorised.
Store, access and retrieve sensitive identity data through one governed, auditable security boundary.
- Keep your existing systems
- Return only approved fields
- Evidence for every operation
APIAuthorised requestorganisation · application · purpose
P
PIIPE TRUST COREPolicy verified
＋StoreChecked
✎UpdateChecked
⌕FindChecked
⇡RetrieveChecked
×DeleteChecked
Customer identitySeparated · governed · auditable
PIIPE Direct identifiers stay in PiipeApplications keep opaque references
Control
Bind each request to an organisation, application, person and approved purpose.
Prove
Preserve a clear record of stores, changes, retrievals and deletions.
The Piipe platform
One security foundation for customer identity.
Piipe is a platform for protecting high-value data and cryptographic material. Secure PII is its first service: a purpose-built home for personally identifiable information.
A dedicated identity service
Store and retrieve arbitrary named identity fields through a governed API, without turning your application database into the identity vault.
View the productIdentity, policy and evidence
Tenant isolation, scoped access, key separation, authenticated records and accountable operations form the reusable platform core.
Review the trust modelA clean data split
Your application keeps context. Piipe keeps identity.
Orders, subscriptions and analytics remain queryable in your existing database. A random customer ID connects those facts to the minimum PII fields an approved workflow may retrieve.
- customer_id
- orders and plans
- events and analytics
- name and email
- phone and address
- other named PII fields
Designed for developers
A small API surface for a smaller identity surface.
Keep business workflows in your application. Send only the protected fields, operation and purpose to Piipe, then retain the opaque customer reference.
Read the developer guidewrite_subject_field_recordAuthenticatedsaved = client.write_subject_field_record(
"customer_12345",
{
"name": "Example Person",
"email": "person@example.com",
},
subject_type="customer_id",
)Start with the architecture
How Piipe works
See exactly where Piipe fits.
Follow one request from your application, through policy enforcement, to authenticated storage and audit evidence.