Vecto — Terms of Service

Version: 1.0 · Effective: 2026-08-23

Please read section 3 first. Vecto is in beta. That is not a disclaimer we hide at the bottom — it changes what you should reasonably expect from the service, and we would rather you know before you sign up than after.

---

1. Who we are, and what this document is

Vecto is operated by ITbrouwerij BV, a company established in Belgium, VAT BE0508.516.956, RPR Antwerp (Mechelen division), registered at Breendonkstraat 342a, 2830 Willebroek, Belgium ("Vecto", "we", "us"). We are contactable at [email protected].

Your agreement is with ITbrouwerij BV. Section 17 sets out what happens if it is ever transferred to another company.

These Terms are the agreement between us and you — the person or organisation using Vecto ("you"). They apply when you create an account, accept an invitation to someone else's workspace, or use the service in any other way. If you are accepting on behalf of an organisation, you confirm you are allowed to bind it.

Our Privacy Policy explains what we do with personal data. It is part of this agreement.

2. What Vecto is

Vecto is a platform on which you describe a product in ordinary business language, and AI "colleagues" — a product manager, an architect, a security reviewer — turn that description into a plan and then into working software. Everything you and the AI produce is stored as a connected graph: ideas, stories, epics, documents, decisions, code, builds, and the audit trail of who authorised what.

Three things about how it works are worth stating up front, because they are also promises:

• You set how much the AI may do on its own. Each AI role has an autonomy setting, from "observe and propose" to "act automatically". Below the top setting, a build is authorised by an explicit two-step confirmation from you — the confirmation is the sign-off.
• The reviewer is not the builder. The AI that writes code never writes its own security verdict. That separation is enforced in the pipeline, not by convention.
• What happened is recorded. Plans, AI dispatches, builds, spend and privileged actions are written to an audit trail attached to your tenant.

3. Beta — what you should and should not expect

Vecto is beta software. Concretely, and without softening it:

• There is no service level agreement. No uptime commitment, no response-time commitment, no credits for downtime.
• The platform runs on a single production machine. There is no high-availability setup and no automatic failover. A hardware failure means a recovery window measured in hours, and a restore from the most recent backup — we take daily backups, so up to roughly a day of work could be lost in a worst-case restore.
• Features change, and some are removed. Interfaces, limits, tiers and behaviour will change during beta, sometimes without notice.
• Things break. AI-generated output can be wrong, builds can fail, and defects reach production.
• Rate limits apply and may change. Requests are limited per tenant according to your tier. The tier structure itself is not final.
• Keep your own copy of anything you cannot afford to lose. Section 8 explains how to get your data out. Please actually do it.

If any of this is incompatible with what you need, Vecto is not the right tool for that workload, and we would rather tell you now than after you have built on it.

4. Your account

• You need an account. During beta, access is generally by invitation.
• Give accurate details and keep your password and any access tokens confidential. Everything done with your credentials is treated as done by you.
• Tell us promptly at [email protected] if you believe your account or a token has been compromised.
• You must be at least 16 years old. Vecto is a tool for professional use and is not directed at children.
• Workspaces can have several members with different roles (owner, admin, member, viewer). If you invite people into your workspace, you are responsible for who you let in and what they can see.

5. Acceptable use

You may not use Vecto to:

• break the law, infringe someone else's rights, or process data you have no right to process;
• upload content you do not have the rights to — including source code you are not licensed to share with a third-party service;
• build or distribute malware, spam infrastructure, phishing pages, or tooling whose purpose is to gain unauthorised access to systems;
• attack, overload or probe our infrastructure, or attempt to reach another customer's data. (Security research on your own tenant is welcome — please tell us what you find, at [email protected], before telling anyone else.);
• circumvent rate limits, tier restrictions, autonomy gates or the compliance lock;
• resell or provide the service to third parties unless we have agreed that in writing.

Automated access through our API or the MCP server is a normal, supported way to use Vecto. Use an access token scoped to what you actually need, and stay inside the published rate limits.

6. Your content and your code — you own it

You keep ownership of everything you bring and everything Vecto produces for you. That includes source code you import, documents you write, product data, and the code the AI generates on your instruction. We claim no ownership in it, and gaining rights to your material is not the point of the service.

To be precise about what we do need: you grant us a limited, non-exclusive licence to host, store, copy, transmit, analyse and display your content solely to provide the service to you — that is, so the platform can run your builds, index your graph, show you your own data, sync it to the systems you connect, and keep backups. That licence lasts as long as your content is on the platform and no longer, and it covers nothing else.

We do not use your content to train AI models. Not our own, and we do not submit it to third parties for their training — see the Privacy Policy for how engine choice affects which providers see your content, and read their terms if you supply your own key.

We do not trade access for insight into your data. If we ever offer a tier that works that way, it would be opt-in with your explicit consent, alongside a paid alternative that shares nothing — and it would require your separate agreement. Nothing of the kind happens under these terms.

Third-party components. Generated code may include open-source libraries under their own licences. Those licences govern that code, and complying with them is your responsibility as the person shipping the result.

Feedback you send us about Vecto itself — bug reports, suggestions — we may use freely, without obligation to you. That is about the product, never about your content.

7. AI output — read this before you ship anything

Vecto generates software using large language models. That has consequences you have to own:

• Output can be wrong, insecure, or nonsensical. It can also look confident while being wrong. Everything Vecto produces is a proposal until you have reviewed it.
• The security review is a control, not a guarantee. An AI security reviewer reads the result and issues a verdict before deployment. It reduces risk; it does not certify that code is safe. It has no professional liability and neither do we.
• Output is not advice. Nothing Vecto generates is legal, financial, medical or other professional advice, whatever it looks like.
• Generated output is not guaranteed to be unique. Two users describing similar things may get similar code, and we make no representation that output is original or non-infringing.
• You are responsible for what you deploy. Review, test, and where the stakes justify it, have a human expert review it. Especially if it processes other people's personal data, handles money, or matters to safety.

