Evidence before promises
Trust and file processing
These statements describe the current TapScanner web implementation. Each one has an owner, a dated evidence source, and an expiry date so unsupported claims disappear instead of becoming permanent marketing copy.
Follow the file lifecycle
A clear path from upload to cleanup
Use this timeline to see what the current evidence supports at each stage. A pending or partial label is intentional: TapScanner does not turn a source contract into a stronger runtime promise.
- 1
Processing boundary
1. Add and process
Evidence refresh required
View evidence cardThis stage has no current published runtime evidence. We will not infer a stronger claim until the owner revalidates it.
- 2
Temporary-file lifecycle
2. Review and download
Evidence refresh required
View evidence cardThis stage has no current published runtime evidence. We will not infer a stronger claim until the owner revalidates it.
- 3
Result-screen control
3. Delete when offered
Evidence refresh required
View evidence cardThis stage has no current published runtime evidence. We will not infer a stronger claim until the owner revalidates it.
- 4
Analytics data boundary
4. Measurement boundary
Evidence refresh required
View evidence cardThis stage has no current published runtime evidence. We will not infer a stronger claim until the owner revalidates it.
No implementation claim currently has unexpired evidence. The Trust Center will republish a claim only after its owner revalidates it.
Publication boundary
What still needs evidence
TapScanner does not publish implementation promises for these topics yet. The named owner must supply the stated evidence before the claim can appear as a verified fact.
Encryption for stored files and backups
Production evidence requiredEvidence needed: Current production storage inventory, provider configuration, key-management boundary, and backup coverage.
Owner: TapScanner Security · Boundary reviewed 2026-07-31
Use of document content for AI model training
Production evidence requiredEvidence needed: Current first- and third-party AI data-flow inventory, provider terms, retention settings, and an approved product policy.
Owner: TapScanner AI and Privacy · Boundary reviewed 2026-07-31
Processing regions and subprocessors
Third-party evidence requiredEvidence needed: Production provider inventory, contracted processing locations, subprocessors, and a dated owner approval.
Owner: TapScanner Privacy · Boundary reviewed 2026-07-31
Data Processing Addendum availability
Legal confirmation requiredEvidence needed: Approved customer eligibility, current executed terms, subprocessors, transfer mechanism, and request process.
Owner: TapScanner Legal · Boundary reviewed 2026-07-31
Independent security or compliance certifications
Third-party evidence requiredEvidence needed: Current certification report or public registry entry with scope, legal entity, validity period, and owner approval.
Owner: TapScanner Security and Legal · Boundary reviewed 2026-07-31
What we do not claim
This page does not claim a universal deletion deadline, browser-only processing, a selectable processing country, storage encryption coverage, an AI-training policy, DPA availability, or an independent certification unless a current evidence card explicitly says so. Check a tool's result screen for any tool-specific delete control.