Recount sits in the code paths that matter most, next to applications, payments and personal details. So it’s built to see as little as it needs, and to keep what it does see safe.
In your app
{
name: 'Sam Lee',
taxFileNumber: '123 456 782',
income: 7771
}What Recount receives
{
name: 'Sam Lee',
taxFileNumber: ****,
income: 7771
}List a field as sensitive and the SDK replaces it before anything is sent, so it never reaches us.
Authorization, cookie and API key headers on recorded requests are always removed, with no setup.
In transit and at rest.
Once a decision is recorded, it stays exactly as it happened. Reports never change once made.
Traces for up to 365 days, records for up to 25 months, reports for as long as your plan allows.
Owner, admin, developer and member roles for your team. Portals show each client only their own decisions, and only the steps you mark public.
On AWS in Sydney.
Our agreements are public. If you need a security questionnaire completed, email support@refactor.gg.
Fields you mark as sensitive are removed inside your app, so they never reach us. Everything else is encrypted in transit and at rest, stored in Australia, and can’t be edited once it’s recorded. You choose how long it’s kept and who can see it. If you need a security questionnaire completed, email support@refactor.gg.
On AWS in Sydney, Australia. Our subprocessors are listed publicly, and our Data Processing Agreement covers how we handle your data.
Authorization, cookie and API key headers on recorded HTTP requests are always redacted. Any other field, in a request, query, table or JSON step, is redacted when you list it, and is replaced inside your app before anything is sent.
Free to start. No credit card required.