Application information

Private services. Clear permissions.

This page explains the Google sign-in and API access used by a small collection of personally operated, self-hosted applications. These services are not offered as a general public sign-up platform.

Immich — photo library sign-in

Immich is a self-hosted photo and video library. Google OAuth may be used to authenticate the account holder, with basic identity details such as name, email address and profile information returned by Google when authorised. Photo storage and management take place in the self-hosted Immich service.

Musubi — calendar connection

Musubi is a self-hosted calendar interface. When a user explicitly connects a Google account, the application requests permission to discover subscribed calendars and read or modify calendar events. These permissions support showing events, creating and editing them, and keeping connected calendars synchronised.

Other private integrations

Additional account-specific integrations may use Google OAuth for authentication. Each client requests its own permissions, as disclosed on Google's consent screen. A PostgreSQL MCP integration is maintained separately for authorised database workflows; it is not presented as a Google Calendar data recipient.

User control and security

Access to the underlying applications is restricted to authorised users. Google permissions are requested during the relevant sign-in or account-connection flow, and can be revoked in Google Account connections. For details on storage, use, retention and deletion, read the Privacy Policy.

Contact

Operator: Taj (independent, personal self-hosting). Contact: qnapsyno@gmail.com.