Privacy & verification

What we can see, and what we cannot

The short version: your voice, your transcripts and your translations never reach Kizuna AI. The long version is this page — including which parts of that you can check for yourself and which parts you are taking our word for.

Where your audio goes

This holds whether the key is yours or comes from a Kizuna AI account. The only difference is who issues the credential and who settles the bill; the vendor running the model is the same either way, and it is the vendor — never us — that receives your audio.

Your deviceaudio · transcript · translationAI provider

Kizuna AIapi key issuance · usage metering · no audio

The provider you pick does receive your audio, under their terms — that is what they are for. Choosing on-device inference removes that hop as well, and then nothing leaves your machine.

Everything we store about you

Not a summary of a longer list. This is the list.

WhatWhy

Your email addressTo verify the account and to grant trial credit

Balance and usage countersTo meter what you spend through a Kizuna AI account, and show it back to you

Nothing elseNo audio, no transcripts, no translations, no meeting names, no participant lists, no recordings

What you can check yourself

The app is AGPL-3.0 licensed, and the app is the piece that decides where your audio goes. Every one of these is verifiable without asking us anything.

ClaimWhere to look

No request carrying audio, transcripts or translations is ever addressed to Kizuna AIsrc/services/clients/ — every network destination

On-device inference works with the network offsrc/services/providers/LocalInferenceProviderConfig.ts

The extension touches only the meeting sites it declaresextension/manifest.json

The app is AGPL-3.0 licensed, and builds from sourceLICENSE

None of the above changes once you sign inrun a proxy and watch a whole session

What you are taking on trust

Our account service is not open source. What it does with an email address and a usage counter cannot be proved by reading code, so we are not going to dress it up as if it could be.

These are promises: that the only user data we store is your email address and your balance; that we issue vendor credentials and meter spend and do nothing else with them; that we neither sell, share nor analyse anything about you. They are load-bearing and we intend to keep them — but they are promises, and the honest thing is to say so next to the claims you can actually verify.

If that is not good enough, it does not have to be. Sokuji works with no Kizuna AI account at all: use your own key, or run on-device, and the account service is never in the picture.

If you would rather not trust us at all

Run it with no account

On-device inference needs no sign-in and no key. Sokuji is fully functional without ever contacting Kizuna AI.

Bring your own key

Then the only parties are you and the provider you chose. We are not in the transaction or the path.

Watch it on the wire

Point Sokuji at a proxy and run a whole session. Every destination is a vendor you chose; none of them is us.