Effective 18 October 2026

Privacy Policy

This policy describes how Taj, the independent operator of these personally hosted applications, handles information accessed through Google OAuth and connected services. Contact: qnapsyno@gmail.com.

Information accessed

Why information is used

Information is used to authenticate authorised users, show and synchronise their chosen calendars, perform actions they request, maintain account connections, and protect or troubleshoot the services. Google user data is not used to serve advertising or to sell personal information.

Where data is stored and who can access it

Application databases and files are hosted on infrastructure administered by the operator, with backups potentially stored on separate operator-controlled storage. Google remains the provider of the connected account and calendar service. The operator and infrastructure services necessary to run the applications may process information required for these functions. Access to the private applications and data is limited to authorised accounts and administrative operations.

Sharing and onward transfers

Google account information is not sold or supplied to advertising networks. Data may be exchanged with Google APIs to complete a requested sign-in or calendar synchronisation action. Additional disclosure may occur if required by law or to protect the services. This public information site does not itself request Google account data.

Retention and deletion

Connected data and authentication records may remain while an account or integration is active. Disconnecting an integration or deleting an account may remove associated local tokens and stored data, subject to application behaviour and backup retention. Backups may persist temporarily until their normal rotation. To request account/data deletion or ask about retention for a specific service, email qnapsyno@gmail.com.

Control of Google access

Users can withdraw Google OAuth permissions at any time from Google Account connections. Revocation stops future authorised API access once the relevant credentials cease to be usable. It does not necessarily delete previously synchronised local data; contact the operator if removal is required.

Security

Services use HTTPS for public access and access controls for private applications. Reasonable precautions are taken to restrict credentials and administrator access. No network service can be guaranteed entirely free from risk.

Changes and questions

This policy may be updated when services, integrations or data practices change. The updated date will appear on this page. Direct privacy questions to qnapsyno@gmail.com.