Privacy at a glance
- Backup and restore content is processed locally and is not uploaded to BinaryPaper.
- By default, accepted scan progress is encrypted and saved in private storage on the Android device so an interrupted restore can continue. You can turn this off and keep scan progress in memory only.
- Core backup and recovery workflows work offline.
- The Play-distributed app communicates with Google Play for optional PRO purchases.
- Files or messages leave the app only through an action you choose, such as Save, Share, Open with, Print, or contacting support.
- BinaryPaper does not use advertising, analytics, or crash-reporting SDKs in the app.
1. Scope and developer
This policy applies to the BinaryPaper Android app and the public website at binarypaper.app. BinaryPaper turns selected files or text into printable QR-code backups and restores compatible backups by scanning those codes.
BinaryPaper is developed and operated by Vadym Miakishev. Questions about this policy can be sent to support@binarypaper.app.
2. Information processed on your device
The app accesses information only when needed for features you use. The following processing takes place on your Android device and is not sent to BinaryPaper.
Files, text, passwords, and backup payloads
When you create a backup, the app reads the files, folders, file names, directory structure, or text note you select. It packages that content, optionally compresses and encrypts it with the password you provide, adds recovery data, and generates a printable PDF. When you restore a backup, it performs the reverse process locally. Passwords are used for encryption or decryption during the active workflow and are not sent to us or stored as an account credential.
If you create a backup without a password, its content is not protected by BinaryPaper encryption. Anyone who obtains enough readable QR codes may be able to restore it.
Camera frames and scanned QR codes
Camera access is used to find and decode BinaryPaper QR codes. Camera frames are analyzed in memory; the app does not take or keep camera photos or video.
By default, after the app validates and accepts a unique QR code, it saves the compact decoded symbol payload in one encrypted, app-private scan checkpoint. This checkpoint lets one unfinished scan survive switching apps, returning to the BinaryPaper landing screen, removal from Recents, process failure or reclamation, force-stop, reboot after the device is unlocked, and an app update that preserves application data. Pressing Home or Back does not silently discard it.
The checkpoint can contain encrypted backup data or, for a no-password backup, unencrypted backup data from the printed capsule. It does not store camera photos or video, raw camera frames, passwords, extracted files, duplicate QR payloads, or filenames and restored-content metadata as separate fields. The checkpoint is stored only on the Android device and is never uploaded, synced, exported, shared with BinaryPaper or another party, or included in Android cloud backup or device transfer.
Save scan progress is enabled by default. You can turn it off in Settings after confirming that choice. Turning it off deletes the saved checkpoint and its encryption key; accepted codes already in the current session may remain in memory only. In memory-only mode, closing the app, process death, force-stop, reboot, or an app update that ends the process loses the unfinished scan and requires rescanning. Turning saving back on creates an encrypted checkpoint for the current scan before the app represents that cold resume is available.
Generated and restored files
Generated backup PDFs, density-test PDFs, restored files, and temporary share bundles may be held in app-private storage while the relevant workflow is available. A new generated backup replaces the previous app-private generated backup. Restored content is replaced or removed when you start over, discard or close the restore, or begin another restore. Some app-private generated files may remain until replaced, app data is cleared, or the app is uninstalled.
Settings, calibration, and verification records
The app stores local settings and operational records, which may include:
- language, theme, vibration, help-screen, and scan-progress-saving preferences;
- a local Boolean recording whether Google Play reports that PRO is owned;
- pending backup-verification references, consisting of a capsule identifier and time;
- calibration profiles, including paper and print settings, calibration observations, names you give printers or scanners, opaque profile identifiers, and timestamps; and
- the Android device identifier used as a local stable identity for a current-device calibration profile.
The Android device identifier and calibration records stay on the device. BinaryPaper does not use them to track you across apps or send them to a BinaryPaper service.
Scoped document access and local diagnostics
Android's document picker grants the app access only to files, folders, and destinations you select. Android may retain that scoped permission so the app can complete a backup, revisit a chosen destination, or delete a verification copy you asked it to track. The app also writes local technical log messages about scanner state, counts, failures, and component operation. It does not automatically upload those logs. Technical details are shared only if you deliberately include them in a support request.
3. Google Play and optional PRO purchases
The Play-distributed app uses Google Play Billing to load PRO product information, start a purchase, check purchase state, restore ownership, and acknowledge a completed purchase. These operations communicate with Google Play and may involve purchase history, product identifiers, purchase state, a purchase token, and information Google uses to operate and secure its billing service.
BinaryPaper does not receive your full payment-card details. The current app does not send purchase tokens to a BinaryPaper backend and does not attach a BinaryPaper account identifier to the billing flow. It stores only the resulting PRO-owned state locally so eligible features can remain available offline. Google's handling of billing data is governed by the Google Privacy Policy and Google Play terms.
4. When you choose to send or save information elsewhere
BinaryPaper uses Android system interfaces for actions you initiate. The destination you choose then handles the information under its own terms and privacy practices.
- Save: copies a generated PDF or restored content to the document provider, folder, removable storage, or cloud-backed location you select.
- Share: gives the recipient app temporary read access to the generated PDF, restored file, or share bundle you choose.
- Open with: gives the app you select access to the chosen restored file.
- Print: sends the generated PDF to Android's print service and the printer or print provider you select.
- Contact support: sends the message, attachments, and technical details you choose through your email provider.
Copies saved or sent outside BinaryPaper are not deleted when BinaryPaper's app data is cleared or the app is uninstalled. Manage those copies in the destination app or storage provider.
5. Website data
The BinaryPaper website is a static site hosted by Cloudflare. Cloudflare necessarily processes network and request information, such as IP address, request headers, time, requested URL, and security signals, to deliver and protect the site. Cloudflare acts under its own privacy policy and applicable service terms.
BinaryPaper does not enable Cloudflare Web Analytics, embed another browser-analytics service, or create its own visitor profile on this website. Cloudflare may make aggregated edge traffic, security metrics, and short-lived operational request information available to the site operator. We use that information only where needed to deliver, protect, and troubleshoot the site.
The site content does not set cookies. Cloudflare may use strictly necessary cookies if required to provide or protect its service under its privacy policy; BinaryPaper does not configure advertising or analytics cookies. The site does not accept payments, comments, or form submissions. If that changes, this policy will be updated before the new behavior is enabled.
BinaryPaper does not sell or rent personal information, and it does not use app, website, or correspondence data for advertising or unrelated profiling.
6. Support and privacy correspondence
When you contact BinaryPaper for technical support, privacy inquiries, purchase assistance, or another request, we may process the information you provide, including your email address, name, message content, attachments, and relevant technical information.
We use this information to respond, investigate and resolve issues, maintain the security and reliability of BinaryPaper, and comply with applicable legal obligations. Messages sent to support@binarypaper.app are routed by Cloudflare Email Routing to a Gmail mailbox. Cloudflare and Google may therefore process message content and delivery metadata as service providers under their respective terms and privacy policies.
7. Retention and deletion
Data on your device
- Saved scan checkpoint: one unfinished scan is kept without an automatic expiry. It remains through Home, Back, process death or reclamation, removal from Recents, force-stop, reboot, app update, password retries, recovery, and output review. It is deleted when you choose Start over or Discard saved scan, confirm replacement by another capsule, confirm a switch to memory-only scanning, finish a successful restoration and choose Done, clear BinaryPaper app data, or uninstall the app. Saving or sharing restored output before Done does not delete the checkpoint.
- Memory-only scan progress: held only in the current app process and lost when that process ends. Turning memory-only mode on deletes the existing saved checkpoint and its key.
- Restored content: kept in app-private storage until the associated reset, discard, close, replacement, app-data clear, or uninstall action removes it.
- Generated PDFs: kept in app-private storage until replaced, app data is cleared, or the app is uninstalled. Copies you save, share, or print are controlled by their destination.
- Calibration profiles: kept until you delete the profile, clear app data, or uninstall the app.
- Preferences, pending-verification records, document permissions, and local PRO state: kept until changed or cleared by the relevant app or Android action, or until app data is cleared or the app is uninstalled.
Clearing BinaryPaper's app data or uninstalling it removes its app-private files, settings, and saved scan checkpoint under Android's control. It does not remove copies previously saved to another location or sent to another app.
Support and privacy correspondence
Correspondence is ordinarily retained for up to 24 months after the request is resolved or the last communication, whichever is later. It may be retained longer where reasonably necessary to comply with legal obligations, prevent fraud or abuse, establish or defend legal claims, or resolve an ongoing dispute.
After the applicable retention period, correspondence is deleted or anonymized. You may request deletion by contacting support@binarypaper.app. Certain information may be retained where continued retention is required or permitted by law.
8. Security
BinaryPaper limits access to the data needed for the feature you choose. App working files are stored in Android app-private storage, Android backup of BinaryPaper app data is disabled, and external apps receive only scoped access for user-initiated actions.
Every saved scan checkpoint uses a fresh AES-256-GCM key generated inside Android Keystore. The key material is non-exportable, and hardware-backed key storage is used when the device provides it. Checkpoint records are authenticated as well as encrypted and are kept in Android's credential-encrypted, app-private no-backup storage. The checkpoint and its key are never included in Android cloud backup or device transfer. When a checkpoint is deleted, the app deletes its Keystore key before removing the checkpoint file so a stale file is not decryptable through a still-live app key.
Checkpoint encryption protects saved scan progress on the Android device even when the printed backup has no password. It does not add password protection to the printed QR codes themselves. Password-protected backup payloads use authenticated encryption before they are encoded into QR codes. A no-password printed backup and a restored plaintext file do not have that protection.
No system can guarantee absolute security. A person who fully compromises the running device or BinaryPaper process may be able to access live data or ask the device to use an available Keystore key. Protect your device, use a strong and unique backup password where appropriate, store printed pages safely, and review the security and privacy of destinations before saving or sharing content.
9. Children's privacy
BinaryPaper is a general-purpose backup utility and is not directed to children. We do not knowingly collect children's personal information through the app or website. If a parent or guardian believes a child has sent personal information in correspondence, contact us so the request can be reviewed and the information deleted where required.
10. Your choices and privacy requests
You control the principal data handled by BinaryPaper. You can:
- deny or revoke Camera permission, understanding that scanning will not work without it;
- turn off Save scan progress, which deletes the encrypted saved checkpoint and keeps the unfinished scan in memory only while the app process remains alive;
- resume or explicitly discard a saved unfinished scan;
- choose which documents, folders, save destinations, print services, and recipient apps are used;
- start over or finish a successful restoration with Done to clear the associated saved scan checkpoint;
- delete individual calibration profiles;
- clear all BinaryPaper app data through Android Settings or uninstall the app; and
- ask to access, correct, or delete information contained in support or privacy correspondence, subject to applicable law.
11. Changes to this policy
Updates will be published at this same URL and identified by a new “Last updated” date. Material changes to data handling will be reflected here before the changed behavior is released.
Future BinaryPaper accounts, backend services, analytics, advertising, additional production SDKs, or new data-sharing behavior require this policy and the Google Play Data safety declaration to be reviewed and updated before they ship.
12. Contact
For privacy questions, support requests, or correspondence-deletion requests, contact:
Vadym MiakishevBinaryPaper
support@binarypaper.app