Revoke access and remove data
1. Revoke Google access
- Open Google Account third-party connections.
- Select the relevant integration.
- Choose the option to remove or revoke its access.
Revocation prevents the integration from obtaining new Google access tokens. It does not automatically delete data already stored by the integration.
2. Remove the account from the application
If the application provides account-management controls, remove or disable the connected account there. For Bichon, remove or disable the email account and its OAuth authorisation within the Bichon administration interface.
3. Request deletion of retained data
Send a request from the affected Google account to dazza12@gmail.com. Identify the application and account, but do not send passwords, OAuth codes, access tokens or refresh tokens.
The operator will verify the request, remove active application data, and allow any applicable backup retention period to expire. Confirmation will be provided when practical.
Bichon-specific effect
Removing Bichon's local archive does not delete the authoritative messages in Gmail. Revoking OAuth access prevents further synchronisation. If an operator has explicitly restored or changed data in Gmail, revocation does not undo those completed actions.