Trust, security & privacy
RedactTFN exists to remove tax file numbers and other sensitive identifiers from client documents. This page sets out, in plain terms, how the platform handles that data — the questions a firm's risk, compliance or IT reviewer usually needs answered before approving a third-party tool.
Zero document retention
Uploaded files are processed in memory and returned to you redacted. We do not store, archive or back up the documents you upload, and we never use them to train models.
Encrypted end to end in transit
All traffic to the portal, the embed widget and the API is served over HTTPS with TLS. Database storage for account records is encrypted at rest by our managed cloud provider.
Least-privilege access control
Every account record is protected by row-level security so one customer's data is never readable by another. Staff access is role-based (super administrator and assistant administrator) and scoped to what the role requires.
Audit logging
Administrative actions and redaction activity are logged with actor, action and timestamp — metadata only, never document contents — so you can evidence who did what and when.
No card data on our systems
Payments are handled by Stripe. Card numbers are entered directly into Stripe's PCI-DSS compliant checkout and are never transmitted to or stored by RedactTFN.
Hardened API surface
API access requires a hashed, revocable key and is available on paid plans only. Inbound webhooks are signature-verified and processed idempotently. Uploads are size- and type-checked, including archive expansion limits.
What data we handle
Privacy & regulatory position
Australian Privacy Act 1988. We handle personal information in line with the Australian Privacy Principles: we collect only what is needed to deliver the service, use it only for that purpose, keep it secure, and destroy or de-identify it when it is no longer needed. Because uploaded documents are not retained, the personal information inside them is destroyed at the end of processing.
Tax file numbers. TFNs are treated as the most sensitive class of data on the platform. They are never stored, never written to logs, and never displayed back to anyone other than the user processing the document. Our purpose in touching a TFN is solely to remove it.
No secondary use. We do not sell, rent or share your data or your clients' data. We do not use uploaded content for analytics, marketing or model training.
Sub-processors. The platform relies on a managed cloud database and application host for the service itself, Stripe for payments, and an email provider for transactional messages such as receipts and account notices. Uploaded documents are not sent to any third-party service for processing.
Data residency. Australian data centre hosting is being arranged. Until that is confirmed we make no residency claim here, and we will publish the region on this page once it is in place. Ask us if residency is a condition of your engagement.
Your rights and controls
- Request access to, correction of, or deletion of the account data we hold about you.
- Revoke or rotate your API keys at any time from the portal.
- Cancel your subscription and retain access until the end of the paid period.
- Ask for a copy of your activity log for your own audit file.
Security and privacy contact
Vulnerability reports, privacy requests, due diligence questionnaires and incident enquiries: hello@removetfn.com.au. Please include enough detail to reproduce or action the issue. We acknowledge reports and will work with you on a fix; we ask that you do not publicly disclose an unpatched issue in the meantime.
This page describes the commitments of the operator of RedactTFN. It is not a certification and does not claim independent audit or accreditation. Where a claim depends on work still in progress, we say so.