Data handling
Adapted per engagement.
We adapt data handling per engagement; this page explains the posture, not the technology stack.
Engagement-side posture
- Confidentiality is a primary engagement constraint — we treat your data and your problem framing as such by default.
- Deployment is per engagement: we adapt to your data-residency, access-control, and environment requirements rather than forcing one shape.
- We do not train models on your data. AI proposals are generated for your engagement; nothing is reused outside it.
- Specific technology, deployment, and data-flow details are agreed in the Smart Enquiry / discovery call, then written into the engagement.
- Where work needs to run inside your environment, we adapt — see /scoped-pilot for engagement mechanics.
Product-side posture
- Your data is account-tied — accessible only to your account holder.
- Inputs and outputs are not used to train any model.
- Account-tied data is deletable on request; the deletion path is in the Privacy Policy.
- Your data and AI-generated outputs are exportable in formats you can re-use outside the platform.
- Some inputs are stored to enable session continuity; transient inputs are kept only as long as needed for the analysis to complete.
Public courses
Courses are free. Sign-in is required only so we can save your progress through lessons. We store your enrolment record, lesson completion state, and any questions you ask the Learning Assistant during a lesson. Learner data is not used to train models, and the same deletion path as for product accounts applies. See /courses for the catalogue.
Where to go next
Two paths from here: corporate buyers start a Smart Enquiry; individual users try EIS Fitting.