Agent plugin privacy.
This DEV plugin is separate from the Tanral Dashboard and shares the Tanral Cognito identity service. The account service terms and general privacy policy remain available at app.tanral.com.
What the plugin stores
Client display names, client-reported hostnames, operating system and architecture, harness/profile/Node/Electron and plugin/runtime versions, observed host package and client type with provenance and collection time, locale and time zone, random machine and installation identifiers, first/last activity and authorization/replacement history, hashed credentials, enabled project names and optional Git references, hashed session identifiers, turn start/end times, and short milestones, decisions, lessons and handoff notes submitted by your Agent. Local absolute paths remain local. We do not upload full chats, prompts, code, files or raw tool output, and do not run a separate model to summarize them.
An explicitly authorized, server-allowlisted DEV diagnostic profile can additionally collect available native session events, including prompt, tool and code content, after credential and email redaction. This is separate from normal compact reporting and is not enabled for all clients.
Security records
The service records server-observed IP addresses, request identifiers, bounded user-agent and accepted-language headers, plugin source/version declarations, authorization/revocation and refusal outcomes, and separate device pairing, authorization-page request, signed-in view and approval events for future abuse investigation. Browser declarations may include a random browser-instance identifier, time zone, language, platform and browser-provided Client Hints. The browser identifier is held in local storage until cleared; it is not a hardware identifier or authentication credential. No automated fraud score or restriction is applied from these observations. Device details are client-reported; IP addresses may represent a proxy. Raw request content, credentials and work summaries are excluded from these security logs. Security events are eligible for cleanup after 30 days during later service activity, so cleanup can occur later; API access logs are retained for 7 days. Identity and version snapshots remain with the client authorization history until that client is deleted.
Retention and control
Operational events are eligible for cleanup after 7 days, turn intervals after 90 days, and upload receipts after 30 days. Cleanup runs during later service activity and may occur later. Key records remain until deletion; up to 10 versions are kept per key. Failed uploads can remain in a bounded local queue. Device credentials are stored locally in a permissions-restricted file, expire after 30 days, and can be revoked in the plugin device settings. Request deletion or assistance at support@tanral.com.
Agent-generated conclusions can be incomplete or incorrect. Evidence supplied is not human acceptance. Turn intervals include waiting and are not human working time or pure model compute time. Preparing short records may use your Agent's tokens.