Delete your data
Complete Local-first data guidelines, local storage wipe protocols, and verification instructions for Dayaside on Android.
Dayaside is architected as an offline, sovereign, local-first Android recorder. Audio files and metadata are stored exclusively in your device's private app sandbox.
Because Dayaside operates with zero server accounts, no cloud database, and no telemetry backend, there is no remote cloud account or server-side data for us to wipe. You hold 100% custody of your data at all times. All deletion actions occur instantaneously on your local hardware.
Local Storage Deletion Procedure
Wipe local sandbox data & audio recordings
Settings → Apps → Dayaside → Storage & cache → Clear storage / Clear data
This immediately and irrevocably purges all encrypted local database records, schedule triggers, geofence rules, and ambient mic audio recordings from device storage.
Uninstall the Dayaside application
Long-press Dayaside icon on home screen/drawer → Tap Uninstall (or remove via Google Play)
Removes the application binary, foreground audio capture services, ambient listener alarms, and revokes all system runtime permissions (Microphone, Notifications).
Manage externally shared files
Files by Google, Google Drive, Third-Party Messaging, or Email Downloads
If you manually exported or shared individual recording files (.m4a/.wav) to third-party apps or cloud drives, Dayaside cannot access those directories; please delete external copies manually.
Data Governance & Technical Verification
Do you keep backups on Dayaside servers?
No. Dayaside has no ingestion servers, cloud databases, user credential registries, or telemetry clusters. All data originates, is processed, and resides strictly on the local hardware layer. There is literally no central database to back up or breach.
Does Dayaside record phone calls?
No. Under standard Android security architecture and platform privacy restrictions, voice call streams are isolated from standard audio-record sources. Dayaside only interfaces with ambient microphone inputs when explicit capture conditions are active.
How do automatic retention rules work?
If enabled in app settings, Dayaside's internal background worker periodically evaluates recording timestamps and automatically overwrites/purges files older than your configured threshold (e.g. 24 hours, 7 days, or 30 days) directly on your device storage without requiring manual intervention.
Need assistance or deletion verification?
If you require guidance on verifying sandbox eradication on custom Android ROMs or OEM forks (Samsung OneUI, Xiaomi MIUI, Google Pixel), reach out directly to our engineering desk at support@dayaside.app.
Google Play Data Safety Declaration Summary
Zero user data collected or transmitted to external entities.
No ad SDKs, analytics brokers, or telemetry third parties embedded.
100% on-device private app sandbox with scoped storage.
Operates friction-free without login, password, or cloud identity.