Calendar Bump Privacy Policy

Calendar Bump is a Google Calendar add-on provided by Clarity Board ("we," "us," or "our"). It helps you manage overlapping commitments by moving a displaced event from the app's Calendar calendar to its Bumped calendar until you choose a new time.

This policy explains what information Calendar Bump accesses, how it is used, where it is stored, and how you can delete it.

Summary

• Calendar Bump is designed to work only with the Calendar and Bumped calendars created by the add-on.
• It does not intentionally read, change, or monitor your primary calendar or unrelated calendars.
• Automatic sync is optional. If you enable it, Calendar Bump stores encrypted Google authorization credentials and limited calendar and event metadata in Google Cloud so it can detect conflicts while the side panel is closed.
• We do not sell Google user data, use it for advertising or credit decisions, or use it to train artificial-intelligence or machine-learning models.
• You can disconnect automatic sync and delete the associated server-side data from the add-on.

Information Calendar Bump accesses

With your authorization, Calendar Bump may access or process:

Google Account information

• Your verified Google Account email address, used to authenticate your connection and create a hashed account identifier.

The raw email address is used during authentication but is not stored in the Calendar Bump application database. The database uses a one-way hashed identifier instead.

Calendar information

• The identifiers of the Calendar and Bumped calendars created by the add-on.
• Events and event changes in those calendars, including event identifiers, titles, start and end times, duration, updated time, and collision status.
• Private event metadata added by Calendar Bump to identify whether an event is waiting to be rescheduled.
• Your Google Calendar time-zone setting, used to place reassigned events at the time you selected.

Google's permission model authorizes Calendar Bump to work with events on calendars you own because moving an event between the app's two calendars requires that permission. Calendar Bump is designed to use that access only for the Calendar and Bumped calendars created by the add-on.

Technical information for automatic sync

If you connect automatic sync, Calendar Bump also stores:

• Encrypted Google authorization credentials.
• Calendar notification-channel identifiers and verification tokens.
• Synchronization tokens, connection status, and timestamps.
• A limited Bumped-item record containing the event identifier, event title, original time, duration, the title of the event that displaced it, and the time of displacement.

How Calendar Bump uses information

Calendar Bump uses this information only to:

• Create and identify its two managed calendars.
• Detect overlapping events in the Calendar calendar.
• Keep the newly moved event in its selected time and move the displaced event to Bumped.
• Display Bumped events in the Google Calendar side panel.
• Return a Bumped event to Calendar at the new time you select.
• Operate and renew automatic synchronization when you enable it.
• Authenticate requests, protect the service, diagnose errors, and maintain reliability.

Google API Limited Use disclosure

Calendar Bump's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

Calendar Bump does not:

• Sell Google user data.
• Use Google user data for advertising, retargeting, or personalized marketing.
• Use Google user data to determine creditworthiness or for lending purposes.
• Use Google user data to create, train, or improve a general artificial-intelligence or machine-learning model.
• Transfer Google user data to third-party AI or machine-learning services.
• Allow people to read Google user data except when you specifically request support and authorize access to relevant information, when necessary for security or abuse investigation, or when required by law.

Storage and security

Calendar Bump uses Google Apps Script and Google Cloud services. Basic configuration and temporary Bumped-item metadata may be stored in Google Apps Script user properties associated with your use of the add-on. When automatic sync is enabled, the server-side information described above is stored in Google Cloud Firestore.

Information is transmitted using HTTPS. Google authorization credentials are encrypted before storage using AES-256-GCM. Access to production systems is limited to people and service accounts that need it to operate or protect Calendar Bump.

No online service can guarantee absolute security, but we use reasonable administrative and technical measures designed to protect the information Calendar Bump processes.

Sharing and transfers

We do not sell or rent personal information or Google user data.

Information may be processed by Google and Google Cloud as service providers supporting authentication, calendars, hosting, storage, logging, and security. We may also disclose limited information:

• When you ask us to provide support and authorize the disclosure.
• When reasonably necessary to investigate fraud, abuse, or a security incident.
• When required by law or a valid legal process.
• In connection with a merger, acquisition, or sale of assets, only with the notice and consent required by the Google API Services User Data Policy and applicable law.

Retention and deletion

Calendar Bump retains connection information and Bumped-item records while automatic sync remains connected. A server-side Bumped-item record is deleted when the event is successfully assigned a new time.

To disconnect automatic sync and delete its server-side data:

1. Open Calendar Bump in the Google Calendar side panel.
2. Select Delete automatic sync data.
3. Confirm Delete now.

This deletes the encrypted authorization credentials, notification-channel details, connection record, and server-side Bumped list associated with your account. It does not delete the Calendar or Bumped calendars or their events from Google Calendar.

You can separately delete those calendars in Google Calendar if you no longer want them. You can also revoke Calendar Bump's access from your Google Account permissions.

Uninstalling the add-on or revoking Google access may stop future access, but it may not by itself delete information already stored by the automatic-sync service. For complete server-side deletion, use Delete automatic sync data before uninstalling or email us from the Google Account connected to Calendar Bump.

You may request deletion or assistance by emailing hello@theclarityboard.com. We will verify the request and process it within 30 days.

Limited security and operational logs may be retained temporarily when reasonably necessary for security, fraud prevention, troubleshooting, and legal compliance.

Your choices

You may:

• Use manual conflict checks without connecting automatic sync.
• Disconnect automatic sync and delete its server-side data.
• Revoke Calendar Bump's Google access.
• Uninstall the add-on.
• Delete the Calendar and Bumped calendars from Google Calendar.
• Contact us to request access, correction, or deletion where applicable.

Children

Calendar Bump is not directed to children under 13 or to anyone below the minimum age required to use a Google Account in their jurisdiction. We do not knowingly collect personal information from children.

Changes to this policy

We may update this policy as Calendar Bump changes. We will update the effective date on this page and provide additional notice when required by law.

Contact

For privacy questions or requests:

Clarity Board
hello@theclarityboard.com