Last Updated: September 5th, 2026
The website www.callstrike.ai (the “Website”), operated by CALLSTRIKE LTD (“Callstrike”, “we”, or “our”), a company incorporated in England and Wales (company number 16572896, registered office 71-75 Shelton Street, Covent Garden, London, WC2H 9JQ, United Kingdom), provides access to the Callstrike platform (the “Platform”), a solution designed to help organizations train employees and increase awareness of voice-based and message-based social engineering threats, including vishing, phishing and deepfake impersonation, by running simulated attacks against that organization's own personnel (the “Security Training Services”).
By accessing, browsing, or using the Website and the Callstrike Platform, you may provide personal data to Callstrike. The Platform also generates personal data about you when a simulation is delivered to you.
Please read this Privacy Policy carefully. It outlines how we collect, use, share, and protect your personal information, and explains your rights in relation to your data. This Privacy Policy supplements our Terms of Service and any other related agreements or notices referencing this policy.
If you have any questions or concerns, feel free to contact us at privacy@callstrike.ai.
When using the publicly available Website:
Callstrike acts as the data controller for any personal data collected and processed for the administrative, operational, and commercial management of the Website as its publisher.
When using the Callstrike Platform:
Your employer is the data controller for personal data collected and processed in connection with the Security Training Services they have subscribed to.
Callstrike acts as the data processor, processing personal data solely on behalf of and under the instructions of your employer, in accordance with the subscribed Security Training Services.
This includes simulations that use a synthetic voice, a synthetic video likeness, a telephone call, or a messaging channel. In every case your employer decides who is simulated, who is targeted, and on what lawful basis. Callstrike does not select targets, does not verify authorization, and acts on your employer's documented instructions.
All personal data is either directly provided by your employer, you, or one of our external partners. Additional data is also generated through your use of, or your participation in, the Security Training Services, including but not limited to:
| Type of Data | Examples | Required |
|---|---|---|
Identification Data | First name, last name | Yes |
Contact Details (professional and/or personal) | Email address, phone number, messaging identifier such as a WhatsApp number | Yes |
Professional Data | Company, position, department, country | Optional |
| Voice samples and derived synthetic voice models (where your employer configures a voice-cloning simulation) | An audio sample of a person's voice supplied by your employer, and the synthetic voice model derived from it and held by our speech provider. Callstrike treats voice samples and derived voice models as biometric data and applies special category safeguards to them. See the note below this table. | Only where your employer configures such a simulation |
| Likeness, image and video used for synthetic video impersonation | A photograph or video of a person supplied by your employer, and the synthetic video output generated from it | Only where your employer configures such a simulation |
| Call recordings of simulated calls | Audio recording of the simulated call, including your side of the conversation. Recording is on by default and your employer can turn it off for a given campaign. See the note below this table. | Only where your employer leaves recording enabled |
| Call transcripts and conversation content | Machine transcription of the simulated call, turn by turn, attributed to you or to the simulated caller; an automatically generated call summary and outcome evaluation | Transcript only where recording is enabled; summary and outcome always |
| Message-based simulation content | The content of simulated WhatsApp, message and email exchanges, your replies, and any attachment or media exchanged | Yes, where a message simulation is delivered |
| Training & Security Awareness Data (based on subscribed Security Training Services) | Training history, phishing and vishing campaign actions (e.g. answered, engaged, disclosed, ignored, reported), awareness score, risk history | Yes |
Account and technical log data | Account identifiers, sign-in events, and an append-only administrative audit record of actions taken in your employer's workspace | Yes |
Communication Data with Callstrike | Date, subject, voice recordings with our internal teams/bots | Optional |
Note on call recording. Whether a simulated call is recorded is a decision your employer makes for each campaign. Recording is enabled by default and your employer can turn it off in the campaign's call settings. Where recording is turned off, neither the call audio nor the turn by turn transcript is retained; only a high-level summary of the call and the outcome appear in your employer's reports. Where a simulation asks you to call a number back, that call is always recorded and the per-campaign setting does not apply to it.
Note on voice, likeness and AI processing. A voice sample and the voice model derived from it can identify a specific person. Callstrike therefore handles them as biometric data and as a special category of personal data, and restricts them to the simulation your employer configured. Because your employer is the controller, your employer is responsible for identifying the condition under law that permits this processing and for obtaining any authorization required from the person whose voice or likeness is used. Under our Terms of Service your employer warrants that it has done so before launching a simulation.
Note on realtime voice and video impersonation sessions. Where your employer runs a realtime session, the voice or video conversion happens on a compute instance that is provisioned for that session and destroyed when it ends. The conversion model is a general purpose model that is not built from any individual's voice, and no model derived from your voice is created for these sessions.
To set the target voice, your employer either uploads an audio sample for that session only, in which case it is held on that instance and destroyed with it, or selects a previously saved voice, in which case the stored audio sample described in the table above is used. That stored sample is retained until your employer deletes it.
Where the session is recorded, the recording and its transcript are stored and follow the retention period in Section 7. Where a session joins a video meeting, other participants in that meeting may be recorded as part of it.
Note on AI and automated processing. Simulated conversations are conducted by an AI system, not by a human caller. During a simulated call, what you say is transcribed by a speech recognition provider and the transcript is passed to a large language model, which generates the simulated caller's replies in real time. Transcripts, summaries and outcome evaluations are produced by these AI systems. Content you submit to the Platform, including scenario and template text, may also be processed by a large language model in order to draft, translate or refine simulation material. These systems do not make decisions about you that have legal effect. The outcome of a simulation may contribute to an awareness score held by your employer; how your employer uses that score is your employer's decision.
The provision of certain types of personal data may be required or optional to fully access and utilize the Callstrike Platform and the Security Training Services subscribed to by your employer. Any mandatory data fields will be clearly identified at the point of collection.
If you choose not to provide mandatory information, Callstrike may be unable to process your request, such as creating your Callstrike account, delivering training services, or processing a job application.
When you are using the Callstrike Platform, Callstrike operates as the data processor (as indicated in Section 1 of this policy). Your personal data is processed solely for the following purposes:
| Purposes | Examples of use of your personal data | Legal bases that may be used by the controller |
|---|---|---|
Creation and management of your Callstrike account | to create your Callstrike account and authenticate you, including through the identity provider your employer has connected (for example Microsoft Entra ID or Google Workspace), and to keep your account details up to date | Legitimate interest of your employer to train and raise employee awareness about cybersecurity risks in order to protect its information systems |
Provision of the security training services subscribed by your employer | to deliver the simulations and training your employer has configured, including simulated voice calls, simulated WhatsApp and message exchanges, and simulated email, and to compile statistics on your cybersecurity awareness level | Legitimate interest of your employer to train and raise employee awareness about cybersecurity risks in order to protect its information systems |
Generation of a synthetic voice for a simulation | to create a synthetic voice from a voice sample your employer supplies, and to use that voice in the simulations your employer configures | Legitimate interest of your employer, plus, because voice data is treated as a special category of personal data, a further condition under Article 9 UK GDPR which your employer as controller must identify (see Section 2) |
Generation of a synthetic video likeness for a simulation | to create and deliver a synthetic video impersonation from an image or video your employer supplies | Legitimate interest of your employer, plus, where the material identifies a specific person, a further condition your employer must identify |
Recording, transcription and evaluation of simulated calls | where your employer has enabled recording for a campaign, to record a simulated call, transcribe it, summarize it, and determine and report the outcome to your employer as part of the training result. Where recording is disabled, only the summary and outcome are produced. | Legitimate interest of your employer to train and raise employee awareness about cybersecurity risks in order to protect its information systems |
AI processing of simulation content | to conduct the simulated conversation in real time, and to draft, translate and refine simulation scenarios and templates | Legitimate interest of your employer |
Security, integrity and administrative audit of the service | to keep the Platform secure, to maintain an append-only record of administrative actions in your employer's workspace, and to investigate misuse | Legitimate interest of your employer and of Callstrike in securing the service |
Compliance with legal and regulatory obligations | to comply with applicable legal and regulatory requirements; and to process requests to exercise your data subject rights | Legal and regulatory obligations to which Callstrike is subject as data processor |
At your employer's discretion, the Platform may deploy features powered by artificial intelligence to enhance the effectiveness of the security training services and strengthen user awareness around data protection and cyber threats. Section 2 describes how that processing works.
Callstrike does not use your personal data to train or improve any artificial intelligence model of its own. We may use aggregated, de-identified data that does not identify your employer or any individual to operate, secure and improve the Platform.
Whether the third party providers listed in Section 4 use data submitted to them for their own model training is governed by our contract with each provider, and those terms differ between providers. Where we can state the position contractually: Anthropic's terms prohibit training its models on customer content; OpenAI does not use data submitted through its API to train its models; and AssemblyAI's data processing agreement prohibits using the data for any purpose other than performing the service. If you need the position for a specific provider, write to privacy@callstrike.ai and we will tell you what our contract with that provider says.
| Who | Why |
|---|---|
Callstrike and its duly authorized employees | For the management of the Website and the provision of the security training services, as detailed in Section 3 of this policy. |
Callstrike sub-processors | Named in the table below. Each is engaged under a written contract, processes personal data only on Callstrike's instructions for the purposes described in Section 3, and is bound by confidentiality and security obligations. |
The identity provider your employer connects | Where your employer uses single sign-on or directory synchronization, your authentication and directory data is exchanged with the identity provider your employer has chosen (for example Microsoft Entra ID, Google Workspace, or another SAML or OIDC provider), on your employer's instruction. |
Administrative or judiciary authorities | Only in the event of a lawful and justified request, or in the case of a suspected violation of legal or regulatory obligations. |
Lawyers and other interested parties | Only in the context of handling disputes, claims, or legal matters when applicable. |
Other third parties | In the event of restructuring, acquisition, merger, sale of assets, or insolvency of Callstrike, personal data may be transferred as part of the business assets to one or more third parties. |
The following sub-processors are engaged by Callstrike to deliver the Website and the Security Training Services. Which of them process your data depends on which Security Training Services your employer has subscribed to.
| Sub-processor | What it does for Callstrike | Processing location |
|---|---|---|
Google Cloud Platform | Cloud hosting for the Platform and its database | European Union (Belgium) |
Google Cloud Platform (GPU compute) | Ephemeral GPU compute for realtime synthetic voice and video sessions | United States |
Amazon Web Services (S3) | Storage for call recordings, synthetic media and uploads | United States and European Union |
Amazon Web Services (SES) | Email delivery | United States |
Vercel | Hosting for the Website and the web applications | United States |
Twilio | Telephony for simulated calls | United States |
Vapi | Realtime voice call orchestration | United States |
Deepgram | Speech to text during a simulated call, and during the free AI Voice Cloning Test on the Website | United States |
OpenAI | Language model for simulated conversations and simulation content, and for the conversation in the free AI Voice Cloning Test on the Website | United States |
Anthropic | Language model for simulation content | United States |
ElevenLabs | Synthetic speech and synthetic voice models | United States |
AssemblyAI | Audio transcription | United States |
Cartesia | Synthetic speech, and the temporary voice model made in the free AI Voice Cloning Test on the Website, deleted when the session ends | United States |
WorkOS | Authentication and single sign-on | United States |
MongoDB Atlas | Session storage for message-based simulations | United States |
Courier | Notification delivery | United States |
Slack Technologies | Workplace messaging, where your employer connects it | United States |
Microsoft | Authentication and email, where your employer connects it | Determined by your employer's own Microsoft tenant |
Google (Tag Manager and Analytics) | Website analytics on the public pages | United States |
Calendly | Demo booking on the Website | United States |
Our sub-processors may engage their own sub-processors in order to provide their services to us. Where they do, they are required to do so under a written contract that passes on equivalent data protection obligations.
We may add or replace a sub-processor as the Platform develops. DigitalOcean is under evaluation as an additional provider of GPU compute for realtime synthetic voice and video sessions, and is not in use today.
An up to date list of sub-processors is available on request from privacy@callstrike.ai, and customers may ask us for advance notice of changes to it.
Callstrike is established in the United Kingdom. The Platform application and its primary database are hosted in the European Union (Belgium). A number of the sub-processors listed in Section 4.1 are located outside the United Kingdom and the European Economic Area, principally in the United States. In particular, call recordings and other stored media are held in the United States and the European Union, and the speech recognition, language model and synthetic voice providers involved in a simulated call are located in the United States.
Transfers are made on the following basis:
These safeguards are contained in the data processing terms we have entered into with each sub-processor that receives personal data outside the United Kingdom and the European Economic Area.
You may request a copy of the safeguards in place for a given transfer, with commercial terms redacted, by writing to privacy@callstrike.ai. Where you are a member of a customer's personnel, that request may be routed through your employer as the controller.
Callstrike has implemented technical and organizational measures to safeguard your personal data against accidental or unlawful destruction, loss, alteration, unauthorized access, or disclosure. The measures below are those in place today.
Encryption. The Website, the administrator console and the learner portal are served over HTTPS only, with plain HTTP requests redirected and HTTP Strict Transport Security enabled. Our API is available over HTTPS and all first party applications are configured to use it. Personal data is encrypted at rest: the primary database is encrypted using platform-managed keys, and stored media, including call recordings and voice samples, is encrypted server side using AES-256.
Access to stored media. The media store blocks all public access. Media is not directly readable from the internet; it is served only through our content delivery network, under a policy that permits read access to that single distribution and nothing else, and delivery is authenticated using signed URLs or signed cookies depending on the environment.
Authentication. Authentication is delegated to WorkOS AuthKit. Your employer may connect its own identity provider for single sign-on, in which case authentication happens against that provider and we never receive your password. Sessions use short-lived, cryptographically signed access tokens which are verified against the provider's public keys on every request and are refreshed automatically. Callstrike does not store passwords.
Separation between customers. Each customer's data is held in a separate workspace. The workspace a request may act on is derived from the verified access token rather than from anything the client can set, and every query that reads or writes customer data is scoped to that workspace. Administrators and learners authenticate through separate paths with separate permissions.
Secrets. Credentials for the Platform and for the third party services listed in Section 4.1 are held in a managed secrets service, are not stored in source code, and are not committed to our code repositories. An automated check compares the configuration of our staging and production environments on every change and fails if they diverge.
Audit trail. Administrative actions within a workspace are recorded in an append-only audit log. Each record captures who acted, what action was taken, on what, the outcome, when it happened, and the originating network address, user agent and request identifier. Records are chained together cryptographically per workspace, so that any later alteration or removal of a record is detectable. The chain is computed over the structural fields only and deliberately excludes personal data, so that an erasure request can redact the personal details from a record without destroying the evidence that the event occurred.
Change control. Our production and staging branches are protected: direct force-pushes are blocked, protections apply to administrators as well, and defined automated checks must pass before a change can be merged. Every proposed change is subject to an automated code review and a separate automated security review covering authentication, separation between customers, secret handling and injection risks. The backend test suite must pass before a change can be deployed.
Environment separation. We operate distinct local development, staging and production environments, and changes are promoted in that order. Development and staging are seeded with synthetic test data. Production personal data is not copied into development, staging or test environments.
Resilience. The production database runs in a highly available configuration replicated across zones, is backed up automatically each day, and supports point in time recovery. See Section 7 for how long backups are retained.
If you discover a vulnerability or wish to report a security incident, please contact us at security@callstrike.ai. We ask that you give us a reasonable opportunity to remediate before disclosing publicly.
As a general rule, your personal data is retained only for the duration necessary to fulfil the purposes for which it was collected, or as required to meet legal or regulatory obligations.
When Callstrike acts as data controller for the publicly available Website (see Section 1):
When Callstrike acts as data processor for the Platform (see Section 1), data provided or generated during your use of the Platform is retained for the duration of the contractual relationship with your employer, subject to the specific periods below.
| Category | Retention |
|---|---|
Call recordings of simulated calls, and call transcripts, summaries and message attachments | Retained for a period configurable by your employer, with a platform default of twelve (12) months from the simulation. At the end of that period the recording audio, the transcript text and the recording references are erased, and the simulation outcome record is kept so that your employer's training statistics and your risk history remain intact. |
Recordings and transcripts of realtime voice impersonation sessions | Same twelve (12) month window as above. The GPU instance that performs the realtime voice or video conversion is ephemeral and is destroyed at the end of the session, so no model or intermediate audio persists on it; only the session recording and transcript are stored, and those follow the window above. |
Simulation outcome records, awareness scores and training history | Retained for the duration of the contractual relationship with your employer, then handled as set out below. This is the behavioural record, and it does not contain the recording or transcript content. |
Synthetic voice models used in vishing simulations, and the voice sample they were created from | Retained until deleted. A synthetic voice model is not subject to the automatic retention period above. It persists for as long as your employer keeps it in their workspace. See the note below this table. |
Administrative audit records | Retained for a period configurable by your employer, with a platform default of twenty-four (24) months. This is a separate setting from the recording and transcript window above. |
Account data | Retained for the duration of the contractual relationship with your employer. |
Note on synthetic voice models. Where your employer creates a synthetic voice for use in a vishing simulation, two artefacts are held: the audio sample the voice was created from, stored by Callstrike, and the derived voice model, held by our speech provider. Neither is removed by the automatic twelve month period that applies to recordings and transcripts, and neither is removed by an individual erasure request, which follows a separate path. They are deleted when your employer deletes the voice in the Platform, which removes the sample from our storage and instructs our speech provider to delete the model. Deletion is refused while the voice is in use by an active campaign, so that a running simulation cannot lose its voice mid-campaign; it can be deleted once that campaign completes. If you want a synthetic voice created from your voice to be deleted, contact your employer as the controller, who can delete it and can ask Callstrike for assistance under the data processing terms described in Section 8.
Note on recordings held by our voice provider. For simulated telephone calls, the call audio is captured and stored by our voice orchestration provider rather than by Callstrike. When the retention period expires, Callstrike erases the transcript held in the Platform and its reference to that recording. The underlying audio held by that provider is deleted according to that provider's own retention terms rather than by our retention period, and those terms are set out in the agreement between Callstrike and that provider. You may ask us for the current position at privacy@callstrike.ai.
Backups. Separately from the periods above, personal data persists for a limited period in operational backups. Our primary database is backed up automatically each day, and we retain seven (7) days of daily backups and seven (7) days of transaction logs for point in time recovery. Data deleted from the live Platform, whether by the retention purge, by an erasure request or by your employer, therefore remains recoverable from backups for up to seven days before it ages out. Stored media files are not versioned, so deleting a media file removes it immediately and irreversibly.
After the end of the relationship with your employer. On termination, access to the Platform ends. Your employer may request an export of its data by contacting us at privacy@callstrike.ai. Our Terms of Service give your employer thirty (30) days from termination to request an export.
Deletion after termination is automatic. When a customer relationship ends, we retain that customer's data for thirty (30) days and then permanently delete it. Nobody has to ask us: the deletion runs on a schedule. Your employer may also delete an individual workspace themselves from inside the Platform. A workspace holding no learners, campaigns or phone numbers is deleted immediately and cannot be recovered; a workspace holding data enters a thirty (30) day period during which any administrator of that workspace can restore it, after which it is permanently deleted. The retention periods in the table above continue to apply for as long as data remains in the Platform, and the backup window described above applies to data deleted this way as well.
Where Callstrike acts as data processor, we process personal data only on the documented instructions of the customer as controller, under the agreement between Callstrike and that customer and as described in this policy. Where the Platform is purchased through a reseller or other intermediary, the controller is the organization that determines how the Platform is used against its own personnel.
Customers, and prospective customers under evaluation, can contact us at privacy@callstrike.ai to discuss the data protection terms that apply to their engagement, including the sub-processor list and notice of changes to it, the international transfer safeguards described in Section 5, assistance with data subject requests, security measures, breach notification, and the return or deletion of data at the end of the relationship.
When you are using the publicly available Callstrike Website and Callstrike acts as the data controller (as outlined in Section 1 of this policy), you may contact Callstrike directly regarding your personal data rights by emailing privacy@callstrike.ai.
When you are using the Callstrike Platform and Callstrike acts as the data processor (as outlined in Section 1), you should contact your employer directly to exercise your data protection rights. Callstrike will assist your employer in responding, under the data processing terms described in Section 8.
In accordance with applicable data protection regulations, you have the following rights concerning your personal data:
Where erasure is exercised through your employer, the Platform replaces your identifying details with a non-identifying placeholder and erases the associated recordings, transcripts and media it holds, while retaining the de-identified outcome record. A synthetic voice model is handled separately, as described in Section 7.
Depending on your country of residence, you may have additional rights under local data protection laws.
The availability of these rights depends on the legal basis under which your personal data is being processed, as outlined below:
| Legal basis | Access | Rectification | Erasure | Restriction | Data portability | Objection |
|---|---|---|---|---|---|---|
Consent | Yes | Yes | Yes | Yes | Yes | Withdrawal of consent |
Steps prior to entering into a contract | Yes | Yes | Yes | Yes | Yes | No |
Contract | Yes | Yes | Yes | Yes | Yes | No |
Legitimate interest | Yes | Yes | Yes | Yes | No | Yes |
Legal obligation | Yes | Yes | No | Yes | No | No |
In certain circumstances, we may request specific information to verify your identity and ensure that your rights are exercised securely. This is an appropriate safeguard to prevent unauthorized access to your personal data by individuals who are not entitled to receive it.
If needed, you also have the right to lodge a complaint with a data protection supervisory authority. Callstrike is established in the United Kingdom, so the relevant authority is the Information Commissioner's Office (ICO), whose complaints process is described at ico.org.uk. If you are located in the European Economic Area, you may instead lodge a complaint with the supervisory authority of your own country of residence or place of work. This right may be exercised at any time and free of charge, except for any postal or legal assistance costs should you choose to engage third-party support during the procedure.
This privacy policy may be updated from time to time, particularly to reflect changes to the Website, the Security Training Services, our sub-processors, or applicable regulations. We therefore recommend reviewing this policy periodically, especially each time you use the Callstrike Website or Platform.