NacreInk Data Safety
Last updated: 2026-07-24
This summary explains NacreInk data practices and serves as a public reference for Google Play Data Safety and Apple privacy labels.
| Data type | Collected? | Purpose | Sold? | Deletion |
|---|---|---|---|---|
| Email address and account ID | Yes | Account, login, verification, password recovery | No | Yes |
| Device name, model, MAC, firmware, and battery | Yes | Connect and manage user devices | No | Yes |
| IP address and coarse region | Yes | Security, abuse prevention, troubleshooting | No | Deleted or anonymized |
| Photos | User-selected and mainly processed locally | Generate E-Ink transfer data | No | Can be deleted locally |
| AI prompts and generation requests | Only when AI creation is requested | Provide AI creation | Service processors only | Deletion can be requested |
| AI content reports and compressed preview | Only when a report is submitted | Safety review and filter improvement | No | Deleted with the account |
| Precise location, advertising ID, health, or financial data | No | Not collected | No | N/A |
Key points: data is encrypted in transit using HTTPS; users can request deletion in the app or on the public account deletion page; location permission on older Android versions is used only to meet Bluetooth scanning requirements.