Skip to main content

TRUST / ORBINTU

Built to earn authority, not assume it.

ORBI can understand more than it is allowed to act on. Authority remains explicit.

  1. UNDERSTAND
  2. PERMISSION
  3. ACT
  4. VERIFY

AVAILABLETrue of this website today.

PLANNEDDesigned or built, not live. Do not rely on it.

POLICYA rule held by design.

The account backend is connected on this build. No security certification is claimed.

TRUST INFORMATION LAST REVIEWED · 26 SEPTEMBER 2026

01TRUST / AUTHORITY

Intelligence ≠ authority.

ORBI may understand what should happen. That does not automatically mean it is permitted to do it. Nothing acts outside the authority you gave it.

ORBI understands. NTU acts. You decide what either is allowed to do.

  • UNDERSTANDING ≠ PERMISSION

    ORBI can understand what a system contains without being allowed to change it.

  • PREDICTION ≠ AUTHORITY

    Expecting an action to be right does not make the decision ORBI’s to take.

  • CAPABILITY ≠ AUTHORIZATION

    That a tool can do something is not a reason it is allowed to.

02TRUST / MODEL

Every step has a boundary.

Understanding, permission and action are separate things in ORBINTU, and they stay separate. Nothing you did not allow becomes something that happens.

ORBI AND NTU, DEFINED

ORBIORBI is the persistent intelligence system that develops a working model of a person and their world, interprets what they are trying to accomplish, determines what is missing between current and desired reality, assembles relevant information and intelligence, and forms correct work for NTU.

NTUNTU is the Navigating Task Unit. It receives correctly formed, bounded work from ORBI and navigates the capabilities required to execute it without losing the work’s purpose, permissions, or success conditions.

03TRUST / PRIVACY

Public identity. Private everything else.

Your ORBI identity is meant to be seen. Your account, contact and working information are not.

PUBLIC VISIBLE TO ANYONE USING ORBINTU

  • ORBI IDSystem-assigned. Never chosen by you or anyone else.
  • DISPLAY NAMEOnly if you choose to publish it. Hidden until you do.
  • HANDLEOptional. Only if you choose to publish it.
  • BIOOptional. Only if you choose to publish it. Leave it blank and nothing is shown.
  • POSITION COLOURBlack or white on a Standard Position; an ORBI identity colour on a Founding Position.
  • POSITIONCoordinate and cell in the ORBI field.
  • FOUNDING CROWNStatus and Founding number, if your Position carries it.
  • JOIN DATEWhen the Position was claimed.

PRIVATE NEVER ON YOUR PUBLIC PROFILE

  • EMAILOnly you. Used to sign in. Never on your public profile.
  • PHONEOnly you. Optional. Not verified.
  • AUTH DATASign-in and session records held by the auth provider.
  • SECURITY / SESSION
  • WORKSPACE PLANNEDThe ORBI workspace does not exist yet.
  • CONNECTION DATA PLANNEDPermission required. Each connected app only within the scope you grant.

WHAT YOU CHOOSE TO SHAREis public. What belongs to the account remains private.

  • AVAILABLENo analytics or advertising trackers run on this website, and ORBINTU’s own code sets no cookies.
  • POLICYPrivate by default. Only the fields that make up your public ORBI identity are public.
  • POLICYORBINTU does not sell personal information.

Privacy Policy Cookie audit

04TRUST / PERMISSIONS

Authority is explicit.

ORBI may understand what should happen. That does not mean it has permission to do it. NTU executes only within the authority attached to the work.

PERMISSION VOCABULARY POLICY CONTROLS NOT LIVE YET

ReadSee content.

Actual authority is always scoped: to one piece of work, one connected service, one action. Holding a higher permission somewhere never grants it everywhere.

You can always intervene.

CONTROLS PLANNED

PauseHolds all work on this Need. Nothing new starts. Resume whenever you choose.

05TRUST / AI + DATA

ORBI forms the work. NTU does it. Neither decides its own authority.

ORBI understands context and forms correctly bounded work. NTU receives that bounded work and navigates the capabilities needed to execute it.

  1. YOUR CONTEXTPRIVATE
  2. ORBINTUSCOPED
  3. ANY CAPABILITY USEDPERMISSION REQUIRED
  • AI output can be wrong. Review what matters before relying on it.
  • ORBI does not gain authority merely from having context.
  • NTU operates within the bounds the task defines.
  • Completion is verified, not assumed.
  • AVAILABLENo AI processing of your data on this site. The ORBI and NTU demonstrations here run a fixed, scripted scenario. Nothing you type into them is sent to a model.
  • DECISION PENDINGModel training on user content: not decided yet. Until it is decided and published, no use of your content for training is authorised.
  • PLANNEDThird-party model providers: ORBI and NTU may use external models. Providers and their data terms will be listed before launch.
