Privacy
What we collect, and what we do with it
Consedge is a business-to-business engineering company. Almost everyone who contacts us does so from a work address, about work, and this notice is written for that — plainly, and specifically about the systems we actually run.
Updated22 September 2026
Who we are
Consedge Tech LLC, 8 The Green, Ste B, Dover, DE 19901, United States. We are the controller of the personal data described here.
For anything in this notice — a question, a correction, a deletion request — write to ceo@consedge.com. A person reads that address.
What we collect
Four things, and nothing beyond them.
- What you send us
- When you use a form on this site — the enquiry form, a Feasibility Review or Production Readiness Audit booking, or the drawing-generation demo — we receive what you typed: your name, work email, company, role, an optional phone number, and your message. Nothing is pre-filled and nothing is inferred.
- Chat conversations
- If you use the assistant on this site, we receive your messages, its replies, which page you opened it on, and an opaque identifier that groups one conversation together. That identifier is generated in your browser, is not linked to you, and is discarded when the conversation ends.
- Business information about your company
- When a work enquiry arrives, we may look up publicly available business information about the company and the role — company size, sector, the platforms it works with, a work email format — through a third-party business-data provider, so that the engineer who replies has read up before the call. This concerns your professional capacity, never your personal life.
- How the site is used
- Standard server logs from our hosting provider, and analytics that record which pages are read, what is clicked and how far people scroll. We do not use this to identify individuals.
The chat assistant, specifically
The assistant is an AI, and it says so in its first message. It is there to answer technical questions about Revit, Tekla, NX, SolidWorks and the Autodesk platform, and to put you in front of an engineer when it cannot.
To produce a reply, your messages are sent to Anthropic's API. Anthropic processes them on our behalf and does not use them to train its models. Transcripts are kept for twelve months, so that a conversation from the spring still makes sense when you come back in the autumn, and so we can see which questions we keep failing to answer well. After twelve months they are deleted.
Please do not paste confidential model data, client information or credentials into it. Nothing in the assistant needs them, and a chat window is the wrong place for them. If you need to share something under NDA, write to us and we will sign one first.
Why we are allowed to
If you are in the UK or the EU, the UK GDPR and the GDPR give us a short list of lawful bases. These are the ones we rely on.
- Legitimate interests
- Replying to a business enquiry, preparing for a call you asked for, and keeping a record of the conversation. We think you would expect all three when you write to a supplier from a work address. You can object at any time, and we will stop.
- Consent
- Analytics and heatmap tracking, where your jurisdiction requires it. You can withdraw it by blocking the scripts in your browser; nothing on this site stops working if you do.
- Contract
- Where you become a client, the information needed to do the work and to invoice for it.
Who else sees it
We do not sell personal data and we do not share it for anyone else's marketing. These are the services we use to run the company, each doing one job.
- Vercel
- Hosting and server logs.
- Anthropic
- Generating the chat assistant's replies.
- Telegram
- Delivering enquiries to our internal inbox.
- Notion
- Our record of enquiries, accounts and conversations.
- n8n Cloud
- Routing an enquiry from the website into that record.
- Apollo
- The business-data lookup described above.
- Prismic
- The content management system behind articles and case studies.
- Google Tag Manager and Plerdy
- Site analytics and heatmaps.
Where it goes
We are a United States company and our suppliers are largely United States companies, so personal data from the UK or the EU is transferred to the United States. Where that transfer needs a safeguard, we rely on the Standard Contractual Clauses in our agreements with those suppliers.
How long we keep it
Longer than we need is a liability, not an asset.
- Chat transcripts
- Twelve months.
- Enquiries and contact records
- Twenty-four months after the last contact, unless you become a client, in which case for as long as the engagement and our record-keeping obligations require.
- Do-not-contact requests
- Indefinitely. Keeping a note that you asked not to be contacted is the only way to honour it, and we keep nothing else alongside it.
- Server logs and analytics
- As set by the providers above, typically weeks rather than years.
What this site stores in your browser
No advertising cookies and no cross-site tracking of our own. The site keeps three small values locally, which never leave your browser and which clearing site data removes.
- consedge.visits, consedge.lastSeen
- Counts whether you have been here before, so we do not show a first-time prompt to a returning reader.
- consedge:chat-bucket
- A number that decides whether you are shown the chat assistant while it is being rolled out gradually.
Your rights
You can ask us for a copy of what we hold about you, ask us to correct it, ask us to delete it, object to what we are doing with it, or ask for it in a portable form. If you are in the UK or the EU these are rights; everywhere else we will honour them anyway, because the alternative is arguing about geography.
Write to ceo@consedge.com. We will reply within thirty days, and usually much sooner. If you are in the UK or the EU and we have got something wrong, you may also complain to your national data protection authority.
Children
This site is for people doing their jobs. It is not directed at children and we do not knowingly collect their data.
Changes
Last updated 22 September 2026. When we change how any of this works, we change this page in the same release, not afterwards.