개인정보 처리방침

Agent Guard supervises browser-visible activity performed by AI agents on websites a user explicitly authorizes. It identifies supported high-risk actions and sensitive-data categories, compares actions with user-confirmed intent and deterministic policy, requests approval or blocks supported actions, and keeps a redacted local audit trail.

Agent Guard is not a general chatbot, password manager, tracker blocker, endpoint DLP system, or guarantee against every prompt-injection attack.

On authorized sites, Agent Guard may transiently process browser-visible field values or metadata to classify personally identifiable information, health information, financial or payment information, authentication information, precise-location fields, and other sensitive categories.

It may inspect bounded page text on authorized webmail, messaging, collaboration, or other pages for prompt-injection signals. It may also process authorized site origin, redacted URL, timestamps, browser-visible clicks, input attempts, submissions, sends, uploads, downloads, navigation, approvals, settings, field labels, target descriptions, links, and destination origins.

Agent Guard does not intentionally perform keystroke logging or retain typed text as a transcript.

Raw form values and bounded page text are inspected transiently in the page and are not intentionally stored in the audit model. Persistent records use sensitive-data category indicators, redacted labels, redacted URLs, origin names, amount buckets, action metadata, policy decisions, and other minimized context.

A page-local masked preview can be shown during approval but is not sent to the extension service worker or included in exports. Agent Guard does not intentionally read or retain file contents, Cookie values, browser-storage values, full request bodies, or private keys.

Information is used only to show Guard Health and session status; evaluate intent contracts, risk budgets, profiles, and local policy; pause, approve, block, or replay supported actions; build local data-lineage and prompt-risk associations; compare local sessions; generate user-requested exports; link optional cross-tab workflows; and install optional temporary network-quarantine rules.

Policy decisions are deterministic in the current release. Agent Guard does not send prompts or page content to a developer-operated AI service.

세 템플릿은 확장 UI에서 명시적으로 확인한 후 현재 Origin에 적용되며 한 시간 동안 유효합니다. 의도를 교체하고 예산을 초기화하며 임시 권한을 지웁니다. 승인 대기·실행 중 동작이나 페이지 변경 시 안전하지 않은 교체를 거부합니다.

관리 정책과 사용자 규칙은 계속 적용됩니다. 합성 테스트는 정책 엔진만 실행하며 실제 네트워크 전송이나 동작 재실행은 하지 않습니다. 전체 보호의 증명은 아닙니다.

만료 시간을 확인하고 명시적 확인 후 작업 종료 및 잠금을 선택하여 권한을 지우고 Panic Lock을 켤 수 있습니다. 이미 전달한 동작은 취소할 수 없습니다.

로컬 감사는 최소화된 권한·예산 메타데이터를 보관할 수 있습니다. 예산은 승인 시도를 보수적으로 계산하며 전달 실패 시 자동 환급하지 않습니다. worker 재시작 시 실행 중 동작을 자동 재실행하지 않습니다.

진단은 사용자 요청으로 생성되고 내보내집니다. 버전, 상태, 집계와 로컬 설정만 포함하며 호스트, URL, 탭·문서 ID, 페이지 내용, 상세 감사 기록은 제외합니다. 예산은 승인 시도를 보수적으로 계산하며 전송 실패 시 자동 환급하지 않습니다. 새로운 텔레메트리나 원격 AI는 추가하지 않았습니다.

Agent Guard can connect locally to the separately installed SiteEgress extension. Both local bridge settings must be enabled before a summary is exchanged.

Agent Guard can receive minimized SiteEgress privacy context for an origin or requested destination, and can return minimized action, destination-category, policy-outcome, and evidence metadata. Sensitive values and raw IP addresses are excluded.

SiteEgress evidence is advisory context. It cannot create an Agent Guard approval, grant, policy decision, or enforcement result.

Live sessions are stored in chrome.storage.session. Settings, user rules, imported policy, and optional bounded history are stored in chrome.storage.local. Administrator policy may be read from chrome.storage.managed.

Users can disable history, set available retention limits, clear local data, remove rules, revoke grants, and uninstall the extension.

Agent Guard has no developer-operated analytics, telemetry endpoint, cloud account, remote AI service or remote executable rule feed. It does not automatically upload audit reports, browsing activity, form values, settings or local history to a developer server.

If enabled in both products, the optional local bridge exchanges only the minimized metadata listed in its section. Audit exports are created on your device; you decide whether to share them. Agent Guard does not sell user data or use it for advertising, creditworthiness or lending.

Default API permissions are activeTab, scripting, sidePanel, and storage. HTTP and HTTPS site access is optional and requested per origin only after the user chooses to authorize that site.

Optional permissions may include notifications for a generic approval notice, webNavigation for local cross-tab workflow linkage and document lifecycle, and declarativeNetRequestWithHostAccess for temporary tab-scoped destination quarantine without reading request bodies. Users can revoke site access and optional permissions.

Agent Guard uses bounded messages and collections, sender and document binding, redaction, export sanitization, packaged executable code, and explicit coverage reporting.

No software can identify every agent, detect every prompt injection, observe server-to-server processing, stop synchronous channels that cannot wait for approval, or guarantee complete security. Page-derived evidence is untrusted and can be influenced by the website.

Users may revoke site access and optional permissions, disable Deep Probe and local history, clear history or all extension data, remove rules, reject actions, use Panic Lock, uninstall the extension, and delete exported files.

Privacy questions can be sent to agentguard@siteegress.com or privacy@siteegress.com. Material changes will be reflected in this policy before or when the new processing becomes available.