Privacy
This Privacy Policy explains how Cloud9.0 Pty Ltd handles information when you use OpsLantern, a Google Workspace administration product.
Last updated: April 26, 2026OpsLantern is currently operated by Cloud9.0 Pty Ltd. In this policy, “OpsLantern”, “we”, “us”, and “our” refer to Cloud9.0 Pty Ltd in connection with the OpsLantern product.
OpsLantern supports Free, paid, and support-managed access paths. Some deployments or pilot environments may still use private access controls.
OpsLantern uses Google OAuth for sign-in. During sign-in, we receive basic Google account information needed to authenticate you, such as your email address and profile information made available through the Google OAuth userinfo scopes.
OpsLantern requests the Google Workspace API scopes needed for the current product: reading groups, reading users, and reading or changing direct group membership. These scopes allow the app to show group and user information and to add or remove group members when an authorized administrator requests that change.
OpsLantern is a front end for Google Workspace data. The app calls Google APIs to display Workspace groups, users, and direct group memberships, and to apply membership changes requested through the product.
Google Workspace remains the system of record for Workspace users, groups, and memberships. When you add or remove a member from a group, the change is written to Google Workspace through Google APIs.
OpsLantern stores the application records needed to operate access and billing, such as tenant identifiers, owner and assigned-admin records, Free-plan managed-user configuration, entitlement state, agreements, manual overrides, billing audit records, and Stripe event metadata. These records may include user email addresses, Google Workspace customer IDs, Google user IDs, plan and billing status, timestamps, and support notes.
Public self-serve paid subscriptions are processed through Stripe. Stripe may collect payment details, invoice information, tax information, billing contact information, and other payment information under Stripe's own terms and privacy policy.
OpsLantern stores Stripe customer, subscription, subscription item, price, invoice, checkout, and webhook event identifiers so that the app can activate, pause, renew, cancel, and audit paid entitlements.
OpsLantern uses Supabase/Postgres as the application datastore for tenant, entitlement, billing, admin-seat, agreement, manual override, Stripe event, and audit records.
OpsLantern is hosted on Google Cloud Run and uses Google Cloud operational logging. Logs may include timestamps, request identifiers, request metadata produced by the hosting platform, tenant domain, signed-in administrator email address, action type, group email, member email, result, and error details.
We use operational logs to run the service, troubleshoot issues, investigate failed or unexpected membership changes, improve reliability, and protect the product. We do not use operational logs for advertising.
We use Google account information, Workspace data returned by Google APIs, billing and entitlement records, agreement records, support records, and operational logs to provide OpsLantern, authenticate users, check administrative access, manage tenant setup, display group and membership information, apply membership changes, process billing state, troubleshoot support requests, and secure the service.
We do not sell Google Workspace data. We do not use Google Workspace data for advertising. We do not use Google Workspace data to train artificial intelligence or machine learning models.
OpsLantern's use and transfer of information received from Google APIs will comply with the Google API Services User Data Policy, including the Limited Use requirements.
We do not share Google Workspace data with third parties except as needed to provide, host, secure, or support OpsLantern, comply with law, or respond to valid legal process.
Because OpsLantern is hosted on Google Cloud, integrates with Google Workspace, uses Supabase/Postgres for application records, and uses Stripe for billing, those providers may process information as part of providing their services.
Operational logs are kept for a limited operational period as configured in Google Cloud, then deleted or aged out under those logging settings.
Billing, entitlement, agreement, audit, and support records may be retained for security, accounting, legal, troubleshooting, abuse-prevention, and operational reasons. If you ask us to purge or remove tenant records, we will review the request and act where reasonably practicable.
You may contact us to ask what information we hold about you, request correction, request deletion where applicable, ask us to remove access, or request a tenant purge.
Some operational records may need to be retained for security, troubleshooting, legal, or legitimate business reasons.
We use Google OAuth, Google Workspace tenant checks, entitlement checks, assigned-admin checks, administrative capability checks, and hosting controls to limit access to OpsLantern. Private or pilot deployments may also use domain allowlists.
No internet service can be guaranteed to be completely secure. If you believe OpsLantern has handled information incorrectly or may be affected by a security issue, contact us promptly.
For privacy questions or requests, contact help@opslantern.dev.
