Privacy Policy

Effective date: August 20, 2026

Cal2Meet ("we," "us," or "our") is committed to protecting your privacy. This Privacy Policy explains how the Cal2Meet macOS application handles information. Cal2Meet runs entirely on your Mac and acts as a client-side tool with no backend servers.

1. Information We Access

Cal2Meet accesses your Google Calendar data to provide its core functionality. Using the read-only scope https://www.googleapis.com/auth/calendar.events.readonly, the app reads, from your primary calendar:

• Event titles
• Event start and end times
• Conference links, such as Google Meet URLs

Only events for the current day are requested. Cal2Meet never modifies, creates, or deletes calendar events.

2. How We Use the Information

The accessed information is used locally on your device to:

• Display a countdown to your next meeting in the macOS menu bar.
• Provide audio and visual alerts as a meeting approaches.
• Automatically open meeting URLs in your default browser for your convenience.

3. Data Storage and Retention

• No remote storage. We do not store your calendar data on any server. All information fetched from the Google Calendar API is kept in memory and processed locally on your device, and it is discarded when the app quits.
• No sharing. We do not share, sell, or trade your personal information or calendar data with any third party.
• No tracking. Cal2Meet contains no analytics, advertising, or usage-tracking software.

4. Authentication and Security

Cal2Meet uses Google OAuth 2.0 for sign-in. Your authentication tokens are stored securely in the macOS Keychain on your device and are used only to access the Google Calendar API on your behalf. You can revoke Cal2Meet's access at any time from your Google Account permissions page.

Safeguards for Google user data

Cal2Meet protects the Google user data it accesses with the following measures:

• App Sandbox. Cal2Meet runs inside the macOS App Sandbox. It is confined to its own container and cannot read the files, data, or memory of other applications.
• Outbound-only network access. The app holds the outgoing network entitlement only. It cannot accept inbound connections, and it exposes no listening port or remote interface.
• Encrypted transport. All calendar requests are made over HTTPS/TLS directly to Google's API endpoints. Calendar data never traverses a server operated by us, because we operate none.
• Credentials are never seen by the app. Sign-in is performed by Google's own authorization flow. Cal2Meet never receives, handles, or stores your Google password.
• Tokens protected by the operating system. OAuth tokens are held in the macOS Keychain, which encrypts them at rest and restricts access to this application. Signing out removes them.
• No persistence of calendar data. Events exist only in memory while the app is running. The single value Cal2Meet writes to disk is your mute preference; no event title, time, attendee, or meeting link is ever written to storage.
• Least privilege. Cal2Meet requests exactly one scope, calendar.events.readonly, which is read-only. The app has no technical ability to create, modify, or delete calendar data.
• No third-party data processors. There is no backend, no database, and no analytics, advertising, or crash-reporting SDK. Google user data is not transmitted to any party other than Google.
• Verified distribution. Every build is code-signed with an Apple-issued certificate and distributed through the Mac App Store, so the binary you run is the one we published.

5. Google API Limited Use Disclosure

Cal2Meet's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

6. Third-Party Services

Cal2Meet relies on Google OAuth for authentication and the Google Calendar API for data access. Please refer to Google's Privacy Policy for details on how Google handles your data.

7. Children's Privacy

Cal2Meet is not directed to children under the age of 13 and does not knowingly collect information from them.

8. Changes to This Policy

We may update this Privacy Policy from time to time. The latest version will always be available at this page with an updated effective date.

9. Contact Us

If you have any questions about this Privacy Policy, contact us at support@lakesoft.jp.