What local file options prove: atomic writes, backup exclusion and carrier scope
Local write options do not replace network, remote, backup and retention review
Source paths use different options: some iOS cache/pending/temporary-image writes specify completeFileProtection; inbox manifests and note metadata use atomic writes, with backup exclusion on selected directories. Review actual paths instead of claiming end-to-end encryption, uniform protection or disappearance of every copy.
Different from redaction, removal and retention mapping
Redaction checks content, removal checks deletion scope, retention maps evidence. Here which carriers options cover and what needs actual attributes/system checks matters. No private files/properties, backups or restores are operated.
| Check | Verified scope | Manual review | Not established |
|---|---|---|---|
| atomic | Write-replacement consistency option | Actual file/failure | Encryption/signature/directory transaction |
| iOS cache/pending | Cited paths specify completeFileProtection | Actual file/system conditions | Every platform/file identical |
| Temporary image | Explicit staged JPEG protection write | Staged file versus later copies | All shared files get identical options |
| Manifest/note metadata | Some writes specify only atomic | Defaults/inheritance separately | Missing explicit option proves plaintext |
| Backup exclusion | Per-directory, differing error handling | Success/other copies | No backups or permanent non-retention |
| Network/remote | Local options do not cover service | Actual target/network/authority | End-to-end encryption or remote wipe |
| Platform branches | iOS/test-platform options differ | Conditional code/runtime | macOS branch proves a shipped Mac app |
| Security/retention | Actual scope/policy required | Content/copies/access separately | Certification/permanent backup/restore SLA |
Synthetic protection review
Known: one sample write explicitly specifies completeFileProtection. Unknown: other-copy attributes/destination retention. Report that call only, not whole-package end-to-end encryption or irreversible deletion.
Absent explicit options do not prove plaintext; defaults/inheritance need authorized inspection. No security audit/device unlock ran, and atomic/exclusion does not establish evidence truth or compliance.
FAQ
Is atomic encryption?
No encryption/signing follows from that option alone.
Does one protected path cover every attachment?
No. Writes/later copies need separate review.
Does atomic alone guarantee plaintext?
No. Defaults/inheritance/actual system conditions matter.
Does backup exclusion prove no copies exist?
No. Setting success, other backups/remotes/manual copies differ.
Does macOS conditional code prove a live Mac app?
No. Test/conditional paths establish neither distribution nor store/production support.
Is this privacy or recovery certification?
No certification/backup/restore service is added; actual permissions/policies remain.
Reading and source
Content redaction · Removal scope · Material retention · Start · Privacy
Pending writes/attributes · Cache/draft platform options · Note writes/exclusion · Temporary image · Manifest writes
