← Back to home

Privacy Policy

EFFECTIVE: 18 September 2026  ·  LAST UPDATED: 18 September 2026

This policy explains what happens to your call recordings. The essential fact first: recordings are created and stored on our servers, not on your iPhone. Everything else follows from that, so please read section 3 before you record anything.

Who we are

Call Recorder Tapecall ACR is published by the company identified below. Under the GDPR, the UK GDPR and the Turkish Personal Data Protection Law (KVKK) we are the data controller for the personal data described here — the party that decides why and how it is processed, and the party you can hold responsible for it.

What this policy covers

It covers the iOS app, the recording service it connects to — including the telephone line the app dials and the servers that create and store recordings — and this website.

It does not cover your mobile network operator, who carries your calls under its own terms; Apple, who operates the App Store and processes your payment; or any service you choose to send a recording to. Once you share a recording outside the app, that copy is beyond our control.

How recording actually works, and why it matters here

iOS does not allow any app to record the audio of a normal phone call. There is no permission and no setting that changes this. This app works around the restriction the way conference calls work: when you start a recording, the app places a second call to our recording line and merges that line into your conversation.

The consequence is the most important sentence in this policy: the audio is captured on our servers, not on your iPhone. The recording file is created there and stored there. When you play a recording back, the app streams it from our server.

  • We hold the audio of your calls — the original, not a copy you sent us afterwards.
  • The other person on the call is recorded too, and their voice is stored alongside yours. They are not our user and may not know we exist.
  • If your network or plan does not support three-way calling, the app cannot record. That is a limitation of the telephone network, not a fault in the app.

Who controls what

We are the controller for the recordings on our servers, the metadata attached to them, your subscription status, and the advertising and diagnostic data described below. We decide that recordings are stored, where, for how long and who can reach them — so we are a controller in our own right, not merely a technical service acting on your instructions. We say this deliberately, because claiming to be only a processor would be convenient and untrue.

You are also responsible in relation to the other person on the call. You choose whom to call, when to record, and whether to tell them.

What we process

  • Recording content: the full audio from the moment you start recording — your voice and words, and those of every other participant. Conversations are unbounded, so a recording may incidentally contain sensitive information. We do not listen to it, index it or analyse it, but we do store it.
  • Call metadata: the telephone numbers involved, the date, the time, the duration, and the contact name shown in your history.
  • Titles you create when you rename a recording.
  • Subscription data: whether a subscription is active, its renewal date, and the anonymous transaction identifier Apple gives us. We never receive your card details or Apple ID password.
  • Technical data: device model, iOS and app version, language and region, crash reports, and the IP address your device connects from.
  • Advertising data, described below.

Our lawful bases

  • Creating, storing and playing back the recordings you ask for — performance of our contract with you (GDPR Art. 6(1)(b); KVKK Art. 5(2)(c)).
  • Holding the other party's voice and data — our legitimate interests in operating the service you asked for (GDPR Art. 6(1)(f); KVKK Art. 5(2)(f)). See the next section; this basis is qualified and we do not pretend otherwise.
  • Managing your subscription and meeting tax and accounting obligations — contract and legal obligation.
  • Keeping the service secure — legitimate interests.
  • Crash reporting and analytics — legitimate interests, and your consent where the law requires it.
  • Personalised advertising — your consent.

We do not process recordings to identify anyone by the sound of their voice. There is no voiceprint, no speaker recognition and no biometric matching, so we do not process biometric data.

The other person on the call

This is the hardest problem this service creates, and we would rather state it than leave it unsaid.

Your obligation: in most countries, recording a telephone conversation without the knowledge and agreement of everyone on the line is unlawful, and in some — including Türkiye — it can be a criminal offence. By using this app you undertake to tell every participant that the call is being recorded and to obtain their agreement before you start. We cannot verify that you have done so and we cannot discharge that duty for you.

Our obligation: your consent does not make the other party's data lawful for us to hold. Consent must come from the person whose data it is, and the other party has given us nothing. We therefore rely on legitimate interests, and we limit the processing as far as we can — we store the recording, we do not analyse it, we do not use it for advertising or any other purpose, we build no profile of the other party, and we give them the same rights against us that you have.

Where recordings are stored, how long, and what delete does

Recordings are created and stored on servers operated for us. They are not kept on your device.

The hosting provider, the country of storage and the retention period are being finalised and will be stated here before this service is offered further.

When you delete a recording in the app, the file is deleted from our server. It is a real deletion, not a hidden item in your list.

Invoicing and transaction records are kept for the period Turkish tax and commercial law requires, even after you close your account. Those records never contain recordings.

Advertising — Google AdMob

The app is free to download and shows advertising supplied by Google AdMob. To serve ads, the AdMob SDK sends Google your device's advertising identifier where you have permitted it, a device identifier, IP address, device model and operating system, app version, language and region, and how you interacted with the ads.

For advertising, Google acts as an independent controller under its own privacy policy. We do not receive the profile Google builds and we cannot delete it for you — you use Google's own controls for that.

