Privacy policy

Receipt Ledger / Чеки / 收据通 · com.yltech.shoujutong
Updated: 4 November 2026 · YLTech

Your receipt data

No account is required. Receipts, amounts, stores, item and price history, photos, categories, budgets, drafts and preferences are stored on your device. We do not operate a server that stores your receipt database. QR decoding and OCR process images on the device using bundled ML Kit models; input images and recognition results are not sent to Google.

Advertising and SDKs by distribution

Google distribution: Google AdMob displays adaptive banners on the main tabs and occasional interstitials after completed receipt tasks. AdMob collects and shares IP addresses (used for approximate location), ad interactions, diagnostics and device/account identifiers such as the advertising ID, for advertising, analytics and fraud prevention. AdMob requests begin only when Google UMP reports that ads may be requested. Where required, a consent form is shown and Settings provides Ad privacy options to revisit your choice. Receipt contents and photos are not passed to AdMob. The Google distribution does not include Yandex Mobile Ads, AppMetrica, RuStore review or bank-SMS import.

RuStore distribution: Yandex Mobile Ads provides banners and app-open ads; AppMetrica collects usage events, device/app information, identifiers and crash diagnostics. Events do not contain receipt contents or amounts. Third-party processing follows the providers’ policies linked below.

Both distributions: ML Kit may send app/device information, per-installation identifiers, API configuration, event/error types, input/output sizes and performance metrics to Google for diagnostics and usage analytics. This technical telemetry is separate from receipt image processing. Google SDK transmissions use HTTPS.

Optional online lookup and permissions

Only after you request and confirm online item lookup, the app sends the original receipt QR payload and your API key over HTTPS to proverkacheka.com. The QR includes fiscal identifiers, time, amount and operation type. The image itself is not sent to that service. Camera access is requested for scanning; selected photos use the system photo picker without full gallery access. Network access supports SDKs and optional lookup; advertising permissions support ad delivery. Only RuStore can request READ_SMS when you choose bank-SMS import; messages are parsed locally and are not uploaded by the app. No precise-location, contacts, microphone or call-log access is requested.

Copies, retention and deletion

Your local records remain until you delete them. Settings → Delete all data clears receipt and budget records, but does not erase photo files, preferences or existing backup files. For a complete local reset use Android Settings → Apps → Receipt Ledger → Storage → Clear storage, or uninstall. Optional weekly backups keep the latest five copies in app storage. JSON/CSV exports and copies saved outside the app remain wherever you saved or shared them and must be deleted there. JSON does not embed original photos. Android/manufacturer backup and transfer may also apply according to your system settings; the app does not control those services.

We do not set a separate server retention period for your receipt data because we do not host it. Advertising and SDK data retention is governed by Google/Yandex policies and your settings; clearing this app does not delete data held by those providers. See data deletion instructions and manage your Android advertising ID or Google account advertising activity separately.

Providers, transfers and your choices

SDK providers may process technical data on infrastructure outside your country under their policies. Review Google Privacy Policy, AdMob data disclosure, ML Kit data disclosure, Yandex Mobile Ads terms, Yandex Privacy Policy and proverkacheka.com. The app is not directed to children under 13. This page will show future policy changes. Contact: iptton@gmail.com.