OwnWise Privacy Policy

Effective date: 22 October 2026

OwnWise is published by AshishKapoor30. This policy applies to the OwnWise Android application, package com1.ownwise.app.

Privacy and support contact: kapoorashish213@gmail.com.

Your collection stays on your device

OwnWise stores your local profile name, item details, purchase prices and dates, product photos, invoices, warranty cards, registration notes, vehicle details and expiry dates, reminders, theme and currency preferences, and repair or service records with their original attachments on your device. It also keeps unfinished drafts, files shared into its private inbox, and physical pouch/leaf labels and document-location mappings locally. It uses this information to organise your collection, display warranty, vehicle and care dates, find filed papers, prepare exports, and schedule the reminders you choose.

OwnWise does not upload this collection to a publisher-operated server. It does not provide cloud synchronization or an online OwnWise account. Your local profile is independent of the Google Play account used for purchases. We do not sell your collection or use it for advertising.

Invoice recognition

Automatic invoice recognition is not available in the current Add Item flow. Add Item opens a form for user-entered details. Images, PDF and Word documents are attached as originals and do not automatically fill in or change product fields. Documents are read on your device; Word uses a reading layout that may differ from its original formatting. Bundled Google ML Kit text-recognition and language-identification helpers remain in the app for future reviewed imports. OwnWise does not send your invoice images or text to an online OCR service.

When ML Kit features are used, their SDKs collect technical information for diagnostics and usage analytics. This includes device model and operating-system information, app package and version, device or per-installation identifiers depending on the SDK, performance and error information, feature events, configuration such as image format and resolution, and input/output sizes. Language identification also reports identified languages when used. Google states that this SDK information is encrypted in transit using HTTPS and is not transferred by ML Kit to third parties. These diagnostics are separate from your locally stored invoice contents. Bundled recognition helpers do not mean that every document upload invokes recognition.

See Google ML Kit's data disclosures and Google's Privacy Policy for Google's handling of this information.

Google Play purchases

Google Play processes Pro payments and subscriptions. OwnWise checks purchase status, verifies purchase data, and acknowledges completed purchases to enable paid features and restore access. Purchase tokens and verification data are handled by the native app; OwnWise does not send them to a publisher-operated billing server. We do not receive your payment-card details. Google retains purchase and account information according to its own policies. Cancelling a subscription is done through Google Play; deleting app data does not cancel a subscription. Closed-testing builds provide temporary feature access without requiring a purchase.

Production builds start a 10-day Pro trial when you first complete Google connection and enter OwnWise. It requires no payment details and does not automatically create or charge a subscription. Trial start, expiry and last-observed time are kept in private device preferences separately from collection backups. After expiry, existing records, originals and the selected theme remain; adding beyond Free limits requires a verified Play subscription. Annual Pro costs ₹249 in India, US$7 in the United States and a regional Play price based on US$7 elsewhere, subject to local conversion, rounding and tax rules. The app uses the current Play billing country only to check the displayed price, without storing it in your profile or using it for tracking or marketing.

Permissions and reminders

OwnWise sends only reminders requiring your attention, never promotional notifications.

OwnWise accesses images or documents when you choose files or capture a photo through your device's picker or camera. It saves attached copies in the app's local storage. Files are exported outside the app only when you choose a save, share, or export action. Original photos may contain metadata such as location information added by your camera; consider removing that metadata before sharing originals or backups.

Document capture uses Google's on-device document scanner to create a reviewed PDF. Native QR scanning uses Google Code Scanner. Google Play services may download the required scanner components and process technical diagnostics under Google's policies. OwnWise does not upload the captured document contents to its publisher. You can also choose existing files, use a QR photo or enter a pocket code manually.

Notification permission is requested at startup for warranty, registration, vehicle insurance/PUC, service, and optional purchase reminders. An optional next-service date produces a daily alert from 14 calendar days before the due date, including that date, and then daily while overdue until marked done. Reminder schedules and responses are stored on your device. Notifications may display item names or dates on your lock screen according to your device settings. Use Android Settings → Apps → OwnWise → Notifications to control alerts and lock-screen visibility. The purchase notification's “Don't ask me again” action stops purchase prompts while other enabled reminders continue.

Physical filing and QR labels

