Revoke access and delete GUBUS data

1. Stop Google access

Use Revoke OAuth access in the GUBUS developer dashboard. GUBUS first asks Google to revoke the grant and then erases encrypted access and refresh-token material from its primary database. You can also revoke GUBUS directly in Google Account permissions.

2. Delete a project or account

Use the project deletion and account deletion controls in the authenticated developer dashboard. Review the deletion summary before confirming. For assisted deletion, email privacy@gubus.io from the registered address and identify the account or project.

3. Choose what happens to Google artifacts

GUBUS-created Drive files may be retained in your Drive, moved to Trash, or deleted according to the option shown by the product. Some Apps Script artifacts can require owner-side deletion when Google’s API does not permit automatic removal. GUBUS must report any such remainder rather than claim it was deleted.

Timing

OAuth ciphertext is erased immediately after successful revocation; 24 hours is the support escalation ceiling if the operation fails. Deleted primary database data may remain in Cloud SQL point-in-time recovery logs for up to seven days and in the seven most recent scheduled backups. Ordinary logs expire after 30 days; required security/audit logs may remain for up to 400 days.

Need help?

Email privacy@gubus.io. The support/privacy mailboxes must be activated and tested before verification submission.