Privacy
Scope
This policy covers two things: this website, and the data Tuft Mesh Vault handles when you use the community forum, open a support request, or sign a support or enterprise contract. It does not cover the data that flows through your own mesh — that stays on your hardware, under your control, and we never see it. The policy is written to meet Japan's Act on the Protection of Personal Information (APPI); the operator is Tuft Mesh Vault, 5-8-11 Nakanobu, Shinagawa, Tokyo 142-0053.
The software phones home to nobody
The Tuft Mesh Vault binary contains no telemetry, no update pinger and no licence check. It does not open outbound connections except the ones you configure. Crash reports are written to local disk and are sent to us only if you attach them to a support request yourself. If a future release ever adds an opt-in diagnostics channel it will be off by default, documented in the changelog, and described here before it ships.
This website
The site is static HTML. It sets no analytics or advertising cookies and loads no third-party scripts. One flag is written to your browser's local storage when you dismiss the notice at the bottom of the page; it never leaves your device. Server logs on the hosting provider record the IP address and requested path for each hit, are kept for thirty days for abuse detection, and are not joined to anything else.
The community forum and the issue tracker
Both are public. Anything you post — a username, a stack trace, a config excerpt — is visible to anyone and indexed by search engines. Strip secrets, internal hostnames and customer data before pasting; we redact on request but cannot recall what a crawler has already copied. The issue tracker is hosted on GitHub and subject to GitHub's own privacy terms; we see the same public information you do, plus the email address GitHub attaches to notifications.
Support requests
Standard Support and Enterprise customers reach a private queue. A request carries your name, work email, company, the plan you are on and whatever you attach: logs, policy files, routing tables, occasionally a packet capture. We use it to answer the request and to spot recurring bugs. Attachments are stored encrypted, restricted to the engineers working the ticket, and deleted ninety days after the ticket closes unless the contract sets a different period. Please redact end-user data from captures before sending; if you cannot, say so in the ticket and we will agree a handling procedure first.
Enterprise contracts
An enterprise agreement adds a dedicated Slack channel, a data-processing agreement and, for regulated workloads, whatever additional undertakings the contract lists. Slack is a sub-processor for that channel only. Contact names, billing details and the contract itself are kept for the life of the agreement and seven years after it ends, as Japanese tax and commercial law require.
Sub-processors
Email provider (support queue and general correspondence); GitHub (issue tracker); the forum hosting provider; Slack (enterprise channels only); an invoicing and accounting service; the web host for this site. Each processes data only on our instructions under contract. Some are located outside Japan; cross-border transfers rely on the provider's contractual safeguards as required by the APPI. A current list with locations is available to any customer on request.
What we never do
We do not sell or rent contact lists. We do not use support attachments to train models. We do not scan customer configurations for marketing signals. We do not add you to a newsletter — release notes go to the forum and the changelog, and you pull them.
Retention
Website server logs: thirty days. Forum and issue-tracker posts: public, indefinitely, unless you delete them or ask us to. Support tickets: three years for the text, ninety days for attachments after closure. Enterprise contracts and invoices: seven years after termination. Job applications: six months after the role is filled.
Your rights
Under the APPI you may ask what personal data we hold, request correction or deletion, or object to a use. Email hello@tuftmeshvault.com from the address we hold for you, or from the address on the contract for enterprise customers. We answer within ten working days. Deleting a forum post is something you can do yourself; deleting a support ticket that is still under a live contract may need to wait until the contract ends, and we will say so.
Security
Support storage and the backup of it are encrypted at rest and in transit. Access is limited to the engineers on the queue, with logged access. If a breach affects your data we will notify you and, where required, the Personal Information Protection Commission without unreasonable delay, and we will publish a post-incident report to the forum.
Questions and revisions
Questions about this policy go to hello@tuftmeshvault.com or +81 3-3782-5733, support queue hours Mon-Fri 9:00-18:00 JST. This policy was last revised on 7 September 2026; the previous version is available on request, and material changes are announced in the changelog.