Security approach
Luxa applies technical and organizational safeguards designed around least privilege, explicit user action, workspace separation, and minimizing exposure of third-party credentials. Security is an ongoing process, and no system can guarantee absolute protection.
Google connection safeguards
- OAuth access and refresh tokens are encrypted with AES-256-GCM before database storage.
- Encryption binds each token to the Luxa user and token type, helping prevent ciphertext from being reused in a different context.
- OAuth client secrets and token-encryption keys remain server-side.
- Stored token ciphertext is not returned to browser clients.
- Google API operations validate the authenticated Luxa account and required service scope.
- Disconnecting Google revokes the authorization and deletes the stored connection.
Workspace and data safeguards
- Personal and Team workspace context is resolved on the server for Google attachment and file imports.
- Database row-level security and service-role boundaries restrict direct access to integration records.
- Imported files use private storage and explicit workspace or project records.
- File identifiers, types, sizes, and intended destinations are validated before import.
- Private integration responses use no-store cache controls.
- Account and plan boundaries are enforced for protected product and API routes.
Responsible data handling
Luxa limits Google data to visible, user-facing features and prohibits its sale, advertising use, credit use, and generalized or personalized AI-model training. See How Luxa Uses Google Data and the Privacy Policy.
Report a security concern
Send a concise description, affected URL or feature, reproduction steps, and potential impact to elijahisrael@luxastudiocos.net. Do not include passwords, OAuth tokens, private keys, or unnecessary personal data.