ALL AI + DATA PRINCIPLES
  1. AI output can be wrong. Review what matters before relying on it.
  2. Important actions may require your approval, not just your permission.
  3. Permissions are explicit, per action and per connected service.
  4. Connected services keep their own access scopes. ORBINTU does not widen them.
  5. ORBI does not gain authority merely from having context.
  6. NTU operates within the bounds the task defines.
  7. Completion is verified, not assumed.

Read the AI Terms

06TRUST / VERIFICATION

Completion is evidence. Verification closes the need.

A report that something finished is a claim, not a result. ORBINTU stays with whether the thing you wanted is actually true, and tells you when it is not. POLICY

07TRUST / SECURITY

Identity, permissions and execution stay separated.

Principles first, with the status of each stated. We will list certifications only once they are actually held.

  1. Identity

    Accounts, authentication and sessions stay separate from your public ORBI identity.

    • AVAILABLEPasswordless sign-in
    • AVAILABLESession handling
    • POLICYRecovery through your inbox
    • PLANNEDTwo-factor authentication
    IMPLEMENTATION STATUS
    Passwordless sign-in AVAILABLE
    Accounts use a one-time code sent to your email. ORBINTU never asks for or stores a password.
    Session handling AVAILABLE
    Sessions are issued and refreshed by the authentication provider. Signing out ends the session on that device.
    Recovery through your inbox POLICY
    Whoever controls your email can sign in. Protecting that inbox protects your account. ORBINTU will never ask you for your code.
    Two-factor authentication PLANNED
    An authenticator-app second factor. Your account page shows it as not active.

  2. Access

    Designed so each account reaches only its own private data, and privileged keys never reach the browser.

    • AVAILABLEAuthenticated account boundaries
    • AVAILABLELeast-privilege keys
    • PLANNEDScoped connected-service access
    IMPLEMENTATION STATUS
    Authenticated account boundaries AVAILABLE
    Row-level security rules restrict each account’s private data to its owner. One account holds at most one ORBI identity and one Position.
    Least-privilege keys AVAILABLE
    The browser holds only a public, row-level-security-limited key. The privileged service key is never shipped to the browser.
    Scoped connected-service access PLANNED
    Each connected app limited to the scope you grant, and revocable.

  3. Data

    Public fields come from a separate public view. Ownership is decided on the server, never in your browser.

    • AVAILABLEProtected private fields
    • AVAILABLEServer-authoritative ownership
    • PLANNEDSelf-service account deletion
    IMPLEMENTATION STATUS
    Protected private fields AVAILABLE
    Strangers can read only a public view of an ORBI. Email, phone and account identifiers are not in that view.
    Server-authoritative ownership AVAILABLE
    Claims and Founding status are decided by a single server-side function. Your browser cannot supply or change them.
    Self-service account deletion PLANNED
    Deleting your account, ORBI and Position from the account page. Until then, request it through Contact.

  4. Operations

    Failure is shown rather than disguised, and dependencies change only on purpose.

    • AVAILABLEFailure is visible, not disguised
    • AVAILABLEDemos are labelled as demos
    • POLICYPinned dependencies
    • PLANNEDAuditable sensitive actions
    • PLANNEDStatus page and incident notes
    • PLANNEDService commitments
    IMPLEMENTATION STATUS
    Failure is visible, not disguised AVAILABLE
    When the account backend is not connected, sign-in says so instead of pretending. Demo claims are labelled session-only.
    Demos are labelled as demos AVAILABLE
    Every interactive ORBI and NTU example on this site runs a fixed, scripted scenario and says so.
    Pinned dependencies POLICY
    Third-party libraries are pinned to exact versions and updated deliberately, not silently.
    Auditable sensitive actions PLANNED
    A log you can inspect for approvals, permission changes and consequential actions.
    Status page and incident notes PLANNED
    A public place to see outages and what was done about them.
    Service commitments PLANNED
    No uptime commitment is offered yet. One will be published only when it can be met.

TRUST / DISCLOSURE DEDICATED CHANNEL PLANNED

Found something?

Security issues should have a clear path to us. A dedicated security address has not been set up yet. Until it is, report vulnerabilities to hello@yuvi.it.com with “SECURITY” in the subject.

WHAT WE ASK OF RESEARCHERS
  • Describe the issue, where it is, and steps to reproduce it.
  • Access only the data you need to demonstrate the issue, and never other people’s data.
  • Do not degrade the service: no denial-of-service, spam or automated mass claiming.
  • No social engineering, phishing or physical attacks.
  • Give us reasonable time to fix it before disclosing publicly.

Safe-harbour terms for good-faith research are being drafted with counsel and will be published here. Automated scanning is covered by the Acceptable Use Policy.

Autonomy should increase only where trust has been earned.

STILL HAVE A QUESTION?

hello@yuvi.it.com

Contact us

Third-party & open-source transparency

The terms, in writing.

Terms, privacy, AI, cookies and what a Position and the Founding Crown mean.

LEGAL CENTER