Effective date: 12 October 2026
SWIP is published by ARMYS Designlabs, a brand of VRUKSHAROOP TECHLABS (OPC) PRIVATE LIMITED (“we”, “us” or “our”), based in Mumbai, Maharashtra, India.
This Privacy Policy explains how the SWIP app handles information, what information stays on your device, what information may be sent to third parties, and the choices available to you.
Privacy policy URL: https://www.vruksharoop.site/privacy
Contact: support.armysdesignlabs@gmail.com
SWIP has no account system of our own, no servers of our own, no analytics of our own and no advertising.
Your captures are stored on your phone and nowhere else that we control. We never receive your captured history, so we cannot sell, share or lose that history.
If you choose to sign in with Google and enable cloud backup, an encrypted copy can also be stored in your own Google Drive. It can only be unlocked using your recovery words.
If you enable automatic problem reports or usage statistics—both of which are off by default—we receive limited technical reports about failures and counts describing how the app is used. These reports are designed not to contain the information you capture.
Some information may leave your phone through Google components that SWIP uses, or through services and actions you explicitly choose to enable. Every such instance is described in this policy.
When you scan a shop’s QR code or tap a card terminal, SWIP saves a record in a database inside the app’s private storage.
Depending on what the QR code or terminal provides, a record may contain:
Merchant information: The shop’s Merchant Category Code (MCC), name, city and country, where available, and its payment address, such as a UPI ID.
Transaction information: The amount and currency, if included in the scanned code or terminal data.
Date and time: When the capture took place.
QR code content: The text of the code itself.
Card label: Which of your cards you say you used. This is a label you choose; SWIP never asks for or stores your card number.
Your corrections: A shop name or category code you enter to correct a capture. Your correction is stored alongside the information SWIP originally read, not in place of it, and is displayed in a different colour so the two are distinguishable.
Privacy consent: Which version of this policy you agreed to and when you agreed to it.
SWIP also stores your app settings and the information it has learned about shops you have scanned before.
SWIP keeps a short technical log on your phone so you can investigate problems and, if you choose, send us a report.
The log records technical events such as:
Whether the camera started and, if it did not, the error it returned.
Whether a code was read and what type of code it was.
Which steps of a card-terminal tap took place and where the process stopped.
Errors that occurred inside the app.
When a capture was saved, which capture route was used and whether a category was present—never the category itself.
Whether a backup or restore operation succeeded.
Changes you made to settings.
Your phone’s model, Android version and the way SWIP last closed.
You can view the log as a timeline in Settings → Super black box → Technical.
The log does not contain the codes you scan, payment addresses, shop names, amounts, place names or your capture history. Older entries are deleted as new ones are written.
The log leaves your phone only when you export it yourself or when an automatic problem report is sent, if you have enabled that feature.
SWIP includes a list of shops and their category codes built into the app.
SWIP reads this list locally to fill in a merchant category or name that was not included in a code. Information filled in this way is displayed in a different colour and labelled with its source.
Reading this list does not send anything anywhere.
When you tap a card terminal, SWIP also reads the information provided by the terminal itself. This may include:
Merchant Category Code (MCC).
Merchant and terminal numbers.
Merchant name.
Transaction amount.
Terminal clock information.
Country.
Bank identifier.
Machine serial number.
These fields describe the shop’s payment terminal and its transaction data, rather than being personal identifiers about you.
SWIP uses Google ML Kit to read QR codes. QR scanning is processed on your phone.
ML Kit sends Google certain diagnostic and usage information to help maintain the service. This may include your device model, operating system version, app version, performance measurements and an identifier that Google says is not intended to identify you or your device.
ML Kit does not send the QR codes you scan or camera images through this diagnostic process.
Google’s Privacy Policy: https://policies.google.com/privacy
If you grant location permission, SWIP can use your phone’s built-in geocoding service to turn your approximate position into a place name.
This process may send coordinates to Google.
You can refuse location permission. SWIP continues to work without it.
Merchant-name lookup is off unless you choose to enable it.
If you enter your own Razorpay API key in Settings, SWIP can send a scanned shop’s payment address to Razorpay to look up the shop’s registered name.
SWIP does not send additional information about you for this lookup.
Razorpay’s Privacy Policy: https://razorpay.com/privacy/
SWIP costs ₹99 as a one-time purchase and has no in-app purchases.
Google Play processes the payment. Through Google’s sales reports, we receive the order number, price, purchase date, and the buyer’s country, state and postal code, which Google provides for tax purposes.
We do not receive your name, email address or payment details through these reports. We also do not link a Google Play order to information stored inside SWIP on your phone.
The following actions occur only when you explicitly choose them:
Exporting or backing up your history: You choose to create or export a file containing your data.
Share your shops: Creates a file containing shop names and category codes, which you can review line by line first. It excludes transaction amounts, dates, places and personal UPI IDs.
Wrong? Help fix it: If you correct a shop and leave Also send it to SWIP’s shop list switched on, SWIP hands a single line containing the shop’s name and category code to the app you choose. It does not include details about your visit.
Continue payment: Hands the code to the payment app you select.
Support link: Opens a payment page in your browser.
Export a problem report: In Settings → Super black box → Technical, you can export the technical log as a file that you can read before sending it.
An exported file is never sent automatically. Automatic problem reports are a separate feature and can be switched off.
When something fails in SWIP—for example, the camera does not start, a card-terminal tap stops before completion, a hand-off from another app fails, or the app crashes—SWIP can send a technical report to us through Google Firebase Crashlytics.
If you enable automatic problem reports, the report may contain:
The error and where it occurred in SWIP’s code.
The technical log events described in Section 2.2 since the previous report.
Your phone’s model, Android version and SWIP version.
An identifier Firebase creates for that installation of SWIP.
SWIP sends at most one report every six hours, and only after something has failed.
Reports do not contain the QR codes you scan, payment addresses, shop names, amounts, places or your capture history. Any information in an error message that could identify a person or shop is removed before the report is sent.
Automatic problem reports are off until you enable them on the agreement screen. You can change your choice at any time in Settings → Super black box → Technical → Send problem reports automatically.
Firebase retains crash data for 90 days.
Google Firebase privacy information: https://firebase.google.com/support/privacy
SWIP can count how its features are used through Google Analytics for Firebase.
If you enable usage statistics, the information sent may include:
When the scanner opens.
Whether the camera starts.
Whether a code is read and the type of code read, such as a UPI code from a Paytm sticker with no category.
How a hand-off from another app ends.
How long individual operations take.
This information may be accompanied by your phone’s model, Android version, SWIP version, approximate country and an identifier Analytics creates for that installation.
Usage statistics do not contain the codes you scan, payment addresses, shop names, amounts, places or your capture history. SWIP does not collect the advertising ID.
We use these statistics only to understand what needs to be fixed or improved. They are not used for advertising and are not sold.
Usage statistics are off until you enable them on the agreement screen. You can change your choice at any time in Settings → Super black box → Technical → Share usage statistics.
Google Analytics retains this data for 14 months.
You can sign in with your Google account in Settings → Your Google account.
When you sign in, Google provides SWIP with your email address and name. SWIP stores these details on your phone only to show which account is signed in. They are not sent to us or added to SWIP’s problem reports or usage statistics.
If you also enable Keep a locked copy in my Google Drive, SWIP stores an encrypted backup in a hidden SWIP folder in your own Google Drive.
The backup contains the same data as the encrypted backup created using SWIP’s backup feature: your captures, linked shops, certain settings and your SWIP ID.
Important details about this backup:
The backup counts towards your Google Drive storage.
SWIP cannot access any other files in your Google Drive.
The backup can be opened only with your twelve recovery words.
Google stores the encrypted file but cannot read its contents, according to the backup design described here.
We never receive the backup.
When you leave the app, SWIP creates a new backup if something has changed. It checks that Drive stored exactly what was sent before removing older copies.
SWIP normally retains the newest two copies. It also retains the largest older copy when the newest backup contains fewer captures, allowing you to recover from certain mistaken deletions. There can be up to three backup files.
To remove your Drive backup and disconnect the account, use Settings → Your Google account → Remove my copy and disconnect. This deletes every SWIP backup copy from your Drive and withdraws SWIP’s access. You can also remove SWIP’s access through Google Drive under Settings → Manage apps.
Google’s Privacy Policy: https://policies.google.com/privacy
SWIP is designed to keep your capture history under your control.
SWIP:
Does not read the screens, messages, contacts, photos or SMS of other apps.
Does not use an accessibility service.
Does not track you across apps or websites.
Does not sell or rent information.
Does not contain advertising.
These statements are subject to the specific third-party data flows described in Section 3.
The first time you open SWIP, the app displays information about its data practices and asks you to agree before the camera or any other feature starts.
Nothing is collected until you tap I agree.
SWIP records on your phone which version of this policy you agreed to and when.
You can read this policy at any time in Settings → Privacy policy and withdraw your agreement there. If you withdraw your agreement, SWIP stops and asks you to agree again before it runs.
Withdrawing your agreement does not delete your existing history. To remove it, use Settings → Delete everything.
SWIP requests permissions to provide specific features. Some are optional; SWIP continues to work without optional permissions where the corresponding feature is not needed.
Permission
Why it is used
Camera
To read QR codes. Images are processed on your phone and are not saved.
NFC
To read a card terminal when you tap your phone on it.
Approximate location
To add a place name to a capture. This permission is optional.
Display over other apps
To show the floating button you can enable to open the scanner over another app.
Notifications
To show the notification Android requires while the floating button is running.
Run at startup
To restore the floating button after a restart, if you had it enabled.
Internet
To support optional merchant-name lookup, enabled problem reports and usage statistics, Google sign-in, and Google Drive backup.
You remain in control of optional permissions and features through your device settings and SWIP’s settings.
Your capture history remains on your phone until you delete it.
Settings → Delete everything removes all captures and everything SWIP has learned.
Uninstalling SWIP also removes its local data.
An encrypted backup that you export is protected by a phrase known only to you. The file remains wherever you choose to save it.
Besides your captures, it contains the shops you linked, certain settings—such as your theme and which guides you have already seen—and a random SWIP ID generated on your phone to associate your backups.
The SWIP ID is not linked to your name, phone number or Google account. It leaves your phone only inside that encrypted backup file.
SWIP disables Android’s automatic backup to Google Drive. Therefore, your SWIP history is not copied into your Google account through Android’s automatic backup mechanism.
A Google Drive backup is created only if you sign in and enable the separate encrypted backup feature described in Section 3.8.
If you move to a new phone using Android’s phone-to-phone transfer over a cable or direct wireless connection, on Android 12 and later, your history can transfer with your other apps directly from your old phone to your new one. This transfer does not pass through us.
We do not receive or store your capture history, so we have no copy of that history to delete.
If you created a Google Drive backup, use Settings → Your Google account → Remove my copy and disconnect to remove it and disconnect SWIP.
For information handled by the Google components described in this policy, please refer to Google’s Privacy Policy and the relevant Google service documentation.
SWIP stores your history in the app’s private storage, which other apps cannot read under the platform’s normal security model.
Backups are encrypted using AES-GCM, with a key derived from your backup phrase.
Everything SWIP sends over the internet uses HTTPS.
You should keep your recovery words or backup phrase secure. Anyone who obtains the required recovery information may be able to access a backup.
SWIP is intended for adults who hold payment cards and is not directed at children under the age of 18.
If this Privacy Policy changes, we will update this page and its effective date.
If SWIP begins collecting information in a new way, this policy will describe the change before the app version that introduces it is released. SWIP will ask you to agree again before continuing.
For questions about this Privacy Policy or SWIP’s handling of information, contact:
VRUKSHAROOP TECHLABS (OPC) PRIVATE LIMITED
Trading as ARMYS Designlabs
Mumbai, Maharashtra, India
Email: support.armysdesignlabs@gmail.com
Privacy policy: https://www.vruksharoop.site/privacy
Last updated: 12 October 2026