Lost Wizard Corp.

Privacy Policy – AnnouncingDJ

Data Collection and Usage
AnnouncingDJ does not require users to log in or provide personally identifiable information (PII) such as names, emails, or account details. Users create and manage team names, player names, and voice announcements within the app. These are stored locally on the device and are not uploaded to any backend server by the app.

However, some non-personal usage data may be collected via third-party SDKs for analytics and advertising performance, as outlined below.

Voice Recordings and Audio Files
Users may choose to record player names using their device microphone or generate voice announcements via AI-powered Text-to-Speech (TTS). These audio files are stored locally on the device and are not automatically shared or uploaded by the app.

When using the Google Cloud Text-to-Speech API, the app sends the typed or selected text string to Google’s servers to generate audio. This text is processed solely for generating the audio clip and is not stored or reused by the app.

YouTube Integration
Users may input YouTube video or clip URLs for walk-up music. These are loaded directly within a local WebView for playback and are not transmitted to external servers or collected by the app.

Third-Party Services and SDKs
AnnouncingDJ integrates with the following third-party services:

  • Google Cloud Text-to-Speech API – Used to generate voice clips from user input text. Only the voice text string is sent; no personal identifiers are transmitted.

  • Unity Ads – Used to display banner and rewarded ads to unlock premium voice features. Unity may collect device identifiers (e.g., advertising ID), app usage patterns, and ad interaction metrics to serve and optimize ads. This data is handled in accordance with Unity’s privacy policy.

Data Shared or Collected via Third Parties

  • App Interactions: Collected and shared for analytics and ad personalization

  • Voice Recordings: Collected (stored locally); not shared

  • Other Audio Files: Collected (stored locally); not shared

  • Crash Logs & Diagnostics: Collected and shared to improve performance

  • Device ID (e.g., Ad ID): Collected and shared for advertising and analytics

All data sent off the device is transmitted securely using encryption (HTTPS).

Permissions Used

  • Microphone – Used only for recording custom name audio. Audio remains on the user’s device.

  • Storage – Used to read and save audio files and team data.

  • Internet Access – Required for YouTube playback, ad services, and TTS audio generation.

Data Encryption
Local data such as team lineups and audio clips is not encrypted on the device. However, all data transmitted off the device (e.g., to Google or Unity services) is encrypted in transit.

User Control
Users can:

  • Create, modify, or delete teams and players

  • Delete or replace recorded and TTS-generated audio files

  • Choose between recording or generating audio

  • Choose whether to view ads to unlock additional voice generation

No accounts are required, and the app does not permanently store any user-submitted data.