Wrenfold Labs

Keevan / Privacy policy

Document Vault: ID Card Wallet (Keevan) privacy policy

Who this policy covers
App on Google Play
Document Vault: ID Card Wallet
Name inside the app
Keevan
Store names in other languages
Porta Documentos Digital; Dokumentensafe: Ausweis-Wallet; Coffre-fort numérique & cartes; Simpan Dokumen & Kartu ID; Kimlik, Belge ve Kart Cüzdanı; 身分証・書類・カードの保管アプリ; 신분증·문서 보관함, 카드 지갑; حفظ الوثائق وبطاقات الهوية; डॉक्यूमेंट रखने वाला ऐप
Package name
com.siva.virtualWallet
Developer on Google Play
Wrenfold Labs
Developer's legal name
Malapati Sivakumar Reddy, Nellore, Andhra Pradesh, India
Contact
wrenfoldlabs@gmail.com

In this policy, "we" and "us" mean Wrenfold Labs, and "Keevan" means the app above.

This privacy policy explains what Keevan does and does not do with your information. Keevan works on your own phone, with no Keevan account and no server of ours. Your items leave your phone only when you choose to send them, and they never come to us. Please read this so you understand exactly what that means before you use the app.

What Keevan stores

Keevan stores photos, scans and files of your own cards, IDs, and documents, only what you choose to add yourself. You can sort each item into a category (Proof of Identity, Passport, Driver's License, Health/Insurance Card, Debit Card, Credit Card, or one you type in yourself, such as a family member's name), add a note, and add an expiry date so Keevan can remind you before it runs out. You can also save Private details: words and numbers you type, with no photo, such as a bank account's number and IFSC, a login, an insurance policy's number, or a Wi-Fi network's password.

Keevan also keeps the numbers it reads on your photos, such as an ID or card number, so you can copy them. If you add your signature for self-attested copies, Keevan keeps that too. Your signature stays on this phone only: backups never include it.

When you delete an item, it waits in Recently deleted for 30 days, so you can bring it back, and is then deleted permanently. You can also delete it permanently sooner. Items in Recently deleted aren't included in backups.

What Keevan does not collect

Keevan does not ask for a username, an email address, or a Keevan account. There is nothing to sign up for. Your photos, files, notes, and details stay on your own phone, encrypted. They leave it only when you choose: when you share, open, or print an item in another app, or back them up to a place you choose, such as your own Google Drive. None of it ever comes to us. Keevan does not track who you are or what you personally store. It does send anonymous crash and usage data to help find and fix bugs, and Google Play handles the one-time purchase that unlocks unlimited storage. Both are covered in full below.

Permissions Keevan requests

Keevan asks for three permissions, and explains why each one matters the moment it actually needs it:

  • Camera, to photograph a card or document when you choose to add one. Most phones scan with Google's document scanner (see Google Play below), which uses its own camera access instead; Keevan only asks for this permission on phones where that scanner isn't available.
  • Notifications, to remind you about an item that's expiring soon, to tell you if Emergency Backup could not keep your backup up to date, and for backup to Google Drive: at most once, to suggest turning it on, and if your latest changes haven't been backed up for 7 days.
  • Internet, used for four things: processing the one-time purchase that removes the free tier's saved-item limit, sending anonymous crash and usage data that helps find and fix bugs, the technical details Google's document scanner, code scanner, and text reader send about how they're working, and, only if you turn it on, backing up to and restoring from your own Google Drive. Your saved items go over the internet only inside that backup, locked with your password. See "Crash reports and app analytics", "Backup, restore, and Emergency Backup" and "Google Play and other Google services" below for the full detail.

Keevan does not request access to your photo gallery as a standing permission. When you pick an existing photo, Android's own Photo Picker hands Keevan only the specific photo you selected, nothing else.

Crash reports and app analytics

Keevan uses Google's Firebase Crashlytics and Firebase Analytics to catch bugs and see which parts of the app are actually being used, so real problems get fixed and real features get improved.

