Published October 7, 2026

Trumpet Privacy Policy

Trumpet: Call Alerts is operated by Adriel Acevedo. Contact trumpetcallalerts@gmail.com for privacy questions or data requests.

Voice calls and audio-output status

Trumpet sends voice audio and audio-output reports through LiveKit to connect callers and announce output changes. Network transport is encrypted; end-to-end encryption is not enabled. Trumpet does not record or transcribe call audio. Audio-output reports do not establish who can hear a call or guarantee privacy.

Phone-number registration

Direct contact calling requires verification of your own supported mobile number through Twilio Verify. Twilio processes your number and verification information and may retain service records under its own policies. Trumpet temporarily stores a verification challenge containing your number for up to ten minutes, with expired records removed during cleanup. It stores a keyed phone-number identifier associated with a random account identifier, verification date, discoverability preference, and expiring authentication sessions. These identifiers are associated with your registration and are not treated as anonymous data. Reverification may be required.

Optional contacts and discovery

Contacts access is optional and follows the contacts permissions you grant on your iPhone. Contact names stay on your device. Checking a number sends it to Trumpet for normalization and matching. Choosing Find Trumpet contacts sends numbers from the contacts you allowed in batches. Lookup numbers are processed transiently and are not saved as an uploaded address book in Trumpet's directory. Matching identifies discoverable, verified registrations, not everyone who has downloaded the app. You can also check a number manually without granting contacts access.

Trumpet retains caller and recipient account references and call-state metadata for direct calls. This is distinct from transient contact lookup. Invitation messages are prepared for you to send using your chosen messaging service; Trumpet does not send those invitations automatically.

Incoming calls

Trumpet stores your iPhone's Apple VoIP notification token, notification environment, and associated registration to deliver incoming calls. Notification payloads contain opaque caller and call references and expiry information, rather than contact names, phone numbers, call audio, or call-access credentials. Apple and infrastructure providers process notification delivery and service metadata.

Invitations and purchase verification

The Railway-hosted service stores room identifiers, hashes of invitation and call-close credentials, hashed guest-device claims, and expiry information. Invitation records are deleted following successful cleanup; failures can delay cleanup and provider backups may retain earlier copies.

Apple-signed app transaction information and a device-verification identifier are sent to the service to verify app acquisition and authorize hosting. The service stores a one-way purchase identifier with an active call to enforce capacity limits. It does not intentionally persist or log the signed purchase proof or raw device-verification identifier.

Favorites and Recents

Favorites stores references to contacts you choose on this iPhone. Recents stores up to 100 outgoing call attempts and answered incoming contact calls, including the other account reference, date, and call direction. These lists are stored in protected device-local storage and are not uploaded as Favorites or Recents lists. Contact names are resolved from the contacts you permit on the receiving device; names are not stored in recent-call entries. Recents is separate from the temporary audio-output timeline and remains after restarting the app. You can clear Recents, remove favorites, or delete phone registration to clear these local lists. Server call-service records described in this policy are separate.

Device storage and service records

Trumpet stores preferences and credentials needed to operate the app on your iPhone, including protected credentials in Keychain. The current call timeline is held in memory and cleared by a new call or app restart. The server also retains registration, notification, and call-service records described above. Verification-budget accounting retains an aggregate reserved-cost total.

Providers and processing locations

Apple, Twilio, LiveKit, Railway, and the website and email providers process information needed to deliver their services. This may include network addresses, connection and session statistics, delivery information, diagnostics, fraud prevention, billing, logs, and backups. Provider retention varies; deleting a Trumpet registration does not necessarily erase independently retained provider records. Processing is not exclusively in the United States: the inspected LiveKit project uses a United States region and the Railway server uses a European region. Locations and provider practices may change.

Trumpet uses this information for functionality, authentication, incoming calls, service reliability, and abuse prevention. It does not include an advertising SDK or use these data for advertising tracking.

Your choices and deletion

You can manage contacts and microphone permissions in iPhone Settings. In the redesigned app, open Settings > Registration & incoming calls to turn off discoverability or delete your phone registration. In earlier versions, these controls are in Contacts. Turning off discoverability prevents new discovery and direct-call initiation through that registration; it does not erase an ongoing call.

Deleting registration removes the directory account, authentication sessions, outstanding verification challenges, associated block records, and notification registration. Active direct-call records are closed and removed during cleanup. It does not delete your App Store purchase or necessarily remove provider logs, backups, billing, security, or legally retained records. Contact support for questions about service or support records.

Support email and this website

If you email support, the operator and email provider receive your address and message. Send only information needed for your request. The support website contains no app-owned advertising or analytics scripts or forms. Its hosting provider receives ordinary connection information when serving pages.

Updates

We may update this policy when Trumpet’s data practices change. Contact trumpetcallalerts@gmail.com with questions about this policy.