TRUST CENTRE
Trust you can check
What we promise about your data in Tsunagu, and how you can check each promise yourself without taking our word for it.
Tsunagu is at prototype stage and the cloud edition is in development. Items marked “Planned” are not built yet; we list them so you know what to expect.
What we say, and what we never say
| Edition | What we say | What we never say |
|---|---|---|
| On-premise | Your content stays on your own hardware. The box connects only to the places listed on this page, and none of them carries your content unless you send it yourself: a support message you write, or an AI supplier you configure. | “We cannot change the software.” Whoever ships updates could, which is why updates are yours to control. |
| Cloud | Your content is kept separate for each organization and encrypted at rest. Takiang staff have no routine access. A log of any staff access, visible to you, is planned. | “It is technically impossible for us to see.” It is not: we run the servers, and the AI needs readable text. |
How you can check: on-premise
Watch the traffic
Block all outbound traffic except the destinations listed below, and compare with your firewall log. Every connection is started by the box; nothing connects in from Takiang.
Cut it off
Block all of it. Messaging, files, the kanban board, the calendar, the local AI and phone access on your own network keep working. The table below shows what pauses.
Check that the relay cannot read
The private key for phone access is created on the box and never leaves it. Takiang’s relay passes encrypted traffic by name and never decrypts it. You can compare the certificate your browser shows with the one in Settings → Phone access.
Control updatesPlanned
Every release signed, with its hash published. The box installs only signed releases and, if you choose, only after your administrator approves.
Ask for the evidenceBy agreement
For large customers: source code escrow, or an independent audit that states the hash of the build it reviewed.
How you can check: cloud
Takiang access logPlanned
In Settings: every time Takiang staff opened anything of your organization’s, with when, who, why (the support case) and what. Staff cannot reach content without a case you opened.
AI suppliers in use
Settings → AI lists the AI suppliers in use. Content is never sent to a supplier that is not approved for customer data. A monthly record of which supplier handled your requests is planned.
Export and deletion
A full export of your data at any time, and true deletion.
Outbound connections of an on-premise box
Every place an on-premise box connects to. All connections are started by the box; Takiang never connects in.
| # | Destination | When | What is sent | Your content? | If you block it |
|---|---|---|---|---|---|
| 1 | Takiang account service | Account page; plan and seat check | Your organization’s key id and a signature; the number of seats in use | No | The Account page says it cannot reach Takiang; nothing else stops |
| 2 | Takiang support | Only when an administrator writes to support | What the administrator typed and the files they chose to attach | Only what you chose to send | The Support page is unavailable; e-mail us instead |
| 3 | Takiang phone-access naming | At start-up and certificate renewal | The box’s address on your network, certificate challenge tokens, relay on or off | No | Phone access by name stops when the certificate expires; access by IP address on your network still works |
| 4 | Let’s Encrypt (certificate authority) | Certificate issue and renewal, about every 60 days | A certificate request for the box’s names (public key only) | No | Same as the row above |
| 5 | Takiang relay | Only if you turn on phone access from outside your network | Encrypted traffic of phone visitors | Encrypted end to end; the relay cannot read it | Phones outside your network cannot connect; your own network is unaffected |
| 6 | AI supplier | Only if you configure one; the default is the local model on the box | Prompts with content, only to suppliers you approved for customer data | Yes, to the supplier you configured | AI features pause |
| 7 | Speech-to-text service | Only if you configure one; the default runs on the box | Voice clips | Yes, to where you pointed it | Voice input pauses |
| 8 | Sign-in providers (Google, Microsoft, Takiang ID) | Only if you turn them on | Standard sign-in exchanges (codes and keys) | No | That sign-in method is unavailable; passwords and passkeys work |
| 9 | Your mail server | Only if configured | The e-mail your own rules send and receive | Yes, to your own mail server | Mail features pause |
| 10 | Accounting connection | Only if you add one | The accounting entries you chose to send | Yes, to your own system | Entries wait until it can be reached |
| 11 | Software registries (Docker Hub, GitHub) | Installation and updates only | Software downloads | No | Updates wait |
Never sent anywhere: messages, files, AI prompts, people’s names or e-mail addresses (except what an administrator types to support), activity logs and backups.
What we are still working on
Some bundled components are not yet pinned to exact, signed versions. Signed releases (planned above) close this gap.
Not planned, and why
Open-sourcing the whole product
Customers ask for evidence, not source code. If wanted later, we would open only the boundary parts (the tunnel client, the relay, the update checker and the export tool): small, and exactly the code that could let data out.
Confidential computing for the cloud edition
Sealed, attested servers are far beyond our size today. We will revisit this only if customers require it.
Last reviewed: 13 November 2026