Model quality varies significantly between engines, and the smallest local models are noticeably weaker than the large hosted ones. Which engine ran a given step is recorded and visible to you.

8. Getting your data out

Your data is exportable while your account is active:

• through the REST API (/api/v1/…) and the MCP server, which read your graph nodes, documents and files;
• documents are stored as plain Markdown and files can be downloaded individually;
• generated code is written into a repository you can retrieve.

If you need a complete extract of everything, ask us at [email protected] and we produce one for you. We handle it ourselves rather than behind a button, so that what you get is complete and you know when it is ready.

9. Preview deployments are public

When Vecto builds and deploys an application for you, it is published at a URL derived from your tenant and product name (for example yourtenant-yourproduct.vecto.build). These previews are served publicly over the internet and are not password-protected. Anyone who knows or guesses the URL can open them.

Do not put real personal data, credentials or confidential material into a previewed application, and treat everything a preview exposes as public.

10. Fees

During beta, access is provided on the terms we agree with you individually — for most beta participants, at no charge. The tier and pricing model is not final.

If you use an AI engine that we pay for on your behalf, we record the usage and cost per call and you can see it. We will not start charging you for something you previously had for free without telling you in advance and giving you the chance to stop.

If you supply your own provider key, you pay that provider directly under their terms, and their rate limits and outages are between you and them.

11. Third-party services you connect

Vecto can connect to systems you own — Jira, Confluence, GitHub, Slack, your own AI provider accounts. You choose to connect those, you provide the credentials, and their terms govern them. We are not responsible for what those services do, for their availability, or for what happens to data once you have instructed us to sync it there.

12. Our intellectual property

The Vecto platform, its source, its brand and its documentation are ours (or our licensors'). These Terms give you the right to use the service, not to copy, resell or reverse-engineer it. Some components are or will be released as open source; where that is the case, the open-source licence governs those components and is more permissive than this section.

13. Suspension and termination

You can stop using Vecto at any time, and ask us to close your account by writing to [email protected].

We may suspend or terminate access if you materially breach these Terms — in particular section 5 — if your use threatens the platform's security or stability, or if we are legally required to. Except where the situation is urgent or unlawful, we will tell you first and give you a reasonable chance to fix it.

We may also discontinue the beta, or the service, with reasonable notice. If we do, we will tell you before it happens and give you time to export.

What happens to your data

• Export first. After termination we will retain your content for 30 days, during which you can ask us to extract it. Do not rely on this window — export as you go.
• Then deletion. After that period we delete your workspace content from the live system.
• Backups lag. Deletion from the live database does not immediately remove data from encrypted backup snapshots; those age out on their own backup rotation.
• Some records survive, and must. Audit-log entries, usage/spend records and invoicing data are retained because we need them for security, accountability and legal obligations, and because an audit trail you can delete is not an audit trail. They are not used for anything else.
• Account deletion involves us. Write to us and we carry it out, and confirm when it is done. We handle it ourselves rather than behind a button, so that what is removed is what you meant.

The Privacy Policy sets out your rights over personal data, which are separate from and additional to this section.

14. Warranties and liability

Vecto is provided "as is" and "as available". To the fullest extent the law allows, we exclude all implied warranties — including fitness for a particular purpose, uninterrupted availability, and that output will be accurate, secure, or free of third-party rights.

We do not exclude liability for death or personal injury caused by our negligence, for fraud, or anything else that cannot be excluded under Belgian law. Nothing here limits the rights you have as a consumer, if you are one.

Subject to that, and to the extent the law allows:

• we are not liable for indirect or consequential loss, loss of profit, loss of business, loss of goodwill, or loss or corruption of data;
• our total aggregate liability under this agreement is limited to the amounts you paid us in the 12 months before the claim, or EUR 100 if that is greater — which, during a free beta, is a low number, and you should factor that into how you use the service.

15. Personal data

Where we process personal data on your behalf — the content you put into your workspace — you are the controller and we act as your processor. Where we process personal data about you as our customer or as a visitor to our website, we are the controller. The Privacy Policy explains both. If you need a written data processing agreement under Article 28 GDPR, contact us and we will put one in place.

16. Changes to these Terms

We will update these Terms as the platform changes. For material changes we will notify account holders — by email or in the app — before they take effect. Continuing to use Vecto after that means you accept them. If you do not accept them, stop using the service and ask us to export and close your account.

Every version is kept in our source repository, so what changed and when is traceable.

17. General

• Governing law: Belgian law.
• Venue: the courts of Mechelen — formally the Antwerp judicial district, Mechelen division, which is the district of our registered office — unless mandatory consumer rules give you another forum.
• Severability: if a provision is unenforceable, the rest stays in force.
• No waiver: not enforcing something once does not waive it.
• Assignment: you may not assign this agreement without our consent; we may assign it to a successor entity. That is not a theoretical clause: Vecto is operated by ITbrouwerij BV today, and a separate company for Vecto is intended later. If the agreement moves, you will be told.
• Entire agreement: these Terms plus the Privacy Policy are the whole agreement, replacing earlier discussions.

18. Contact

ITbrouwerij BV Breendonkstraat 342a, 2830 Willebroek, Belgium VAT BE0508.516.956 · RPR Antwerp, Mechelen division Email: [email protected] Web: https://vecto.build

---

Draft prepared 2026-07-29 under US-1286. Every operational statement in this document was checked against the Vecto source code and the internal compliance documentation; the mapping from claim to evidence is in compliance/pipelines/legal-transparency.md. This draft has not been reviewed by a lawyer.