# Privacy Policy — Yap!

Last updated: April 2026

Rokitskiy.DEV built the Yap! app as a paid app. This SERVICE is provided by
Rokitskiy.DEV and is intended for use as is.

This page informs visitors about my policies regarding the collection, use, and disclosure of
information when you use Yap!. By using the Service, you agree to the terms of this policy.

Yap! is designed with privacy in mind: it does not contain ads, analytics SDKs, third-party
trackers, or cloud sync for your notes. All voice recordings and transcriptions are stored
exclusively on your device.

Information Collection and Use

Voice Recordings

Yap! records audio through your device microphone when you explicitly start a recording. All
audio files are stored locally on your device in app-private storage. Rokitskiy.DEV does not
have access to, transmit, or store your recordings on any server.

Speech Transcription

Yap! optionally transcribes your voice recordings using Android’s built-in
SpeechRecognizer API. When on-device speech recognition is available on your
device, transcription is performed entirely offline. When on-device recognition is not available,
audio may be sent to Google’s servers for processing. In that case, Google’s privacy policy
applies. Transcription is opt-in and can be disabled in the app settings. The resulting
text transcriptions are stored only on your device and are never transmitted to Rokitskiy.DEV.

Device Identifier (Android ID)

To verify your purchase and manage your license, Yap! reads the Android ID
— a unique, pseudonymous, per-app, per-device identifier provided by the Android operating system. This
identifier is used exclusively as a document key in Firebase Firestore (see below) to store
your license record. It is not linked to your name, email, Google account, or any other
personally identifiable information, and is not used for advertising or tracking purposes.

Purchase and License Data

When you purchase Yap!, the following data is stored in Google Firebase Firestore:

Android ID — used as a pseudonymous document key.
Purchase status — whether the license is active.
Trial start timestamp — the date your trial period began, if applicable.

This data is used solely to verify your access to the paid app. It is not shared with
third parties and is not used for marketing or analytics.

Permissions

Permission	Purpose
`RECORD_AUDIO`	Required to record voice notes. Only active while you are actively recording.
`POST_NOTIFICATIONS`	Used to display a notification while a recording is in progress (required for foreground services on Android 13+).
`FOREGROUND_SERVICE` / `FOREGROUND_SERVICE_MICROPHONE`	Allows the recording service to continue running while the app is in the background, so recordings are not interrupted.

Third-Party Services

Yap! uses the following third-party services. Each has its own privacy policy governing
the data they process:

Google Play Services
— used for app distribution, in-app updates, and platform integrity.
Firebase (Google)
— Firebase Firestore is used to store your license record (Android ID + purchase status).
Firebase App Check with Play Integrity is used to protect the backend from unauthorized
access.
Google Play Billing
— used to process the one-time purchase of Yap!. Payment data is handled entirely by
Google and is not accessible to Rokitskiy.DEV.

Data Retention and Deletion

Your recordings and transcriptions exist only on your device and are deleted when you delete
them in the app or uninstall the app. Your license record in Firebase Firestore is retained as
long as needed to validate your purchase. To request deletion of your Firestore record, contact
us at info@rokitskiy.dev with the subject
“Yap! data deletion request”.

Children’s Privacy

Yap! is not directed at children under the age of 13. We do not knowingly collect personal
information from children under 13. If you believe your child has used the app and you have
concerns, please contact us so we can take appropriate action.

Security

Access to Firebase Firestore is protected by Firebase App Check using the Play Integrity API,
which ensures only genuine, unmodified builds of Yap! can interact with the backend. All
communication with Firebase services is encrypted in transit using TLS.

Changes to This Privacy Policy

This Privacy Policy may be updated from time to time. Changes are effective immediately upon
posting to this page. You are advised to review this page periodically.

Contact Us

If you have any questions or suggestions about this Privacy Policy, contact us at
info@rokitskiy.dev.