Privacy Policy
Nenapo · Last updated August 14, 2026
The short version: Nenapo and its developer don’t collect your data. Your stores, grocery items, and shopping history are stored on your devices. Information leaves the app only when you deliberately share a shopping list, use a device speech-recognition service, use a paired-device companion feature, or rely on an operating-system backup that you control through your Apple or Google account settings.
What Nenapo collects
Nothing. Nenapo has no account system, no sign-in, and no servers of its own. Nenapo does not use analytics, advertising, or crash-reporting services, and does not integrate any third-party analytics, advertising, or crash-reporting software development kit (SDK).
Where your data lives
Everything you add to Nenapo — stores, grocery items, shopping sessions, purchase history, corrections, and settings — is stored locally on your device. On Apple platforms, Nenapo uses Apple’s on-device database and App Group technologies. On Android, Nenapo uses an app-private local database. Nenapo has no account system or developer-operated server, and the developer does not receive your stores, items, or purchase history. You can remove local Nenapo data by deleting the app or clearing its app storage in the operating system settings, subject to any device backup you have enabled.
List Sharing
When you choose Share List, Nenapo creates a one-time file containing the selected store name, item names, and quantities. The file does not include purchase history, memory statistics, account information, or device identifiers. You choose where to send or save it using the system share sheet on your device. Nenapo and its developer do not receive the file, cannot see its destination, and cannot know whether it was delivered or opened. Importing a list is a one-time transfer, not ongoing synchronization.
Apple Watch
If you install the Nenapo Apple Watch companion, the app transfers the active store list and shopping actions between your paired iPhone and Apple Watch using Apple’s WatchConnectivity framework. This information stays within your paired devices and is not sent to Nenapo or its developer. The iPhone remains the authoritative data store.
Android backup
On Android, Nenapo allows Android’s operating-system backup to include the local Nenapo database so your shopping memory can move with you when you change phones. This backup is controlled by your Android and Google account settings. It is not sent to a Nenapo or Mavyasa server, and Mavyasa cannot read it.
Microphone and Speech Recognition
Nenapo requests microphone or speech-recognition access only when you use voice capture. On Apple platforms, audio is processed through Apple’s Speech framework. On Android, audio is processed through the speech-recognition service available on your device, which may be provided by Google or another system speech provider. Nenapo does not retain the audio or send it to a Nenapo or developer-operated server. You can deny these permissions and use typed entry instead.
Location
Nenapo does not request location access and does not read or use your location. A future store-arrival reminder feature may require location permission, but that feature is not part of the current app.
Notifications
Nenapo does not currently send notifications. A future reminders feature may ask for notification permission only when notifications become useful.
Security practices
Nenapo’s main security protection is architectural: there is no Nenapo account, no developer-operated server, no advertising SDK, and no analytics SDK. The Android app does not request the Internet permission. Data stored on your device is protected by the security features of iOS, iPadOS, watchOS, or Android, including the device lock and operating-system app sandbox. More detail is available on the Nenapo Security page.
Children’s privacy
Nenapo does not knowingly collect information from anyone, including children, because Nenapo does not collect information at all.
Changes to this policy
If Nenapo’s data practices change in the future — for example, if an optional sync feature is introduced — this page will be updated first, and the update will describe exactly what changes and why, before that feature is available.
Contact
Questions about this policy can be sent to support@mavyasa.com.