What this sends: technical details about what the app was doing when it crashed, and basic usage events, like which screen you opened, which category you tapped (a category you named yourself is sent only as "custom"), whether a save succeeded, the size range of a file you added (such as 1 to 5 MB), or that the one-time unlock was bought, with its price and currency. If you installed Keevan from a link someone shared from Keevan, it also notes which kind of link it was, such as the link on a PDF, never who shared it. This is tied to a random ID Firebase generates for your install of the app, not to you personally, and Keevan never adds your name or email to it.

What this never sends: any photo, file, card, ID, note, number Keevan read, detail you typed (such as an account number or a password), expiry date, name or label you typed, your signature, your Google account, your backup password, or the app PIN itself. None of your saved items, or anything inside them, are ever part of a crash report or an analytics event. This data is processed by Google under its own privacy terms, not this one, and you can see exactly what Keevan reports about itself in the Data Safety section of its Play Store listing.

How your data is protected

Every saved photo, file, note, and detail, the numbers Keevan reads, your signature, and your automatic backup password are encrypted using your phone's own hardware security chip (Android Keystore, with StrongBox hardware isolation on phones that support it), the same category of protection banking apps use.

Opening Keevan requires your phone's own lock (fingerprint, face, or PIN), the same one that protects the rest of your phone. You can also turn on, from Settings, entirely at your own choice:

  • A separate 6-digit app PIN, for a second lock on top of your phone's own.
  • An auto-lock timer that re-locks Keevan after it's been in the background for a while.
  • A setting that blocks screenshots and screen recording while Keevan is open. Show it big, which shows a hidden detail large, always blocks them; a saved Wi-Fi network's QR code always allows them, so you can send it to a guest.

Sharing, opening, and printing

When you share, open, or print an item, Keevan hands a copy to the app or printer you pick. What that app does with it is covered by its own privacy policy. Keevan deletes its own short-lived copy when you come back to Keevan.

Photos leave Keevan without their location or motion clip. Phone cameras can record where a photo was taken, and a motion photo carries a few seconds of video, so Keevan removes both from every photo it shares or opens in another app. The photo saved in Keevan, and its backups, keep them.

When another app shares a file with Keevan (Share, then Save to Keevan), Keevan receives only the files you picked, and keeps them encrypted. The original stays where it was.

