Souffleur · Kontrastudio OÜ · Private preview
Privacy and data handling
A factual pre-launch outline of the current private relay. Last reviewed in product: 2026-10-14. Review required before external accounts are offered.
1. What the relay handles
To pair and authenticate devices or clients, the relay stores device identifiers and names, credential hashes, grants, token and session metadata, and security events. To provide owner analytics, it stores tool names, client and device labels, timestamps, outcomes, timings, execution approvals and aggregate volumes.
2. Sensitive operational traces
Audit records may include redacted or shortened file paths, command arguments, error messages and output previews. Redaction is best-effort and does not guarantee that all sensitive values are removed. Do not treat activity logs as a secret-safe vault. The current system is not designed to train AI models on these logs.
3. Where data resides
The relay holds its local state and activity logs on its configured host. Requested file content and execution results are routed between the authorised client and paired device to carry out the operation. Connected AI providers may independently process requests and outputs under their own policies. Consult each provider's terms for its data practices.
4. Retention as currently implemented
Daily aggregate metrics are pruned after approximately 400 days. Expired short-lived tokens and sessions are periodically swept. The audit log currently rotates by file size rather than a fixed retention deadline. A time-based audit retention and deletion mechanism, plus data-export and deletion controls, are prerequisites for a commercial release.
5. Security and control
Access uses owner authentication, revocable device and client credentials, restricted device workspaces and gated execution. The owner can revoke paired devices and client grants. Some approved execution paths may have wider local operating-system permissions, and no remote system is risk-free.
6. Cookies and third parties
The signed-in dashboard uses an HttpOnly owner-session cookie for authentication. Provider OAuth flows and their own sites operate under separate privacy rules. No third-party advertising or audience-tracking scripts are loaded by the server-rendered dashboard.
7. Rights and product readiness
For access, correction or deletion requests relating to personal data, contact studio@kontrastudio.eu. A definitive controller/processor assessment, legal bases, hosting and subprocessors list, retention schedule, and GDPR-facing policy are still required before external availability.