Privacy Statement

Last updated April 22, 2026

What Reczzz stores

Reczzz is designed so your recordings and related sleep-audio data stay on your device. Depending on how you use the app, that may include the recorded audio file itself, recording metadata such as date, duration, and file path, sound-analysis results such as spikes or likely labels, and local settings such as quality preferences or disclaimer acceptance.

Audio stays on your device unless you act

We do not provide a Reczzz cloud where your recordings are uploaded. Recordings stay on your device unless you choose to export, share, import from another source, open an external link, or otherwise send data outside the app yourself.

On-device analysis and playback tools

Reczzz uses on-device playback and analysis features to help you review the night, including spike detection, likely sound suggestions, denoise, and enhancement. These features are intended to work locally on your device rather than by sending recordings to our servers for remote processing.

No account and limited direct collection

You do not need an account to use Reczzz. We do not ask you to create a profile before recording. In normal use, Reczzz is not designed to collect or analyze your data, or to upload your recordings for analytics, advertising, or cloud playback.

Minimal crash reporting

If the app crashes, we may receive only a small amount of technical data to diagnose and fix the bug. This is intended to be limited to technical crash information, not your recordings or sleep-audio content. This may include battery state and available memory or storage at the time of the crash, because those are often directly relevant to overnight recorder failures. Where the app would otherwise need to send a precise number about your recording, it sends only a coarse category instead so the value cannot be reversed into your sleep duration or schedule.

Device model

Helps us see whether a crash affects a specific phone model.

OS version

Helps identify issues tied to a specific Android or iOS version.

App version

Shows which app build the crash happened in.

Locale and timezone

Helps diagnose region-specific formatting or time-related issues.

Error details and stack trace

Lets us understand what failed technically so we can fix it.

Battery state

Helps us tell whether the phone was low on battery or charging when the crash happened.

Available memory and storage

Helps diagnose crashes caused by low RAM or low free storage during long overnight recordings.

Recording state label

A short label such as idle, starting, active, stopping, stopped, or errored, so we can tell which step a crash happened in. It does not say what was being recorded or for how long.

Quality preset label

Which of the named quality profiles was selected (lossless, standard, or compact). Helps us tell whether a crash is tied to a specific encoder or format. It is a settings label, not a measurement.

Bucketed recovery outcome

When the app finds an unfinished recording on next launch, we may report a coarse category for what happened (for example, audio file missing, very small, or that the file size category was small/medium/large) so we can fix the bugs that lose recordings overnight. We do not send the precise size or precise duration.

What is not intended to be collected

Reczzz is intended to avoid collecting personal data, audio recordings, sound-analysis results, precise recording durations, file paths, recording identifiers, IP addresses, screenshots, view hierarchies, breadcrumbs, and user-tracking data as part of crash reporting.

Download, export, and share recordings

If you choose to export or share a recording, that file may be copied to another location, another app, or another service under your control. If you import audio into Reczzz, the source file may come from your device, a connected file provider, or another storage service you use. If you open legal links, support links, or other external URLs, your browser or another app may handle that request under its own terms and privacy practices.

Permissions, explained

Reczzz asks for permissions and device features only when needed to record, manage, and optionally export audio.

Microphone

Needed to record the sounds of the night.

Export or share access

Used only when you choose to export or share a recording.

Background audio / foreground service / notifications

Needed to keep long overnight recording sessions running reliably, especially when the screen is off or when the operating system requires a persistent notification.

Retention, deletion, and your responsibility

You control whether to keep or delete recordings stored in the app. If you delete a recording in Reczzz, the app is intended to remove it from the app-managed storage it controls. You are responsible for what you record, where you export or share it, and for complying with any laws that apply to recording other people or sensitive sounds in your jurisdiction.

Children, medical use, and contact

Reczzz is not intended as a medical device, diagnostic tool, emergency service, or product directed to children. If you have questions, concerns, or privacy requests, use the contact option below.

Privacy questions? Email .