Trust center
Last checked against its sources: October 13, 2026
This page says only what is already true about how Yooha protects the people and organizations who use it. What we have not done yet is listed separately, as plans.
Every statement here is tied to a named source in our code, configuration or operating records, and an automated check refuses a change that adds a statement without one.
Your data
- Every table is labelled with how sensitive its data is, and a change that adds an unlabelled table is refused.
- Connections between your device and Yooha are encrypted with TLS, version 1.2 or newer. TLS 1.3 is switched on, and with it our network edge uses hybrid post-quantum key agreement whenever your device supports it.
- Backups are encrypted before they are stored. The most sensitive fields, such as the credentials of connected services and identity documents, are also encrypted inside the application under a key kept for each organization; those keys are wrapped by a root key in a managed key service, and destroying an organization’s key makes what it protected unreadable.
- Each organization’s data is walled off from every other organization’s at the database row level, and that wall is tested automatically for every table on every change.
- Data is kept only as long as its retention rule allows, and a legal hold can pause a deletion. A destroyed key stays destroyed after a restore: the restore procedure applies the list of destroyed keys again, so a backup cannot bring that content back.
Where data is stored, deleting it and getting a copy
Where your data is stored, how long it is kept, how to delete it and how to ask for a copy are set out in the Privacy Policy. We link to it instead of repeating it, so the two pages cannot disagree.
Companies that process data for us
The service providers that handle data for us, and what each of them does, are named in the Privacy Policy. A formal sub-processor list is available on request: write to support@gi2t.com.
Signing in and acting
- Yooha does not offer password sign-in. You sign in with an account you already have or with a one-time code sent to your email address, and a sensitive action asks you to confirm with a passkey first.
- Permission decisions are made in one place, against one set of policies, and an AI agent can act only within what a person delegated to it.
How we build and run Yooha
- Our security rules are enforced by automated checks on every change, and a database change can only add, each with a way back.
- Yooha’s services reach the internet through a single gateway, and only to destinations on its allowlist.
- Our AI treats incoming text as untrusted: content is marked with where it came from, tools are allowlisted and need permission for each use, answers are checked, and anything uncertain fails closed.
- We keep a register of the figures the product depends on and check each of them on a schedule. When one stops updating, our operators are told once, in their own app and by email, and it shows on the system health board. Administrative actions on our infrastructure leave an audit trail.
- One organization’s heavy traffic is kept from slowing down the others, and we load-test that separation.
- An encrypted backup of the database is written every day to two separate storage providers, each set so that a stored backup cannot be changed or deleted for a fixed period. The same daily job restores that backup into an empty database and checks it; a day on which the restore or the check fails is recorded as failed.
What we never do
- We never use an organization’s data to compete with it, and Yooha does not export an organization’s raw data.
- We do not sell personal data.
Not done yet
These are plans, not claims. A line moves up to the lists above only once it is true.
- Yooha has not yet been audited by an independent third party. No audit, certification or penetration test has been completed.
- SOC 2 Type II for the whole platform: planned. We have assessed our readiness; the audit has not started, and we have no report yet.
- An independent penetration test: planned before public launch; not done yet.
- ISO 27001: planned for a later phase.
- An unbroken record for the daily restore check: not yet. The check has failed for several days in a row and had to be repaired, so we do not claim that it has always passed.
- Reminders that repeat while a figure stays stale, and delivery of alerts by push notification: not yet.
- A written procedure, with a deadline, for telling the people and organizations affected by a security incident: not finished yet.
- A public vulnerability disclosure and rewards program: its text is prepared, but it is not open yet. Until then, report problems as described below.
- Automated scanning of our dependencies for known vulnerabilities: planned.
- Single sign-on and automatic user provisioning for organizations: planned.
- Choosing where an organization’s data is stored: planned. Today Yooha is offered in the United States only.
- A data processing agreement template, and a sub-processor page of its own with notice of changes: planned.
Report a security problem
If you think you have found a security problem in Yooha, email support@gi2t.com with what you found and the steps to reproduce it. Use only your own accounts, and stop if you can see someone else’s data. Our security.txt is at /.well-known/security.txt.
- Operated by
- gi2t Labs LLC
- support@gi2t.com