Last Updated: May 11, 2026 Effective Date: May 11, 2026 Scope: This policy applies to Senko users in the United States. International users may be subject to additional disclosures and protections under their local laws; a separate policy will be published when Senko launches in other markets.
Senko does not collect any personal information about you. Your pantry, recipes, meal plans, and all other data you enter stay on your device. Some optional features cause data to leave your device in specific, limited ways — those are described in detail below.
Senko itself collects no personal information. We do not collect:
Names
Email addresses
Phone numbers
Device identifiers
Location data
Usage analytics
Behavioral tracking
Advertising identifiers
There are no accounts, no sign-ups, and no Senko-operated servers receiving your data.
All data you enter into Senko — pantry inventory, recipes, meal plans, shopping lists, custom storage locations, Quick Add tiles, themes, settings — is stored locally on your device using on-device SQLite storage. Senko does not use cookies, web storage, or any cloud-based persistence mechanism.
Data is retained on your device until you delete it through the app's controls or uninstall the app. We have no ability to access, view, or recover your data.
While Senko itself collects nothing, the following features cause data to be transmitted in specific ways. Each is fully optional and is only triggered by your direct action.
When you scan a product barcode, Senko sends the barcode number (UPC or EAN) to the Open Food Facts database (openfoodfacts.org) to retrieve product information. Open Food Facts is an independent, open-source food product database operated by a French nonprofit.
What Open Food Facts receives:
The barcode number you scanned
Your IP address (as required by HTTP communication)
A timestamp of the request
What Open Food Facts does not receive:
Your name, email, or any account information (you have none)
Your location beyond what your IP address may approximate
Any other information from Senko
Open Food Facts has its own privacy policy at https://world.openfoodfacts.org/privacy. Senko does not control what Open Food Facts does with their data.
You can use Senko without ever scanning a barcode; barcode scanning is purely a convenience feature.
Senko's QR code scanner is used for two features:
Receiving shared recipes from another Senko user
Receiving a household pantry invite from another Senko device
QR code scanning happens entirely on your device. No data is transmitted to any server. The scanner reads codes within Senko's own format only.
Senko requests camera permission to operate the barcode and QR code scanners. The camera is only active while you have the scanner open. Images are never stored, transmitted, or retained. The scanner extracts only the barcode number or QR code data and discards the image immediately.
Sync Lite is an optional feature that lets you share one pantry across multiple devices in your household over your local WiFi network. When you use Sync Lite:
Your pantry data flows between the participating devices on your local network
mDNS (Multicast DNS) is used to discover other Senko devices on the network — this involves your device announcing its presence to your local network so other Senko devices can find it
The Android "Nearby Devices" permission must be granted to enable mDNS discovery on Android 13 and newer
No data passes through any external server. Sync Lite communication does not leave your local network.
Sync Lite is off by default. You must explicitly enable it and pair devices to use it. When Sync Lite is active, your pantry data is shared between paired household devices, not with any third party.
You can export your pantry data to a .senko backup file at any time. This file is created on your device. Once you have an exported file, you control where it goes — you can save it locally, transfer it to another device, or share it through any method you choose. Senko has no control over what happens to exported files after they leave the app. We recommend treating these files as sensitive if you store them on cloud services.
You can also import a .senko file to restore data. Import is entirely local; no transmission occurs.
Senko does not collect crash reports by default. We have included an opt-in setting that lets you enable anonymized crash reporting if you wish to help us improve the app.
If you enable crash reporting:
Anonymized stack traces and basic device information (Android version, device model, app version) are sent to our crash reporting provider
No personal data, pantry contents, or app data is included
You can disable crash reporting at any time in Settings, which stops further transmission immediately
Specific crash reporting provider details and the provider's privacy policy link will be published in this policy when the feature is activated. Until then, the feature is not present in the app.
Senko does not integrate any of the following:
Advertising networks
Analytics services (Google Analytics, Firebase Analytics, Mixpanel, etc.)
Social media SDKs
Third-party tracking tools
Senko is distributed through the Google Play Store. When you download Senko from the Play Store, Google collects information about your device, account, and the installation. This data collection is governed by Google's Privacy Policy (https://policies.google.com/privacy), not by this policy. Senko does not receive this data.
In the future, Senko plans to offer paid extensions and features through Google Play Billing. When that feature is activated:
Purchase transactions will be processed entirely by Google Play Billing
Google will handle all payment information (credit cards, billing addresses, payment methods)
Senko will receive only transaction metadata: a purchase identifier, the product purchased, and the purchase status
Senko will not see, store, or transmit your payment method or billing details
Payment data handling is governed by Google's Privacy Policy
If we integrate a third-party billing wrapper (such as RevenueCat) to manage purchase entitlements, this policy will be updated to disclose that integration and link to the provider's privacy policy.
Senko is rated for ages 3 and up. Senko does not knowingly collect personal information from children, because Senko does not collect personal information from anyone.
If a child uses Senko on a device managed by a parent or guardian under a family Google account, Google's family account policies apply to any Play Store and Billing activity. Those policies are outside the scope of this document.
If you believe a child has somehow had personal information collected through Senko, please contact us at the email below.
You have full control over your data in Senko:
Access: All your data is on your device and accessible to you through the app at any time.
Correction: Edit any item, recipe, or setting in the app directly.
Deletion: Delete individual items through the app, or uninstall the app to remove all Senko data from your device.
Portability: Use the Export feature to obtain a copy of your data in .senko format.
Disable optional features: Sync Lite, crash reporting (when available), and any future opt-in features can be disabled at any time in Settings.
Because Senko stores nothing on our end, we cannot delete your data on your behalf — you do this directly through the app. We also cannot recover lost data; if you uninstall without exporting, your data is gone.
We may update this policy as Senko evolves. Material changes will be noted at the top of this policy with an updated "Last Updated" date. The policy in effect at the time you use Senko is the policy that applies.
We will not retroactively apply new data collection practices to data already on your device without first updating this policy.
Questions about this privacy policy or about how Senko handles data can be sent to:
f7203074@gmail.com
This email is monitored by Senko's developer.
This privacy policy is governed by the laws of the United States. Senko is currently distributed to United States users only. A separate policy will be published before Senko is offered in other jurisdictions.
Privacy Policy v2.0 Effective May 11, 2026 Supersedes Privacy Policy v1.0 (April 2026)