App Tracking Transparency: on first launch iOS asks whether the app may track you across other companies' apps and websites. If you decline, your advertising identifier is not shared and the ads you see are not personalised. You can change the answer at any time in Settings → Privacy & Security → Tracking.

If you are in the EEA, the UK or Switzerland, a Google-certified consent form is shown before personalised advertising is enabled, and you can change that choice from the privacy option in the app.

Analytics and crash reporting — Google Firebase

We use Firebase for two things only: understanding in aggregate how the app is used, and receiving automatic reports when it crashes. Firebase receives a randomly generated app-instance identifier, device model, operating system and app version, language and region, in-app events such as which screens are opened, and crash diagnostics.

For these purposes Google acts as our processor. No audio, no transcript and no fragment of a recording is ever sent to Firebase or to any analytics service.

Subscriptions and payments

The app is free to download and offers an auto-renewing subscription. All payments are handled by Apple. We never see your card number, bank details, billing address or Apple ID credentials; from Apple we receive only confirmation that a subscription is active, which product it is, the renewal date and an anonymous transaction identifier. Managing and cancelling a subscription is done in your Apple account settings.

Who else we disclose data to

We do not sell personal data. We do not trade recordings. We do not give recordings to advertisers or data brokers.

  • Our processors — the providers that operate the recording line and the servers — acting on our instructions under written contracts.
  • Google, for the advertising described above.
  • Where we are legally required to: a valid order from a competent authority. We assess each request, refuse those that are overbroad or improperly made, and, unless the law forbids it, tell the affected user.
  • An acquirer, if the business or this app is sold — with equivalent protections in place and prior notice to users.

International transfers

We are established in Türkiye, which is not covered by a European Commission adequacy decision. Advertising, analytics and crash data are processed by Google in the United States and elsewhere; Google relies on the EU–US Data Privacy Framework and on the European Commission's Standard Contractual Clauses. Transfers of personal data out of Türkiye are made on the safeguards KVKK Art. 9 provides.

Your rights

Under the GDPR, the UK GDPR and KVKK Art. 11 you may ask us to tell you what we hold, give you a copy, correct it, delete it, restrict or object to how we use it, port it, or withdraw a consent you gave.

Write to the address at the end of this policy and say which right you are using. We will ask you to prove who you are before we release or delete anything — handing a recording of your calls to someone impersonating you would be a far worse outcome than a slow answer. We reply within one month under the GDPR and within thirty days under KVKK.

One honest limit: a recording contains at least two people. We give you a copy of a recording you made, because you were a party to it. We will not give a copy of a recording to anyone else, because that would disclose your voice and words to them.

If you were recorded but do not use this app

If someone recorded a call with you using this app, we may hold that audio. You did not agree to that with us, and you have rights against us regardless.

Write to us with the telephone number involved and, as closely as you can, the date and time of the call. We will search for recordings matching that number. You may ask us to confirm whether we hold one, to stop holding it, or to delete it — and when you object or ask for erasure, we delete it, unless the law requires us to keep it for a specific legal claim. We do not weigh our convenience against your objection.

Two limits we will be honest about. We will not give you a copy of the audio and we will not always tell you who made it, because the recording contains another person's voice and reveals who they called and when; that is a matter for a court or a prosecutor, and we comply with a lawful order. And we can only find what you can help us identify — a telephone number is the only key we have.

Security

Traffic between the app and our servers is encrypted in transit. Access to stored recordings is restricted to the people who need it to keep the service running, and we treat any unauthorised access to recording audio as a high-risk event by default.

Children

This app is not for children and you must be an adult to use it. We do not knowingly collect personal data from children. If we learn that a child has used the app, we close the account and delete the recordings.

If something goes wrong

If personal data we hold is lost, exposed or accessed without authorisation, we investigate and contain it immediately, notify the competent supervisory authority without undue delay and within 72 hours where the breach is likely to risk people's rights, and tell affected individuals directly where the risk to them is high — including people who are not our users, where a recording containing them is affected and we are able to reach them.

Automated decisions

We make no automated decisions that produce legal effects or similarly significantly affect you. We do not transcribe, analyse, score or profile the content of recordings.

Your responsibilities when recording

The law on recording telephone conversations differs sharply between countries and, in the United States, between states. In many places it is lawful only if every participant knows and agrees; in others, including Türkiye, recording or disclosing a private conversation without consent can be a criminal offence. Before you record: tell every participant, get their agreement, and if you are unsure whether it is lawful in your situation, do not record. Sharing a recording can carry its own, separate liability.

Changes and complaints

We update this policy when the app or our handling of data changes; the current version and its date are always at this address, and we tell you in the app before a change that materially affects your rights takes effect.

If you think we have handled your data wrongly, tell us first — it is usually the fastest fix. You may also complain to a supervisory authority: in Türkiye the Kişisel Verileri Koruma Kurumu, in the UK the Information Commissioner's Office, and in the EEA the authority of the country where you live or work.