Clario is a meeting recording, transcription and summary app operated by Emiactech, at emiactech.com. This policy explains what information the app and its supporting services process, why, and how you can control it.
Transcription runs on your device. Meeting audio leaves it only in the ways described below: training contributions, which are on by default, and Google Drive archiving and server meeting bots, which you choose. Google Calendar and AI summaries involve the data flows described below too.
Your account and Google sign-in
When you sign in with Google, Clario receives your Google account identifier, email address and profile name to create or identify your Clario account. Our server stores account information and session records to authenticate you and control access to your data. Google handles your Google password; Clario does not receive it.
Google Calendar access
Connecting your calendar is optional. With your permission, our server reads events from your primary Google Calendar to display your schedule and, according to your chosen settings, send a meeting bot even when your computer is offline.
The calendar cache includes event identifiers, titles, times, meeting links and your response status. Clario stores an encrypted refresh token on its server to keep the connection working. Calendar data is also cached on your device for the calendar view.
The requested Google permission, calendar.events, permits
viewing and editing events. The current calendar integration reads events;
it does not yet create, change or delete your Google events. It does not
request Gmail access. Google Drive access is a separate permission, asked for
only if you connect Drive (see Google Drive archiving).
Clario uses Google data to provide the features you request. We do not sell Google user data, use it for advertising, or use it to train generalized AI models. Our use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.
Local recordings and screen text
In Local Recording mode, captured audio and imported audio files are processed on your device. Transcription runs locally, and no audio is sent to a speech-to-text provider. Audio can leave your device in two ways, described below: training contributions, which are on by default, and Google Drive archiving, if you use it.
If you use screen context, text recognition happens locally. Recorded screen images are not sent to a summary provider. Your local library contains the recordings, transcripts, summaries and related information that you keep in the app.
Training contributions
Clario uses meeting audio to improve its transcription. While the setting Help improve Clario is on, and it is on by default, the audio of completed meetings is uploaded to storage Clario operates, one meeting at a time while the app is open and idle. For a local recording that is its microphone and computer-audio tracks; for a server meeting bot recording, the mixed recording.
It never includes the screen video, the meeting title, the transcript, screen text, calendar data, file paths or participant names. The audio is kept with no deletion date. Switching the setting off in Settings stops future uploads and discards any not yet sent; audio already uploaded is kept. The people you record are in this audio, so tell them you are recording.
Google Drive archiving
If you connect a Google account for Drive, you can copy a meeting's playable
recording into your own Google Drive, in a folder of Clario's. Clario asks only
for the drive.file permission, which reaches the files Clario creates
and nothing else in your Drive.
Our server keeps that permission's refresh token, encrypted, and gives the app short-lived access. The file goes from your device straight to Google and does not pass through our server. Clario can also show how much space your Drive has, list its own folder, and move a file you choose to your Drive's trash. It never sends the minutes, the transcript or screen text to Drive.
Server meeting bots
Server Bot mode is a separate recording path. When you request a bot or enable automatic joining, a bot joins the meeting and captures audio in Clario-controlled infrastructure using Vexa. This meeting audio is processed on the server for recording and delivery, then downloaded to your device for local transcription.
Our server stores meeting identifiers and links, bot status and account access records to operate the bot and deliver its recording. Other authorized participants using Clario may have access to the same bot recording. Removing your access does not remove another participant's access.
Use meeting bots only when you have permission to record, and tell participants that recording is taking place.
AI summaries and questions
When you request a summary or ask a question using an AI provider, relevant transcript text, your question and any included screen text are sent to the provider you selected. Audio and screen images are not sent through this summary path.
The provider connection you configure is used for these requests. Desktop provider credentials are stored on your device. The provider processes requests under its own privacy and retention terms, which you should review before sending meeting content.
Usage information and service operation
Clario collects usage counts, durations, app and operating-system versions, and typed error codes to understand reliability and feature use. This telemetry may be associated with your Clario account. It does not contain recording titles, transcripts, screen text, audio, images or file paths. Telemetry is on by default and can be switched off in the app.
Our hosting infrastructure processes network information, such as IP addresses and request metadata, when you visit the website or connect to the service. Operational records help us run and troubleshoot authentication, calendar connections and meeting bots.
Who processes your information
Google processes sign-in, calendar and Drive requests, and stores training contributions in a Google Workspace shared drive that Clario operates. Our hosting infrastructure processes server account, calendar and bot data. The AI provider you choose processes the text you submit to it. These services may process information outside your country.
Access to server data is restricted to operating and supporting the service. Google refresh tokens are encrypted at rest. We may disclose information where required by law. No storage or transmission method can guarantee absolute security.
Retention, deletion and your choices
- Local library: recordings and related data remain on your device until you delete them. Copies you export or back up are managed separately.
- Calendar: disconnecting in Clario deletes the server's calendar grant and associated cached events and channels. You can also revoke access in your Google Account connections. Revoking Google access does not itself delete your Clario account.
- Server records: account, bot-delivery and operational records are retained to provide and maintain the service. Contact us to request deletion of your account or server-held data, including bot recordings. Shared access, backups and legal obligations can affect what can be removed immediately.
- Training contributions: uploaded audio is kept with no deletion date. Switching Help improve Clario off stops future uploads.
- Google Drive: files you archive are in your own Drive, under your control, until you remove them.
- AI providers: deleting a local summary does not delete data already processed by your selected provider. Its retention and deletion procedures apply.
You may contact us to request access, correction or deletion of personal information, or ask about retention. We may need to verify that a request concerns your account before acting on it.
Contact and policy changes
For privacy questions or requests, email abhishek@emiactech.com.
We will update this page when our data practices change and revise the date above. Changes that require additional permission will be presented through the relevant consent flow.