Nenapo Security

Nenapo · Last updated August 13, 2026

Nenapo is designed to reduce what needs protecting in the first place: no Nenapo account, no developer-operated server, no advertising SDK, and no analytics SDK. Your shopping memory lives in app-private storage on your device.

Local-first architecture

Nenapo stores your stores, grocery items, shopping sessions, purchase history, corrections, and settings locally on your device. Mavyasa does not operate a Nenapo backend that receives this data.

Android network posture

The Android app does not request the Android Internet permission, and the core app experience works offline. Without that permission, the app cannot make ordinary outbound network requests.

Platform protection

Nenapo relies on the operating system’s app sandbox and your device security settings to protect local app data. Keeping your device updated and protected with a passcode, PIN, password, or biometric unlock strengthens that protection.

Sharing

When you share a list, Nenapo creates a one-time file and hands it to the system share sheet. Nenapo does not receive delivery status, cannot see the destination you choose, and does not create ongoing synchronization between devices.

Backups

Device backups are controlled by your Apple or Google account and operating-system settings. On Android, Nenapo allows the local database to be included in Android backup so your shopping memory can transfer to a new device. This backup is not sent to Mavyasa.

Contact

Security questions can be sent to support@mavyasa.com.