Data Safety
Short summary of what SeshLog collects and how it handles data. Detailed terms: Privacy Policy.
At a glance
- All data is stored only on the user's device.
- No data is shared with third parties.
- No advertising, analytics, or tracking SDKs are used.
- Data is never transmitted, so encryption in transit is not applicable. Storage is sandboxed by the operating system / browser.
- Users can delete any record from inside the app at any time, or wipe everything with DELETE ALL.
- Export is initiated by the user; the resulting ZIP is the only way data leaves the device.
Data types
| Data type | Collected | Shared | Purpose |
|---|---|---|---|
| Name | Yes | No | App functionality (participant record) |
| Phone number | Yes | No | App functionality (optional contact) |
| Photos (personal) | Yes | No | App functionality (identification) |
| Photos (government ID) | Yes | No | App functionality (identification) |
| Email address | No | No | — |
| Precise or approximate location | No | No | — |
| Contacts | No | No | — |
| Messages / SMS / Email content | No | No | — |
| Audio / Microphone | No | No | — |
| Web browsing history | No | No | — |
| App activity / analytics | No | No | — |
| Device or advertising IDs | No | No | — |
| Financial info | No | No | — |
| Health & fitness | No | No | — |
Security practices
- Data is not transferred off the device by the app.
- Data is stored in app-sandboxed local storage (IndexedDB).
- Users can request deletion in-app — handled instantly by the Delete and DELETE ALL controls.
- The developer follows the Google Play Families Policy and Apple App Store Review Guidelines around user-generated data.