These terms govern use of Alexandria, provided by MilUX Ltd (company no. 11937659, registered in England and Wales), by the subscribing organisation and its authorised users ("you").
Alexandria answers questions from MilUX's own knowledge corpus, cites the notes it draws on, and says plainly when the corpus does not cover a question. Some questions invoke MilUX's proprietary instruments, which run on MilUX's systems; you receive their output only. The service is not advice tailored to your circumstances, and decisions made on its output remain yours.
Paid plans are billed by Stripe on a monthly subscription; prices include VAT, and VAT-registered businesses may enter a VAT number at checkout for the applicable treatment. A question spends credits only when it produces a substantive answer; refusals, clarifying questions and truncated responses are not charged. Unused credits do not roll over except where a plan says otherwise. Plans can be changed or cancelled self-serve at any time, taking effect per the billing portal. The advisory tier is contracted and invoiced separately and these terms apply to its Alexandria access only.
3.1 The corpus and instruments are MilUX's. MilUX retains all rights in the corpus, the note packs, the instruments and the skills.
3.2 Your outputs are yours to use. You may use answers and generated outputs freely inside your organisation and in your own work products.
3.3 Pack and skills licence. Corpus packs, notes and skills made available to subscribers are licensed to the subscribing organisation for its internal business use for the duration of the subscription: you may install, run, adapt and keep working copies for your own use. You may not redistribute, resell, publish, sublicense or make them available outside your organisation, and may not use them to build or train a competing service. Content already published openly by MilUX (the free skill set) carries its own published licence and is unaffected.
3.4 Attempting to extract instruments (prompting the service to reveal gated method text) is a breach of these terms.
No material above OFFICIAL; no personal data you lack a lawful basis to process (see the Data Processing Terms); no unlawful content; no attempts to probe, overload or circumvent the service's security or quota controls; no automated resale of answers. API keys and seats are for your organisation and your responsibility.
The content of questions and attachments is processed, not stored, per the Data Processing Terms, which form part of this agreement where MilUX processes personal data on your behalf. Account deletion is self-serve; statutory billing records are retained by Stripe.
The service is provided with reasonable skill and care but without uptime guarantees at standard tiers. The corpus is versioned; answers cite the version they drew on. MilUX may improve, add or withdraw features with reasonable notice of material reductions.
Nothing excludes liability that cannot lawfully be excluded. Otherwise MilUX's total liability in any 12-month period is capped at the fees paid for the service in that period, and neither party is liable for indirect or consequential loss. The service's outputs are general knowledge products, not professional advice; you remain responsible for decisions, bids and submissions made using them.
Monthly rolling; either party may end it per clause 2. MilUX may suspend for material breach of clause 4, restoring access when resolved or terminating with pro-rata refund if not. On termination, the pack licence in 3.3 ends, except that outputs already produced remain yours under 3.2.
English law and courts. These terms plus the Data Processing Terms are the whole agreement for the service. MilUX may update these terms with notice; continued use after the notice period is acceptance.
These terms form part of the agreement between MilUX Ltd (company no. 11937659, registered in England and Wales) ("MilUX", "we") and the subscribing organisation ("the Customer") for the Alexandria service, and apply where MilUX processes personal data on the Customer's behalf.
1.1 For account and billing data (the account holder's name, email address, company, subscription and payment records, usage counts), MilUX is a controller, processing to provide and bill the service. This processing is described in the MilUX privacy statement.
1.2 For the content of questions, attachments and material submitted to Alexandria ("Customer Content"), the Customer is the controller and MilUX is a processor, acting only under these terms.
Processing of Customer Content to generate responses, for the duration of the subscription. Nature and purpose: transmission of submitted content to a language model to produce an answer or deliverable, returned to the Customer. Data subjects and categories: those contained in what the Customer chooses to submit, which MilUX does not determine and the Customer is responsible for keeping within clause 6.
MilUX shall:
a) process Customer Content only on the Customer's documented instructions, the submission of content through the service constituting the instruction to process it as described here, and inform the Customer if in MilUX's opinion an instruction infringes data protection law;
b) ensure persons authorised to process Customer Content are committed to confidentiality;
c) implement the technical and organisational measures in clause 5;
d) engage sub-processors only per clause 4;
e) taking into account the nature of the processing, assist the Customer with data subject rights requests, which given clause 5(a) will ordinarily be by confirming that no Customer Content is retained;
f) assist the Customer with security, breach notification and impact-assessment obligations under Articles 32 to 36, and notify the Customer without undue delay on becoming aware of a personal data breach affecting Customer Content;
g) at the end of the subscription, delete Customer Content, which by clause 5(a) is already the standing state, and delete account data on request per the in-service deletion function;
h) make available information necessary to demonstrate compliance with these terms, and allow and contribute to audits conducted reasonably, on notice, no more than annually except after a breach.
4.1 The Customer authorises these sub-processors:
| Sub-processor | Purpose | Location of processing | |---|---|---| | Anthropic PBC | Language model inference | United States | | Fly.io Inc | Application hosting and database | United Kingdom (London region) | | Stripe Payments Europe / Stripe Inc | Billing and payment (controller in its own right for payment data) | EU / US | | Twilio SendGrid | Transactional email (sign-in links) | US |
4.2 MilUX shall give 30 days' notice of any intended addition or replacement, during which the Customer may object on reasonable data-protection grounds; if the objection cannot be resolved, the Customer may terminate the affected service with a pro-rata refund. MilUX imposes on each sub-processor data-protection obligations materially equivalent to these terms and remains liable for their performance.
a) No retention of Customer Content by MilUX. Question text, attachments and deliverable inputs are processed in memory and are not written to any database, log, error message or metric. This is enforced structurally in the service and asserted by automated test. What is retained: a count of questions for billing, an anonymised topic record with no link to the Customer, and, on account deletion, an anonymised hashed marker of the current month's usage retained as an anti-abuse measure, from which no personal data is recoverable.
b) Model-provider retention. Inference uses Anthropic's API under commercial terms with zero data retention for eligible models; Customer Content is not used to train models. Model selection is restricted in code to zero-retention-eligible models.
c) Encryption in transit (TLS) throughout; encryption at rest for the database; credentials hashed; row-level tenant isolation enforced in the database and asserted at deployment; access to production restricted to named MilUX personnel; audit logging of security events.
d) Location. Hosting and data at rest: London. Inference: United States (clause 4.1), which the Customer acknowledges as a restricted transfer addressed by Anthropic's applicable safeguards (the EU-US Data Privacy Framework and/or standard contractual clauses per Anthropic's terms). Customers should not submit special category data, and must not submit material classified above OFFICIAL.
The Customer instructs only lawful processing; is responsible for what its users submit, including not submitting special category data, others' personal data without a lawful basis, or material above OFFICIAL; and is responsible for the acts of those it gives seats or API keys to.
These terms are subject to the limitations of liability in the main agreement. Where these terms conflict with the privacy statement in respect of processor processing, these terms prevail.
Effective 26 July 2026. Questions: contact@milux.co.uk.
