Last updated: October 2026
CallAttend ("we", "us") operates the callattend.com website and AI phone answering service. This policy explains how we collect, use, and protect your information.
When you use our service we collect: your name and email address, your business details, phone numbers assigned to your account, call recordings and transcriptions, and usage data (call durations, timestamps).
We use your data to: provide and improve our phone answering service, send you voicemail notifications and transcriptions, process your subscription and billing, and communicate with you about your account.
Calls are processed by AI and may be recorded and transcribed. Callers are informed at the start of each call with the message: "This call may be recorded and transcribed." For voicemail services, callers hear: "Your call will be transcribed by CallAttend." Recordings are stored securely and are accessible only to you and authorised administrators.
To deliver our service, call audio and transcribed text are processed by third-party providers in the following categories:
We select providers based on quality, reliability, and data protection standards, and may change providers from time to time. All providers process data under appropriate contracts and data processing agreements. Data is processed within the EU/UK where possible. Call audio may be relayed, without being stored, through our servers in the United States and Singapore when a user is in or near those regions. A current list of specific sub-processors is available on request via our contact form.
Call recordings and transcriptions are retained for 90 days unless you request earlier deletion. Account data is retained while your account is active.
When someone calls a number managed by CallAttend, we process: their phone number (caller ID), the audio of their call, and any information they provide during the conversation (name, company, message). This data is shared with the account holder (our customer) via email notifications, dashboard access, and optional Slack integration. Callers are informed of recording and transcription at the start of each call.
The CallAttend app for iPhone (from the App Store) and for Android (from Google Play, as com.callmonitor.callattend) rings, answers and places calls on your business number. The two apps collect the same things for the same reasons, and where they differ this section says so. Everything below is tied to your CallAttend account and to the device row for that handset. We do not hold app data that is not attached to an account.
What it is used for. Everything the apps collect is used only to run the app for you: signing you in, ringing your phone, carrying your calls, showing your calls and messages, and working out why a phone did or did not ring. None of it is used for advertising or analytics, and none of it is shared with or sold to anyone for their own use. The apps contain no advertising or analytics SDK. Everything the apps send to us travels over an encrypted (HTTPS) connection.
Signing in and your account. You sign in with the email address on your CallAttend account, and we email you a one-time code. The app then holds your account, user and device identifiers so that what it shows and sends belongs to you. The app shows the calls, messages and voicemail on your account, including recordings you choose to play; these are the same records described in the sections above.
Calls and the microphone. The app uses the microphone only while a call is connected, so you can be heard. Call audio is carried by our telephony provider and is covered by the "Call recordings" and "Third parties" sections above. The app does not record or store call audio itself.
Push notifications. An incoming call reaches your phone as a push notification, so the handset holds a push token, which the calling SDK on the handset registers with our telephony provider. For calls, our servers record only whether the handset currently holds that token. The notification tokens described below are kept with the device row and used only for message alerts.
Calling registration. To make and receive calls the app requests a short-lived access token (one hour) naming an opaque per-device identifier. It is returned once and is never logged or stored by us.
Install identifier. When the app adds this phone to your account it sends an install identifier, so that a repeated request, or a reinstall, finds the same device instead of adding another. On iPhone it is a random value the app makes once. On Android it is derived on the phone from Android's app-scoped identifier for this app (which Android resets on a factory reset) by a one-way hash; the Android identifier itself is never sent to us or logged. It is kept with the device and deleted with it.
Facts the app reports about itself. When the app asks for that token it may also report a fixed list of facts about the app and the handset, kept so we can explain why a phone did or did not ring: app version and build number, calling SDK version, whether a push token is held, microphone and notification permission states, whether the phone is saving power (Low Power Mode on iPhone, Battery Saver on Android), the device model identifier (for example "iPhone15,3"), and whether the phone has warned the app it is short of memory. The iPhone app also reports its push environment (sandbox or production), its Background App Refresh state and the iOS version; older iPhone builds also reported free storage in whole megabytes. The Android app also reports whether full-screen incoming calls are allowed, whether the app is exempt from battery optimisation, Data Saver's state for the app, the network type (Wi-Fi or mobile data, never the network's name), the device manufacturer and model (for example "samsung" and "SM-F966B"), and the Android version and API level. The Android app also sends the name the phone shows for itself in its Settings (for example "Galaxy Z Fold8", or a name you gave it), which we use only to name the device on your dashboard; it is not logged. You can rename a device on the dashboard at any time, and a name you type is never replaced. We also record when the app was last seen and how many access tokens it has been issued. Anything outside that list is discarded on arrival. These are kept while the device is on your account and are deleted with it.
Diagnostics. The app keeps a small log of call events on the phone. A copy is sent to us when you press Send diagnostics, and also automatically after a call that went badly (for example one that lost audio quality, reconnected or failed to answer), so the record survives the app being closed. It carries call metadata only: event names, timings, durations, connection and registration state, error codes and messages, call-quality warning names, network type and cellular generation, audio device type, and the call identifier, together with your account, user and device identifiers. This is also how we see an app error on iPhone, which has no separate crash reporting service. The Android app sends crash reports (device model, OS version, app version, stack trace) to Google Firebase to diagnose faults. Anything shaped like a phone number or an email address is blanked, and no audio, transcript, phone number or caller name is stored. Diagnostic logs are deleted 30 days after upload.
What the apps do not collect. The apps are built to refuse the following and they are not sent to us: location, your phone number, your contacts, call content, any advertising or cross-app identifier (including IDFA and IDFV on iPhone and the advertising ID on Android), the list of installed apps, an iPhone's device name (for example "Richard's iPhone"), the Wi-Fi network name, battery level, locale, timezone, and mobile carrier. The apps do no advertising or cross-app tracking of any kind.
Deleting your data. To have your account and everything held under it deleted, including the device rows and diagnostics above, email [email protected] from the address on the account; the Support page says what is removed.
Under UK GDPR you have the right to access, correct, or delete your personal data. Contact us via the contact form on our website.
CallAttend is operated by Callmonitor Ltd. Contact us