TL;DR
Snikko stores your codes on your device. We don't sell data, run ads, or build a profile of you. We never see what's in your stash.
- No account required to use the app.
- Scans happen on-device. Nothing in your stash is uploaded.
- Sharing a code makes a private, expiring link — only that one item's display details go to our server, and you can revoke it any time.
- Crash reports and product analytics go to Firebase. Analytics is on by default and can be turned off in Settings.
What we collect
On your device only:
the QR/barcode payloads you scan, the metadata Snikko auto-fills (venue, time, expiry), photos of your codes, your profile, your saved parking pins, and your app settings — all stored in a local SQLite database on your device. This content stays on your device unless your phone backs it up to iCloud / Google, or you turn on a public profile or create a share link (see Public profile and Share links below), which send a limited set of fields to our own server.
Sent to Firebase (Google):
a small set of operational data, never the contents of your stash:
- Crash reports — stack trace, device model, OS version, app version, locale, and a non-resettable install ID. Sent to Firebase Crashlytics whenever the app crashes so we can fix bugs.
- Product analytics — typed events like "scan succeeded", "stash created (kind=parking)", "stash archived", plus Firebase's standard device/session metadata. On by default; toggle it off in Settings → Analytics.
- A push messaging token — issued by Firebase Cloud Messaging if you allow notifications, used to deliver expiry reminders and the occasional product update.
- Remote Config fetches — we ship feature flags (for example, to enable or disable AI features) via Firebase Remote Config. These fetches happen even when analytics is off so kill-switches still work.
If you email us:
your email address and message, retained for as long as the support thread is open.
Permissions we request
- Camera — only while you are scanning a QR / barcode. Frames are processed on-device and discarded.
- Photo library — only if you tap "Scan from photo" so the app can open the one image you pick.
- Location — only when you save a parking stash with location on, or tap "Walk me there" / open the where-I-parked map. Coordinates stay on the device alongside the stash.
- Notifications — only to deliver expiry reminders you schedule and the occasional product notification.
On-device AI
Snikko offers optional AI features — smart-categorize, read-ticket / smart-scan from photos, and semantic duplicate detection — powered by Google's Gemma models running through the LiteRT-LM runtime. When you choose to install a model from the AI Setup screen, the model file (roughly 500 MB to 3.5 GB depending on which one you pick) is downloaded from Hugging Face to your device. After that, inference happens entirely on your phone: the prompts you type, the photos you scan, and the model's outputs never leave the device and are not sent to us, to Google, or to Hugging Face. You can delete the model any time from AI Setup.
Third-party services
Only the limited data above ever reaches a third party. Their use of it is governed by their own privacy policies:
- Firebase Crashlytics, Analytics, Cloud Messaging, Remote Config (Google) — firebase.google.com/support/privacy
- Hugging Face — receives a standard HTTP request when you download an AI model. huggingface.co/privacy
- OpenStreetMap — receives only the tile coordinates needed to render the where-I-parked map. openstreetmap.org/copyright
How we use it
The data on your device is used solely to run the app — show your codes, count down parking timers, find your car on the map. Crash reports go straight into bug-fixing. Analytics events tell us which features are being used so we can prioritize improvements. We never use any of it to build advertising profiles.
Public profile
Snikko works fully offline by default. If you choose to turn on a public profile, Snikko uploads your profile to our own server (not Firebase) and publishes it as a web page at snikko.nat-touring.dev/your-handle, so you can hand out one link instead of your codes.
- What we publish — your display name, handle, chosen accent colour, and any optional pronouns, bio, and city. Your email, phone, and the codes in your stash are never published.
- Who can see it — anyone with the address, and search engines may index it. A public profile is meant to be public; that is the point.
- Staying in control — switch your profile back to private in the app any time and we take the page down and remove it from our server.
Your rights
You can:
- Edit your profile, codes, and metadata directly in the app.
- Delete any stash from its detail screen, or uninstall Snikko to wipe everything on the device.
- Turn analytics off any time in Settings → Analytics; revoke camera / photos / location / notifications in your device settings.
- Request a portable copy of the on-device data we hold for you (PDPA Section 31). The app does not have a one-tap export yet — email [email protected] and we will respond within 30 days.
Contact
Questions? Email [email protected]. We respond within a day, by an actual person.