The poison0 agent protects your agents’ memory and is engineered to collect as little about your team as technically possible.
Device liveness is a relative countdown a scheduled sweep decrements; a heartbeat resets it. No absolute timestamp is persisted, so the dashboard cannot reconstruct working hours. (GDPR Art. 5(1)(c); relevant to co-determination under German BetrVG §87(1) No. 6.)
Before any content leaves the device, secrets and personal data are stripped and home paths masked. Only added lines of a change are evaluated; review prompts carry only a redacted, length-capped diff.
Dedicated enterprise instances are provisioned in the customer’s chosen region; the tenant database location follows that choice (Germany/EU/US/Asia). The shared default tier is hosted in Frankfurt.
All traffic uses TLS. Data at rest is encrypted with AES-256 on Google Cloud. Models on the device are stored encrypted, each model version with its own key. That key is derived from root keys in Google Cloud hardware security modules (HSM) that cannot be read out; a device receives only the keys of the models it is allowed to use, wrapped to a key of the device.
In private mode the daemon contacts the network at most once every 30 days, to a documented update URL. The analysis model runs locally - no content goes to third-party AI APIs. A fully air-gapped offline install and a stand-down kill-switch are available.
We don’t profile activity, sell data, or run ad-tech. A data processing agreement (DPA/AVV) is available for enterprise customers. Audit data has retention limits and is deletable on request.