How we keep clients, sites and work apart.
Each client's agent is kept to that client's folder and access. Each site is kept apart from the others. Every change leaves a record you can read. This page also says what we do not have yet.
Written for technical buyers. Where we have no answer yet, we say so.
The Orchestrator keeps every project to its own folder.
Each client has its own agent, and each project has its own. A project agent is kept to its own project's folder and access.
- One folder per project. Each agent has its own memory and its own folder. A check runs before an agent touches a file.
- Plans before work. By default, anything non-trivial starts as a numbered plan with its risk and the way back. You approve, change or reject the plan before the work starts.
- A full trail. Every run is logged as it happens. Every job ends with a written validation: what changed, what was tested and what is still open.
- Watched while it runs. Every job is checked automatically for stalls, loops and silence. Nothing is stopped unless a person decides.
Big jobs are split between helper workers on a cheaper model. They stay inside the same project, and the project agent checks their work before it reports back.
Acme client · Size guides
Project agent, kept to its own folder
- Acme client · Size guides
Can read and change - Hale client
Outside its folder - Larch client
Outside its folder - Northgate client
Outside its folder
Each Webgentic site is kept apart.
Webgentic for ecommerce is hosted by us. The agent works in a working copy of your site. We connect with access you give us, and the details are in your onboarding.
Every site is kept apart.
Each site is set up on its own, so the work on one site is kept apart from the work on another.
- Each site is set up on its own
- Work happens in a working copy of your site
- We connect with access you give us
A way back for every change.
A change made through Webgentic is live as soon as the agent writes it. There is no approval step, so the way back matters: History and restore let you undo it.
- A plan comes first, and the change appears on the page as it is made
- Stop cancels the job
- Every change is saved with a plain-English note
- Any earlier version restores in one click, at no charge
History · Hale client site
- Moved the booking button up the classes page
- Updated the Saturday class prices
- Changed the heading on the home page
Payments and customer data on a store.
What an agent can reach is set by the project it works on. A store is one project, kept apart from other clients and sites.
- It reaches one store. The agent for a store is kept to that store's folder and access.
- Checkout jobs start as plans. In the Orchestrator, a change to checkout or the basket is a numbered plan first, with its risk and the way back, and by default nothing changes until you approve it. On Store care, a developer checks it first and you approve it.
- Proof after the change. Every job ends with a written note of what changed and what was tested, so you can see that the basket still works.
- Limits we state. Webgentic for ecommerce cannot edit products, prices or stock on WooCommerce or Magento, and has no access to orders or customer data today, because that side is not built. Those jobs go through Store care or the Orchestrator.
You decide who gets in.
We load your clients and their access with you when we set up your Orchestrator.
- Client workspaces see one project. A client you invite sees their own project, signed in with Google. You choose who is on the list.
- Removal takes effect at once. Take a person off the list and their next request is refused.
- Email starts as drafts. Client and project agents can draft email but not send it. You can allow sending for a client or a project.
Your clients' knowledge is kept in your Orchestrator.
Each client and project agent keeps its own memory, so one client's notes and instructions are kept to that client's agent.
- Memory kept apart. What an agent learns about a client stays with that client's agent, inside your Orchestrator.
- Playbooks come to you. Our core playbooks keep improving and reach you as updates. Lessons are shared as general platform know-how. Client names, data and details stay with the agency that owns them.
- A log of every site request. Webgentic for ecommerce records each request and what it cost.
- The terms are in writing. How we handle personal data is set out in our data processing addendum.
The AI providers we use.
We move to newer versions as they arrive, so this page names the providers, not the versions.
| Provider | What it does | What it sees |
|---|---|---|
| AI model providers | Anthropic, OpenAI and Google process the text and screenshots needed for a request. | Your request, the files it works on and the images the agent sends to be checked. |
| A second AI model | Checks screenshots and designs as a second opinion on anything visual. | The images the agent sends to be checked. |
| Speech to text, from OpenAI | Turns voice notes into text in the Orchestrator. | The voice note. |
If a client's contract rules out sending its images to other AI providers, the image cross-check can be switched off for that client.
What we have, and what we do not have yet.
Some things a buyer expects are not there. We would rather say so here than have you find out later.
| Area | What we have | What we do not have yet |
|---|---|---|
| Sign-in and roles | Client workspaces sign in with Google and see one project. You choose who is on the list. | No single sign-on. There are no named permission roles for your team yet. |
| Certifications and audits | A written data processing addendum, and a written validation at the end of every Orchestrator job. | We hold no security certification. We have not had a penetration test or an independent audit. |
Report a security problem.
If you think you have found a weakness in Webgentic, email us. Your message goes to a developer on our team.
- Email info@webgentic.ai with the word Security in the subject.
- Say what you found and how we can see it for ourselves.
- Please do not test against other customers' sites or data.
- Please give us a chance to fix the problem before you share it.
Security questions, answered plainly
How is one client's work kept apart from another's?
Each agent is kept to its own client or project folder and access, and a check runs before it touches a file. Client names, data and details stay with the agency that owns them.
How are Webgentic sites kept apart?
Each site is set up on its own, so the work on one site is kept apart from the work on another. The details are in your onboarding.
Can I undo a change Webgentic makes to my site?
Yes. Every change is saved with a plain-English note, and any earlier version restores in one click. There is no approval step first, so history and restore are how you undo a change.
Do you offer single sign-on?
No, not yet. There are also no named permission roles for your team.
Are you audited or certified?
No. We hold no security certification and have not had a penetration test or an independent audit.
How do I report a security problem?
Email info@webgentic.ai with Security in the subject. The report a security problem section above says what to include.
Something else on your mind?
Ask us directly and a developer will reply.
Ask a question
Questions from your security review?
Tell us what it needs. A developer will answer, not a chatbot.
