Choose the path
Confirm the browser, AI destination, document format, and required outcome.
AI file redaction
AI file redaction. Keep the useful document.
Evaluate a supported employee upload path for DOCX, Excel, or PDF before a file reaches an AI service. Aona can return a redacted copy when the configured policy and route support it.
Supported browser upload
Employee upload
Attach renewal-summary.docx for a concise customer brief
Sensitive fields matched
Synthetic policy response on a supported evaluation path.
Redacted copy returnedSupported file workflow
Start with file type, upload path and output.
Apply the policy
Inspect a synthetic file against the configured sensitive-data rules.
Review the returned file
Inspect the policy response, usability, and evidence for the supported configuration.
Synthetic before / after
A synthetic DOCX example
A customer-success team prepares a renewal summary. The redacted copy retains the narrative and structure while masking the customer reference and account field.
Original synthetic sampleSynthetic
Renewal brief for Acme Health, account 481-209
Document formats
DOCX Validate layoutXLSX Check formulas + hidden sheetsPDF Check text + scanned pages
YOUR EVALUATION, MADE PRACTICAL
Start with a test.
Leave with evidence.
Use a synthetic example, agree the result you need, then record what actually happened.
Claude web · document attachmentSynthetic input
A useful document after sensitive details are removed.
Renewal summary Customer: Morgan Hale Email: morgan.hale@example.com Account: AC-48217 Next step: review the renewal on Friday.Download document test recipe
WHAT TO CHECK
- 01
Create a synthetic DOCX with these fields and a small table.
- 02
Test attachment and drag-and-drop as separate input paths.
- 03
Inspect the returned file, its layout and the matching policy outcome.
This is a file-test recipe, not a processed document. Check each format and current Claude client independently.
Get the acceptance checklistBuyer questions
File formats and route limits to check.
What is supported today?
DOCX, Excel, and PDF inline redaction are documented with layout preservation. Validate the required file, AI destination, and client path during an evaluation.
What does the browser path not cover?
Browser extensions do not cover mobile AI use or native desktop AI apps. Coverage depends on the installed client, supported platform path, and current extension version.
What does the visual show?
The document and policy response above are synthetic evaluation examples, not a customer file or a guarantee that every entity, tool, or configuration is supported.
Which formats should we start with?
Start with the real workflow and a synthetic DOCX, XLSX, or PDF. Confirm the employee upload route, required policy response, and returned-file criteria before expanding scope.
What should we inspect in a DOCX, XLSX, or PDF result?
For the document type in scope, compare the original and returned synthetic file. Check the required layout and text, then explicitly test formulas and hidden sheets in XLSX, and OCR or scanned pages in PDF where those matter.
Can we approve the control from a detection result alone?
No. A useful acceptance test records the exact upload path and policy response, then has the workflow owner inspect the resulting file for the task it must still support.
Does redaction mean the original cannot leave the device?
With a redaction policy, the redacted copy is what reaches the AI tool; the original file stays where it was. With a block policy the upload is stopped before it leaves the device. Test it with a synthetic DOCX, XLSX or PDF on your own route during the 30-day trial.
What should a pilot measure?
Expected action, resulting file, usability, audit evidence, and known failure cases, not an unsupported universal accuracy number.
Focused evaluation
Bring one real decision. Leave with the next validation step.
We’ll keep the discussion to your intended workflow, data categories and technical boundaries.
Book a focused demo