Privacy

• No third-party analytics script and no tag manager.
• No advertising or conversion pixel, from anyone.
• No chat widget sitting in the corner listening.
• No session replay. Your scrolling and typing are not recorded.
• No A/B testing tool and no personalisation engine.
• Fonts are served from this domain. They are downloaded when the site is built, so your browser never asks a font network for them, and no font network learns that you visited.
• No cross-site identifier. Nothing here follows you to another website, because there is nothing here that could.

Which is why there is no cookie banner interrupting you. There is nothing to consent to. A consent wall on the site of a company selling governance would also have been a poor first impression.

Which pages were opened, how far down them people read, which sections came into view, which buttons and links were clicked, which questions were expanded, and whether the contact form was started, errored, or completed. Page-level, not person-level: we are trying to learn which pages convince people and which lose them.

Two things are stored in your browser, in local storage rather than in a cookie: a random identifier that is meaningless outside this site, and a first-touch record — any campaign parameters in the link you followed, the site that referred you, the first page you landed on, and the time you arrived. Those are attached to the events above so that a visit holds together as one story rather than twelve disconnected fragments.

The events are sent in batches to our own endpoint on our own domain. No third party receives them. They are not sold, not shared with an advertising network, and not joined to anything about you from elsewhere.

Block the request, use a private window, or clear this site’s storage — the identifier and the first-touch record go with it. Nothing on the site depends on the measurement, so blocking it changes nothing you can see. We would rather tell you that plainly than hide it in a paragraph about improving your experience.

The form asks for four things: your name, your work email, your company, and one sentence about the workflow that costs you most. It also records which offer you selected and the first-touch record described above. That goes to our own intake, and a person reads it.

It is used to reply to you — normally within one business hour — and, if you engage us, to do the work. It is not sold, not rented, and not added to a mailing sequence you did not ask for. If you tell us it is not a fit, we stop contacting you. That is a rule rather than a courtesy.

We keep it while the conversation is live and the record is useful. Ask us to delete it and we will, and we will confirm that we have.

One sentence about the workflow is genuinely all we need before a call. Do not paste customer records, credentials, or protected health information into a form on the internet — ours or anybody else’s. If you need to send us something sensitive, say so on the call and we will agree a channel for it first.

Data inside a workspace under a delivery engagement is a different subject with different answers: what is collected, who can see it, which model providers are involved and on what retention terms, where it lives, how long it is kept, and what happens when you leave. Those are governed by the agreement and set out in the security pack. The security page describes what is in place today and what is not, including the parts we have not finished.

For a copy of what you sent, a correction, or a deletion, write to victor@vertixone.com. A person handles it. There is no self-service portal, and at our size a portal would be theatre.

This page carries a review date and is reviewed at every release. When the counsel-reviewed notice replaces this summary, that will be dated too. We do not quietly rewrite the page and leave the old date on it.