Meeting Intelligence
Privacy policy
This policy explains how Meeting Intelligence handles information when you visit this site, sign in, connect accounts or use meeting assistance.
The essentials
- Listening starts when you choose to start it.
- Meeting audio and text are processed by AI services to provide assistance.
- Connected accounts are used to find related work; creating a Jira task requires your confirmation.
- You can stop listening, disconnect integrations and contact us about deletion.
1. Who we are
Meeting Intelligence is operated by Auriqis Technologies, India (“we”, “us”). Contact us about privacy at hello@auriqis.com.
2. Information we process
- Account information: your email address, account identifier, sign-in events and session credentials. We use email codes to authenticate you.
- Meeting information: microphone and meeting-tab audio while listening is active, text transcribed from that audio, recent conversation context, suggested tasks and search queries.
- Connected services: authorization tokens, authorized Atlassian sites and related search results, including file or page names, issue details, descriptions, identifiers, links and timestamps.
- Operational information: device and connection information, IP addresses used for request limits, errors and service logs. Logs can include meeting excerpts, search terms and returned file names.
- Communications: information you include when you email us, including requests for early access or support.
We do not capture camera video or share your screen. Live listening currently supports Google Meet.
3. How we use information
We use this information to authenticate you, transcribe meeting speech, identify relevant topics, search accounts you connect, suggest follow-ups, create Jira tasks you confirm, recover interrupted sessions, prevent abuse and provide support. We do not sell personal information or use connected-service data for advertising.
You are responsible for informing meeting participants and obtaining any consent or authorization required before listening starts. If you do not want meeting information processed, do not start listening or stop the active session.
4. Google Drive and Atlassian access
Connecting an account is optional and requires your authorization. Google Drive authorization currently grants read-only access. The app searches for related files and retrieves file metadata and links; it does not edit or delete Drive files. In the current implementation, Drive search results are not sent to AI providers.
Atlassian access supports Jira and Confluence searches and creating Jira tasks after you choose a project and confirm. Atlassian’s authorization permissions are broader than the task-creation action offered in our interface. Your access is also limited by the permissions of your connected account.
Our use and transfer of information received from Google APIs is subject to the Google API Services User Data Policy, including its Limited Use requirements. We do not use Google API user data to train generalized AI models. We do not permit human access to that data except as allowed by the policy, such as with your consent for support, security investigations or legal obligations.
5. AI processing and service providers
We use OpenRouter and the model providers it routes requests to for transcription and meeting analysis. Audio and relevant meeting text are transmitted to these providers to produce the features you request. AI output can be inaccurate; review it before acting.
We use Amazon Web Services for hosting, account authentication, email delivery, storage and encryption. Google and Atlassian process authorized searches and requests through their own services. Our principal application infrastructure is in Mumbai, India; content delivery and third-party processing can occur in other countries.
Providers have their own processing and retention practices. We do not claim that all providers offer zero retention. See OpenRouter’s privacy policy, AWS’s privacy notice, Google’s privacy policy and Atlassian’s privacy policy. We may also disclose information where required by law or reasonably necessary to protect people, investigate abuse or defend legal rights.
6. Storage and retention
- Audio: processed in short windows. Temporary audio files are removed after processing; we do not maintain a full meeting recording in our application. This does not determine AI providers’ retention.
- Meeting recovery: encrypted checkpoints can contain recent transcript context, task suggestions and search results. They are marked to expire 24 hours after their last update. Expired records may remain physically stored until automatic cleanup.
- Connected-account credentials: encrypted and kept while the connection is active. Disconnecting clears the active stored credentials. Historical backup copies follow backup retention and are not necessarily erased immediately.
- Accounts: retained while you use the service, until deletion is requested, or as needed for security or legal obligations. Signing out is not account deletion.
- Other records: sign-in codes expire after five minutes. Authentication logs are configured for 30-day retention. Meeting-service logs rotate by size rather than a fixed day count; they may retain meeting excerpts and search information beyond the 24-hour checkpoint period. Storage backups and security records may remain longer.
The extension stores sign-in session information and settings locally in your browser. These support session renewal and your preferences.
7. Your choices and requests
You can stop listening, disconnect accounts in the extension and revoke the app’s access through Google or Atlassian account settings. Revoking a connection prevents future authorized access; it does not delete items already created in Jira or information held by those services.
For account deletion, access, correction or other privacy requests, email hello@auriqis.com from your account address. Account deletion currently requires contacting us; there is no automated deletion button. We may verify your identity and retain information required for legal or security reasons. Rights depend on the laws that apply to you.
8. Website storage, security and children
This website has no advertising trackers or analytics scripts and does not set application cookies. Our hosting provider processes connection information to deliver and protect the site. The extension uses local browser storage for its operation.
We use encrypted connections, encrypted stored integration credentials and access controls. No system is guaranteed secure. Do not use the service for information you are not authorized to share or for highly sensitive material without confirming that the service is suitable for your requirements.
The service is intended for adults and is not directed to children under 18. Contact us if you believe a child has provided personal information.
9. Changes and contact
We will update the effective date when this policy changes. For material changes, we will provide an appropriate notice on the site or in the product. Questions and requests: hello@auriqis.com.