Last updated: June 24, 2026 · Effective date: June 20, 2026
Your meeting audio and transcripts never leave your device. MeetingChamp processes everything locally. We only collect what is strictly necessary to operate the service.
Important note on voice data: If you use the speaker recognition feature, MeetingChamp stores voice embedding vectors on your device. These are biometric identifiers under GDPR Article 9 and are processed only with your explicit consent. You can delete them at any time from History → People.
This Privacy Policy describes how Xurg Ltd ("MeetingChamp", "we", "us", or "our"), a company incorporated in England and Wales (Company No. 16964915), collects, uses, and protects your information when you use the MeetingChamp desktop application ("the App").
By using MeetingChamp, you agree to the practices described in this policy. If you do not agree, please do not use the App.
Account information — When you sign in with Google, we receive your name and email address from Google. This is stored in our AWS database (Amazon DynamoDB, us-east-1 region) to identify your account.
Usage logs — If you consent during setup, we collect anonymous technical events such as: app opened, recording started, recording stopped (duration only), summary generated (counts only — not content), errors. We never log transcript content, summary content, key points, action items, or any meeting data.
Device information — We log your device platform (Mac), architecture (arm64/x64), and app version for debugging purposes.
If you choose to enable speaker recognition, MeetingChamp creates and stores mathematical voice embeddings (voice fingerprints) to identify speakers across meetings. This data:
You may withdraw consent at any time by deleting all voice profiles from the app.
Voice profiles of meeting participants other than the account holder are stored exclusively on the recording user's local device and are never transmitted to Xurg Ltd or any server. This processing falls within the personal/household use exemption under GDPR Article 2(2)(c).
The device owner is solely responsible for ensuring appropriate awareness from meeting participants where required by applicable law. MeetingChamp displays a reminder to users before saving any participant's voice profile.
The account holder's own voice profile is securely backed up to our AWS servers (us-east-1) to enable recognition across devices. This is processed under your explicit consent and can be deleted by contacting abhinav@bidturns.com or deleting your account.
On-device processing — Audio recording, transcription (WhisperKit), and AI summarisation (Apple Intelligence) all run locally on your Mac. No audio or transcript data is transmitted to any server at any point.
Third party integrations — If you connect Slack, Notion, or Gmail, your meeting summary is sent directly from your device to those services using your own credentials. MeetingChamp does not see, store, or transmit this data through our servers.
AWS infrastructure — Your account details and usage logs are stored on Amazon Web Services in the us-east-1 (US East, Virginia) region. This constitutes a transfer of personal data outside the UK/EEA. AWS participates in the EU-US Data Privacy Framework and provides appropriate safeguards via Standard Contractual Clauses (SCCs) under UK GDPR Article 46. AWS is certified to ISO 27001 and SOC 2.
For users in the UK and European Economic Area, we process your data under the following legal bases:
We do not sell, rent, or share your personal data with third parties for marketing purposes. We share data only in the following limited circumstances:
Voice profiles of meeting participants are never shared with Xurg Ltd or any third party. They exist solely on the recording user's local device and are outside the control of Xurg Ltd.
You have the following rights regarding your personal data:
To exercise any of these rights, contact us at: abhinav@bidturns.com
You can manage your privacy preferences directly in MeetingChamp:
MeetingChamp is not intended for use by anyone under the age of 16. We do not knowingly collect data from children. If you believe a child has provided us with personal data, please contact us and we will delete it immediately.
We may update this Privacy Policy from time to time. We will notify you of material changes via the App or by email. Continued use of the App after changes constitutes acceptance of the updated policy.