Elyxr Labs Docs
  • Introduction
    • About Elyxr Labs
    • About AlphaSum v0.8.1
  • AlphaSum User Guide
    • Authorization Process
      • Disclosures
      • QR Code Login
      • Revoking Access
    • Whitelisting Groups
      • Overview
      • Adding Groups
      • Common Restrictions
    • Generating Summaries
      • Single vs Multi-Group
      • Depth Control
      • Advanced Filtering
      • Outputs & Customization
      • Summary History
    • Security & Privacy
      • Encryption
      • Data Scope
      • Privacy Considerations
    • FAQs
  • Legal
    • Terms of Service
    • Privacy Policy
Powered by GitBook
On this page
  • In-Bot Revocation
  • Manual Device Removal
  • Consequences of Revocation
  1. AlphaSum User Guide
  2. Authorization Process

Revoking Access

AlphaSum respects user autonomy by providing a clear revocation mechanism:

In-Bot Revocation

Users wishing to terminate AlphaSum’s access can do so via AlphaSum’s built-in “Revoke Access” feature in “My Account”. This action triggers deletion of all user-specific data, including session tokens, summaries, and whitelisted group records from Elyxr Labs' servers.

Manual Device Removal

If the user opts to remove AlphaSum solely through Telegram’s Settings → Devices interface, the bot’s session on Telegram will end, but the Elyxr Labs server cannot detect this external removal. Consequently, any previously stored data, including summaries, may remain on Elyxr Labs' systems.

For comprehensive data purging, users must perform the in-bot revocation to ensure that all personal records and session links are securely erased.

Consequences of Revocation

Once revocation is completed, all associated credentials and stored summary data are immediately purged. Reinstating AlphaSum at a later time requires repeating the entire authorization process, including QR code login.

PreviousQR Code LoginNextWhitelisting Groups

Last updated 3 months ago