Privacy Policy

chief822 Google Calendar Booking

Effective Date: November 2, 2026

Last Updated: November 2, 2026

1. Introduction

This Privacy Policy explains how chief822 Google Calendar Booking ("Application", "we", "our", or "us") collects, accesses, uses, and protects information when businesses connect their Google accounts to our appointment-management integration.

The Application is independently operated by Muhammad Ali Khalid.

Our service allows multiple businesses to connect their individual Google accounts to manage appointments through Google Calendar and send automated transactional emails through Gmail. These emails may include customer email verification messages, booking confirmations, booking updates, cancellation notifications, and appointment reminders.

We respect user privacy and are committed to protecting information accessed through Google APIs.

2. Information We Access

When a business connects its Google account and grants the requested permissions, the Application may access the following information:

Google Calendar Data

Depending on the permissions authorized by the user, the Application may:

Calendar information is accessed only to perform appointment-management operations requested through the Application.

Gmail Data

The Application requests permission to send emails through the connected Google account using Gmail.

This permission is used exclusively to send automated transactional communications requested or triggered through the Application, including:

To prepare and send these emails, the Application may temporarily process information such as:

This information is processed only to generate and deliver the relevant transactional email.

The Application does not request permission to read Gmail inboxes, access email conversations, or retrieve existing email messages.

Emails are sent through the Gmail account connected and authorized by the relevant business. The business is responsible for the accuracy of customer information and the appropriateness of the communications it sends.

OAuth Authentication Information

When a business authorizes Google access, the Application receives OAuth authentication credentials, which may include:

These credentials are retained to maintain the connection between the business's Google account and the Application.

3. How We Use Information

Information accessed through Google APIs is used exclusively to provide the Application's functionality.

Our uses include:

We do not use Google user data for unrelated purposes.

4. Data Storage and Retention

The Application is designed to minimize the storage of Google user data.

OAuth Tokens

OAuth access and refresh tokens may be stored to maintain authorized Google account connections and avoid requiring businesses to authenticate repeatedly.

These credentials are treated as sensitive authentication information and are protected using appropriate access restrictions and security safeguards.

Calendar Information

Calendar information is retrieved from Google when required to perform appointment-management operations.

The Application does not intentionally maintain a separate persistent database of Google Calendar event contents.

Events created or updated through the Application remain in the connected user's Google Calendar.

Email Information

Gmail is used to send automated transactional emails through the connected and authorized Google account.

These emails may include:

To send these communications, the Application may temporarily process customer email addresses, names, booking information, appointment dates and times, booking statuses, email subject lines, and message content.

The Application does not intentionally maintain a separate persistent database of Gmail inbox contents, existing email conversations, or sent email message bodies.

Information necessary to prepare and send transactional emails may be processed temporarily. Emails sent through Gmail may remain in the connected business's Gmail Sent folder and are subject to Google's data retention practices.

Retention Period

OAuth tokens are retained while the associated Google account connection remains active and authorized.

When a business disconnects its Google account or revokes authorization, the associated stored OAuth credentials will be deleted within a reasonable period, subject to applicable legal or security requirements.

5. Multi-Business Data Separation

The Application supports multiple independent businesses.

Each business connects its own Google account and authorizes access independently.

We maintain logical separation between business connections and their associated authorization credentials.

One business's Google account credentials and information are not made available to another business through the Application.

Each business is responsible for authorizing the Google account it intends to connect.

Transactional emails are sent through the Google account authorized by the relevant business. Customer booking information and email communications are associated with the business that generated the relevant booking. One business's Gmail account is not used to send another business's transactional emails.

6. Sharing of Information

We do not sell, rent, or trade Google user data.

Google user data is not shared with advertising networks, data brokers, or unrelated third parties.

Information may be processed by infrastructure or service providers strictly as necessary to operate and maintain the Application, subject to appropriate confidentiality and security obligations.

Information may also be disclosed where required by applicable law or to protect the security and integrity of the Application.

Transactional emails are delivered using Google's Gmail service through the Google account authorized by the relevant business. Google processes these communications in accordance with its applicable privacy policies and terms. We do not sell or use customer email addresses or booking information for advertising or unrelated marketing purposes.

7. Google API Services User Data Policy and Limited Use

The Application's use and transfer of information received from Google APIs will comply with the Google API Services User Data Policy, including its Limited Use requirements.

Specifically:

The Application does not use Google user data for generalized artificial intelligence or machine-learning model training.

Official policy: https://developers.google.com/terms/api-services-user-data-policy

8. Security

We take reasonable technical and organizational measures to protect authentication credentials and information processed through the Application.

These measures include restricting access to OAuth credentials and limiting access to information to what is necessary to operate the service.

However, no internet-based system can guarantee absolute security.

9. Revoking Google Account Access

Businesses can revoke the Application's access to their Google accounts at any time through their Google Account security settings.

Google account permissions can be reviewed or revoked here:

https://myaccount.google.com/permissions

After authorization is revoked, the Application can no longer access the associated Google services using that authorization.

10. Children's Privacy

The Application is intended for businesses and their authorized users. It is not designed to collect personal information directly from children under the age applicable under relevant privacy laws.

11. Changes to This Privacy Policy

We may update this Privacy Policy to reflect changes in our services, technical operations, or applicable legal requirements.

Updated versions will be published on this page with a revised Last Updated date.

12. Contact Information

For questions, privacy concerns, or requests concerning information handled by the Application, contact:

Application: chief822 Google Calendar Booking

Operator: Muhammad Ali Khalid

Email: khalidmuhammadali822@gmail.com

Go to homepage