Using Assist
These conditions apply to your use of this development build of Assist, provided by Hariharasudhan. Use Assist only where you have permission to use AI assistance and to process the information involved. If you do not agree, do not download or use this build.
Respect the people in the meeting
Before listening, transcribing, or capturing screen content, provide the notices and obtain the permissions and consent required by applicable law and the rules of your workplace, school, and meeting platform. Do not use Assist for unauthorized surveillance, prohibited assistance, impersonation, or misleading others about your work. A hidden panel does not remove these responsibilities. Your agreement here does not establish consent from meeting participants.
Choose where your data goes
On-device mode processes meeting audio and answers on your Mac after the required models are downloaded. When you select a cloud provider, relevant conversation text, context notes, and questions are sent to that provider; pressing Screen in cloud mode can also send a screenshot. Review the selected provider’s terms and privacy practices. Only process content you are authorized to share, and avoid sending sensitive information without the necessary authorization.
Understand what is retained
Assist does not save meeting audio. Its live transcript is held in memory and clears when you quit. Settings and context notes may persist locally, and API keys are stored in macOS Keychain. Cloud providers may retain information under their own policies. The acceptance step on this page saves a version and timestamp locally in your browser when storage is available; it does not send an acceptance record to Assist’s developer. Clearing browser data removes that local record.
Check the suggestions
AI answers and transcripts may be inaccurate, incomplete, or unsuitable. You remain responsible for checking information and deciding what to say or do. Do not rely on Assist as a substitute for qualified professional advice or as the sole basis for decisions with significant consequences.
Development-build limitations
This download is an Apple Development-signed build, not a notarized public release. It requires Apple silicon and macOS 26 or newer. Features and compatibility may change, and uninterrupted operation or a particular result is not promised. Review your Mac’s security prompts before installing. Nothing in these conditions excludes rights or protections that applicable law does not allow to be excluded.
If you stop using Assist
You can stop listening, quit, or uninstall Assist at any time. You can remove downloaded models in the app’s settings. Remove any context or credentials you no longer need. Updated terms will carry a new version and will be presented for acceptance on future website downloads.
Worldwide use
These conditions apply wherever you use Assist. You must assess the laws and rules relevant to you, your organization, each participant, and any cloud-provider destination. Obtain required notices, permissions, and consent before processing meeting or screen content. If you cannot establish that a use is permitted, do not use Assist for that activity. Mandatory local rights and duties continue to apply. These terms do not certify legal compliance or replace participant consent, a privacy notice, a data-processing agreement, or professional legal advice.
Regional guidance
These source-linked notes cover 16 jurisdictions or regions. They are a starting point, not an exhaustive review of every country, state, sector, or exception. Check current rules before use. Reviewed October 8, 2026.
Read the regional notes
United States
Federal law includes a one-party-consent exception for certain private interceptions, subject to limits. State laws and the locations of every participant can impose additional requirements. Before using Assist, check the applicable state recording, privacy, employment, and sector-specific rules; the federal exception is not a nationwide permission slip.
US Department of Justice — consent exceptionsCanada
For organizations covered by PIPEDA, the Privacy Commissioner’s customer-call guidance requires an appropriate purpose, notice of recording and its purpose, and consent. Provincial laws and workplace rules can also apply. Transcription and cloud processing need their own assessment; a download checkbox is not the callers’ consent.
Office of the Privacy Commissioner — customer callsEuropean Union / European Economic Area
Identify an applicable GDPR lawful basis before processing personal data. Consent is one possible basis, not a universal shortcut. Assess transparency, minimization, individual rights, sensitive information, and any processor agreement. Transfers outside the EEA must also meet Chapter V requirements; national recording and employment rules still matter.
EDPB — lawful processing and international transfersUnited Kingdom
The ICO’s online-meeting guidance calls for a justified purpose, a lawful basis, and clear information for participants about recording and its use. Consider less intrusive alternatives, access, security, and retention. Check international-transfer rules separately when selecting a cloud provider.
ICO — online meetings and surveillance principlesSwitzerland
Under the FADP, sending personal data abroad requires an appropriate level of protection or another permitted route. Individuals must receive required information about foreign disclosure. Review the destination and safeguards before using a cloud AI provider; also check rules governing the conversation itself.
FDPIC — cross-border transfer of personal dataAustralia
Where the Australian Privacy Principles apply, APP 5 addresses collection notices and APP 8 addresses overseas disclosure. Check whether a cloud-provider arrangement is a use or disclosure and what safeguards apply. State and territory listening-device and workplace-surveillance rules must be checked separately.
OAIC — Australian Privacy PrinciplesNew Zealand
Information Privacy Principle 12 regulates disclosures to foreign recipients, with comparable safeguards or other permitted conditions. An overseas agent acting only on your behalf may be treated differently from a recipient using data for its own purposes. Check your provider’s actual role and policies.
Privacy Commissioner — Principle 12India
The DPDP framework has a published commencement timeline alongside the 2025 Rules. Verify which provisions are in force when you deploy; do not assume every obligation began on the same date. Review the applicable notice, consent or other permitted processing route, security, children’s-data, and transfer requirements, together with other relevant laws.
MeitY — DPDP Rules and enforcement timelineSingapore
The PDPA’s Transfer Limitation Obligation requires the relevant protections when personal data is transferred overseas, including applicable comparable-protection arrangements. Review consent, purpose, and notification requirements separately; agreeing to Assist’s terms does not authorize disclosure of someone else’s personal data.
PDPC — Transfer Limitation ObligationJapan
Review the APPI rules on purposes of use, third-party provision, and provision to recipients in foreign countries before sharing meeting content with a cloud provider. The required information and consent or other permitted arrangement depend on the transfer. Consult the current Japanese legal text; English translations are reference materials.
PPC — APPI laws and policiesBrazil
International transfers must comply with the LGPD and the applicable ANPD transfer framework. Resolution 19/2024 addresses routes including adequacy, contractual clauses, and binding corporate rules. A valid transfer mechanism does not replace the other requirements that apply to processing the meeting content.
ANPD — international data transfer regulationSouth Africa
POPIA sets conditions for processing personal information and regulates transfers abroad. Review those conditions, including section 72 when sharing with a foreign recipient, before enabling a cloud provider. Consider notice, purpose, security, and the rights of the people whose data you process.
South African Government — POPIASouth Korea
The PIPC’s overseas-business guidance highlights PIPA obligations including privacy notices, individuals’ rights, and cross-border-transfer procedures under Article 28-8. Check the applicable processing and transfer route before sending Korean participants’ information to a provider abroad.
PIPC — guidance for overseas businessesChina
PIPL requires a permitted basis for processing, transparency, a specific purpose, and limits on collection and retention. It can apply to certain processing outside China as well. Review separate-consent and cross-border requirements where applicable before cloud use; ordinary download acceptance is not a substitute.
Official PIPL textSaudi Arabia
The PDPL can apply to processing in the Kingdom and certain processing abroad involving residents. Check the law and the current regulation on transfers outside the Kingdom before sharing meeting data with a foreign cloud provider. Identify the applicable processing basis, disclosures, and safeguards.
SDAIA — PDPL knowledge centerUnited Arab Emirates
Check whether the federal personal-data law or a separate regime, such as the DIFC’s, governs your activity. Review the applicable processing and overseas-transfer conditions and any sector rules. Do not assume one set of UAE terms covers every free zone, employer, or category of information.
UAE — federal personal-data protection lawOther countries, territories, and cross-border calls
The worldwide-use conditions above still apply. A missing country is not permission to record or process information. Obtain local advice about interception, privacy, labor, confidentiality, children’s data, international transfers, and any sector rules before using Assist. The locations of other participants can matter as well as your own.
Find privacy authorities through the Global Privacy Assembly