EcoSynq Connect Account and Data Deletion

Self-service deletion

There is no single Connect button that deletes all data across the device, Codex/OpenAI and every external provider. Complete the separate steps below for each data type actually used.

1. Stop any running assistant action and automatic notification for the account.
2. API/OAuth connection: disconnect/delete the credential for that Connect account, then separately revoke its OAuth grant, token, app password, bot, webhook or subscription on the provider's Connected Apps or security page. Neither step substitutes for the other.
3. WebView2: in the service account settings, delete only that exact account's isolated WebView2 profile. This removes its cookies, cache, local storage and session without affecting other accounts. WebView profile storage is separate from the DPAPI-protected API credential vault.
4. Notifications and WebView cache: separately clear Connect notification history and the relevant WebView profile. Opening a message or dismissing a Windows notification does not delete the provider's original message.
5. Assistant/Codex: separately delete the Connect conversation/session and its Codex thread. If the selected OpenAI service retains its own server-side history, delete that separately using the OpenAI account data controls.
6. Telegram/TDLib: separately log out TDLib, terminate the active device session in Telegram, and delete that account's local TDLib database. Deleting a WebView profile does not do this.
7. Backups: Connect's secret-free state-recovery backups are retained for 30 days and the system keeps at most 180 snapshots; 180 is a snapshot-count cap, not a retention period. AGENTS/skill backup retention is a separate setting that defaults to 30 days. These Connect backups do not contain the live WebView2 profile or DPAPI credential vault. The user or system administrator controls Windows, enterprise and other external backups.

What is deleted

Each action above deletes only the named data category. Local disconnection does not automatically delete original email, messages, files, posts, tasks or organizational retention records held by the provider. Those require a separate confirmed provider operation or provider administrator. Uninstalling the app alone does not guarantee provider-side token revocation or content deletion.

Revoke provider access

• Google: third-party connections
• Microsoft: permissions or the organization's Entra enterprise applications
• Meta/Facebook/Instagram: Facebook Settings → Business Integrations / Apps and Websites
• Slack: workspace app management / Installed apps; an organization admin may be required
• GitHub: Applications settings
• Discord: User Settings → Authorized Apps, and remove the bot from servers
• Telegram: Settings → Devices / Active Sessions, then log out TDLib and delete the local database
• X: Settings → Security and account access → Apps and sessions → Connected apps
• LinkedIn: Settings & Privacy → Data privacy → Permitted services
• Todoist, Trello, Mailchimp, Zendesk and others: revoke in the provider's Integrations/Connected Apps/API tokens page or ask the organization administrator.

Deletion for manual and runtime-gated connections

Mattermost, Matrix/Element, Rocket.Chat, Zulip, Nextcloud Talk, Webex, Chatwork, Toggl Track, Teamwork Projects, GroupMe, Pushbullet, Twist, Twitch and Zoho Cliq accept separate connection/credential profiles. Their catalog is runtime-gated: only an operation marked Executable for the current build and account can run; AdapterMissing operations remain disabled. Fastmail has 41 built-in executable JMAP operations. Plurk, VK and Threema Gateway are currently AdapterUnavailable and expose no executable API operation. Where a credential profile was used, delete it locally and revoke it separately at the provider/tenant; where only WebView was used, delete the exact isolated profile.

• Webex/Chatwork/GroupMe/Pushbullet/Toggl/Teamwork/Twist/Fastmail/Twitch/Zoho: revoke on the provider Connected Apps, Developer/API or token page, with an organization/tenant admin where applicable.
• Threema Gateway: revoke Gateway secret/E2E key/callback and remove local cryptographic data; this is not a personal Threema-history API.
• Mattermost/Rocket.Chat/Zulip/Nextcloud Talk: revoke the exact instance/workspace user/bot token, PAT, app password and webhook/bot, then request tenant-admin retention/deletion.
• Matrix/Element: revoke token and device/session, remove local keys/key backup, then follow homeserver/room deletion rules; federated or bridged copies may not be erasable from one server.
• JMAP/IMAP/SMTP/CardDAV/CalDAV: revoke the exact account OAuth/app password and session; the provider/tenant controls mailbox, contact, calendar and backup retention.

Meta/Facebook deletion callback

Meta can call https://ecosynq.eu/oauth/meta/data-deletion. The broker verifies Meta's HMAC signature and deletes only matching transient broker-side OAuth state/transactions. The minimal receipt associated with the returned confirmation code is retained for at most 30 days and contains only timestamps, status and an App-Secret-HMAC digest of the Meta user ID—never a raw user ID, token, message or document. The callback cannot authenticate to or erase the Windows device's DPAPI credential, WebView2 profile, TDLib data, notification history or Codex conversation. Until an authenticated device deletion queue exists, configure https://ecosynq.eu/account-data-deletion/ as the deletion-instructions URL in Meta Developer Console; the user must complete the separate device-side and provider-revocation steps above.

Support-assisted request

Email info@e-co-inform.hu with subject “EcoSynq Connect data deletion”, the provider/account label shown in Connect and the data category to remove. Never send a password, token, API key or full message content. We may proportionately verify identity and authority. Under the GDPR, we respond without undue delay and normally within one month of receipt. For complex or numerous requests, this may be extended by two additional months; notice and reasons are provided within the first month.

Legal exceptions

Billing records, legally required records and evidence required for an active security incident or claim may not be immediately erased; they are isolated and used only for the mandatory purpose. Provider retention and organizational eDiscovery/retention rules are controlled by the provider or organization administrator.

Controller: E-co Inform Services Kft., 1147 Budapest, Telepes utca 13. fszt. 1., Hungary · 01-09-200201 · 25108930-2-42 · HU25108930 · info@e-co-inform.hu · +36 30 553 4223