✉
Gmail Send
The user enters a recipient, subject, and message, reviews the content, then confirms sending. Orlixea uses Gmail only to send that confirmed message.
Google OAuth 2.0 · Telegram-based application
Secure actions.
Secure actions.
User controlled.
Orlixea lets users connect their own Google account and perform specific Gmail and YouTube actions from a private Telegram chat. Every action is initiated and confirmed by the authenticated user.
No Gmail inbox reading
No background engagement
Encrypted authorization storage
Disconnect anytime
What Orlixea does
Focused functionality with explicit consent
Orlixea implements only the production actions shown below. It does not read Gmail inbox content and does not provide comment posting or automated video-view generation.
＋
YouTube Subscribe
The user selects a specific channel. Orlixea resolves the channel, displays it for confirmation, and subscribes only after the user confirms.
♥
YouTube Like
The user supplies a specific YouTube video, reviews the target, and confirms the like request before it is submitted.
OAuth permissions
Only two Google scopes are requested
Gmail
https://www.googleapis.com/auth/gmail.send
Used only to send email that the authenticated user composes and explicitly confirms. Orlixea does not request Gmail read, modify, or mailbox scopes.
YouTube
https://www.googleapis.com/auth/youtube
Used only for the production YouTube actions implemented by Orlixea: subscribing to a selected channel and liking a selected video.
Privacy by design
Controls built around user authorization
Encrypted at rest
OAuth token records and temporary operation state are encrypted before local storage on the application host.
Separated by user
Authorization records are keyed to the individual Telegram user. One user cannot use another user's connected Google authorization.
Revocable
Disconnect Google revokes access and deletes stored authorization data. Users can also revoke access from their Google Account settings.
Reviewer resources
Clear documentation for verification
Detailed descriptions of scopes, data handling, retention, deletion, and the end-to-end authorization flow are available below.