SiteLens · Legal

SiteLens Cloud Agent Privacy Notice

This notice explains how SiteLens processes repositories, prompts, model outputs, and related evidence when optional SiteLens Cloud Agent features are made available and you choose to use them.

Effective date: November 6, 2026. Last updated: November 6, 2026. This notice supplements the SiteLens Privacy Policy and does not replace it. “SiteLens Cloud Agent” is the provisional customer-facing name for these features and may change in the product UI.

Availability

SiteLens Cloud Agent capabilities may be limited, invite-only, allowlisted, or unavailable for some workspaces. Publishing this notice does not mean every SiteLens customer currently has access. This notice applies when SiteLens has enabled SiteLens Cloud Agent features for your workspace and you authorize a repository or start a run.

Relationship to the Privacy Policy

The SiteLens Privacy Policy remains the primary statement of how SiteLens handles personal and customer data. This SiteLens Cloud Agent Privacy Notice adds feature-specific detail for repository-connected agent runs. If there is a conflict about SiteLens Cloud Agent processing described here, this notice controls for that subject; otherwise the Privacy Policy controls.

Repository access you authorize

SiteLens Cloud Agent features operate on repositories and branches you explicitly connect or select. You represent that you have authority to grant SiteLens access to that source code and related project content for the purpose of running the agent tasks you request.

Depending on configuration, an agent may read repository contents, compare branches, run tools you enable (including SiteLens browser and QA tools), produce reports or screenshots, and—where permitted by the task—propose or push changes only within repositories you authorized for that run.

What we process for a run

  • Repository contents and metadata needed to perform the task (for example, files, diffs, branch names, and commit identifiers)
  • Your prompts, follow-up instructions, and configuration for the run
  • Model outputs, tool calls, logs, screenshots, and other artifacts generated during the run
  • Usage and operational metadata SiteLens needs to operate the feature, and billing or allowance records if and when the feature is metered on your workspace

Do not submit secrets, production credentials, payment card data, or regulated health data through SiteLens Cloud Agent prompts or connected repositories unless SiteLens has expressly agreed in writing to process that class of data for your account.

AI and infrastructure providers

To deliver SiteLens Cloud Agent features, SiteLens uses managed AI models and cloud execution infrastructure operated by SiteLens and its subprocessors. Those providers may process repository context, prompts, and outputs solely to provide inference, hosting, security monitoring, and abuse prevention for the services SiteLens purchases on your behalf.

SiteLens configures provider privacy modes intended to prevent ordinary use of your SiteLens Cloud Agent code, prompts, and responses for foundation-model training by those providers, subject to documented security, feedback, consent, abuse-detection, and model-specific exceptions. Some models require additional retention or explicit approval before SiteLens will offer them in the product catalog.

SiteLens does not sell your repository contents. Customers interact with SiteLens; they do not receive separate accounts on underlying agent infrastructure as part of the SiteLens product.

Temporary cloud execution environments

SiteLens Cloud Agent runs execute in isolated cloud virtual machines provisioned for the task. The environment may clone or mount authorized repository content, install dependencies, and run tools required for the job. Runtime workspaces are recycled after the run becomes idle, subject to provider lifecycle timers that may refresh if you continue the conversation.

Encrypted environment snapshots (disk images that can include repository contents) may be retained to resume or accelerate later runs. Unused snapshots expire after a rolling inactivity period of approximately 30 days; reuse of a snapshot renews that period. Snapshots generally cannot be deleted on demand before that window elapses.

Conversation and artifact retention

SiteLens’s product target for completed SiteLens Cloud Agent sessions is to retain conversation history and associated agent-run artifacts for approximately 30 days after completion, unless a shorter or longer period is stated for your plan or you delete the run earlier through SiteLens controls (when available). This 30-day target is a planned SiteLens retention design. It is not a guarantee that automatic deletion is already implemented for every workspace, and it does not override provider-side snapshot limits described above.

Reports, screenshots, or other evidence that you expressly save into your SiteLens workspace (for example, customer-saved SiteLens Reports) may be retained separately under the main Privacy Policy for as long as your workspace keeps them or until you delete them, subject to legal and billing retention needs.

SiteLens may also store operational logs and—if metering is enabled for your workspace—usage or ledger entries in SiteLens systems under the main Privacy Policy.

Deletion and its limits

When SiteLens provides a delete control for a SiteLens Cloud Agent run, requesting deletion is intended to remove:

  • The agent conversation transcript
  • Associated artifacts stored with that agent record

Deletion does not immediately remove encrypted environment snapshots, which continue to follow the inactivity expiry described above. Deletion also may not erase billing records, security logs, or copies already exported to your own systems (for example, screenshots you downloaded), or customer-saved reports kept in your SiteLens workspace. Archive or hide actions—if offered—are not the same as permanent deletion.

Security

SiteLens Cloud Agent environments are isolated per run. Data in transit is protected with modern TLS. Stored agent session data and snapshots are encrypted at rest. Network egress, secrets handling, and repository permissions depend on the controls SiteLens and you configure for the run. Autonomous agents can execute tools you enable; prompt-injection and exfiltration risks exist whenever an agent can browse or call external systems—use least privilege and review outputs before relying on them.

International processing

SiteLens Cloud Agent inference, execution, and storage may occur in the United States and other regions where SiteLens or its infrastructure providers operate, unless a written SiteLens agreement specifies a different residency arrangement for your account.

Model selection

If SiteLens lets you choose among models for a SiteLens Cloud Agent run, the available list may change over time. SiteLens may hide or require additional confirmation for models that impose extra retention or review obligations. Choosing a model authorizes processing under that model’s applicable provider terms as configured by SiteLens for the SiteLens service.

Contact

Privacy questions about SiteLens Cloud Agent features may be sent to support@sitelensapi.com. You may also use the contact form on sitelensapi.com or your SiteLens account support channels. See also the SiteLens Privacy Policy and Terms of Service (including the optional SiteLens Cloud Agent section).