Pouch and leaf records store the names, numbers, private identifiers and selected item/document references that you enter. Printed QR labels contain a lookup identifier, not original document contents, and do not publish your collection. Scanning looks up local records; OwnWise does not open arbitrary scanned QR URLs. Anyone with access to an unlocked device and its collection may be able to see its filing locations. Replacing a label retires the previous code in that collection. Deleting a leaf removes its QR/location metadata while keeping digital products and originals. Existing printed labels and exported copies are not remotely erased.

Android's operating-system cloud backup and device-transfer backup are disabled. Full collection backups include saved items, original files, product photos, service/repair history, reminders, preferences and physical filing mappings/label identities. Unfinished drafts and the incoming inbox are excluded; save incoming files to an item before relying on a backup. Manual full .ownwise exports are encrypted on your device using your backup password. ZIP backups, exported originals, and PDF warranty claim packs have no OwnWise password. Claim packs include the selected original document contents plus any additional files you choose for that pack. Separate service and repair history PDFs include their record details and document contents, with exact original files embedded in the PDF as well. Those additional files are not automatically attached to the saved item. If you share exports, that service or recipient receives the information you select under its own terms and privacy practices. OwnWise does not automatically submit manufacturer registrations or warranty claims.

Google Drive backup uses only the drive.appdata permission: it can access OwnWise's private app-data folder, not your other Drive files. Production builds require Google connection and backup consent before entering the app. Once connected, the local collection also works offline. Closed-test builds retain optional Google connection in Profile and can be used locally without login. After you connect and allow backup access, OwnWise queues a new full ZIP backup after saved collection changes, including a new item or any document added to an existing item. Google receives your saved collection, original documents, product photos, filing mappings, account identifier, backup file names, sizes and upload timing under its own policies. These new Google copies have no separate OwnWise password. Google encrypts Drive data in transit and at rest; this is not OwnWise end-to-end encryption. No publisher-operated server receives the backup. This is backup after saves and recovery on another phone using the same Google account, rather than simultaneous collection synchronization between devices.

New automatic Google backups do not store a recovery password. When migrating from the earlier weekly password-based setup, the new setup removes its protected local password copy and cancels the weekly schedule; earlier encrypted Drive copies remain and require their original password to restore. Each new queued copy is staged separately in app-private storage and uploads when internet is available. A preparation failure preserves preceding copies. Network, power restrictions, force-stop, and account authorization can delay or prevent uploads. Backup settings distinguish waiting uploads from confirmed successful uploads. Drive versions consume your account storage. Disconnecting cancels pending uploads and removes staged phone copies, but retains existing Drive backups and account permission until you remove OwnWise access in Google settings. OwnWise displays up to 30 recent Drive versions for restoration.

Manufacturer links open only when you choose them. Those websites may receive normal browser information and any information you enter there, under their own privacy policies.

Retention, deletion, and your choices

Local records remain until you delete them, replace your collection during restore, clear the app's storage, or uninstall OwnWise. Uninstalling or clearing storage also removes local drafts and incoming files. Choosing Later for an incoming share keeps it in the local inbox. Deleting an item removes its associated records, attached copies and physical filing references from OwnWise. Exported files, printed labels, camera originals, or backups stored elsewhere remain until you delete those copies separately. Google-controlled diagnostic and purchase records follow Google's retention policies.

You can view and edit your records, export a full backup, and delete your local collection. We cannot access or recover your locally stored collection. Keep backups if you want to retain it when changing devices or reinstalling.

If you contact support, your email address and the information you voluntarily send are used to answer your request and resolve the issue. Email is processed by the email service provider. Please avoid sending invoices or other sensitive documents unless necessary. We retain support correspondence while needed to handle your request and follow-up, or where retention is required by applicable law. You may contact us to request deletion of support correspondence; we may retain information where legally required.

Security

Your collection is kept in the app's local storage and protected by Android's application isolation and your device security. Manual encrypted backups and earlier encrypted Drive copies use AES-256-GCM with a random salt and nonce and PBKDF2-HMAC-SHA256 (600,000 iterations); these still need their original password. New automatic Drive ZIP copies restore through the same Google account without a separate OwnWise password. Protect your device, Google account, any retained backup passwords, and exported documents. OwnWise cannot recover a forgotten password for an older encrypted copy.

Children

OwnWise is a general product-record organiser and is not designed specifically for children. It does not operate an online registration service for children. If you believe a child has sent personal information to support, contact us so we can address it.

Changes and contact

We may update this policy when OwnWise's features or data practices change. The effective date above identifies the current version. For privacy questions or requests, email kapoorashish213@gmail.com.