Disconnect and Delete Data

Stop future Google access

Open Google Account connections, select the Pulse application, and remove its access. Follow Google's current account interface. Future API requests will be subject to Google's revocation behavior. If you connected multiple accounts, repeat for each relevant account.

For Zoom, use your account's installed-app management to remove Pulse and its permissions.

Remove local copies

Delete relevant Pulse sessions to remove their session folders, messages, attachments, and stored tool results. Review exported files, downloaded outputs, business records, and your own backups separately. Removing a source does not remove the content already copied into a conversation.

Current limitation: removing a source entry does not itself guarantee deletion of its encrypted-vault credential or provider-side revocation. Revoke access at the provider first. Provider-side revocation and removal of saved local content are both necessary to address these separate forms of access and storage.

Uninstalling Pulse may leave application data behind. Local data can exist under your Pulse configuration/workspace folders and any custom workspace location you selected. Consult support before deleting a folder if it contains files you need. Ordinary file deletion does not guarantee forensic erasure or deletion from system backups.

Information held by services

The OAuth broker has no durable database of your connected-account tokens. Authorization flows expire after five minutes; pending data is removed after collection or cancellation, or by the next cleanup after expiry (normally within 30 seconds). Support messages and infrastructure records may have separate retention as described in the Privacy Policy.

AI services may retain requests under their applicable processing terms. Contact the relevant provider for copies held under your account. We cannot erase a third party's records merely by deleting a local Pulse session.

Ask for help

Contact info@pulseera.ai and identify the information or account concerned. Do not include passwords, access tokens, API keys, or private documents unless a secure, necessary support process has been agreed. The operator may need to verify identity before acting on a request.