Last updated: October 12, 2026
This Policy explains what personal information Ematrics handles, why, and what rights you have over it.
One distinction matters throughout. For the call content our business customers put through the platform, we act on their instructions and they decide what is collected and kept. For our own account and website data, we decide. Section 01 sets out which is which.
This Policy explains how Ematrics handles personal information in connection with the Ematrics platform, including AI training simulations, real-time call assistance, post-call analytics and team reporting.
For call content submitted by a business customer, Ematrics acts as a processor or service provider on that customer's instructions. The customer is the controller and decides what is recorded, on what legal basis, and for how long it is kept.
For our own account, billing, website and marketing data, Ematrics acts as a controller.
If you were a participant on a call processed through Ematrics and want to exercise a right over that recording, the organisation that ran the call is the right place to start. We will assist that organisation in responding, but we cannot act on its data without instruction. Contact details are in the final section.
Where a customer enables an integration, Ematrics exchanges only the data necessary to provide that integration, as determined by the permissions the customer grants. The currently available Google Calendar integration is described in the “Google Workspace data” section below.
Voice recordings may constitute biometric or sensitive personal information under certain laws, including in Illinois, Texas and Washington, and under the GDPR where used to identify an individual.
Ematrics processes call audio to transcribe conversations and to generate coaching analytics. Where our processing of voice data falls within these regimes, the customer that captured the audio is responsible for providing the required notices and obtaining the required written consent before any recording takes place.
We do not sell voice data, do not use it to identify individuals across customers, and do not disclose it other than as described in this Policy.
This section governs information Ematrics receives from Google APIs. Where it differs from anything else in this Policy, this section applies to that information.
Where a user connects a Google account, Ematrics requests the Google Calendar read-only scope (calendar.readonly). Although that scope may permit access to calendars available to the user, Ematrics retrieves event data only from the user’s primary calendar. Ematrics requests no other Google OAuth scope.
From that calendar Ematrics reads event start and end times, event titles, the organiser and attendee email addresses. Ematrics does not read, and does not request access to, Gmail, Google Drive, Google Contacts or any other Google service.
Calendar information is used solely to identify which upcoming meetings are external sales calls, to associate a call with the correct customer account, and to make the Ematrics Assist application ready before the call begins. These are the features presented to the user in the product interface.
Calendar data and an encrypted OAuth refresh token are stored server-side using Ematrics’ hosting and infrastructure service providers, including Supabase, so that synchronisation can operate while the user is not signed in. Those providers may process the data only on Ematrics’ instructions and subject to contractual confidentiality and security obligations. The refresh token is not exposed to the browser or to the desktop application.
Ematrics’ use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Google user data is not sold, is not used for advertising, and is not used to train generalised artificial intelligence or machine learning models. It is transferred only to service providers acting on Ematrics’ behalf where necessary to provide or maintain the user-facing features described above, for security purposes, with the user’s affirmative consent, or where required by applicable law.
Ematrics personnel do not access Google user data except with the user’s affirmative consent to access specific data for support or troubleshooting, when necessary to investigate a security incident or abuse, when required by applicable law, or where the data has been aggregated and de-identified for internal operational purposes.
A user may disconnect Google Calendar at any time in Ematrics settings, or revoke Ematrics’ access directly at myaccount.google.com/permissions. When the user disconnects through Ematrics settings or requests deletion, Ematrics promptly invalidates and deletes the stored refresh token and deletes retrieved Google Calendar data from active systems within thirty (30) days. Residual copies may remain in encrypted backups until those backups expire under Ematrics’ standard retention schedule, and will not be restored except for disaster recovery.
We generate aggregated and de-identified data from use of the Service and use it to operate, benchmark and improve our products and models. This data does not identify any individual, customer or call participant, and we do not attempt to re-identify it.
We do not use identifiable customer call content to train models for the benefit of other customers.
Where the GDPR or UK GDPR applies and we act as a controller, we rely on the following bases:
Where we act as a processor, the legal basis for processing call content is determined by the customer acting as controller.
We do not sell personal information. We disclose it only as follows:
A current list of sub-processors is available on request to info@ematrics.com.
Ematrics is based in the United States and information may be processed there and in other countries where we or our sub-processors operate. Those countries may not provide the same level of protection as your own.
Where we transfer personal data out of the European Economic Area, the United Kingdom or Switzerland, we rely on an approved transfer mechanism, including the Standard Contractual Clauses, together with supplementary measures where appropriate. A copy of the relevant mechanism is available on request.
For call content, retention is configured by the customer. We retain it for as long as the customer's account remains active or as its settings specify, and delete or de-identify it after the applicable period.
Account and billing records are kept for the life of the account and for as long afterwards as needed to meet legal, tax and accounting obligations, and to resolve disputes.
On termination we make customer data available for export for thirty days, after which it may be deleted from active systems. Residual copies may persist in backups for a limited period before being overwritten.
We maintain administrative, technical and physical safeguards designed to protect personal information, including encryption of data in transit, access controls that separate each customer’s data at the database level, least-privilege permissions, logging and monitoring, and periodic review of our practices and those of our sub-processors.
Ematrics does not currently hold SOC 2, ISO 27001 or any comparable certification, and does not represent that it does.
No method of transmission or storage is completely secure, and we cannot guarantee absolute security. Customers are responsible for configuring their own account correctly, managing which of their users has access, and safeguarding credentials.
Where a personal data breach occurs, we will notify affected customers and, where required, regulators and data subjects, within the timeframes applicable law requires. Nothing in this Policy or in our Terms limits any obligation of notification that applies to us by law.
To exercise a right over data we hold as a controller, contact info@ematrics.com. We will verify your identity before responding and will respond within the period the applicable law requires.
Where the request concerns data we process on a customer's behalf, we will refer you to that customer, who is the controller, and support them in responding.
We use strictly necessary cookies to operate the site and keep sessions secure, and may use analytics cookies to understand usage. Non-essential cookies are used only where consent is required and given.
Most browsers allow cookies to be blocked or deleted. Blocking strictly necessary cookies may prevent parts of the Service from working.
The Service is a business product and is not directed to anyone under eighteen. We do not knowingly collect personal information from children. If we learn we have done so, we will delete it. Contact us if you believe a child has provided us with information.
We may update this Policy from time to time. The date above shows the most recent revision. Where changes are material we will provide additional notice, by email or in the product, before they take effect. Continued use after that point constitutes acceptance.
Ematrics LLC, a Wyoming limited liability company, 30 N Gould St Ste R, Sheridan, WY 82801, United States.
Privacy enquiries and rights requests: info@ematrics.com.