Delete an AGENEON account
Send a deletion request through the verified support channel provided in your AGENEON onboarding or account correspondence. Use the email address associated with the account where possible and state “Account deletion,” the account email, and the workspace name. Do not include a password or OAuth token.
Account deletion may affect workspaces you own. We will first determine whether ownership must be transferred, whether the workspace should also be deleted, and whether records must be retained for security or legal reasons.
Request workspace deletion
Only a workspace owner or another person with verified authority may request deletion of an entire workspace. Identify the workspace and confirm whether all business profiles, members, agent configuration, catalog items, Knowledge Base sources/files/chunks, channels, customers, conversations, handoffs, and integration records should be removed. We may ask for a second confirmation because workspace deletion affects other members and customer data.
Delete customer, contact, or conversation data
Workspace owners and administrators may delete individual Knowledge Base sources in the product. A complete in-product deletion control for customer/contact and conversation records is not currently available. An authorized workspace representative can request deletion through the verified support process and identify the relevant customer, contact detail, conversation, or date range.
If you are an end customer or website visitor, contact the business whose AGENEON-powered experience you used. That business controls the data and can verify the request. You may also contact AGENEON with enough information to route the request, but we may need the workspace customer's authorization.
Disconnect integrations and revoke Google access
A workspace owner or administrator can open Connections, choose the Google Calendar connection, and select Disconnect. AGENEON attempts to revoke the Google token and deletes the connection record, encrypted credential, discovered calendar resources, and dependent action definitions through database cascade behavior.
You can also revoke access directly from your Google Account's third-party connections or security settings. Revocation prevents future access but does not itself delete unrelated workspace records or calendar events already created in Google Calendar.
Identity and authority verification
To protect users and business data, AGENEON may verify control of the account email, request a signed-in confirmation, confirm workspace role, or ask for proportionate evidence that you are authorized to act for a customer. We will request only what is reasonably necessary and may decline or narrow a request that cannot be authenticated.
How requests are handled
We acknowledge and evaluate requests through the support process, identify affected systems and processors, and communicate when action is complete or when an exception applies. Exact response and deletion periods depend on applicable law, request scope, production backup rotation, and provider configuration; no fixed period is promised until those facts are confirmed.
Some limited information may remain where required for security, fraud prevention, legal compliance, dispute resolution, or backup integrity, and is isolated from ordinary use until deletion or rotation is permitted.
Submit a request
Use the verified support channel supplied during AGENEON onboarding or in account correspondence. Include your account email, workspace name, request category, and enough detail to locate the data. Dedicated privacy and deletion email addresses are recommended but are not represented as active until the owner confirms them.