Terms of Service

Parrot AI (AI WORKSHOP, "we", "us") operates this service. These Terms of Service (the "Terms") are a binding agreement between us and you — the person or organization using the service ("you").

They cover the hosted service we run at parrot.amorist.cn: the website and catalog, the API, the call proxy, the desktop app when pointed at our servers, and everything reachable from them (together, the "Service").

They do not cover self-hosted instances. If you install the server on your own infrastructure, your relationship with us is governed by the licence that ships with that deployment alone. We have no access to its data and take on no obligations for it.

By creating an account, signing in, or making a call through the Service, you accept these Terms. If you are accepting on behalf of a company, you confirm you're authorized to bind it.

You sign up and sign in with a phone number and a password. You must be at least 16 years old and give a real, working number — verification and password recovery go there, so a wrong number is a security problem, not a typo.

• Keep your account and access tokens secure. Anyone holding a valid token can make calls as you, within whatever access your role and member permissions allow.
• You can revoke every token you hold at once from the console, and we'll do the same on request if you believe a token has leaked.
• If you suspect unauthorized access, change your password and tell us promptly.

Every account belongs to a workspace, and you can create or join others. Within a workspace:

• Owners and admins can add and remove credentials and tools, invite and remove members, set each member's tool access and daily call cap, and delete the workspace and everything in it.
• Members can call the tools they've been granted and read the team's shared skills. They never see raw secret values — the Service is built so a stored credential is never returned to a client.
• Every call is logged who, which tool, which method and path, the status code, and when. Workspace admins can see that log. If that isn't acceptable to you, don't call through a team you don't control.

If you join a workspace you don't own, its owner effectively controls that workspace: they can revoke your access, see your call history in it, and delete shared content. Choose your workspaces accordingly.

The point of the Service is holding credentials so you don't have to hand them out. Concretely:

• Secret values are encrypted at rest with AES-GCM and are never returned through the API or shown in the console after they're stored.
• We inject them only into calls that an authenticated member of the owning workspace makes to a tool they have access to — through the call proxy, a local-run grant, or a server-side run.
• We do not read, mine, sell, or use your credentials or the data they reach for any purpose other than performing the call you asked for and keeping the credential healthy (periodic validity checks and OAuth token refresh).

Your obligations. You must have the right to store and use every credential you add, and the authority to grant your teammates and agents access through it. You are responsible for the calls made with your credentials — including calls made by AI agents you've pointed at the Service. An agent acting under your token is you, as far as these Terms are concerned.

Treat this as a working vault, not a system of record. Keep your own copy of any credential you can't re-issue, and revoke upstream if you ever suspect compromise — revoking at the source is always faster and more complete than anything we can do for you.

When you connect an account (Google Analytics, Search Console, Google Ads, Business Profile, YouTube, Slack, X, or any API you register yourself), calls made through the Service are subject to that provider's terms as well as these. We are not a party to your relationship with them.

• YouTube. The YouTube connection uses YouTube API Services. By connecting a channel you also agree to the YouTube Terms of Service and to Google's Privacy Policy; you can revoke our access at any time from Google security settings. You remain responsible for the content you publish through the Service and for its compliance with YouTube's policies.
• Only grant the scopes you actually need — the connect flow asks you to pick a capability for exactly this reason.
• Rate limits, quotas, billing, and enforcement are the upstream service's. If they suspend or revoke your access, we can't restore it.
• Disconnecting a service in Parrot AI deletes the stored token on our side; revoking our access in that service's own settings is the belt-and-braces version, and we recommend both.

Skills, tool definitions, and their companion files are yours. You keep all rights in them; you grant us only the limited licence needed to store them, show them to the teammates you've shared them with, and run them when you ask us to. We don't use your skill content to train models.

You're responsible for what you put in them. Don't upload content you don't have the rights to, and don't put secrets in a skill's text — that's what the vault is for, and skill text is visible to every member of the team it lives in.

Don't use the Service to:

