Privacy policy
Stega Workspace Connector
Last updated
Stega Networks provides the Stega Workspace Connector to help organizations manage their Google Workspace environment and retain searchable audit records. This policy explains how Stega handles information through that connector and its related inventory, reporting, and audit services.
Who this policy covers
This policy covers administrators who connect an organization and people whose information appears in that organization's Workspace directory, usage reports, audit records, or email delivery logs. It applies to the connector, including its use within StegaApp. It does not describe every activity on Stega's main website or every other Stega service.
We collect organizational information under the customer's authorization. The customer determines which services it uses and is responsible for its own notices and permissions concerning its users. Individuals can contact their organization's administrator or Stega with privacy questions.
Information we collect
Depending on the services enabled, the permissions granted, and the information Google makes available, we collect:
- Organization identifiers, names, domains, domain aliases, organizational units, administrator roles, and role assignments.
- User identifiers, names, email addresses, aliases, account status, organizational placement, and directory profile and account information returned by Google.
- Groups and their members, including membership roles and external members where present.
- Subscription, license, and assignment information obtained through authorized customer or reseller access.
- Organization and user storage totals and service usage statistics available in Google's reports.
- Audit events, including timestamps, actors, email addresses, IP addresses, actions, affected resources, event parameters, and outcomes where Google supplies them. Events may contain file names or identifiers, sharing activity, or other personal information even though the connector does not access files.
- Email delivery log events from Google's Gmail audit log, when an authorized user searches them: the mailbox, Message-ID, subject, recipient addresses, delivery outcome, server replies, size, attachment count, and timestamps. The connector does not read message bodies or attachments.
- Security findings derived from audit events, such as sign-in locations and networks, devices, credential and recovery changes, mail rules and exports, and the incidents and reviews built from them.
- Connection details, authorization tokens, granted permissions, synchronization status, and technical logs needed to operate and troubleshoot the service.
Google authorization
An administrator authorizes access through Google. Stega receives authorization tokens; the connector does not ask for or store the administrator's Google password. Collection can continue in the background while the authorization remains valid.
The connector only reads data; it does not change the customer's Workspace. It does not request access to Google Drive files, and it does not read email message bodies, attachments, or document contents. Audit and delivery-log records can still describe activity involving those services, such as a file name or an email subject.
How we use information
We use information to provide the customer's inventory views, license and storage reporting, searchable audit history, email message tracing, and security threat monitoring. Historical records help authorized users review changes over time, investigate incidents, and answer operational or audit questions.
Threat monitoring compares new audit events with an account's usual activity to detect signs of account takeover, such as a sign-in from an unusual network followed by credential or mail-rule changes. It creates incidents for Stega's security staff to review and may notify them. It reports findings; it does not change the customer's Workspace.
When an incident is serious, an AI model may review a bounded summary of that incident's evidence to suggest whether it looks like a compromise. The summary contains event times and types, networks, devices, counts, the account's usual activity, and the subject of a message involved in the incident, but no message body or recipient address. The summary is sent to an AI service provider solely to produce that suggestion. The suggestion is advisory: Stega staff decide what happens next.
We also use connection and technical information to maintain access, resume interrupted collection, prevent duplicate records, resolve errors, and protect the service. We associate records with the relevant customer so authorized staff can support that organization.
Google data and limited use
Our handling of Google API data follows the Google API Services User Data Policy, including its Limited Use requirements, and the Google Workspace user data and developer policy.
We do not sell Google user data, use it for advertising, or use it to train generalized artificial intelligence or machine-learning models. We use it only for the disclosed service purposes permitted by Google's policies.
Access and sharing
Access is limited to authorized customer representatives and Stega personnel who need it to deliver the authorized service. Human review of Google data requires affirmative authorization for the relevant data, except where Google's policies permit access for security, legal compliance, or permitted internal use of aggregated data.
Service providers may process information on our behalf to provide hosting, storage, search, backup, support, or the AI incident review described above, as necessary for the authorized service. Such processing is limited to the permitted purpose and subject to confidentiality and data-protection obligations. We may disclose information when required by law or necessary to address security incidents, consistent with Google's policies. Any transfer of Google data through a business sale or merger requires prior explicit consent where Google requires it.
Storage and protection
Information is stored in systems operated by Stega or its service providers, including databases, search indexes, archives, and backups. We use access controls and safeguards appropriate to the information to protect it against unauthorized access, alteration, loss, and disclosure. Contact us for information about the hosting and processing arrangements applicable to your organization.
Retention and deletion
Our standard retention period for audit logs and historical records is one calendar year from the event or record time, through the end of the anniversary day. A different contractual period requires agreement with Stega and confirmation that the storage and deletion controls support that period before collection is activated. A legal preservation requirement may require us to retain affected records longer. We retain other information for as long as needed to provide the customer's authorized services and meet applicable obligations.
Long-term audit retention is part of the service. Audit events and historical inventory records may remain available after Google no longer provides them through its APIs, after a source record changes or is deleted, or after the connection is revoked. Revoking access stops future authorized collection; it does not automatically delete previously collected records.
An authorized customer representative can request deletion or a change to retention by contacting us. We verify the request and explain any applicable preservation requirement. Audit archives use immutable storage with retention locks to protect evidence against alteration or premature deletion. Such locks can prevent physical deletion before their retention deadline, including after a deletion request or disconnection. We restrict access where appropriate while the lock remains in effect. Expiry processing removes eligible records and search copies after their applicable retention boundary; it is scheduled rather than immediate.
Search backups normally expire after seven days. The backup policy preserves at least one snapshot if scheduled backups stop, and separately retained manual snapshots or database backups can have different expiry arrangements. Removing a record from active systems does not immediately erase every backup copy. Contact us for the archive, backup, preservation, and deletion arrangements applicable to your organization.
Your choices and requests
You can review or revoke the connector's access through your Google Account connections. Workspace administrators can also control third-party application access through the Google Admin console.
To request access to, correction of, or deletion of personal information, or to raise a concern, email [email protected]. Include your organization and the nature of your request. Please do not send passwords or authorization tokens. We may need to verify your identity and authority and coordinate with your organization's administrator before acting.
Changes to this policy
We update the date above when this policy changes. If we introduce a new use of Google data, we will provide notice and obtain any required consent before using information for that purpose.
Contact
Stega Networks
Privacy inquiries: [email protected]
Website: stega.ca