Some things you send from Keevan carry a link to Keevan on Google Play: the small "Made with Keevan" mark on PDFs Keevan makes (not on files made to fit a form's upload box), a line added when you share only photos to WhatsApp or Gmail (you can delete it before you send), the Emergency Backup message, and Share Keevan in Settings. Each link carries a short tag naming the kind of link, such as "pdf_mark", so we can count how many people install Keevan from each kind. The tag never says who you are or who you sent it to.

Backup, restore, and Emergency Backup

You can create an encrypted backup file of your saved items at any time, protected by a password you choose. You decide where that file is saved. You can restore a backup on any device, including a new phone, by picking the file and entering its password. A backup holds your items with their notes and the numbers Keevan read, and whether the phone that made it had the one-time unlock, so restoring it on a new phone brings back every item.

Automatic backup to Google Drive is optional. If you turn it on, you choose a Google account on Google's own screen, and a password for your backups. Keevan then keeps a backup in that account's Google Drive, checking once a day and sending a new one only when something changed (on Wi-Fi only, if you choose). The backup is locked with your password on your phone, before it leaves, and goes straight to your Drive, never through us. Without that password, no one can open it, not Google and not us. Keevan can see only the files it made in your Drive, never your other files. A few details sit next to the file, outside the lock, so a new phone can show which backup is which: your phone's name, as set in your phone's settings, how many items the backup holds, and a random ID for this install of Keevan. Drive keeps the latest backup and the one before it. To restore on a new phone, choose the same Google account and enter the password.

Keevan keeps your backup password on your phone, encrypted, so it can make each day's backup, and forgets it when you turn automatic backup off. It also offers to save the password in your phone's password manager (Google Password Manager on most phones), so a new phone can fill it in. It's saved there only if you choose to. Turning automatic backup off stops it; the backup stays in your Drive until you delete it there.

Emergency Backup is optional, for one purpose: letting someone you trust open your documents if you can't. You can add their Google email: Keevan then keeps a copy of your vault in your own Google Drive, locked with a random password Keevan makes, shares that one file with them (they can open and download it, not change it), and updates it once a day when your vault has changed. Google emails them a link with Keevan's steps for opening it. The email never contains the password; you send it yourself. Or you can save the backup file somewhere you choose and send it yourself. Keevan keeps the person's email and the name on their Google account only on your phone. It gives the email to Google only to share the file, and never sends it to Keevan's analytics or crash reports. Every Emergency Backup also carries the name on your own Google account, when Keevan knows it, so the person you add can see whose documents and details they are.

Important: the person you add can open your latest documents at any time, not only in an emergency, until you remove them. Removing them, or turning Emergency Backup off, deletes their copy from your Google Drive, so the link stops working. A copy they already downloaded, or a file you sent them, can't be taken back. Treat it the same way you would a spare physical key.

What Keevan does in the background

Keevan does up to three things in the background without you tapping something first, each about once a day:

  • It checks your expiry dates, to remind you before an item runs out.
  • If Emergency Backup is on, it rewrites that backup file at the place you chose, and sends a new version of the copy shared with the person you added, only when your vault has changed.
  • If automatic backup is on, it sends a new backup to your own Google Drive, only when your vault has changed.

Keevan never sends your items anywhere you haven't chosen.

Google Play and other Google services

Keevan uses these Google services, all handled by Google's own systems, not by Keevan itself:

  • Processing the one-time purchase that removes the free tier's saved-item limit. Your payment details are handled entirely by Google Play; Keevan never sees or stores them.
  • Now and then, after something you did in Keevan worked, such as sharing a PDF or restoring a backup, asking Google Play to show its own rating card. Keevan asks at most once every 90 days, and Google decides whether the card appears. "Help Keevan grow" in Settings only opens Keevan's page on Google Play.
  • Scanning a document when you tap "Scan with camera". This uses Google's own document scanner, part of Google Play services on your phone. The scan happens on your phone, and the photo goes straight back to Keevan, which encrypts it; it is not sent to Google. Google's scanner code, both inside Keevan and in Google Play services, may send Google technical details about the scanner, never the image: your phone's model and Android version, the app's version, how long a scan took, the image's size and format, and an ID for your phone. Google uses these to check how well the scanner works and to fix problems with it.
  • Reading a Wi-Fi network's QR code when you tap "Scan the Wi-Fi QR code". This uses Google's own code scanner, part of Google Play services on your phone. The scan happens on your phone, and only the network's name, password, and security come back to Keevan, which encrypts them; the camera image is not sent to Google. Like the document scanner, Google's code may send Google technical details about how the scanner is working, never the image.
  • Reading the numbers and expiry dates on your photos. This uses Google's text reader (ML Kit text recognition), which runs inside Keevan on your phone: your photos, and the text it reads, never leave your phone. Like the scanner, it may send Google technical details about how it's working, never the image or the text: your phone's model and Android version, the app's version, how long a reading took, the image's size, error codes, and an ID for this install of Keevan that isn't meant to identify you or your phone. Google uses these to check how well the reader works and to fix problems with it.
  • Google's own sign-in screens, if you turn on automatic backup or add someone to Emergency Backup. You pick the Google account there. Google then lets Keevan use that account's Drive for Keevan's own backup files only, and tells Keevan the account's email address and the name on it. Both stay on your phone: the email so Keevan can show where your backups go, and the name so an Emergency Backup can say whose it is.

All of these are covered by Google's own privacy policy, not this one.

Children's privacy

Keevan does not knowingly collect personal information from anyone, including children, because it never asks anyone, of any age, to identify themselves to us. There is no Keevan account and no server of ours, so there is no mechanism for Keevan to collect personal information from a child, or from anyone else.

Confirming this yourself

You do not have to take this policy's word for it. Android's own Data Safety section for Keevan on the Play Store listing, and independent tools like Exodus Privacy, let you check exactly what permissions and trackers an app actually has.

Changes to this policy

If Keevan's features change in a way that affects your data, this page will be updated, and the date at the top will change.

Contact us

Questions, concerns, or feedback about this policy can be sent to Wrenfold Labs at wrenfoldlabs@gmail.com.