1. Agreement to Terms
By accessing or using BytesBrains's website, applications, or services (collectively, the “Services”), you agree to be bound by these Terms and our Privacy Policy. If you do not agree, please do not use the Services. If you are using the Services on behalf of an organization, you represent that you have authority to bind that organization to these Terms.
2. Our Services
BytesBrains builds SaaS products and provides AI and technology consulting and contract engineering services. Some features require an account; others, such as our public website, do not. We may add, change, or discontinue features at any time.
3. Accounts & Eligibility
Certain features require you to sign in (for example, through Google authentication). You are responsible for the activity that occurs under your account and for keeping your credentials secure. You must be at least 18 years old, or the age of majority in your jurisdiction, to create an account. Provide accurate information and keep it up to date.
4. Acceptable Use
You agree not to:
- Use the Services in violation of any applicable law or regulation;
- Attempt to gain unauthorized access to any system, account, or data;
- Interfere with, disrupt, or overload the Services or related infrastructure;
- Reverse engineer or copy any part of the Services except as permitted by law;
- Submit unlawful, infringing, harmful, or misleading content; or
- Use the Services to build a competing product or for unauthorized resale.
5. Client Engagements & Statements of Work
Paid consulting or contract engineering services are governed by a separate written agreement or statement of work (“SOW”). Where an SOW conflicts with these Terms, the SOW controls for that engagement. Inquiries submitted through our website do not create a binding engagement until a separate agreement is signed.
6. Intellectual Property
The Services, including all software, text, designs, and trademarks, are owned by BytesBrains or its licensors and are protected by intellectual property laws. We grant you a limited, non-exclusive, non-transferable right to use the Services for their intended purpose. Ownership of deliverables produced under a client engagement is governed by the applicable SOW. You retain ownership of content you submit, and grant us the rights needed to operate the Services and respond to your inquiries.
7. Third-Party Services
The Services rely on third-party providers (for example, Google Cloud and Firebase for authentication, data storage, and hosting). Your use of those services may be subject to their own terms. We are not responsible for third-party services we do not control.
8. Fees
Use of our public website is free. Paid products or services, and any associated fees, billing, and refund terms, are described in the applicable order form or SOW. Domains and business email are sold directly rather than under an SOW, and their fees, renewal and refund terms are set out in sections 9 and 10 below. Cruise credits, the card fee and refunds of unused credit are set out in section 11.
9. Domain Registration & Business Email
We resell domain registrations through our registrar partner, Tucows/OpenSRS, and business email through the same supplier. When you register a domain through us you also agree to their Registration Agreement, and to the policies of ICANN and of the registry operating your chosen extension. Where those rules conflict with these Terms, theirs control — they are not ours to override.
Domain registrations are non-refundable once the registration has been submitted to the registry. The registry charges us at that moment and does not reverse it, so neither can we. If an order fails before registration — a declined payment, a name taken while you were checking out, a registration the registry refuses — you are refunded in full, and you do not need to ask. If a registration succeeds, the name is yours for the term you bought and the fee is spent.
Registrations run for the term shown at checkout and do not renew automatically; we contact you before expiry. Keeping your registrant contact details accurate is a requirement of ICANN policy, not a preference — a registration whose contacts cannot be reached may be suspended. Your rights and responsibilities as a registrant are set out in ICANN's Registrant Rights & Responsibilities.
We may suspend or terminate a domain or mailbox used for phishing, malware distribution, spam, or other abuse, and we may act on a registry, registrar or law-enforcement instruction. To report abuse, see Report Abuse, which sets out the address, the process and the response times we hold ourselves to.
10. Business Email Billing
Mailboxes are sold as a subscription, priced per mailbox, and charged in advance. You choose monthly or yearly when you create the first mailbox on a domain, and every mailbox on that domain then shares that billing period. The first charge is taken at the moment the mailbox is created — not at the end of the period — and the subscription renews automatically on the same schedule until you remove the mailbox.
Paying yearly costs twelve times the monthly rate less the discount shown at the time of purchase. That discount is fixed when you buy and is not affected by any later change to the rate we advertise; equally, a discount we introduce later does not apply to a subscription already running. Adding a mailbox part-way through a period is charged immediately for the remainder of that period, pro rata, and it then renews with the others.
Mailbox fees are not refundable, in whole or in part. Removing a mailbox stops it renewing and does not refund the period you have already paid for. It keeps working until the end of that period, and is deleted then — on a yearly subscription that means a year is a year's commitment, but it is a year you keep the use of. You may change your mind at any point before that date and keep the mailbox, from the same place you removed it; once the date passes it is deleted and we cannot reverse that, so please export anything you want to keep beforehand.
If a payment is refused we do not switch anything off at once. We retry the card two days and five days after the failed date, and your mailboxes work normally throughout. Seven days after it, the subscription enters a grace period: we keep retrying every three days and your mailboxes still work. Twenty-one days after the failed date, mailboxes on the subscription are suspended — sign-in, sending and delivery stop, so you should assume mail sent to you while suspended may not reach you. We continue retrying weekly, and a payment that succeeds restores access automatically on the next nightly run.
Suspension does not delete anything. We never delete a mailbox automatically for non-payment. Deletion only ever follows from you removing the mailbox, from the abuse process described above, or from a decision we take and tell you about. You can end the suspension at any point by settling the balance.
Nothing here limits any right you have under consumer law that cannot be excluded by agreement. Where such a right conflicts with this section, that right applies.
11. Cruise
Cruise is BytesBrains's LLM gateway. We resell provider capacity: when you send a request, it is forwarded to a third-party model host. We do not run the model ourselves. The hosts that may receive content are named on our Sub-processors page; that list is kept current as hosts are added.
11.1 Provider choice
You name a lane (a job), not a laboratory. The lane picks which host serves each request. We do not promise that any particular provider will handle a given call. Which model actually answered is returned on the response (x-cruise-model) and recorded in the ledger.
11.2 Models, training and your content
Every priced, usage-reporting model is available to a billed workspace by default — including models whose providers may train on prompts, and models whose retention posture is unrecorded (null on the catalogue). Retention is disclosed per model on GET /v1/models (x-cruise.data_retention: none, retained, trains, or null). Unrecorded means we have not verified what that host does with prompts — not that it is safe. Each lane also shows the privacy-worst fold across its members.
Callers who refuse unknowns or training can use a lane with the no-training-on-data requirement; that lane fails closed on both trains and null. Filling unrecorded rows is ongoing work; it does not change the default that those models remain reachable until a lane opts out.
You are responsible for what you send. If you put personal data, confidential material or anything your own policies forbid into a request that can reach a training model or a host whose retention we have not recorded, that is your decision and your compliance obligation — not ours. Read the per-model and per-lane disclosure before you send traffic that matters.
11.3 Gateway and caching
Customer workspaces run on a gateway that does not log request or response payloads. Cached answers, when caching is enabled, are the model's complete output stored for up to the configured TTL (ceiling thirty days). Production lanes start with caching off unless you ask for it. The default cache pool is per-project; choosing a wider pool (tenant or, where offered, platform) at key issue is the consent to that wider sharing.
11.4 Budgets and the wallet
Project budgets refuse at a hard cap. The workspace wallet hard-stops at $0 — service stops rather than overspending, including for a production dependency. A soft warning may fire earlier; it does not change the hard stop.
11.5 Credits, fees and refunds
Usage is billed from prepaid credit. The credit you buy is added to your balance in full, and each request served is deducted from it at the provider's list rate plus a markup of 3% by default, or a different rate agreed with us in writing for your workspace. A cache hit that returns a stored answer is billed at 20% of list. Both figures are dated commercial terms and may change; the rate in force when the request is served is what you pay.
When you top up you may also pay a payment fee. It depends on the payment method you choose, is shown with the total before you pay, and is not added to your credit balance. Your own bank or card issuer may charge fees of its own, including for currency conversion; those are theirs, not ours. Credit never expires.
Unused credit from a top-up made in the last 30 days is refundable on request, up to the unspent balance of that top-up, minus the payment fee. Spent credit is never refundable. Free credit an administrator grants is not money and is not refundable.
11.6 Acceptable use of Cruise
In addition to section 4, you agree that:
- Each request remains subject to the acceptable-use and content policies of the provider that serves it;
- BytesBrains neither generates nor moderates model outputs — the answer is the provider's; and
- You will not use Cruise to violate law, to abuse another person's rights, or to circumvent a provider's own restrictions by routing through us.
11.7 When you leave
Ending a Cruise workspace disables it: keys are revoked, lanes are archived, memberships end. Ledger and audit rows that name those identifiers — including a body digest, not the prompt itself — are kept by design. There is no erasure path for that history today. Cache entries expire on their own TTL.
11.8 Staging
Staging and production are separate systems. Staging carries no production guarantees and is not a rehearsal of production behaviour, pricing or retention.
11.9 Cruise Enterprise
Cruise Cloud routes prompts to third-party model providers. If your organisation requires Cruise on your own infrastructure with your own provider keys and models (including AWS Bedrock or self-hosted endpoints), contact us about Cruise Enterprise at contact@bytesbrains.com. Enterprise is a separate deployment and contract in the same product family; Cloud does not offer the same isolation. Engagements are scoped to your needs.
12. Confidentiality
Each party may receive confidential information from the other. The receiving party agrees to protect such information and use it only as necessary to provide or use the Services, except where disclosure is required by law.
13. Disclaimers
The Services are provided “as is” and “as available” without warranties of any kind, whether express or implied, including warranties of merchantability, fitness for a particular purpose, and non-infringement. We do not warrant that the Services will be uninterrupted, error-free, or secure.
14. Limitation of Liability
To the maximum extent permitted by law, BytesBrains will not be liable for any indirect, incidental, special, consequential, or punitive damages, or any loss of profits, revenue, or data, arising from your use of the Services. Our total liability for any claim relating to the Services will not exceed the amount you paid us in the twelve months before the claim.
15. Indemnification
You agree to indemnify and hold BytesBrains harmless from claims, damages, and expenses arising from your use of the Services or your violation of these Terms.
16. Termination
We may suspend or terminate your access to the Services at any time if you violate these Terms or to protect the Services. You may stop using the Services at any time. Provisions that by their nature should survive termination will survive.
17. Governing Law
These Terms are governed by the laws of the jurisdiction in which BytesBrains is registered, without regard to its conflict-of-laws rules. Disputes will be subject to the exclusive jurisdiction of the courts located there.
18. Changes to These Terms
We may update these Terms from time to time. We will revise the “Last updated” date above and, where appropriate, provide additional notice. For Cruise, a material change bumps the terms version recorded at signup; existing members are asked to accept again before the dashboard. Your continued use of the Services after changes take effect constitutes acceptance of the updated Terms where a versioned acceptance is not required.
19. Contact Us
Questions about these Terms? Contact us at hello@bytesbrains.com.