Product approach draft · Last review: August 2026
1. Device-centered storage
Life Card records and document content are handled with a device-centered architecture. Dueriva aims to avoid unnecessary circulation of sensitive content through servers.
2. OCR and date confirmation
Scanning is processed on the device. Raw OCR text is not kept as a permanent product record. An extracted date is a suggestion; it becomes a reminder only after user approval.
3. Encrypted document attachments
Persistent attachments are encrypted with AES-256-GCM in app-private storage. Key material is protected through Android Keystore. A document opened by the user may be temporarily decrypted for an external viewer; temporary-file cleanup is part of the product lifecycle.
4. Limits of Premium verification
A future Premium entitlement verification service should be limited to purchase and entitlement data. Life Card, document and OCR content should not be sent to that service.
5. Deletion and backup
Document deletion aims to remove encrypted files and related temporary copies. Standard Android app backup remains disabled until secure recovery and export are designed. Device loss may therefore cause data loss; encrypted export and restore are a separate development effort.
6. Privacy contact
For privacy, support or Android launch questions, email us. Do not attach identity documents, insurance policies, financial documents or other sensitive content. The email provider processes your address and message. This channel does not create a newsletter or waiting list. Final retention and deletion periods will be stated before public launch.
Absolute claims such as “100% secure”, “no data ever leaves the device” or “fully offline” are avoided. Google Play services may process limited technical diagnostics and usage data. The final public policy must match the released app and its Data Safety declaration.