Privacy Policy

Last Updated: June 18, 2026

This Privacy Policy describes how another-meet ("the application", "we", "our") collects, uses, and handles your information when you use the command-line interface tool.

1. Google API Services Usage Disclosure

another-meet's 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.

Why We Access Your Google Data

another-meet requests access to specific Google API scopes to function directly within your terminal:

  • Google Calendar Data (https://www.googleapis.com/auth/calendar.events): Used strictly to create, schedule, list, and fetch meeting links locally on your machine.
  • User Identity Data (https://www.googleapis.com/auth/userinfo.email and openid): Used solely to retrieve and display your email address in the CLI interface (e.g., "Authenticated as user@example.com") so you can verify which account is active.

How Your Data is Handled

No user calendar data or identity info is sent to external servers. All interactions with the Google APIs happen directly between your local machine (via the CLI) and Google's servers.

We do not collect, store, sell, or share your Calendar data or personal information. The OAuth token generated during the login process is stored locally on your machine at ~/.another-meet/token.json and is used solely to authenticate your local API requests to Google.

2. Information Collection and Use

Because another-meet is a locally executed command-line application, we do not collect any personal data. We do not operate any backend servers that track your usage, read your calendar, or intercept your credentials.

3. Data Security

Your Google OAuth tokens are saved locally in a hidden folder (~/.another-meet) on your hard drive with restricted file permissions (0600). You are responsible for the security of your local environment.

You can revoke another-meet's access to your Google account at any time by running another-meet auth logout, which deletes the local token file, or by removing access via your Google Account Permissions page.

4. Changes to This Privacy Policy

We may update our Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy on this page.

5. Contact Us

If you have any questions about this Privacy Policy, please contact us via the GitHub Repository.