Bhalanetra Labs / OwnWise

OwnWise Privacy Policy

Updated: 12 November 2026

OwnWise is developed and published by Bhalanetra Labs. 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. Your local profile is independent of your Google account and does not create a cloud collection. Optional Google sign-in is used for private Drive backup and online trial or purchase verification as explained below. We do not sell your collection or use it for advertising.

Personal identification documents (My IDs)

Versions with My IDs let you store photos of your own government IDs, driving licences, voter IDs, PAN cards, passports and other licences. You choose a title, document type and up to four camera or library photos per document, with a limit of 20 documents. This optional feature does not verify your identity, confirm government approval, extract text, or request your ID number or date of birth separately. Photos are processed on your device. OwnWise does not send these photos or titles to a publisher-operated server, analytics, advertising, online OCR or AI.

In version 0.6.4 and later, My IDs uses your Android screen lock. Supported Android devices can use a strong fingerprint or face biometric. The Android PIN, pattern or password is also available, and older Android versions use the screen lock credential. OwnWise does not receive your biometric data or Android screen lock credential. The Android Keystore protects a key used to unlock the separately encrypted vault on that phone. My IDs locks when you leave the screen, after two minutes of inactivity, or after 30 seconds away. A camera session can remain open for up to two minutes. The Android app blocks ordinary screenshots and screen recording on the My IDs screen.

Review the storage notice before creating My IDs or switching an older vault to device unlock. Enter the original My IDs password once to switch an existing vault. Versions before 0.6.4 use that password for routine access. Saved titles, types and photos stay encrypted. In versions with ID expiry alerts you can add an optional expiry date and reminder lead time, which are encrypted with the document. To show renewal alerts while My IDs is locked, the app keeps a separate schedule of each document type and expiry date on this device only. That schedule is excluded from backups and removed when the vault changes or is deleted. Where Scan with camera is available, Google Play services opens its on-device scanner to detect document edges and let you review the crop. OwnWise receives the cropped image after you confirm it. Google Play services may download scanner components and process technical diagnostics as described below. Earlier versions that offer Take photo use the Android camera and a temporary app-cache file that OwnWise deletes after capture or cancellation or clears at the next launch. The device camera app may manage its own copies. Scanned or selected photos are resized and re-encoded as JPEG to remove original metadata including location. They are stored in My IDs when you save the document.

Full collection backups include the encrypted My IDs vault. When private Google Drive backup is enabled, ID changes queue the encrypted vault under the existing six-copy rule. The phone's unlock key is excluded from backups. Keep the generated My IDs backup recovery key somewhere private and separate from backups. It can recover IDs if you change phones, reinstall or lose access to the original device lock. OwnWise cannot recover the key for you. Older ID backups still need the password used before switching. Different locked vaults cannot merge automatically. Save a recovery backup before choosing a replacement restore.

You can review selected photos and choose to save or share a compressed PDF with one photo per page or a single combined JPG. Each file is smaller than 300,000 bytes. Compression may reduce clarity, so check every page. Exported copies are unencrypted and leave the vault. Your chosen recipient, service or save location receives the selected information under its own practices. Share only what is needed and prefer a masked Aadhaar where appropriate. OwnWise does not create public links or automatically submit these copies. Temporary app-cache files are removed after a save or share attempt; an interruption can leave app-private cache until cleanup.

Delete an ID inside My IDs to remove it from this device and future backups. Earlier backups, other devices and exported copies remain until separately deleted or pruned. The collection and profile deletion controls also remove the local vault. Authenticated connected-copy deletion removes recognized OwnWise backups in the connected Drive account. Device-only deletion leaves those backups intact. Keep ID copies only while needed and protect your device, backup recovery key or original password, Google account and exported files.

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 sends purchase tokens and verification data from the native app to its online verification service, which checks and acknowledges purchases with Google Play to enable paid features and restore access. 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 or an OwnWise profile does not cancel a subscription. Closed-testing builds may provide temporary feature access without requiring a purchase.

Skip for now opens Free local use. An eligible 10-day Pro trial requires Google sign-in and online eligibility verification, without payment details or automatic billing. Free and the trial both support at most 3 items. Native trial dates and the server's immutable eligibility record are separate from collection backups; restoring or deleting collection data does not restart a trial. Existing records, originals and the selected theme remain after access ends. Verified paid Pro supports more items. Pro is available as a yearly subscription or one-time lifetime purchase. Google Play displays the local price and payment terms before checkout. Lifetime Pro does not cancel an existing yearly subscription; manage renewal in Google Play. The native app uses the Play billing country to check the displayed price, not for marketing.

