Dayaside
[LEGAL / PRIVACY MANIFEST // APP.DAYASIDE.ANDROID]
terminal API 34+ COMPLIANT lock LOCAL-ONLY SANDBOX

Privacy Policy

Last Updated November 4, 2026
Manifest Version Current
Target Platform Android 14+ (API 34)
Architecture shield Local-first storage
verified_user
Executive Privacy Guarantee NO CLOUD DAEMON

"Zero telemetry on audio. On-device local processing. Your life recorder data never leaves your device unless you explicitly export or share it."

Dayaside operates under an local-first design. The Android application has no analytics SDKs, requires zero cloud accounts, and treats ambient recording as private hardware custody.

01 // OVERVIEW

1. Overview & Architectural Purpose

Dayaside (identifiable in the Google Play Store and Android ecosystem as app.dayaside.android) is engineered as an on-device personal audio and contextual life recorder. The application empowers users to archive conversations, daily transit thoughts, verbal meetings, and ambient soundscapes without relinquishing data rights to remote infrastructure.

Traditional life logging and transcription tools rely heavily on continuous cloud backhauls, central data processing lakes, and recurring account authentication. In contrast, Dayaside operates under a strict Privacy-by-Design and Local-First Architecture. We do not maintain server clusters to ingest your recorded voice streams, transcribe audio paths remotely, or monetize human speech logs.

hardware

Local-first rule: The Android device hardware you own remains the sole compute unit and vault for all created assets.

02 // INFORMATION MANIFEST

2. Information We Collect and Process

Dayaside collects only the data explicitly required to facilitate user-configured recording schedules, physical geo-fenced triggers, and indexing on your device.

Audio Recordings (.m4a / .opus / .wav)

Audio data captured through the device hardware microphone is written directly into Android app-private storage or your selected user-scoped storage folder. Raw sound is never routed to Dayaside servers or third-party audio API endpoints.

Geofence & Schedule Coordinates

When you configure automatic triggers (such as "Record when arriving at North Station Commute Terminal"), geographic bounds and timestamps are evaluated entirely locally via the Android OS Geofencing API. Coordinates never transmit over network interfaces.

Local Configurations & Custom Presets

Sampling rates, bitrate selections, noise-suppression parameters, and retention window preferences are stored exclusively on your device within encrypted local room databases or shared preferences.

Zero Authentication Mandate

Dayaside does not require email registration, Google Single Sign-On, phone number identity, or passwords. There is no central user table, cloud subscriber database, or linked advertising profile.

03 // OS PERMISSIONS

3. Android Runtime Permissions & Hardware Access

In compliance with Google Play Developer Policies and Android 14 (API 34) security standards, runtime permissions are requested granularly and only for explicit recording workflows.

android.permission.RECORD_AUDIO REQUIRED FOR CAPTURE

Microphone Interface: Used strictly during active recording periods initiated manually by the user or through an active geofence/timer rule.

Behavior: Hardware indicator LED lights up via Android OS privacy pill. Audio buffer stays in volatile memory until flushed to local storage.
ACCESS_FINE_LOCATION / BACKGROUND_LOCATION OPTIONAL WAYFINDING

Transit & Commute Geofence Triggers: Required solely if you configure automated location triggers (e.g., commute departure/arrival).

Guarantee: Location telemetry is evaluated inside the Android OS Geofence Provider subsystem. Dayaside never logs raw continuous breadcrumbs or maps your route.
android.permission.POST_NOTIFICATIONS MANDATORY FOREGROUND

Foreground Service Notification: Under Android guidelines, background audio recording requires a persistent, non-dismissible status bar notification showing exact recording status, pause controls, and duration.

REQUEST_IGNORE_BATTERY_OPTIMIZATIONS USER-DELEGATED

Reliability Whitelist: Optional exception granted by the user to avoid OEM aggressive task killers (Doze mode) from halting long audio sessions during commutes or sleep recordings.

04 // HARDWARE SECURITY

4. Local Storage Architecture & At-Rest Cryptography

Dayaside isolates recorded audio from other applications using standard Android sandboxing conventions. Unless you explicitly select a public SAF (Storage Access Framework) directory, records remain in the internal app-private sandboxed directory.

Device encryption: Dayaside relies on Android’s standard app sandbox and the device’s existing full-disk encryption and lock-screen protections. Dayaside does not claim a separate custom hardware TEE implementation beyond what the OS provides.

Metadata storage: Recording metadata and preferences are stored locally in the app’s private storage using Android platform APIs.

In the event that you lose physical possession of your Android device, security relies on your OS-level lock screen credentials (PIN, passphrase, or biometrics) alongside full-disk encryption (FBE).

05 // BOUNDARIES & RESTRICTIONS

5. What We Do Not Do: Clear Negative Guarantees

Unlike commercial ad-tech apps, our commitment is characterized equally by the capabilities we intentionally omit:

cloud_off

No Remote Cloud Sync

We operate no server endpoints for audio streams. Dayaside cannot reconstruct or retrieve your recordings if your hardware is damaged.

phone_disabled

No Telephony Interception

Dayaside does not hook into cellular call audio or VoIP channels. Dayaside does not capture the cellular or VoIP call audio path.

money_off

No Data Brokering or Sale

We do not sell, rent, license, or broker personal audio logs, voice prints, or location profiles to data brokers or training corpora.

ad_units

No Ad SDKs or Trackers

Dayaside contains zero tracking SDKs from Google AdMob, Meta Audience Network, AppsFlyer, or Firebase Analytics.

06 // RETENTION & LIFECYCLE

6. Data Retention Windows & Rolling Purge

Because Dayaside acts as a continuous journal rather than a permanent surveillance log, built-in rolling retention controls are embedded in the application's core settings:

Rolling 7-Day Clean Window Deletes raw audio older than 168 hours
Rolling 30-Day Archive Retains for 1 calendar month before local zero-wipe
Indefinite (Manual Purge Only) Retains files until manual disk deletion

When an audio file expires according to your configured rule, Dayaside issues an immediate system unlinking call (File.delete()) directly in Android's flash memory.

07 // USER EXPORT

7. Sharing & User-Initiated Export

Your data is completely under your discretionary control. Sharing audio snippets or exported files occurs strictly through native Android Intent components:

  • Android System Share Sheet: Triggered via Intent.ACTION_SEND using an ephemeral, read-only content URI provided by Android's FileProvider.
  • Local File Export: You can copy files directly to USB On-The-Go (OTG) storage or an SD card without network dependencies.
  • No Background Sync Handshake: Dayaside does not sync exported files with Google Drive, Dropbox, or any external third-party service without your explicit manual input per file.
08 // JUVENILE PROTECTION

8. Children’s Online Privacy Protection (COPPA)

Dayaside is designed for general adult productivity, commute tracking, and personal reflection. The app is not directed at children under the age of 13 (or under 16 in the European Economic Area).

Because Dayaside does not operate accounts or solicit profile metadata, we never knowingly collect, solicit, or index personal information from minors. If a parent or guardian becomes aware that a child has configured the software on a shared device, they can wipe all records instantly by clearing application storage in Android Settings.

09 // ABSOLUTE CONTROL

9. Your Choices & Complete Data Deletion

You maintain uninhibited sovereignty to erase all records without submitting deletion requests or awaiting back-office ticket approvals:

Option A: In-App Immediate Purge

Navigate to Settings > Storage > Purge All Records to immediately delete all database entries, waveform caches, and audio files.

Irreversible Immediate deletion
Option B: Android System Clear

Navigate to Android Settings > Apps > Dayaside > Storage & Cache > Clear Storage.

standard OS-level clear of the app sandbox
10 // DEVELOPER CHANNEL

10. Contact Information & Developer contact

For legal inquiries, privacy questions, or security reports:

Primary Legal Contact mail support@dayaside.app
Android Package Name app.dayaside.android
11 // MANIFEST LOG

11. Changes to This Privacy Policy

We reserve the right to revise this policy in accordance with updates to the Android OS APIs or new features introduced to Dayaside. Any material changes will be documented with an updated "Last Updated" timestamp at the top of this document and highlighted in the application's changelog upon app launch.

Because Dayaside does not collect user contact information, we cannot dispatch direct email notifications. We encourage users to inspect this manifest or verify changes via the this Privacy Policy page prior to installing software updates.