Terms of Use

1. Purpose of the service

cloudcal-bridge connects a Google account to a self-hosted service, reads calendar information with read-only permissions, and generates private ICS subscription URLs for calendars selected by the user. A typical use is subscribing to a Google calendar from Nextcloud or another calendar client inside a personal homelab.

2. Acceptance of these terms

By connecting a Google account to cloudcal-bridge or using a private feed produced by the application, you agree to these Terms of Use and acknowledge the related Privacy Policy. If you do not agree, do not connect an account or use the service.

3. Your account and authorization

You must only connect a Google account that you are authorized to use. You are responsible for reviewing the permissions displayed by Google and deciding whether to grant them. cloudcal-bridge requests read-only calendar permissions and uses an OAuth refresh token so configured feeds can continue refreshing without an interactive browser session.

You may revoke Google's authorization through your Google Account settings. Revoking Google authorization can stop cloudcal-bridge from refreshing calendars until authorization is granted again.

4. Private feed URLs

Private ICS URLs generated by cloudcal-bridge act as bearer credentials. Anyone with a valid feed URL can retrieve the calendar data exposed by that feed without signing in to the management interface. You are responsible for storing those URLs securely and for deciding which calendar clients or people may receive them.

If a feed URL is accidentally shared, recorded in an unsafe log, or otherwise exposed, revoke it through cloudcal-bridge. A replacement feed should use a newly generated URL.

5. Acceptable use

You may use cloudcal-bridge for lawful personal, household, development, or internal administrative purposes. You must not use it to access a Google account or calendar without authorization, defeat Google's access controls, intentionally overload Google APIs or the host system, distribute another person's private calendar information without permission, or use the application in a way that violates applicable law or Google service terms.

6. Self-hosted operation

cloudcal-bridge is designed for self-hosting. The deployment operator is responsible for server administration, HTTPS, firewall rules, DNS, reverse-proxy configuration, secrets, updates, database backups, log retention, access control, and physical or virtual infrastructure. The operator is also responsible for keeping the deployment's Google Cloud OAuth configuration accurate.

A public cloudcal-bridge deployment should use a domain controlled by the operator and valid HTTPS. Management access should be limited to intended users, and the persistent database and application secrets should be backed up and protected appropriately.

7. Google and third-party services

cloudcal-bridge depends on Google OAuth and the Google Calendar API and may be used with third-party calendar clients such as Nextcloud. Those services are provided independently and are governed by their own terms, privacy policies, availability, quotas, and technical behavior. cloudcal-bridge is not affiliated with or endorsed by Google or Nextcloud unless explicitly stated otherwise by those organizations.

8. Availability and changes

The application may change as features, Google APIs, security practices, or homelab requirements evolve. Functionality can also be interrupted by network failures, expired or revoked OAuth grants, Google API changes or quotas, host maintenance, database problems, misconfiguration, or third-party outages. No particular level of uptime or uninterrupted access is guaranteed.

9. Data accuracy

ICS output is generated from data returned by Google Calendar within the configured feed window. Calendar clients may cache subscriptions or refresh them on their own schedule. As a result, a subscribed calendar can temporarily differ from the current state in Google Calendar. You should not rely on cloudcal-bridge as the only record of important calendar information.

10. No warranty

cloudcal-bridge is provided on an “as is” and “as available” basis for self-hosted use. To the extent permitted by applicable law, no warranties are made regarding uninterrupted operation, fitness for a particular purpose, error-free output, data preservation, compatibility with every calendar client, or continued availability of Google APIs.

11. Limitation of responsibility

To the extent permitted by applicable law, the cloudcal-bridge software authors and the operator of a deployment are not responsible for indirect, incidental, special, consequential, or similar losses arising from use of the software, inability to use it, exposure of a private feed URL, calendar-client behavior, third-party services, or loss of locally hosted data. Some jurisdictions do not allow certain limitations, so these limitations apply only to the extent allowed by law.

12. Ending use

You can stop using cloudcal-bridge by revoking generated feeds and removing the application's Google authorization. For a self-hosted deployment, locally stored account data must be removed by the deployment operator. The operator may also disable access to a deployment when necessary for security, maintenance, legal compliance, or retirement of the service.

13. Changes to these terms

These terms may be updated when the application, deployment model, or applicable requirements change. The effective date should be updated when revised terms are published. Material changes should be made available on this page before or when the corresponding application changes are deployed.

14. Contact

Questions about a particular cloudcal-bridge deployment should be directed to the administrator of the domain where it is hosted. That administrator controls the deployment and its local infrastructure.