CELESTIFY LTD

Privacy Policy

Updated October 9, 2026

Who operates our services

CELESTIFY LTD operates PrimeAlarm and the shared product analytics service used by PrimeAlarm and STAY. Contact contact@celestifyltd.com for privacy questions or deletion requests. Other products may provide additional product-specific notices.

PrimeAlarm wake-up calls

Alarm preferences and wake-up history are stored on your device. To schedule and deliver wake-up calls, our server processes the phone numbers you enter, a randomly generated installation identifier, alarm scheduling information and call activity. If you enable trusted-contact calls or texts, we process that contact's number for this purpose. Add only a contact who agrees to receive these communications. Calls and texts use Twilio. Notification and system-alarm permissions are optional and can be managed in iOS Settings.

PrimeAlarm does not require scanning a barcode or photographing an object. Saving our caller number to Contacts is optional. We do not upload your address book.

PrimeAlarm product analytics

Starting with version 1.0.5 build 20, PrimeAlarm sends independent contributions to daily usage and subscription counters. These include app opens, paywall views, product availability, purchase and trial outcomes, errors, restores, onboarding and wake-up interactions. Counts are grouped by day, app version, build, environment and a limited set of product or outcome categories. They help us decide what to fix and improve.

Analytics payloads contain no installation, user, device, session, transaction, alarm or campaign identifiers, phone numbers, custom text or precise event timestamps. We do not keep individual activity histories or join these counts to call-delivery records. Each contribution has a fresh random retry receipt, unrelated to any other event or person, to avoid double counting. The server stores daily totals and separately stores only a hash and expiry for each retry receipt. Receipt hashes expire after seven days and are removed on the next count write; daily totals older than 90 days are also removed on count writes. Requests more than seven days old are rejected. Network addresses are processed transiently for delivery and rate limiting, without analytics access logs. Pending contributions are stored on the device until delivery or rejection.

Earlier identified PrimeAlarm analytics submissions are no longer accepted. Wake-up-call scheduling identifiers remain necessary for delivering calls and are not used for these analytics. Apple processes payments. PrimeAlarm does not use AdServices campaign attribution, IDFA, fingerprinting or cross-company tracking in this version.

STAY product analytics

Instrumented versions of STAY send app-scoped installation identifiers, session and event identifiers, app and build version, environment, event times, screen and feature interactions, subscription product availability, purchase attempts, verified purchase and trial outcomes, cancellations, pending approvals, errors and restore outcomes. STAY can report that a sentence was added or a focus session started or completed, without sending sentence text, camera images or face data. Analytics may begin before purchase. These records help measure reliability, usage and conversion. They are pseudonymous, not anonymous; verified transactions may include product and transaction identifiers and payment or trial type. They exclude phone numbers, contacts, card information and free-form error messages. STAY does not use IDFA, fingerprinting or cross-company tracking for this measurement.

Campaign measurement

In STAY versions that support it, Apple's AdServices framework provides an attribution token which is sent to Apple to request Apple Ads campaign attribution. We store attribution status and campaign identifiers, not the token. App Store campaign links for other channels provide aggregate reports and do not themselves identify an individual inside the installed app. We do not sell these records or share them with other companies for cross-app advertising.

Hosting and retention

The shared analytics collector is hosted on DigitalOcean infrastructure in New York, United States (nyc1). STAY versioned analytics records are deleted from the active collector 90 days after receipt, through a cleanup that runs on startup and hourly. Normal active-file retention is therefore up to 90 days plus one hour. Service or storage outages can delay cleanup. As checked on October 5, 2026, no provider volume snapshots, attached-server backups or scheduled analytics backup jobs were configured for this collector. We do not promise instantaneous deletion from provider-managed underlying storage. If backup arrangements change, the applicable retention must be documented and deletion handled when data is restored.

Older operational analytics and records needed for call delivery or support are separate from this new 90-day rule. We retain those only as needed to operate the service, handle support and meet applicable obligations. Contact us to request deletion. Pending analytics events may remain on your device until delivery; removing the app clears its local app data, subject to your own device backups.

Your choices and requests

PrimeAlarm aggregate counts have no analytics user ID to copy or individual history to retrieve. Contact us separately about call-delivery or support records.

In instrumented STAY versions, use Copy analytics ID in Settings and send that identifier with a deletion request to contact@celestifyltd.com. Please name the app. Server deletion does not itself disable collection on an installed app; close or uninstall it to prevent queued or new events from being sent while your request is handled. You can ask separately about wake-up-call or support records. We may need information to locate your records and verify your request.

Messages you choose to send to support contain the information you include. Please avoid sending unnecessary sensitive information. Manage or cancel subscriptions in your Apple account settings; deleting analytics does not cancel a subscription.