Cruxia Studio · OAuth disclosure
Cruxia Studio Gmail integration
Cruxia Studio is the owner-operated autonomous content-production system inside Crux Terminal. Its Gmail integration is used only with the dedicated Cruxia project account to complete authentication and verification flows for approved external production services.
What the integration does
- Reuses an existing authenticated provider session when available.
- When email verification is required, reads the newest matching authentication message.
- Extracts the one-time code, uses it for that provider login, and does not retain the code as application content.
- Stops rather than bypassing CAPTCHA, hardware-key, biometric, or other provider security challenges.
Google access
The application requests Gmail read-only access. It does not request Gmail send, compose, modify, or delete permissions. OAuth tokens are kept in the protected local secret mechanism used by the owner-operated system.
Data use
Gmail access is limited to the Studio authentication purpose described here. Verification codes are passed back only to the external service that issued them. Google user data is not sold, used for advertising profiles, or used to train models.