Public sector procurement facts

Authorization status

What does exist is a published security whitepaper mapping controls to the SOC 2 Trust Services Criteria, ISO 27001 Annex A, NIST CSF and GDPR Article 32, a public security posture page with the sub-processor list and a responsible disclosure policy, and a public status page with per-service health and 30, 60 and 90 day uptime windows. Those support an evaluation. They do not substitute for an authorization.

No VPAT or Section 508 conformance report has been published either. A solicitation that requires one as a submission item cannot be answered with an existing document.

Hosting and data residency

Data does not leave the United States for storage or processing, with one exception. When a user explicitly triggers an AI analysis, aggregated telemetry summaries are sent to Anthropic's API. AI analysis is user-initiated and never automatic, no personally identifiable information, credentials, file contents or raw event data is included, and Anthropic does not train on API data under its commercial terms. An agency that cannot accept a third-party inference call should disable the feature or deploy self-hosted.

Agent registration and installer downloads are restricted to North American IP addresses at the network edge.

Sub-processors

On a self-hosted deployment, billing and vendor integration surfaces are removed at startup, which removes several of these from the deployment entirely.

The self-hosted option

For an agency that cannot place endpoint telemetry with a cloud vendor, the Local-First tier runs the same server codebase on agency infrastructure with Docker Compose on Linux or Windows Server hosts. It is licensed at a flat rate with unlimited agents.

• The build is composed differently rather than configured differently. Cloud-only surfaces, including billing, vendor integrations and cross-workspace administration, are removed from the application model at startup. Their routes do not exist rather than being blocked.
• No vendor-side secrets ship to agency infrastructure.
• Endpoint telemetry lands only in the agency's own PostgreSQL instance. The documented egress list is the complete set of outbound connections.
• Tenant isolation is identical to the cloud: application-layer query filters plus PostgreSQL row-level security, verified by the same compile-time analyzers.
• Each instance activates from an Ed25519-signed license pinned to the agency's workspace. A lapsed subscription degrades to collection-only mode. Agents keep reporting and no data is deleted; management actions pause until renewal.
• Stored secrets are encrypted at the column level, and the key ring is itself encrypted with an instance-generated certificate held outside the database, so a database dump alone is insufficient to decrypt them.

See the self-hosted documentation for deployment detail.

What is collected, and what is not

Collected: health metrics, kernel trace events covering process creation, file input and output, network connections, registry activity and service state changes, system identity including hostname and OS version, the source IP the agent connects from, event log error summaries, and a stable device fingerprint used to recognize the same physical machine across reinstalls.

Not collected: end-user personal content, browsing history, keystrokes, file contents or employee activity. Raw kernel events are correlated on the endpoint and only sanitized summaries are uploaded. During AI-driven diagnostic sessions, events from additional providers are counted on the host and only the counts are uploaded, so raw payloads never leave the endpoint.

The narrow exposure a reviewer should evaluate is that file paths and process arguments appear in kernel event data, so an application that writes an identifier into a filename puts that string into telemetry. That is the question worth asking, rather than whether documents are uploaded.

Retention and disposal

Retention is configured per agent: 14 days by default, extending to 90, 365 or 730 days. Purging runs as a scheduled background service and deletes permanently, with no archival copy unless the customer configures one at the infrastructure level.

One exception applies. An organization placed under a legal or security hold is skipped by the purge so an evidence trail survives an investigation. Automatic holds expire 365 days after placement, manual holds remain until released, and both can be released early. A records retention schedule should describe that behavior rather than treat the tier as a guaranteed maximum age.

Access, containment and audit records

Identity is handled by Clerk. TOTP, SMS and passkey factors are available, and SAML or OIDC single sign-on is available on Clerk's enterprise plan, which is the relevant path for an agency using a central identity provider.

Every command executed against an endpoint is scored against 18 risk indicators before it runs and recorded with the risk score, matched indicators, user identity, target agent, command hash and execution decision. Executions are rate limited to 30 per user per organization per hour. Script changes carry a SHA-256 content hash.

On a high-confidence behavioral detection the agent isolates the endpoint automatically and opens a ticket carrying the evidence. Lifting isolation requires an authenticated dashboard request plus independent approval from a person at the device, so containment and release are separately attributable.

Tenant isolation runs in two layers on every database read and write, and there is no administrative path to cross-tenant access. Admin endpoints are bound to localhost.

Company and contracting

ET Ducky LLC is organized in Washington State, and the terms of service and end user license agreement are governed by Washington law. Security and procurement correspondence goes to [email protected]. Machine-readable contact detail is published at /.well-known/security.txt under RFC 9116.

ET Ducky is a small company and does not currently hold a cooperative purchasing vehicle or a GSA schedule. A buyer who needs one should expect to route the purchase through a reseller or an existing IT services contract.

If your procurement requires something ET Ducky does not hold

Two of these are worth a conversation rather than a rejection, and two are not.

Worth a conversation: a requirement that telemetry stay inside agency infrastructure, which the self-hosted deployment answers directly, and a requirement for a completed security questionnaire, which can be produced against your form.

Not worth a conversation today: a FedRAMP or StateRAMP authorization requirement, and a requirement for a current SOC 2 report. Neither exists and neither can be produced on a procurement timeline.

Related: SOC 2 endpoint logging controls and GLBA and FFIEC endpoint monitoring evidence.