Privacy policy

Recalling is an outbound calling platform sold to businesses. Two different groups of people appear in it, and the answers below differ for each.

If you are a visitor to this website, the only personal information we take from you is what you type into the contact or trial form.

If a business called you using Recalling, that business decided who to call and why. It holds your record and instructs us; we process on its behalf. Ask it first — it can correct your number, mark you do-not-call, or delete a recording from inside the product. If you cannot reach it, write to us and we will pass your request on and follow up.

From this website: the name, email address and message you type into the contact or trial form, and the IP address the submission came from — the address is what lets us rate-limit abuse of a public form. We do not put any of it in a database. The submission is delivered to our inbox as an email, and that email is the only copy.

From a customer's account: the names, work email addresses, roles and team memberships of the people who sign in; and, for the audit log, sign-in times, session records, IP address and browser user agent.

About the people a customer calls, all of it supplied or generated by that customer's use of the product:

Recording is part of how the product works, not an add-on. By default every call placed through Recalling is recorded: the requirement sits at the organization level, so a campaign or an individual agent cannot turn it off for a single call. An administrator of a customer's organization can relax that requirement for their own organization.

The audio is fetched from the carrier that carried the call and stored as an object in Amazon S3 in the Mumbai (ap-south-1) region, encrypted at rest with a customer-managed key. It is never served from the carrier's own URL: playback issues a signed link that expires within minutes and is scoped to the person who asked for it.

Calls are transcribed, and the transcript is stored encrypted segment by segment. It is used for the live view an agent sees during the call, for automated summaries and outcomes afterwards, and for search.

A call placed by an AI profile announces itself: the opening line says the caller is an AI assistant and that the call may be recorded.

We do not automatically redact personal information out of transcripts. If a caller reads out a card number or a health detail, it is in the transcript until the record is deleted.

Every contact carries a consent state. A contact marked do-not-call or opted out is not dialed. The check runs before the number leaves the queue, in campaigns and in manual dialing alike, and it cannot be overridden from inside the app.

Whether documented consent evidence is required before a recorded call is a setting each customer controls, and it is off by default. That means the customer — not Recalling — is responsible for having a lawful basis to call the people on its list and to record those calls.

Campaign calling is confined to a calling window evaluated in the contact's own timezone; the default is 09:00 to 21:00 and a campaign cannot dial outside it. A manual dial made by an agent from the dashboard is not held to that window.

On the messaging channels, a STOP reply or an unsubscribe click suppresses further messages to that address or number and cannot be overridden by anyone inside the app.

We use it to run the product, and for nothing else:

We do not build or train AI models on customer contacts, recordings or transcripts, and we do not sell personal information or share it for advertising.

Where the providers we use offer it, we ask them not to retain the data either: transcription is configured with provider-side logging disabled, and language-model requests are sent with storage turned off.

These are the third parties that can see customer data while delivering the service. The ones marked optional are used only where a customer's configuration selects them.

The application and its database run on a single virtual machine we operate. Neither the database nor the cache is reachable from the internet.

Call recordings are stored in Amazon S3 in Mumbai (ap-south-1). Transactional email is sent through Amazon SES in the AWS region our SES account is configured in, which is not necessarily the region the recordings are in; ask us and we will name it. Only the recipient address and the body of those emails are processed there. Call audio is carried by the customer's carrier and is processed in that carrier's region. The speech and language providers above are called at their own global endpoints; we do not currently pin them to a region.

How long we keep things:

Phone numbers, email addresses, transcripts, AI-generated text and the before/after states in the audit log are encrypted in the database with AES-256-GCM under a versioned key. Exact-match lookup on a number or an address is done through a keyed hash, so the plain value never has to be indexed.

Recordings in object storage are encrypted at rest with a customer-managed key, and are only ever served over a signed link that expires within minutes.

Phone numbers shown to agents are masked to the last four digits, and audit metadata is masked again when it is read. Access is deny-by-default: a member sees the teams they belong to, and an agent sees their own calls rather than the whole floor's.

Every privileged action is written to a hash-chained audit log, so a modified or missing entry can be detected rather than guessed at.

No system is perfectly secure, and we do not claim certification under any particular security framework. If that matters to your procurement, ask us where we are and we will tell you plainly.

This website sets no cookies. It runs no analytics, no tag manager and no advertising script, and its fonts are served from this domain rather than fetched from a third party.

The product behind sign-in sets four cookies, none of them for tracking or advertising:

You can ask for a copy of the personal information we hold about you, ask us to correct it or delete it, ask who we have shared it with, withdraw a consent you gave, and complain about how we have handled it.

If a business called you using Recalling, that business holds your record. Ask it first: it can correct your number, mark you do-not-call, or delete a call recording — and a deleted recording is destroyed in storage, not merely hidden. If you cannot reach it, write to us and we will pass your request on and follow it up.

If you are a customer of ours, write to us and we will act on the request for your account.

We acknowledge a request within 3 working days and answer it within 30 days. If we need longer, we will say so and why.

If you are unhappy with how we have handled personal information, or with a reply you have had from us, write to our grievance contact with “Grievance” in the subject line. This address is for complaints about personal data; for anything else, use the contact page.

We update this page when what we do changes, and the date at the top is the date of the last change. Where a change materially affects how we handle personal information, we email account administrators before it takes effect.

Questions about this policy, or about anything we hold — write to us and a person will answer.