• store or use credentials you don't have permission to use, or access accounts that aren't yours to access;
• break the terms, rate limits, or anti-abuse measures of any upstream API — including using the Service to disguise the origin of automated traffic;
• attack, overload, or probe the Service or the infrastructure it runs on, or attempt to reach another team's data;
• run malware, mine cryptocurrency, send spam or bulk unsolicited email, or host illegal content;
• use server-side runs to execute code intended to escape the sandbox, or to proxy traffic to destinations unrelated to a registered tool;
• offer the Service (including the upstream keys we hold) to third parties as a competing gateway, or bulk-proxy calls, in a way that resells, sublets, or circumvents metering.

We apply per-member daily call caps, egress restrictions, and sandboxing to protect the Service. Circumventing them is a breach of these Terms.

The Service is in early access. It changes often, and features can be added, altered, or withdrawn. We may change or discontinue the Service, and we'll make a reasonable effort to give notice before anything that would cause you to lose data.

There is no uptime commitment and no support commitment. We aim to be reliable and we answer email, but nothing here is an SLA.

What costs money. Registering tools, storing credentials, and calling an API on your own key are free. Calls we serve on our shared keys are metered against your workspace's prepaid balance, at the price shown for that endpoint before you call it. The balance is prepaid; automatic top-ups only happen if you turn them on and agree to the amount.

The Service has no referral reward programme at the moment. If we introduce subscription plans on top of per-call billing, we'll say so clearly in advance and no recurring charge will apply to you without your explicit agreement.

You can leave at any time: delete a workspace from the console, or contact us to delete your account entirely. Deleting a workspace destroys its stored credentials, tools, and skills.

We may suspend or terminate an account or team — with notice where practical, immediately where necessary — if it breaches these Terms, endangers the Service or other users, or if we're required to by law. If we terminate you without cause, we'll give you a reasonable chance to export your content first.

On termination, your right to use the Service ends. Sections 04 (your obligations), 10, 12, 13, and 14 survive.

THE SERVICE IS PROVIDED "AS IS" AND "AS AVAILABLE", WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, AND NON-INFRINGEMENT. We do not warrant that the Service will be uninterrupted, error-free, or secure against every attack, or that any call made through it will succeed.

Nothing in these Terms excludes liability that cannot lawfully be excluded, including for fraud or for death or personal injury caused by negligence.

Parts of the Service (for example the desktop client) are provided as source or installer packages under the licence that ships with their repository. These Terms govern use of the hosted Service itself; a self-hosted deployment is governed by the licence that ships with that deployment.

You may run a self-hosted instance inside your own organization, and we expressly encourage it. You may not redistribute, resell, or sublet the Service (or its source components) to third parties as a competing hosted, managed, or embedded gateway without prior written authorization.

Calling our hosted API from your own product is different: as long as the calls run under your own account and billing relationship, and follow our terms and rate limits, that use is allowed and no special agreement is needed.

To the maximum extent permitted by law, neither party is liable for indirect, incidental, special, consequential, or punitive damages, or for lost profits, revenue, goodwill, or data, however caused.

Our total aggregate liability arising out of or relating to the Service is limited to the greater of (a) the amount you paid us for the Service in the twelve months before the claim, or (b) US$100. While the Service is free, that means US$100.

You'll defend and indemnify us against claims, losses, and costs arising from your use of the Service in breach of these Terms — in particular, claims that you stored or used a credential you weren't entitled to use, or that calls you made violated an upstream provider's terms.

These Terms are governed by the laws of the People's Republic of China, without regard to its conflict-of-laws rules. Disputes arising from these Terms are subject to the exclusive jurisdiction of the competent courts where the operator is established. If you're a consumer, this doesn't deprive you of the protection of mandatory laws in your country of residence.

Before any dispute, we encourage you to contact us first using the channels in section 16; most issues are resolved at that step.

We may update these Terms. If a change is material we'll notify account holders by email or an in-app notice before it takes effect, and the "last updated" date at the top always reflects the current version. Continuing to use the Service after a change means you accept it; if you don't, stop using the Service and delete your account.

For questions about these Terms, or anything else, reach us through the contact page. Security reports are handled through the support page — please tell us privately first, before discussing anything in public.