Online trial and purchase verification

When you sign in for a trial, verify or restore a purchase, or use authenticated account deletion, Bhalanetra Labs' verification service receives your Google identity token or an OwnWise session token, installation identifier, app/package version, request timestamps, Google Play Integrity token and verdicts, trial eligibility information and, when applicable, purchase tokens, product identifiers and purchase status. A Google identity token can include your Google account identifier, verified email address and profile name. The service uses the account identifier to derive a pseudonymous identifier; it does not store your Google email or name in its entitlement database. Your local profile name, collection, original documents and photos are not sent to this service.

The information is used for account authentication, trial eligibility, fraud prevention, receipt ownership, purchase acknowledgement and restoration, and access revocation. Cloudflare Workers processes requests and private Cloudflare D1 stores entitlement records; Google provides identity, Play Billing/Developer API and Play Integrity verification. Data may be processed in countries where these providers operate. The D1 database was provisioned in the Asia-Pacific region. These providers process information under their own terms and privacy policies. See Cloudflare's Privacy Policy and Google's Privacy Policy.

The service stores pseudonymous trial start/end dates, hashed receipt ownership and purchase state, temporary session records and, if purchase verification needs a retry, an encrypted purchase token. Sessions expire after 7 days, replay-protection hashes after 3 minutes and rate-limit records after about an hour. Encrypted receipt retries expire after 5 days or are removed after successful acknowledgement. Expired temporary rows are removed by scheduled, bounded cleanup, which can take longer during an outage or backlog. Request-body and invocation logging are disabled in the OwnWise service; hosting and Google providers may process ordinary connection and security metadata under their policies.

Minimal pseudonymous trial dates and hashed receipt ownership have no automatic expiry, including after profile deletion. They are retained to prevent repeated trial activation or purchase reuse across accounts and to preserve purchase restoration; they are not used for advertising. They do not contain your collection or original files. Trial proof requires an online recheck at least daily, and the current paid-access proof is short-lived (up to 15 minutes). Verification or connectivity failure does not delete saved records or original files, but may temporarily restrict Pro actions until access can be verified.

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, return-window, claim follow-up, ID renewal and optional purchase reminders. ID renewal alerts name only the document type and expiry date, never the saved title, document number or photo. 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.

Backups, sharing, and external websites

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, physical filing mappings/label identities, and the separately encrypted My IDs vault when used. 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. Google sign-in is optional for local use. Choose Skip for now on the welcome page to continue locally. In version 0.6.2 and later, before enabling automatic backup from welcome or Profile → Backup & restore, OwnWise shows what is uploaded, how copies are protected and the six-copy retention rule. Select Enable automatic backup to authorize it, then complete Google Drive authorization. Not now leaves uploads disabled. Existing enabled backups retain their current behavior. The local collection also works offline. 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. OwnWise keeps the 6 newest completed Google backup versions, counting both ZIP and older encrypted copies. After a new full upload is confirmed, older recognized OwnWise backups are permanently deleted from its private Drive folder. Cleanup reads every listing page first and retries separately if it cannot finish; failed or waiting uploads do not trigger deletion. Extra older copies can remain temporarily while cleanup is pending. Your local collection, pending uploads, unrelated Drive files and manual exports are not removed. 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. The retained copies remain available for restoration; older encrypted copies need their original password.

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.

In Profile → Privacy and data, Delete all user data removes this device's collection, originals, drafts, incoming inbox, pouch mappings and reminders, and pauses/disconnects automatic backup. It keeps your local profile name and remote/manual recovery copies. Delete profile and all data offers a destination choice in version 0.6.2 and later. This device only removes the local profile and collection and disconnects local Google sessions without Google sign-in or a network request; remote backups and verification records remain. This device and connected copies also removes recognized OwnWise backups from the connected Google Drive account and the authenticated service's session and encrypted retry records. That remote choice requires online authorization; a remote failure must be resolved before local erasure completes. Earlier versions may require online authorization for the combined profile-deletion option; local collection erasure and Android storage controls remain available. Other devices, manual exports, unrelated Drive files and Google-held purchase records are managed separately. Native trial dates and minimal server trial/receipt ownership records remain as described above.

To request deletion or ask about retained data without using the app, follow OwnWise deletion instructions or email kapoorashish213@gmail.com with the subject OwnWise data deletion. We may need to verify account ownership before acting. Never send a password, sign-in code, purchase token or payment-card details. We cannot remotely access or erase a local-only collection, manual exports or your private Drive files; the instructions explain how to remove those copies. Support correspondence may be retained where needed to handle the request or meet legal obligations.

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.