Dayaside
ROUTE 04 / SOVEREIGN STORAGE REPOSITORY /
lock ZERO CLOUD TELEMETRY
STATION / 04 — SUPPORT & INQUIRIES

Support & Help Desk

Quiet, sovereign audio recording utilities built for private lives. Direct guidance, verification keys, and architecture notes for Android users.

DISCLOSURE REF: DEV-IND-01
person_pin
Independent Developer Dispatch

Dayaside is conceived, crafted, and maintained by an independent software developer. There are no venture capital growth quotas, no behavioral ad brokers, and no algorithmic data harvesting layers. Support requests are read and resolved by the engineer who wrote the code.

Crafted for human dignity & local privacy
01 COMMUNICATION CHANNELS & DIRECT ACTION
SELECT A DISPATCH TERMINAL
PORT: 01-MAIL SLA: < 24-48h

Direct Email Desk

Send technical logs, bug captures, or general reflections. Handled directly by the core developer.

support@dayaside.app
shield PGP Key: 0x4E9A28B1 Sovereign Verified
PORT: 02-PURGE ON-DEVICE

Local-first data

You possess every bit. Zero central servers hold your audio recordings or temporal metadata.

Need to purge your data? Simply clear app storage or uninstall. No ticket filing or remote deletion requests required.

delete_sweep Instant localized cryptographic erasure
PORT: 03-ANDROID CLOSED TRACK

Testing & Feedback

Pre-release distribution builds and experimental ambient battery-saving features.

PACKAGE IDENTIFIER ACTIVE
app.dayaside.android
android Targeting Android 14+ foreground service APIs
02 WAYFINDING FAQ // SOVEREIGN TECHNICAL RECORD
KNOWLEDGE BASE INDEX
01 // SYNC

Is my audio uploaded automatically?

expand_more

No. Never. Dayaside has zero automated cloud sync or telemetric voice relays. Every audio stream recorded via ambient mic stays strictly on your local Android storage until you explicitly export a single file.

check_circle Network inspection: 0 outbound byte transfers for media files during recording cycles.
02 // TELEPHONY

Does Dayaside record phone call audio?

expand_more

No. Dayaside strictly does not tap, route, or capture the telephony/cellular call audio path. Android platform privacy policies and our local-first architecture restrict recording to ambient microphone audio capture.

When an incoming or outgoing voice call takes hardware priority, Dayaside pauses ambient audio buffering gracefully and resumes only once the telephony connection releases the microphone line.

03 // GEOFENCE

How do I configure geofence and schedule rules?

expand_more

Geofences and schedules are evaluated entirely on-device by Android’s native Geofencing and AlarmManager APIs. You can define specific bounding coordinates (e.g., Home, Commute Rail, Studio) or temporal shifts.

// LOCAL GEOLOCATION INTEGRITY:
• Coordinates are never hashed or transmitted to an external server.
• Triggers simply fire an on-device Intent to start or halt the foreground recorder.
04 // ERASURE

How do I delete my data?

expand_more

Because all files reside exclusively in internal app sandboxed storage (/data/data/app.dayaside.android/files), deleting recordings inside the app or uninstalling Dayaside permanently purges all audio immediately without requiring server-side deletion requests.

05 // RELEASE

When is the Android app available?

expand_more

Dayaside is currently rolling out through Google Play's Closed Testing Track for package app.dayaside.android. Production rollout will begin following battery telemetry calibration across Snapdragon, Pixel Tensor, and MediaTek shipsets.

To request APK early access or sign up for tester seats, email support@dayaside.app with your Android OS version.

03 DIAGNOSTIC MANIFEST & STATION METRICS
NODE: DAYASIDE-SYS-CORE
LOCAL
Architecture State
Local-First Monolith
Zero cloud relays attached
Package Identifier
app.dayaside.android
ARM64 / Android 14+ SDK 34
Direct Dispatch Desk
support@dayaside.app
Direct developer inbox
Response Protocol SLA
schedule 1–2 Business Days
Human-composed resolution
TELEMETRY: DISABLED • VOICE DATA LOG: SANDBOXED • GEO TRIGGER: HARDWARE ON-CHIP
HASH VERIFICATION: SHA256-OK