ClaimCheckEffective date: 01/10/2026
Last updated: 05/11/2026
1. Who we are
ClaimCheck Live is an informational service that helps users identify and examine factual statements in speeches, interviews, debates, and other supported recordings.
This Privacy Policy explains how personal data is processed when you visit claimcheck.watch, create an account, purchase credits, submit or capture content, receive automated analysis, contact us, or otherwise use the Service.
The operator is:
- Legal name: Neuraly Limited
- Trading name: ClaimCheck Live
- Registered or business address: 2 Frederick Street, Kings Cross, London, United Kingdom, WC1X 0ND
- Company registration details, where applicable: 14449403
- Privacy contact: privacy@claimcheck.watch
- Data Protection Officer, if appointed: privacy@claimcheck.watch
References to “we,” “us,” and “our” mean the operator identified above.
This Policy also explains how to contact us if your voice, statements, or other personal data appear in content submitted by another user, even if you do not have an account.
2. Scope and our data-protection roles
This Policy covers personal data associated with:
- Website visitors.
- Account holders and organizational contacts.
- People purchasing or using credits.
- People whose voices or information appear in submitted material.
- People mentioned in transcripts, claims, evidence, or reports.
- People contacting support or exercising privacy rights.
Our role depends on the processing activity.
Where we act as a controller
We act as a controller where we determine the purposes and essential means of processing, including applicable account administration, billing, security, legal compliance, and management of privacy requests.
Our role for content analysis is: we act as controller for account, billing, and security data, and for the processing needed to transcribe and analyse the content you choose to submit; you decide what content to submit and remain responsible for having a lawful basis to submit recordings or text that contain other people’s personal data.
Where we act as a processor
For some organizational customers, we may process submitted content on the customer’s documented instructions under a data processing agreement.
Where that arrangement applies, the customer is responsible for its controller obligations, and we are responsible for our processor obligations.
If a request concerns data we process solely on behalf of a customer, we may direct the request to that customer or assist it in responding, as legally appropriate.
Calling a customer the controller does not, by itself, determine the legal roles. The actual purposes, decisions, and processing arrangements govern.
3. Personal data we process
We process the categories below to the extent they are used by the features you access and the systems identified in this Policy.
| Category | Examples |
|---|---|
| Account and contact information | Name, email address, account identifier, organization, and account preferences. |
| Authentication information | Sign-in records and authentication data handled through the configured login system. |
| Submitted media | Audio or video files, speech captured through supported microphone or browser-tab features, and supported media links. |
| Recording-related information | File name, file type, duration, language, timestamps, and other relevant metadata. |
| Transcripts and speaker labels | Recognized speech, time-aligned text, and automatically assigned speaker labels. |
| Claims and analysis results | Extracted statements, assessments, explanations, citations, and report content. |
| Information about people in content | Names, voices, affiliations, statements, and other information included in recordings or sources. |
| Transaction information | Credit purchases, balances, consumption records, order references, payment status, invoices, and refunds. |
| Technical and security information | IP address, browser and device type, sign-in and verification events, access and error logs, and API usage records (provider, time, and volume) used to secure, operate, and bill the Service. |
| Support and complaint records | Messages, attachments, correction requests, privacy requests, and related correspondence. |
| Cookie and similar-technology information | Browser local storage and essential cookies holding your sign-in session, language choice, cookie choices, and an autosaved copy of an in-progress check, as described in our Cookie Policy. |
Payment card details are handled directly by our payment provider.
Do not state that you never receive full card details unless that has been verified.
Sensitive information
Recordings and transcripts may contain sensitive information, such as political opinions, health information, religious beliefs, or other specially protected data.
A voice recording is personal data where it relates to an identifiable person. Whether voice-related processing constitutes specially protected biometric processing depends on how it is used.
Speaker separation does not necessarily mean that a person’s identity has been verified.
Do not submit specially protected, privileged, or confidential material unless you have established that the processing is lawful and that the Service is suitable for your intended use.
4. Where personal data comes from
We may obtain personal data:
- Directly from you.
- From a person using the Service who submits a recording or captures speech.
- From your organization or account administrator.
- From supported media platforms or links you submit.
- From published sources retrieved to evaluate claims.
- From payment, authentication, hosting, or other providers involved in delivering the Service.
- From your interactions with the website and Service.
Consequently, we may process information about someone who has not registered with ClaimCheck Live.
Where we act as controller and obtain personal data indirectly, we assess applicable transparency duties, including whether we must provide information directly to the affected person. A public policy or a user’s contractual promise does not automatically satisfy every such obligation.
5. Why we process personal data and our legal bases
Where GDPR applies and we act as controller, each processing activity requires an appropriate legal basis.
The following schedule must be finalized against our actual processing arrangements:
| Purpose | Personal data involved | Applicable basis |
|---|---|---|
| Create and administer an individual user’s account | Account, authentication, and contact information | Performance of the contract with that individual, where necessary. |
| Manage organizational account relationships | Business contact and account information | Legitimate interests in administering the business relationship, where applicable. |
| Deliver requested transcription and analysis to an individual user | Submitted content and resulting outputs | Contract necessity for that user’s personal data where applicable; separate assessment required for other people’s data. |
| Process personal data about third-party speakers where we act as controller | Voices, statements, identities, and contextual information | Legitimate interests in verifying public factual claims and supporting informed public debate, balanced against speakers’ interests; processing is limited to statements in content submitted by users, and the special-purpose exemptions for journalism and research may apply where relevant. |
| Process content on an organizational customer’s instructions | Submitted content and outputs | Governed by the controller’s lawful instructions and the data processing agreement. |
| Take payment and administer credits | Transaction, account, and usage records | Contract necessity and applicable legal obligations. |
| Keep required accounting or tax records | Billing and transaction information | Applicable legal obligations. |
| Maintain security and prevent abuse | Relevant technical, account, and transaction information | Legitimate interests in protecting the Service and its users, subject to applicable safeguards. |
| Respond to support and correction requests | Contact information and relevant content | Contract necessity or legitimate interests, depending on the request. |
| Handle privacy requests and legal claims | Request records and relevant evidence | Legal obligations and, where appropriate, legitimate interests in establishing or defending claims. |
| Optional analytics, marketing, or nonessential tracking | None currently; we do not use analytics, advertising, or marketing trackers | Consent, requested through our cookie banner before any such technology is enabled. |
Our contract with an account holder is not automatically a lawful basis for processing every other person’s information in a recording.
Where processing involves special-category data, a separate condition under applicable law may also be required. We do not assume that all information appearing online has been “manifestly made public” by the person concerned.
Where we rely on consent, you may withdraw it by emailing us at hola@claimcheck.watch. Withdrawal does not affect processing lawfully carried out before withdrawal.
Where we rely on legitimate interests, you may object as explained below.
6. How transcription and claim analysis work
Depending on the feature selected:
- You upload supported media, provide a supported link, or activate audio capture.
- Audio needed for transcription is transmitted to our speech transcription provider through an encrypted connection and transcribed on servers in the European Union.
- A transcript is generated, including automated speaker separation where supported.
- The Service identifies statements that appear capable of factual verification.
- Relevant claims or transcript excerpts are processed by AI analysis providers for claim identification and assessment, and by search and evidence-retrieval providers to find existing published fact-checks and web evidence.
- The Service retrieves or compares published evidence and generates assessments.
- Transcripts, claims, and results may be saved to your account.
- You may export supported reports.
We disclose to each provider the information needed for its relevant function, as described in the provider schedule below.
Our speech transcription provider receives the audio. AI analysis providers receive transcript segments to identify claims, and then each individual claim with the retrieved evidence to produce an assessment. Search and evidence-retrieval providers receive only the text of individual claims as search queries. Complete transcripts are not sent to search providers, and your account details are not sent to any analysis or search provider.
7. Uploaded files: encryption and automatic deletion
When you upload a file, including supported audio or video, the material needed for transcription is sent to our speech transcription provider through an encrypted connection.
Transcription — whether the audio comes from live listening or from an uploaded file — is carried out on our speech transcription provider’s European Union servers, so the audio used for transcription is processed within the EU.
Following completion of transcription, ClaimCheck Live automatically deletes the uploaded source file from its upload-processing storage.
This source-file deletion is separate from retention of:
- The resulting transcript.
- Speaker labels and timestamps.
- Extracted claims.
- Assessments and source references.
- Saved reports.
- Credit-consumption and transaction records.
- Technical records retained for permitted operational purposes.
The Service is not a permanent archive or backup service for uploaded media.
If you need the original recording for later verification, retain your own lawful copy.
Failed uploads and temporary processing copies
Failed, interrupted, or abandoned uploads are deleted according to the following rule: uploaded files are sent from your browser directly to our speech transcription provider for transcription and are not stored on ClaimCheck Live servers, so a failed or abandoned upload leaves no copy with us.
Temporary extracted audio, transcoding files, queue artifacts, and other processing copies are handled as follows: ClaimCheck Live does not create server-side extracted audio, transcoding files, or queue copies of your media; audio preparation happens in your browser memory and is discarded when the page or session ends.
The retention of any infrastructure backups containing source files must be stated here if applicable: because source media is not stored on our servers, our infrastructure backups do not contain your source files; they may contain saved transcripts and results.
Live and linked content
Live microphone capture, browser-tab capture, and linked-platform processing may involve different technical buffers or temporary copies.
Their handling is: live microphone and tab audio is streamed from your browser directly to our speech transcription provider in short chunks and is not recorded or stored by ClaimCheck Live. For YouTube links we retrieve only the published captions, not the audio or video. Only the resulting transcript and results are kept, and only if saved to your account.
We do not describe these workflows as identical to uploaded-file deletion unless that is technically accurate.
8. Speech transcription processing and retention
We use a speech transcription provider to convert audio into text.
Our deployment uses:
- Processing region: servers in the European Union.
- Model-improvement participation: opted out — every transcription request includes the provider’s model-improvement opt-out setting.
- Provider-side audio and transcript retention: governed by the speech transcription provider’s data-processing terms and retention policy for business customers.
- Technical metadata and usage-log retention: the speech transcription provider keeps request metadata (such as duration and time) for billing and service operation under its terms.
- Asynchronous delivery or callback retention: not applicable — transcription results are returned directly to your browser, without provider callbacks.
- Applicable processing agreement: the speech transcription provider’s Data Processing Addendum; information about the provider and applicable arrangements is available on request through privacy@claimcheck.watch.
ClaimCheck Live’s deletion of an uploaded file does not independently delete copies or records held by a provider. Provider-side processing is governed by the applicable settings and contractual arrangements.
Any statement that the speech transcription provider does not retain audio or transcripts after processing must be supported by the actual configuration in operation.
9. Model training and product improvement
The policy governing use of submitted recordings, transcripts, and results for model training is:
ClaimCheck Live does not use your recordings, transcripts, or results to train AI models. Speech transcription requests are sent with model-improvement opted out. Our AI analysis provider does not use data submitted through its business API to train its models by default. Search and evidence-retrieval providers receive only claim text as search queries, under their own service terms.
We distinguish:
- Processing needed to generate the result you request.
- Security monitoring and operational diagnostics.
- Analysis of service performance.
- Training or improvement of general-purpose models.
These are not automatically the same purpose.
If content is used for training or another secondary purpose, we will identify the relevant data, recipients, purpose, legal basis, retention, and available controls.
Acceptance of the Terms or this Privacy Policy is not blanket consent to unrelated model training.
We do not describe pseudonymized information as anonymous where it can still be linked to an identifiable person.
10. Informational purpose and limitations of automated analysis
The Service assists research and review. It does not provide a certified transcript or definitive determination of truth.
Automated processing may:
- Mishear words, names, numbers, dates, or qualifications.
- Attribute speech to the wrong speaker.
- Misclassify opinion, satire, or prediction as a factual claim.
- Analyze a statement without adequate context.
- Miss relevant evidence.
- Generate an incorrect explanation or citation.
Live results may appear before the complete statement or surrounding context is available.
Sources may be incomplete, conflicting, outdated, inaccessible, or revised after analysis.
A result about a statement does not establish a person’s intent, honesty, character, or legal liability.
If an output contains inaccurate personal data about you, contact privacy@claimcheck.watch. Depending on the circumstances, appropriate action may include correction of a transcript, annotation, restriction, removal, or another legally appropriate response.
11. Automated decision-making and consequential use
ClaimCheck Live generates automated transcripts and assessments. Users must not confuse those outputs with a human adjudication.
Our use of automated decisions about account holders, including any fraud-related account restrictions, is: limited to automatic, rule-based controls such as stopping a check when your credit balance runs out and enforcing daily usage limits; we do not make automated fraud or profiling decisions about account holders, and you can contact hola@claimcheck.watch to ask for human review of any restriction.
We do not make solely automated decisions that produce legal or similarly significant effects for you. Claim assessments are automated, informational outputs about statements, not decisions about people.
Where applicable law requires additional information, safeguards, human intervention, or a means of contesting a decision, we will provide them.
Users should not rely solely on an automated output for consequential decisions about employment, credit, insurance, education, housing, medical treatment, legal action, or similar matters.
12. Recording permissions and other people’s privacy
Before recording, capturing, transmitting, or submitting speech, users must establish that their intended processing is lawful.
Depending on the circumstances, this may require:
- Notice to participants.
- Permission or consent.
- A lawful basis for personal-data processing.
- Workplace, event, venue, or organizational authorization.
- Compliance with confidentiality and professional obligations.
Activating a browser or microphone permission does not necessarily establish that all participants have consented to recording or that the processing is otherwise lawful.
Public accessibility does not remove privacy obligations.
Users should avoid submitting unnecessary personal information and should take particular care with children’s information, private conversations, health information, political opinions, and other sensitive material.
These user responsibilities do not replace our independent legal obligations.
13. Copyright, platform restrictions, and third-party material
Users must have sufficient rights or another valid legal entitlement to submit and use recordings, videos, audio, transcripts, and other material.
Submitting a YouTube link or other public URL does not establish unrestricted permission to copy, process, or republish its content.
Users must not circumvent access restrictions, paywalls, digital rights management, or other protected controls.
Third-party sources and platforms apply their own privacy practices to interactions with their services.
When you follow an external source link, the external site may collect information about your visit under its own policy.
If the Service embeds external media or transmits data before you follow a link, the relevant recipients and controls are described in our Cookie Policy; for example, embedded YouTube videos on our homepage use YouTube’s privacy-enhanced mode and only load after you click play.
14. Saved results, exports, and redistribution
The Service may save transcripts, claims, and results automatically.
Saved outputs may contain personal data even after the source media has been deleted.
You may export supported results, including PDF reports. A report reflects analysis at the time of generation and does not automatically update after download.
When you download, email, publish, or otherwise share a report:
- A separate copy may leave the Service.
- The recipient may retain or redistribute it.
- Deleting the original account result does not necessarily delete external copies.
You are responsible for the lawfulness of your own publication or disclosure.
You should preserve relevant context, qualifications, and source references.
You should verify speaker attribution and material allegations before publication.
Reports are not certified transcripts, legal findings, or guarantees of accuracy.
Visibility and sharing controls
Account-content visibility is: private — saved checks, reports, notes, and tags are visible only to the account that created them.
Public-link behavior, if available, is: not available — the Service does not currently offer public or shareable links to results; exported PDF and CSV files are shared only if you share them yourself.
Organizational administrator access, if applicable, is: not applicable — the Service does not currently offer team or organisational accounts.
These settings must reflect the actual product. Uploaded content should not be described as private by default unless that is verified.
15. Credits, payments, refunds, and transaction records
ClaimCheck Live operates on pay-as-you-go credits, not a subscription.
We process transaction information to:
- Record purchases.
- Maintain balances.
- Measure billable use.
- Apply the disclosed credit-consumption rules.
- Investigate incorrect deductions.
- Restore credits or process refunds where appropriate.
- Handle payment disputes and fraud.
- Maintain legally required financial records.
Credit consumption is calculated according to the following rule: 1 credit per minute of audio, billed per second (for example, 2 minutes 2 seconds uses 2.0333 credits), and 1 credit per text claim that receives a verdict, including rechecks; checks that fail or time out are not charged, displayed in the pricing information and Terms before the relevant transaction or use.
Records may include purchase references, credit quantities, balance changes, processing durations, payment status, and refund history.
We disclose your email address, the package purchased, and the amount to our payment provider. The payment provider collects your card and billing details directly, and we never receive or store your full card number.
Unused credits are handled under the validity and refund provisions in the Terms. Account deletion does not automatically remove an outstanding payment obligation or eliminate a lawful refund entitlement.
Billing and tax records may need to be retained after account closure or after an unused balance is refunded.
The detailed rules governing credit expiry, failed processing, refunds, withdrawal rights, and unused balances are in the Terms and purchase disclosures. This Policy explains the associated data processing; it does not reduce those rights.
16. Who receives personal data
We disclose personal data where necessary and lawful to the following categories of recipients:
| Category of recipient | Function and data |
|---|---|
| Speech transcription providers | Audio needed for transcription, associated request information, and the resulting transcript. Transcription is carried out on servers in the European Union. |
| Cloud hosting, storage and database providers | Account data, saved checks, reports, and service logs. |
| AI analysis providers | Transcript segments used to identify claims, and individual claims together with retrieved evidence used to assess them. |
| Search and evidence-retrieval providers | The text of individual claims, sent as search queries only. |
| Authentication providers | Email address, password hash, sign-in sessions, and optional two-factor settings. |
| Payment providers | Email address, package, amount, payment status, invoices, and refunds. |
| Email and support providers | Email address, name, and message content for sign-in codes, account emails, and contact-form messages. |
| Translation providers | Interface text only; no user content. |
| Analytics or monitoring providers, if used | None currently. |
| Professional advisers | Relevant information where necessary for legal, accounting, insurance, or professional services. |
| Authorities or courts | Information we are legally required or otherwise lawfully entitled to disclose. |
| Business successors | Relevant information in a lawful restructuring or transfer, subject to appropriate safeguards and notice. |
| Other recipients you select | For example, where you activate a sharing feature or request a disclosure. |
We do not publish a named list of the individual service providers behind these categories. Where you need one — for example as a business customer assessing our processing — we will provide it on request through privacy@claimcheck.watch.
Sale, advertising-related sharing, or other commercial disclosure practices: we do not sell personal data, and we do not share it for advertising or cross-context behavioural advertising.
17. International transfers
Personal data is processed in the UK.
Audio transcription is an exception: it is carried out by our speech transcription provider on servers in the European Union, so the audio you submit for transcription is processed within the EU.
Where personal data is transferred outside the EEA or another jurisdiction with transfer restrictions, we use an applicable lawful mechanism, such as:
- A relevant adequacy decision.
- Approved Standard Contractual Clauses.
- Another legally available safeguard or exception.
Where required, we assess the transfer and apply supplementary measures.
Apart from audio transcription, which is carried out on our speech transcription provider’s European Union servers, encryption does not, by itself, establish that no international transfer occurs.
You may request information about relevant safeguards, including a copy where appropriate and subject to lawful redactions, through privacy@claimcheck.watch.
18. Retention schedule
We retain personal data only for as long as necessary for the stated purposes, subject to lawful retention requirements.
| Data | Retention period or rule |
|---|---|
| Uploaded source media after successful transcription | Automatically deleted after transcription from upload-processing storage. |
| Failed or abandoned uploads | Not stored by ClaimCheck Live; uploads go directly from your browser to our speech transcription provider. |
| Temporary media-processing artifacts | None created on our servers; processing happens in your browser memory. |
| Live-streaming buffers | No persistent storage by ClaimCheck Live; audio is streamed directly to our speech transcription provider. |
| Transcripts, claims, and assessments | Kept while your account is active, until you delete them or delete your account. |
| Saved reports | Kept while your account is active, until you delete your account. |
| Account information | Kept while your account is active; deleted when you delete your account in Profile → Security, except payment and usage records, which are kept without your name or email. |
| Billing and tax records | 6 years from the end of the financial year, as required by UK tax and company law. |
| Security and diagnostic logs | Kept on a rolling basis by our hosting provider, typically for up to 90 days; API usage records are kept for billing. |
| Support and privacy-request records | Up to 3 years after the request is closed, to handle follow-ups and legal claims. |
| Backups | Rolling backups managed by our hosting provider; deleted data is removed as older backups are overwritten. |
| Provider-held information | Governed by each provider’s own terms and retention policies (see section 13). |
Where a fixed period cannot reasonably be specified, we explain the criteria used, such as account status, unresolved disputes, statutory retention, or the continuing necessity of a security investigation.
Content removed from active systems may remain temporarily in restricted backups under the disclosed backup cycle.
We do not use a generic “as long as necessary” statement as a substitute for available, meaningful retention information.
19. Cookies and similar technologies
We use essential browser local storage and cookies only.
Their purposes are keeping you signed in, securing sign-in, remembering your language and cookie choices, and autosaving an in-progress check so it is not lost if the page closes.
Our Cookie Notice identifies:
- The technologies used.
- Their providers.
- Their purposes.
- Their duration.
- Whether they are essential or optional.
- How to manage preferences.
Where consent is required for nonessential technologies, they are not activated until valid consent is obtained.
You can change applicable preferences through cookie preferences at the footer menu on the right side of the page.
If we do not use optional analytics or advertising technologies, this section will state that accurately.
20. Security
We use encrypted transmission when sending material to our speech transcription provider for transcription, and transcription is carried out on our speech transcription provider’s European Union servers.
Other safeguards are: a 6-digit emailed code or authenticator-app code on every sign-in, optional two-factor authentication, database rules that restrict each account to its own records, provider API keys kept on the server only, short-lived 60-second transcription tokens, encrypted connections, encryption at rest by our hosting provider, and logging of provider usage.
Access to personal data is limited according to the roles and controls we actually maintain.
No system is completely secure. If a personal-data breach occurs, we assess and make notifications required by applicable law.
Users should protect account credentials and secure downloaded reports and other copies outside the Service.
21. Your data-protection rights
Depending on the applicable law and our role, you may have the right to:
- Obtain information about processing.
- Access your personal data.
- Correct inaccurate personal data.
- Request erasure.
- Restrict processing.
- Object to processing based on legitimate interests.
- Receive portable data where the relevant conditions apply.
- Withdraw consent.
- Obtain applicable safeguards concerning automated decision-making.
- Complain to a supervisory authority.
These rights are subject to applicable conditions and exceptions. For example, a deletion request may not require removal of financial records that must be retained by law.
Contact privacy@claimcheck.watch to submit a request.
We may request proportionate information to verify identity or locate the relevant data. We do not require excessive identification.
Where GDPR applies, we normally respond within one month. If a lawful extension is needed, we explain the reason and applicable timing.
We do not require you to have an account to raise a privacy concern.
22. If your voice or information was submitted by someone else
If you believe a recording, transcript, claim, or report contains your personal data, contact privacy@claimcheck.watch.
Where reasonably available, provide:
- A session or report reference.
- The relevant passage or statement.
- The approximate recording date.
- A link or other information identifying the material.
- The right or concern you wish us to address.
Avoid sending unnecessary sensitive information.
We will determine whether we act as controller or processor for the relevant activity and respond or route the request appropriately.
We will consider other people’s rights, lawful retention, applicable expression or information protections, and other relevant legal requirements. We do not assume those considerations automatically override your rights.
23. Children
The Service is intended for adults aged 18 and over.
User-submitted material may nevertheless contain children’s personal data. Account eligibility restrictions do not prevent that possibility.
Users should avoid submitting unnecessary information about children and must have the permissions and lawful grounds required for their intended processing.
If you believe children’s information has been processed improperly, contact privacy@claimcheck.watch.
24. Complaints
Please contact us first if you have a concern so we can investigate.
You may also complain to the data-protection authority available to you under applicable law, including, where GDPR applies, an authority in the Member State of your habitual residence, workplace, or the alleged infringement.
Our relevant supervisory authority, where applicable, is:
The Information Commissioner’s Office (ICO), Wycliffe House, Water Lane, Wilmslow, Cheshire SK9 5AF, United Kingdom — ico.org.uk, telephone 0303 123 1113.
We do not require you to complete an internal complaint process before exercising statutory rights.
25. Changes to this Policy
We may update this Policy to reflect changes in processing, technology, or legal requirements.
We will display the revised date and provide additional notice where required.
If a new processing activity requires consent, we will request it rather than treating continued use as automatic consent.
Before using existing personal data for a new purpose, we will assess the applicable legal requirements and provide any required information.
26. Contact
For privacy requests, correction concerns, or questions about this Policy:
- Neuraly Limited
- 2 Frederick Street, Kings Cross, London, United Kingdom, WC1X 0ND
- privacy@claimcheck.watch