Google Data, Deletion and Revocation

Procedure index

Google data revocation and deletion procedure

DISCONNECT GMAIL INSIDE HONEST CODES
What user does
Sign in as a tenant administrator and use the Google Data Rights panel to disconnect Gmail.
Immediate effect
Honest Codes archives the tenant-scoped local Gmail credential and active Gmail channel mapping when the connection can be safely identified.
What does not happen automatically
This does not revoke the Google Account authorization and does not delete stored Google-derived data.
What data remains
Existing conversations, messages, drafts, approvals, reports, customer memory, and audit records remain until a deletion request is reviewed.
Next step
Open Google Account permissions and revoke Honest Codes if access is still listed.
REVOKE GOOGLE AUTHORIZATION
What user does
Remove Honest Codes from Google Account permissions.
Immediate effect
Google stops the application from using that authorization to access new Gmail data.
What does not happen automatically
Google revocation does not remove records already stored inside Honest Codes.
What data remains
Tenant-scoped stored Gmail-derived records remain subject to Honest Codes retention and deletion review.
Next step
Submit a deletion request from the authenticated admin workspace.
REQUEST DELETION FROM HONEST CODES
What user does
Use the authenticated Google Data Rights panel in Honest Codes. If you cannot access it, email admin@honest.codes from an address we can verify.
Immediate effect
A tenant-scoped request is recorded with selected data categories, contact method, request reference, and operator-review status.
What does not happen automatically
The request does not execute deletion, certify deletion completion, or revoke Google authorization.
What data remains
Google-derived records remain until reviewed and handled by an authorized operator under the applicable retention exceptions.
Next step
We will confirm the request and communicate its status through the contact method associated with the request.
TRACK THE REQUEST AND UNDERSTAND RETENTION
What user does
Track the request reference and status in the admin workspace or through the contact fallback.
Immediate effect
The request status shows whether the request is submitted, acknowledged, under review, ready for execution, completed, partially completed, cancelled, or rejected as invalid.
What does not happen automatically
Status tracking does not change stored data by itself.
What data remains
Limited security, fraud-prevention, legal, billing, abuse-investigation, and audit records may remain when reasonably necessary.
Next step
Ask support to explain any retained record tied to a deletion request.

1DISCONNECT GMAIL INSIDE HONEST CODES

Sign in as a tenant administrator and use the Google Data Rights panel in the admin workspace. The same panel shows the current masked Gmail connection state and provides the existing Disconnect Gmail action.

Disconnect archives the tenant-scoped local Gmail credential and active Gmail channel mapping when the connection can be safely identified. It does not revoke Google authorization and does not delete stored Google-derived records.

2REVOKE GOOGLE AUTHORIZATION

Remove Honest Codes from Google Account permissions. Google revocation is the authoritative way to stop the application from using that Google grant for new Gmail access. It does not automatically remove data already stored inside Honest Codes.

3REQUEST DELETION FROM HONEST CODES

The primary request path is the authenticated Google Data Rights panel in the Honest Codes admin workspace. If you cannot access the panel, email admin@honest.codes from an address that can be verified as an authorized tenant administrator. Do not send OAuth tokens, passwords, raw message content, or secrets.

The request records selected data categories, a contact method, a request reference, and operator-review status. It does not execute deletion automatically and it does not certify deletion completion.

We will confirm the request and communicate its status through the contact method associated with the request.

4TRACK THE REQUEST AND UNDERSTAND RETENTION

Request statuses are submitted, acknowledged, under_review, ready_for_execution, completed, partially_completed, cancelled, and rejected_invalid_request. Status tracking does not change stored data by itself.

Limited security, fraud-prevention, legal, billing, abuse-investigation, and audit records may remain when reasonably necessary. Those records are access-controlled and are not used to reconnect Gmail, advertise to users, sell data, or train generalized AI or machine-learning models.

5Google API Limited Use

Honest Codes' use and transfer of information received from Google APIs complies with the Google API Services User Data Policy, including the Limited Use requirements.

6Support