What Recalled actually solves
Hand-picked, concrete examples of what an audit log replaces inside your product, with the code snippet to wire it up in under 5 minutes.
Log every waitlist signup
Log every waitlist signup with actor, email, source, referrer and timestamp. Hand the list to sales when you open the doors, or replay it when a beta invite bounces.
Audit every admin action
Log every sensitive action taken by a staff member from your back-office: suspensions, refunds, impersonations, role changes. Answer 'who did this and when' before anyone has to ask.
Reconstruct any user's timeline
Query every event by actor id to rebuild a minute-by-minute timeline of what a user did. Perfect for support investigations, bug reports, and replaying the context of a complaint.
GDPR-ready audit trail
Recalled is hosted in the EU, encrypted at rest, and exposes a one-call anonymization endpoint for Article 17. Ship a GDPR-ready audit trail without building your own data protection layer.
Audit payments and subscription changes
Log paid invoices, failed charges, refunds, subscription upgrades and cancellations in one tamper-proof trail, separate from your production DB and your Stripe dashboard.
Log every security event
Log authentication events with actor, IP, user agent and outcome. Detect credential stuffing, replay suspicious sessions, and prove to enterprise customers that security matters to you.
Ship SOC 2 / ISO 27001 evidence
SOC 2 and ISO 27001 both require an immutable record of sensitive actions. Recalled emits hash-chained, signed events so your auditor can verify integrity without trusting your database.
Give support the full context
Mint a short-lived embed token server-side, drop the `<RecalledFeed />` React component into your support tool, and give your agents the last 25 actions of the customer without switching tabs.
Audit your AI agent actions
Your AI agent acts on behalf of users. Recalled records every action with actor.type set to 'agent', a hash chain and an HMAC signature, plus the conversation id and the user who triggered it. When the agent gets it wrong, you have a forensic trail.
Cryptographic receipts for any action
Every Recalled event ships with a portable receipt: a JSON object plus a public webpage URL. Send it to a customer who disputes an action, attach it to a support ticket, paste it in a Slack reply, or let your AI agent cite it. The recipient clicks, sees the action, the timestamp and a green Verified banner, with no Recalled account or API key required.