Privacy Policy
Alarm Announcer Pro - iOS
Last Updated: 3 July 2026
1. Introduction
Your privacy is important to us. Alarm Announcer Pro is published by bazzaztech (bazzaztech.com). This policy explains exactly what data the app collects, why, and how long we keep it.
2. Summary
| Data | Collected? | Sent off-device? | Stored on server? |
|---|---|---|---|
| Real name, email, phone | No | No | No |
| IDFA / IDFV | No | No | No |
| Anonymous install UUID | Yes | Yes | Yes |
| Device model + OS version | Yes (crash reports only) | Yes | 30 days |
| Approximate location | Yes (Celestial Arc, optional) | No — on-device only | No |
| Voice recording sample | Yes (Studio, with consent) | Yes | Not stored — discarded immediately after processing |
| Generated voice clone | Yes (Studio) | Yes | Not stored — streamed to your device |
| Purchase receipt | Yes (credit purchases) | Yes | Yes (audit log) |
| Apple ID subject token (optional) | Yes (if you Sign in with Apple) | Yes | Yes (anonymous opaque ID only) |
| Crash stack traces | Yes (opt-out available) | Yes | 30 days |
3. Data We Collect and Why
3.1 Anonymous Install Identifier
On first launch we generate a random UUID and store it in UserDefaults on your device. This identifier is not your Apple ID, IDFA, IDFV, or any value that could identify you personally.
Purpose: Authenticate API requests via JWT tokens, associate purchased credits with your installation, and enable server-side credit tracking as the source of truth.
3.2 Crash Reports
If the app crashes, the following is recorded locally and sent to https://bazzaztech.com/api/crash on the next launch:
- App version and build number
- iOS version
- Device model (e.g., "iPhone15,3")
- Anonymous install UUID (see §3.1)
- Crash type (exception or signal)
- Full stack trace
- Last 20 in-app breadcrumbs (screen names and actions)
- Timestamp
What we do NOT include: Real name, email, Apple ID, IDFA, IDFV, phone number, or any sensor data.
Opt-out: Go to Settings → Privacy → Send Crash Reports and disable the toggle. All pending crash reports are deleted immediately.
Retention: Crash reports are kept for 30 days and then automatically purged.
We use our own self-hosted crash reporting — no third-party SDK such as Firebase Crashlytics or Sentry is used.
3.3 Celestial Arc (Optional)
The Celestial Arc shows a decorative sun/moon position indicator on the main screen. If you enable "Accurate Sun & Moon Times", the app requests a one-time location fix from CoreLocation to compute precise local sunrise and sunset times. This calculation happens entirely on your device — your coordinates are never sent to any server. Moon phase is computed locally from the date with no location required.
3.4 Voice Cloning — Studio (Optional)
If you use the Studio feature to create a personalised announcement voice:
- Recording: You record a 15–25 second voice sample using the device microphone. The audio stays on your device until you tap Submit.
- Upload: The raw audio file (M4A/AAC, up to 10 MB), your chosen announcement text, and your anonymous install UUID are sent to
https://bazzaztech.com/api/alarmannouncerpro/clone, which forwards the audio directly to our AI provider (Cartesia). Your recording is never stored on our servers. - Processing: Cartesia clones the voice from your sample and synthesises the announcement audio. The voice profile exists only for the duration of the API call and is permanently deleted by Cartesia immediately after synthesis completes.
- Download: The finished audio is streamed back to your device (
Documents/cloned_announcements/) and is not retained on our servers. - Local storage: Generated clones are kept in the app's private sandbox, accessible only to this app.
- Sharing: If you share a clone via the Clone Share feature (AirDrop, Files, iMessage, etc.), the export and transfer happen entirely on your device — we do not receive or log any share activity.
Microphone permission: Used only while you are actively recording in Studio. The app does not access the microphone in the background.
Before using Studio you must accept the in-app Studio Terms & Conditions, which are shown the first time you tap Record.
3.5 In-App Purchases (Credits)
Credit packs are purchased through the Apple App Store using StoreKit 2. Apple handles all payment processing. We receive only a JWS (JSON Web Signature) receipt token to verify the purchase server-side.
- The JWS token is stored as a replay-protection guard (to prevent a token being used twice).
- We log the event type, product ID, platform, credit amount, and timestamp for accounting and fraud prevention.
- We do not receive or store your payment card number, Apple ID email, or billing address.
Apple's App Store Privacy Policy governs their processing.
3.6 Content Store
The app fetches a catalogue of announcement audio files and ringtones from our servers. Requests include only your anonymous install UUID and a JWT bearer token. No browsing history or usage patterns are recorded. Downloaded audio is stored in the app's private sandbox.
3.7 AlarmKit
The app uses Apple AlarmKit to schedule and fire alarms reliably, even in Silent mode and Focus modes. Alarm data is stored by the operating system on your device. No alarm content or schedule information is transmitted to our servers.
3.8 Social Account Linking — Sign in with Apple (Optional)
To protect your credits from being lost if you uninstall and reinstall the app, you can optionally sign in with your Apple ID. After a credit purchase, the app displays a "Protect your credits" prompt.
- What we receive: An opaque Apple subject identifier — an app-specific, non-reversible token provided by Apple's Sign in with Apple framework. This is not your Apple ID email address or name. Apple never shares your real Apple ID with us.
- What we store: Only this opaque subject ID, linked to your store account. We never store your Apple ID email or any other personal information.
- How it works: Your Apple subject ID is sent to our server, which maps it to your credit balance. If you reinstall the app, signing in with the same Apple ID restores your credits — even on a different device.
- Revoking access: You can revoke app access via Settings → [Your Name] → Sign in with Apple on your iPhone, or email [email protected]. After revocation, credits revert to the current install's anonymous ID.
- This step is entirely optional. Credits function without signing in; signing in only ensures credits survive a reinstall.
Sign in with Apple is handled entirely by Apple's AuthenticationServices framework. See Apple Privacy Policy.
4. Data We Do NOT Collect
- Real names, email addresses, or phone numbers
- IDFA (Identifier for Advertisers) or IDFV (Identifier for Vendors)
- Device serial number
- Contact lists or calendar data
- Continuous location tracking
- Usage analytics or behavioural tracking
5. Data Storage and Retention
All app settings and preferences are stored locally on your device in UserDefaults. Server-side retention periods are as follows:
| Data | Retention |
|---|---|
| Install UUID + credit balance | Until you request deletion |
| Purchase audit log | 7 years (financial record requirement) |
| Voice recording sample (server) | Not stored — discarded immediately after processing |
| Generated voice clone (server) | Not stored — streamed directly to your device |
| Crash reports | 30 days |
| JWT tokens | 90 days per token; refreshed automatically |
| Weather cache (local only) | Up to 2 hours |
| Apple social account link (optional) | Until you request deletion |
6. Your Control and Rights
You can manage or revoke permissions at any time in your device's Settings app:
- Location: Revoking disables weather announcements and accurate Celestial Arc times.
- Microphone: Revoking disables voice recording in Studio.
- Crash reports: Disable in Settings → Privacy → Send Crash Reports.
To request deletion of your server-side data, email [email protected] with your anonymous install UUID (found in Settings → Support → Install ID). We will delete your credit balance and purchase history records. Purchase audit records required for legal or financial compliance cannot be deleted.
7. Third-Party Services
- Apple App Store — in-app billing. See Apple Privacy Policy.
- Apple AlarmKit — alarm scheduling. Governed by iOS / Apple Privacy Policy.
- Sign in with Apple — optional social sign-in to protect credits across reinstalls. Apple provides only an opaque app-specific subject ID. See Apple Privacy Policy.
- Cartesia — AI voice cloning and synthesis. See Cartesia Privacy Policy.
- Cloudflare — API gateway for all server requests. See Cloudflare Privacy Policy.
8. Security
All network communication uses HTTPS (TLS 1.2+). API requests are authenticated with per-install JWT tokens. We do not store passwords. Voice data is routed via our Cloudflare-gated API rather than directly to the AI provider.
9. Children
This app is not directed at children under 13. We do not knowingly collect any data from children.
10. Changes to This Policy
If we make changes, we will update the "Last Updated" date above. Continued use of the app after a change indicates acceptance of the updated policy. Significant changes will also be notified in-app.
11. Contact Us
Questions? Contact us here or email [email protected].