Apps by Keith

Privacy Policy

Last updated September 14, 2026

SnapGas is a fuel purchase tracker. You photograph a gas station receipt and your odometer, the app reads the numbers off the photos, and it tracks your MPG and cost trends over time, per vehicle.

This policy explains what the app keeps on your device, the very little it sends to its server, and what happens to it. It is written to be read, not survived - if anything here is unclear, use the Contact form in Settings and ask.

The short version

• Your data never leaves your device, with one narrow exception: if the app crashes or hits an error, a scrubbed technical report is sent so it can be fixed. Nothing else about your vehicles, fill-ups or photos is ever transmitted.
• The app does not have accounts. There is no sign-up, no password, and no email address required to use it.
• There is no usage tracking of any kind. SnapGas does not report device counts, how many vehicles you have, how many fill-ups you have logged, or anything else about how you use it. There is no switch for this because there is nothing to switch off.
• There are no advertisements, and no third-party analytics or tracking SDKs.
• Receipt and odometer photos are read on your device, not uploaded. The text recognition that reads gallons, price and odometer digits runs entirely on-device - a photo is never sent anywhere for this or any other reason.
• The app asks for the camera permission when you take a photo, and for photo library access if you choose an existing photo instead - only to let you pick that one photo. Nothing in your library is touched, stored, or sent anywhere. It never asks for your location, contacts or microphone.

Who is responsible

SnapGas is published by Keith Rochkind, an individual developer based in California, United States. For the purposes of the GDPR, that is the "data controller" for the information described here.

The way to reach the developer about anything in this policy - including a request to see or delete data - is the Contact form in the app, under Settings.

What stays on your device

Everything about your fuel purchases stays only on your phone or tablet, and is never transmitted:

| What | Where it lives | | ------------------------------------------- | -------------------------- | | Vehicles, and every fill-up you have logged | The app's private database | | Receipt and odometer photos | The app's private storage | | Which vehicle you last had selected | The app's private storage |

Deleting the app removes all of it. There is no cloud copy, no backup, and no way for the developer to recover it - see "Exporting your own data" below.

What the app sends, and when

1. When something goes wrong

If the app hits an error it did not expect, it sends a small report so the fault can be fixed: what went wrong, roughly where in the code, a short category tag (for example "OCR parsing" or "database write"), the app version, the platform (iOS, Android or web), and a timestamp.

No device ID and no user ID are ever included, because the app has none to send. The message is also stripped before it leaves your device - file paths, web addresses and anything in quotes are removed, since an error about a photo file is exactly the kind of error that would otherwise name it. No vehicle name, station name, or fuel purchase amount is ever in one of these reports.

There is no crash-reporting service in the app - no Firebase, no Crashlytics, no third party of any kind. Reports go to the developer's own server, which forwards them to Azure Application Insights and nowhere else.

2. Written documents

When you open this policy, the Terms of Service, or the FAQ, the app requests the current text from the server. Nothing about you is sent with that request beyond the ordinary technical details described next.

3. Messages you send through the Contact form

If you write to the developer through the app, it sends what you typed: your name (optional), your email address, the subject, and the message. The message is stored and is also emailed to the developer, so a reply can reach you.

4. Ordinary technical details

Like any app that talks to a server, these requests carry your device's IP address, recorded in the server's diagnostic logs alongside error traces used to diagnose faults. This is not linked to anything else described here and is not used to build a profile of you.

What the app never collects

• Precise or approximate location. SnapGas requests no location permission and holds no location data.
• Contacts, calendar, health, or microphone data, or any photo beyond the one you take or choose for a fill-up. The only permissions requested are the camera, when you take a photo, and photo library access, when you choose an existing one instead - and even then, nothing besides the photo you pick is ever touched, stored, or sent anywhere.
• Advertising identifiers. There is no advertising in SnapGas, and no advertising SDK.
• Third-party analytics. There is no Google Analytics, Firebase, Meta SDK or comparable tracker in the app.
• Payment information. SnapGas is free and takes no payments.

Exporting your own data

SnapGas can export your fuel purchase history to a CSV file, which you can email to yourself using your device's own mail app. This is entirely initiated by you and handled by your device's mail client - the file does not pass through the developer's server.

There is no automatic backup. If you want a copy of your data kept somewhere other than your device, export it yourself.

Why this information is used

| Purpose | What is used | | --------------------------------------- | ----------------------------------- | | Finding and fixing faults | Error reports, diagnostic logs | | Knowing what a support message is about | Contact messages | | Answering you | Your email address, if you write in |

Under the GDPR, the lawful basis for error reports and diagnostic logs is legitimate interest - keeping an app the developer maintains alone working correctly. The lawful basis for handling a message you send is that you chose to send it.

Nothing here is used to build advertising profiles, is sold, or is shared for cross-context behavioural advertising.

Who else sees it

Microsoft Azure hosts the server, stores error reports and contact messages, and delivers the email a contact message becomes. Microsoft acts as a service provider and processes this information on the developer's instructions. Data is stored in the United States.

Information may also be disclosed if required by law, or to protect the rights and safety of users or the developer. Beyond that, nothing is shared with anyone.

International transfers

The servers are in the United States. If you use SnapGas from outside the United States - including from the United Kingdom or the European Economic Area - the information described here is transferred there. Where the GDPR or UK GDPR applies, that transfer relies on the European Commission's Standard Contractual Clauses as implemented in Microsoft's data protection terms.

How long it is kept

Error reports and contact messages are kept for as long as SnapGas is operated. If SnapGas is retired, they are deleted with it. Anything on your own device is kept until you delete it, or delete the app.

Security

Traffic between the app and the server is encrypted in transit with HTTPS. Stored records are encrypted at rest by Azure. Access to them is restricted to the developer.

No system is perfectly secure, and no promise is made that one is. What can be said honestly is that the server holds very little worth taking: no passwords, no payment details, no vehicles, and no fuel purchase data - that never leaves your device in the first place.

Your choices and rights

Since SnapGas keeps no account and no persistent identifier tied to you, there is nothing to opt out of beyond simply not writing to the developer. Deleting the app removes everything it holds locally.

If you are in California, the CCPA as amended by the CPRA gives you the right to know what personal information is collected and why; to obtain a copy of it; to have it corrected; and to have it deleted. You also have the right not to be discriminated against for exercising any of these rights. SnapGas does not sell personal information, and does not share it for cross-context behavioural advertising, and collects no sensitive personal information as the CPRA defines it.

If you are in the United Kingdom or the European Economic Area, the GDPR gives you the rights of access, rectification, erasure, restriction, portability and objection. To exercise any of these, use the Contact form. A request will be answered within 30 days. No fee is charged.

Children

SnapGas is not directed to children under 13, and is not intended for their use. No information is knowingly collected from a child under 13. If you believe a child under 13 has used the app and information has been collected, use the Contact form and it will be deleted.

Changes to this policy

This policy is delivered to the app from the server, so a change appears without needing an app update. Where a change materially affects what is collected or what it is used for, the effective date at the top will be updated and the change noted in the app.

Contact

Questions, requests and complaints about this policy all go to the same place: Settings → Contact in the app.