Terms of service

These terms are between you and Transition 2 Consulting Inc. ("we", "us"), governed by the laws of British Columbia, Canada. Questions about these terms: contact@transition2.ai, we aim to respond within 2 business days.

1. What Hawkeye is

Hawkeye is a control plane for machines you own and for the AI agents running on them. It can run commands, transfer files and drive a signed-in desktop on any machine you enrol. That is a powerful thing to hand to software, and the terms below exist mostly to be clear about who is responsible for what happens as a result.

2. Your account

You are responsible for what happens under your account and for keeping your credentials to yourself. Tell us promptly if you think a session, an install token or a paired device has been compromised — every one of those is individually revocable, which is why they are separate objects.

3. Machines you may enrol

Enrol only machines you own or are explicitly authorised to administer. Using Hawkeye to reach a machine you do not have permission to control is a breach of these terms and, in most places, of the law. Enrolment is deliberately a two-sided act — a token gets a machine as far as asking, and a human in the org approves what actually runs.

4. Approvals, automation and responsibility

Authority boundary today (observe_only). Enrollment and client pairing require approval. After pairing, allowed actions execute without per-action approval: each machine's policy is evaluated and written to the audit trail in observe mode (XFER_POLICY_MODE defaults to observe, deliberately) rather than applied. A connected AI client can still raise an explicit human request when it creates one, and cross-org access is still a request the other side grants. What that gives you between those boundaries is a record of what was done, not a gate in front of it. Read it as evidence after the fact, not as a control that stops something first. One caller stands outside even the record's attribution: the shared fleet key is a break-glass credential, accepted without an identity chain, so its actions are attributable to the key rather than to a person, and the policy that is being observed is not evaluated for it at all. Its uses are counted and the recent ones kept, which is how a machine can show you how often break-glass was reached for. Narrowing it is open work, not a shipped property — treat possession of that key as possession of the fleet.

Standing grants exist for the explicit requests a connected client raises; a grant is scoped to specific actions, and it is off until you turn it on. You remain responsible for the actions your org approves — and, because individual actions are not separately approved in the state described above, for what an AI client does with a session you paired. We are not responsible for what your agents do on your machines with permissions you gave them.

5. Acceptable use

• No unauthorised access to any system, network or account.
• No using Hawkeye to attack, scan or disrupt anyone else's infrastructure.
• No unlawful content or activity, and nothing that would make us party to one.
• No attempt to defeat the org boundary, another org's approval step, or the audit trail. Crossing an org boundary is a request the other side grants; treating it as an obstacle to route around is a breach.

6. Plans, billing and cancellation

Plans and prices are on the pricing page, billed monthly per organization in US dollars. Stated honestly: payments run through Stripe. Once you have a paid plan, an owner can open Stripe's hosted billing portal from the Plan page — invoices, card updates and cancellation, all self-serve, effective from the next billing period. The Free tier is not a timed trial and does not expire. Refunds and proration: cancel a paid plan at any time; the current billing period is not refunded, and a mid-period downgrade takes effect at the next billing period rather than a partial credit. We'll make a genuine billing error or service failure right on a case-by-case basis — reach out at the address above.

7. Service status and changes

This is pre-1.0 software under active development. Interfaces change, features arrive, and not every row on the pricing page is working software you can use today. As of this writing that is: Single sign-on (not built yet); Priority support (included, fulfilled by a person). Each is labelled that way on the pricing page itself, on the same line as the plan that lists it. The desktop installers are not code-signed today, which your operating system will tell you in its own words; that is stated on the download page rather than discovered.

8. Suspension and termination

You may stop using Hawkeye at any time, and you may ask for your org and its data to be deleted — see Privacy for what that covers and what survives it. We may suspend an account that is breaching section 5, or that is being used in a way that endangers other people's machines, and we will say why.

9. No warranty

Hawkeye is provided as is, without warranty of any kind, express or implied. It is not certified for any regulated use, and nothing on this site is a compliance attestation. Keep your own backups; a control plane is not one.

10. Limitation of liability

To the maximum extent permitted by the laws of British Columbia, Canada, liability for any claim arising out of your use of Hawkeye is limited to the amount you paid in the twelve months before the claim. Disputes arising from these terms are resolved in the courts of British Columbia, Canada, which have exclusive jurisdiction.

11. Changes to these terms

When these terms change materially, the date at the top changes and account holders are told through the notification channels they have configured. Continuing to use the product after that is acceptance.