Privacy Policy & Data Use Statement

Application: ATMGC — Add To My Google Calendar
Project ID: calendar-bot-488812
Last updated: May 21, 2026

Google API Limited Use Disclosure

The use and transfer of information received from Google APIs to ATMGC will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Specifically, ATMGC:

• Uses Google Calendar data only to create calendar events explicitly requested by the user.
• Does not share, sell, or transfer Google user data to any third party for advertising or other purposes unrelated to the app's core functionality.
• Does not use Google user data to train, improve, or develop any AI or machine-learning models — including third-party AI models.
• Does not allow humans to read Google user data unless the user explicitly requests support assistance, doing so is necessary for security purposes, or required by law.

Data We Access

ATMGC requests the following Google OAuth scope:

• https://www.googleapis.com/auth/calendar — used solely to create Google Calendar events on the authenticated user's behalf.

No other Google account data is accessed, read, or stored.

Third-Party AI Services

ATMGC uses third-party AI services to process user-provided message text and voice recordings before creating a calendar event. These services receive only the content of messages the user directly sends to the bot:

• Anthropic Claude (claude-sonnet-4-6) — parses natural language text to extract event details (title, date, time, location). No Google API data is passed to this service.
• Google Gemini (gemini-2.5-flash) — transcribes voice messages to text. Audio is uploaded temporarily via the Gemini Files API and is not retained. No Google Calendar data is passed to this service.

No data received from Google Workspace APIs is sent to, stored by, or used to train any AI model. The AI services receive only the raw message text or audio provided directly by the user — not any data retrieved from Google Calendar or other Google services.

Data Retention

• Google OAuth tokens are stored in an encrypted SQLite database on the server and used only to authenticate Calendar API calls on the user's behalf.
• No calendar event data is retained after the event is created.
• Users may revoke access at any time via their Google Account permissions page.

Contact

For questions about data use or to request data deletion, contact: ihtiyor2655742@gmail.com