Giya Terms of Use

1. What Giya is

Giya is an AI assistant for school and ERP workflows provided by Livro Systems. It helps you draft, review, and improve outputs such as documents, print formats, and related workspace content. Giya answers from your account, role, and connected tools — not from access you do not have.

2. How Giya retrieves data

When you send a prompt, Giya may gather supporting context for that turn in two ways. It does not search systems you have not connected, and it does not use another person’s private index as if it were yours.

Live retrieval from connected tools

Live calls are role-gated in Giya and authenticated as you on the other system. Giya only attaches a tool if your Giya role includes that permission. Then it calls the system with your signed-in session — not a shared organization API key. On that site you still only see and change records your own ERP (or Google / GitHub) account is allowed to see.

• Livro ERP — your Giya role must include Livro ERP. Sign-in to Giya with Livro creates your ERP session. During chat, Giya may read or update tasks, timesheets, leave, invoices, and similar documents as that Livro user.
• School ERP — your Giya role must include School ERP, and you must sign in to the school site (or open Giya from that desk). During chat, Giya may read or update classes, students, reports, print formats, and related documents as that school user on the site you connected.
• Google Workspace — your Giya role must include Google Workspace, and you must connect your Google account. Giya may then use Calendar, Meet, and Gmail you enabled, under that Google account.
• GitHub — your Giya role must include GitHub access, and you must save a personal access token. Giya may then see repositories that token can access.

Giya is not a general crawl of your organization’s systems, and it does not use a developer MCP token in place of your login. If you are not signed in, or your ERP user cannot open a document, Giya cannot retrieve it either.

Indexed knowledge (retrieval)

Separately, Giya may search a knowledge index of previously stored text that is similar to your prompt, then attach matching excerpts as supporting context. That index can include:

• Files you attach in chat or add under Profile → Tools → Knowledge
• Outputs you generate (for example print HTML, Web Pages, Web Forms)
• Skills you create or install, plus built-in Giya skills
• Organization or school knowledge that administrators have made available for your workspace (for example school-linked documents)

Indexed excerpts are supporting context only. If they conflict with what a live tool returns or with your current instruction, the live tool and your instruction take priority.

Conversation context

Giya may also use recent messages in the same chat so follow-ups make sense. That is limited to the conversation you are in, not a search of every chat in the organization.

3. Storing data for later retrieval

To make later prompts more relevant, Giya may store and later retrieve the kinds of content listed above, within your account and organization context. This is retrieval context for Giya prompts. It does not mean Giya fine-tunes third-party foundation models on your behalf unless a separate written agreement says so.

4. Passwords and secrets

Giya applies automated filters intended to exclude passwords, API keys, tokens, and similar secrets from the knowledge index. These filters are best-effort. Do not paste production credentials into chat, uploads, or Knowledge, and do not treat Giya as a secrets vault.

5. Your responsibilities

You must have authority to use any organization or company data you bring into Giya. You are responsible for complying with your school’s policies and applicable law when using the app.

6. Third-party AI providers

When you use models or agents from providers such as OpenAI, Google, or Cursor, prompts, retrieved excerpts, and live tool results in that turn may be processed under those providers’ terms and privacy policies.

7. Managing indexed knowledge

Where the product allows it, you may remove knowledge items you own from Profile → Tools → Knowledge. Organization-shared sources may remain available to other authorized users.

8. Acceptance

You must accept the current Terms version to sign in with password or OTP, or to continue after an embed session if you have not yet accepted. If we update these Terms, you may be asked to accept the new version before continuing.