FAQs

A chat assistant answers when you ask. GREX runs whether you ask or not.

The unit here is a process: a named piece of recurring work with a trigger, a written method, an owner and a record of every time it ran. That is what a chat window has no place to put. Ask an assistant to chase overdue invoices and you get a good answer once. Put it in GREX and it happens every Tuesday, and writes down what it did.

The knowledge is the other half. Your methods, your metrics, your tools and who owns what live in one model rather than in a prompt somebody pasted and then lost.

No, and we would rather you did not. GREX connects to the tools you already run and reads and writes through them.

What it adds is the layer above: one place that knows what work exists, who owns it, which tools it touches, and how it is doing. Keep your CRM as your CRM. The point is to stop the answer to "how does this actually get done here" living in four apps and three people's heads.

You do. Everything you put in is yours, and so is everything the system produces from it: your data, your process definitions, your documents, your history.

We own our software. Nothing you build inside GREX gives us any claim over your business or your ways of working, and that does not change if you leave. No licence back to us, no copy retained for our benefit.

No. Your workspace data is used to run your workspace, and for nothing else. We do not train models on it and we do not pool it across customers.

The model providers behind GREX operate under API terms that exclude training on submitted data. Retention and sub-processor detail is set out in our DPA, which we will send you before you sign anything.

You do not have to ask. You get API access from day one and every object in your workspace has a read endpoint, so you can pull a full copy on your own schedule to your own storage. We will also generate a complete export bundle whenever you want one, and automatically on termination before anything is deleted.

What is in it: one JSON file containing everything, the same content split by type with metric history as CSV, and every process method as plain readable Markdown. That last part is the one that matters most. JSON, CSV and Markdown, with nothing that needs our software to open it.

Ask us for the sample export and we will send you the real thing to look at before you commit.

We will put these in the contract:

• Export at any time during the term, at no charge.
• Up to 30 days of transition assistance on notice, extended if your migration needs longer.
• 30 days after termination to retrieve your data, then full deletion with written confirmation.
• No egress or switching charges, ever.

That is the switching standard set by the EU Data Act (Chapter VI). We would rather commit to it in writing than argue about whether it applies to us.

Fair question to ask a company still in stealth, and a promise is the weakest possible answer to it.

The real protection is that you already hold the data. If you run a scheduled export against the API, a current copy sits on your own storage at all times, independent of us and independent of whether we are still here. We will set that up with you during onboarding rather than wait for you to worry about it.

If your legal team wants belt and braces on top, we are open to a source code escrow arrangement.