What you are building
Shopping assistants, post-purchase support agents and personalization services.
Why memory decides whether it works
- One customer appears as an email, a loyalty id, a device and a guest checkout.
- Stale personalization — recommending baby products years later — is a visible failure.
- Customers expect deletion to work.
What Auld provides
- Identities as your canonical customer id, with traits for linked identifiers.
- Supersession for sizes, preferences and life changes.
- Deletion of an identity’s authored data.
- Flex recall without per-call metering for high-traffic assistants.
Getting there
Resolve identifiers first
Use your customer id as the identity; keep links in traits.
Ingest orders, returns and chats
As records with real times.
Recall per session
Before recommending or answering.
Wire deletion
Connect your privacy request flow to identity deletion.
Data and boundaries
Scenarios on this page are illustrative and do not describe a specific customer.
Frequently asked questions
Can we forget a preference without deleting the customer?
Yes: delete the record it came from, or send a dated record that it no longer applies.
High traffic?
Flex does not meter recall; ingestion is metered by bytes.