Terms of Use · Impressum / Legal Notice · Deutsch
Last updated: September 2, 2026
This privacy policy applies to the Android app ReceiptKeep
(package ID: com.receiptkeep.warranty).
Robert Peringer
Ittlinger Hauptstraße 17
94315 Straubing
Germany
Email: FsNaviVfr@gmail.com
ReceiptKeep is a warranty and receipt tracker. The item data you enter (item name, price, warranty duration, expiration date) is stored in a local database on your device. A receipt you attach to a logged purchase — a photo or PDF of the till receipt or invoice, optionally taken with the camera on the spot — is stored as a file in the app’s private storage on the same device (see Section 3.2). There is no user account, no registration, and no server/backend of our own. The app itself never transmits your item data, or the receipts you attach, to the developer or any third party.
Some functions involve third-party services: Google Play Billing is used to process premium purchases, and the Frankfurter API may be contacted directly from your device to fetch exchange rates when you use the currency conversion feature. No advertising, analytics, or tracking services are used.
If Android’s Auto Backup feature is enabled on your device, the app’s local database and any receipts you have attached may be included in a backup associated with your Google Account. The developer has no access to such backups (see Section 5).
Name, price, currency, warranty duration, and expiration date for each item you add are stored in the app’s local database on your device. This data is used to display your items and to schedule local reminder notifications before a warranty expires. It is never uploaded to a server operated by the developer.
If you pick one of the symbols that ship with the app for an entry, that choice is stored there as well. The symbols are part of the app; no image is uploaded and none is fetched from the internet.
For any purchase you log you can attach up to ten receipts — typically the till receipt or the shop’s invoice. There are three ways to do so: an existing photo from your gallery, an existing file from your device storage (a photo or a PDF), or a photo you take with your device camera then and there. The app then makes its own copy in its private storage on your device; photos are scaled down and re-encoded in the process. The metadata embedded in the original does not survive that — including the place the photo was taken and the camera model, where your device had written them. Only the orientation is carried over, so that a receipt photographed upright is not shown lying on its side. Only the file name of that copy is written to the local database, and an original you picked is left untouched.
When you take a photo, the app does not open the camera itself; it hands the capture to the camera app on your device. That app writes the image into a temporary file in ReceiptKeep’s cache, from which the app produces the scaled copy; the temporary file is then deleted. Cancelling the capture deletes it too. Whether the camera app additionally keeps its own copy in your gallery is decided by the camera app alone; ReceiptKeep has no influence over that.
A receipt is free-form content and can therefore contain more than the fields you type elsewhere in the app — a serial number, your name and address, the last digits of a payment card, a retailer’s details, or anything else printed on the document. Please bear that in mind when deciding what to attach.
The app does not read, analyse, or interpret what a receipt contains, and does not upload it to the developer or to any third party. None of the three routes requires an additional Android permission for the app: an existing file is chosen in the Android system’s own photo picker or document picker, which grants the app access to that single file only, and for a capture the camera app asks for whatever permissions it needs itself (see Section 4).
Removing a receipt from an entry, or deleting the entry itself, also deletes the stored copy from your device. Uninstalling the app or clearing its data removes all stored receipts.
Unlike the rest of your data, a receipt is a file rather than a database row, and it is included in Android’s Auto Backup alongside the database. If Auto Backup is enabled on your device, attached receipts can therefore form part of a backup associated with your Google Account (see Sections 5 and 6).
Paid premium features are purchased through Google Play Billing. Payment details (card numbers, billing address, etc.) are processed entirely by Google, which acts as an independent data controller for that processing — ReceiptKeep never sees or receives your payment details.
To determine whether premium features should be unlocked, the app queries your purchase status directly from Google Play each time it starts. This purchase information is not transmitted to the developer — there is no developer-operated server to receive it — and is not stored on your device either; it is only held in memory for the current app session. See Google’s Privacy Policy.
If you use the Insights screen to display totals in a currency other
than the one an item was entered in, the app fetches current exchange
rates from the free, keyless Frankfurter API (api.frankfurter.app,
based on European Central Bank reference rates) over the internet.
The purpose of this request is solely to convert amounts between
currencies for display; no item data or other personal data is
included in or derived from this request, only the currency codes
needed to look up a rate. The request is sent directly from your
device to the Frankfurter API; the developer does not operate or route
this request through its own server, does not receive this request, and
the app does not store your IP address. As with any network request,
your device’s IP address is technically visible to the Frankfurter
service and any technical infrastructure providers (for example hosting
or content-delivery services) it relies on to operate that API. How long
that connection data is retained is determined by those services’ own
policies, not by the developer, who has no control over it. Fetched
rates are cached locally on your device for 24 hours to minimize how
often this request is made.
The app declares and uses the following Android permissions:
| Permission | Purpose |
|---|---|
Notifications (android.permission.POST_NOTIFICATIONS) |
Used to remind you before an item’s warranty expires. Reminders are scheduled entirely on your device. On Android 13+, this requires your explicit consent, which the OS will ask for. |
Internet (android.permission.INTERNET) |
Used for Google Play Billing and fetching exchange rates for currency conversion (see 3.3–3.4). This is a standard permission automatically granted at install time, not something you are separately prompted to approve. |
The app does not request access to your contacts, location, camera, microphone, photos, or other sensitive device data.
This includes attaching a receipt. An existing file is chosen in the Android
system’s own photo picker or document picker, which hands the app a read grant
for the single file you selected and nothing else. The app therefore does not
declare READ_MEDIA_IMAGES or any comparable storage permission.
Taking a receipt photo does not require a camera permission for the app
either. The picture is taken by the camera app on your device, using its own
permissions; ReceiptKeep merely provides a temporary file for it to write
into, and does not declare android.permission.CAMERA.
The app uses Google Play Billing to process premium purchases, and the Frankfurter API to fetch exchange rates for currency conversion in the Insights screen (see 3.4). No advertising, tracking, or analytics/statistics SDKs are used (e.g. no Google Analytics, Firebase Analytics, or similar).
The app also supports Android’s built-in Auto Backup, which — if enabled on your device — automatically backs up the app’s local database and the receipt files you have attached, as part of the standard Android OS backup service. The backup is handled by Android and associated with your Google Account; the developer does not operate this backup service and has no access to its contents. See Google’s documentation on Android Auto Backup for details, and Android’s device backup settings to control it.
Item data you enter is stored in the app’s local database on your device, and receipts you attach are stored as files in the app’s private storage on the same device. Both remain there until you edit or delete them, or delete the app’s local data. The developer does not operate its own server and does not receive or disclose this data to third parties.
If Android Auto Backup is enabled for ReceiptKeep, this local database and the attached receipt files may also be included in a backup associated with your Google Account, as described in Section 5.
Under the GDPR, you generally have the right to access (Art. 15), rectification (Art. 16), erasure (Art. 17), and restriction of processing (Art. 18). Where the respective legal requirements are met, you may also have the right to data portability (Art. 20 GDPR) and the right to object to processing based on legitimate interests (Art. 21 GDPR).
Since ReceiptKeep does not store or transmit your item data, or the receipts you attach, on the developer’s side, most of these rights are already effectively in your own hands: you can view, edit, or delete your item data directly in the app at any time. This is not the same as formally exercising a right under the GDPR, however. To formally invoke any of the above rights — for example regarding the limited technical data described in Sections 3.3–3.4 — please contact the developer using the details in Section 10.
Deleting the app or its local data removes this data from your device. If Android Auto Backup is enabled, a backup may remain associated with your Google Account until it is managed or deleted through Android’s backup settings or your Google Account — the developer cannot delete this on your behalf, as it has no access to it (see Section 5).
You also have the right to lodge a complaint with a data protection supervisory authority.
Where the GDPR applies, different processing activities described in this policy rely on different legal bases:
This privacy policy may be updated as needed, for example due to changes in the app’s functionality or legal requirements. The current version is always available via the link provided in the app and in the Play Store listing.
For privacy-related questions, please contact: FsNaviVfr@gmail.com
ReceiptKeep lets you record items you own, including predefined quick-add suggestions (for example Smartphone, Laptop, TV, or similar) which are generic product categories, not references to any specific brand. Any product names, logos, or brands you choose to enter yourself remain your own data and are the property of their respective owners. Company, product, and service names used in the app are for identification purposes only and do not imply any affiliation, sponsorship, or endorsement by those companies. You are always free to enter a custom item name instead of choosing from the predefined list.