Our shared Yak account privacy policy describes account identity, transactional messages and service providers.
YakTunnel terminates HTTPS at its edge and forwards requests through an encrypted agent connection to your configured service. The relay can process request content in transit. It does not store request bodies as part of normal forwarding.
Request and response captures stay in your CLI process memory by default and disappear when it exits. The local inspector requires a private token. Secrets are masked by default; raw viewing and export are explicit local actions. Masking cannot identify every sensitive field.
A capture is uploaded only when you explicitly confirm sharing. The CLI and server redact known sensitive fields. Shared captures are visible to your account's team and expire after seven days. Review content before sharing it.
We store endpoint configuration, hashed CLI credentials, account activity and aggregate usage to operate the service. Activity expires after thirty days. Old sessions, revoked credentials and resolved abuse reports are retained for ninety days. Monthly usage and billing records remain for accounting. Database backups follow the shared Yak backup policy.
The account site uses an essential sign-in cookie. A team-protected tunnel uses a separate five-minute access cookie. Your local application may set its own cookies. Clearing essential cookies signs you out. This app does not include advertising trackers.
Questions or data requests: support@yakware.com.