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

EditionWhat we sayWhat we never say
On-premiseYour 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.
CloudYour 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

  1. 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.

  2. 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.

  3. 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.

  4. Control updatesPlanned

    Every release signed, with its hash published. The box installs only signed releases and, if you choose, only after your administrator approves.

  5. 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

  1. 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.

  2. 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.

  3. 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.

#DestinationWhenWhat is sentYour content?If you block it
1Takiang account serviceAccount page; plan and seat checkYour organization’s key id and a signature; the number of seats in useNoThe Account page says it cannot reach Takiang; nothing else stops
2Takiang supportOnly when an administrator writes to supportWhat the administrator typed and the files they chose to attachOnly what you chose to sendThe Support page is unavailable; e-mail us instead
3Takiang phone-access namingAt start-up and certificate renewalThe box’s address on your network, certificate challenge tokens, relay on or offNoPhone access by name stops when the certificate expires; access by IP address on your network still works
4Let’s Encrypt (certificate authority)Certificate issue and renewal, about every 60 daysA certificate request for the box’s names (public key only)NoSame as the row above
5Takiang relayOnly if you turn on phone access from outside your networkEncrypted traffic of phone visitorsEncrypted end to end; the relay cannot read itPhones outside your network cannot connect; your own network is unaffected
6AI supplierOnly if you configure one; the default is the local model on the boxPrompts with content, only to suppliers you approved for customer dataYes, to the supplier you configuredAI features pause
7Speech-to-text serviceOnly if you configure one; the default runs on the boxVoice clipsYes, to where you pointed itVoice input pauses
8Sign-in providers (Google, Microsoft, Takiang ID)Only if you turn them onStandard sign-in exchanges (codes and keys)NoThat sign-in method is unavailable; passwords and passkeys work
9Your mail serverOnly if configuredThe e-mail your own rules send and receiveYes, to your own mail serverMail features pause
10Accounting connectionOnly if you add oneThe accounting entries you chose to sendYes, to your own systemEntries wait until it can be reached
11Software registries (Docker Hub, GitHub)Installation and updates onlySoftware downloadsNoUpdates 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