Privacy Policy
Records Retention & Shredding
1. Scope of this notice
This notice describes data handling found in the checked-in Android app source. It does not verify a signed release, the final merged manifest, current Google Play Data Safety answers, or provider-side processing, retention, and deletion. Review those items before relying on this notice as a description of a published build.
2. Information stored in the app
The app stores the organization name and archive batch details you enter. A batch may include an identifier, title or contents description, category, creation date, preset period, calculated review date, storage location, notes, destruction date, selected method, a name or witness you enter, and your optional reference number. These values are saved with Android SharedPreferences in app-private storage. The checked-in source has no app account or record-sync path.
The Android source disables backup and device transfer for app data. The app does not add a separate encryption layer to the SharedPreferences values. Protect access to your device and do not enter information you are not authorized to store. This describes the checked-in Android configuration. Some Android 12+ manufacturers may still allow device-to-device migration; behavior has not been verified across manufacturers.
3. PDF disposal logs
The app creates a PDF log on the device from details marked by the user. It is not an official or verified certificate and is not an immutable audit trail. The app does not verify that disposal took place, the selected method, vendor credentials, signatures, legal requirements, holds, or approvals. A PDF leaves the app only when you choose to print or share it; the destination controls any copy saved or sent.
4. Optional campaign notifications
Campaign notices are off unless you enable the in-app notification setting and grant Android notification permission. When both are enabled, Firebase Cloud Messaging may process a messaging token, app/category/portfolio topic subscriptions, and delivery information to route notices. The app's locally stored batch records are not included in campaign targeting. Turning the setting off requests topic removal, disables FCM automatic initialization, and asks FCM to delete the messaging token. This source review does not confirm provider-side retention or deletion timing.
5. Purchases
The source includes Google Play Billing for a one-time Pro product; availability depends on the build configuration and Play listing. If configured, Google Play processes payment. The app sends the package name, product ID, purchase token, and purchase source to the configured verification service so it can check entitlement. The app does not receive payment-card details. The verification service's provider-side retention and deletion practices have not been independently confirmed in this review.
6. Advertising and analytics
No Google Mobile Ads SDK dependency, ad placement, or AdMob application ID remains in the reviewed Android source. The unused ad configuration files were removed. The September 29 signed candidate predates that cleanup, and the behavior of older published versions has not been verified.
7. Retention and deletion
Delete individual batch records using the in-app delete control. Clear the app's storage in Android Settings or uninstall the app to remove locally stored records and the organization name. A PDF already printed or shared must be removed from the destination separately. Purchase-verification and Firebase messaging data may be held by their providers; their server-side deletion is outside the app's local controls.
8. Children
This is a business recordkeeping utility and is not marketed to children. The app has no age gate; users can enter text into batch and notes fields. Do not enter a child's personal information unless you are authorized to do so and applicable requirements permit it.
9. Contact
For privacy questions, contact raghebtube@gmail.com.