Where your data sits, and who can reach it.

Each client's system runs on its own database, its own hosting and its own accounts. Client data is not shared between systems, and Basecourse does not use one client's data to build for another.

In practice this means a separate project per client rather than one multi-tenant platform: separate credentials, separate backups, separate logs. Nothing is pooled for convenience.

The code, the database and the hosting accounts are in the client's name. Handover is documented, and it is documented from the first module, not at the end.

• Repository in your organisation
• Database and hosting billed to you
• Handover notes kept current

Where a system uses AI, it calls enterprise APIs under terms that do not train on client data. The model sees only what the feature needs: the document being read, or the records behind the report being written.

Nothing is sent to a model in the background, and no client data is used to improve anything we build for anyone else. Which provider a system uses is written into its documentation, and it can be changed.

Systems are hosted with established cloud providers, in the region chosen at the start of the engagement. Where a contract or a ministry requires data to stay in a particular country, say so early and we will host it there.

People see what their role needs. Approvals and documents carry an audit trail: who issued a delivery note, who approved a programme, who changed a quantity and when.

• Role-based access
• Audit trail on approvals and documents
• Access removed on the day someone leaves

Send them to hello@basecourse.io and we will answer in writing. If your IT team has a questionnaire, send it — a short, specific answer beats a brochure.

Found a vulnerability in this website? The same address takes reports; see security.txt. What this website itself collects is in the privacy policy.