These terms and conditions govern paid and payable professional services supplied by STARLIGHT PORTER LTD in connection with AI software development and related fractions. They are designed for organisational clients in the United Kingdom and for work performed under the law of England and Wales.
1. Parties, status and interpretation
STARLIGHT PORTER LTD (“we”, “us”, “the yard”) of 911 Green Lanes, London, United Kingdom, N21 2QP supplies professional AI software development and related fractions to the contracting organisation (“client”) identified on a statement of work, purchase order that we have accepted, or other written instrument. These terms and conditions apply to all such supplies. A consumer who is not acting in the course of business should not rely on these terms for a consumer contract; the public site is aimed at organisational clients. Headings are for navigation. “Including” means including without limitation. “Software” includes source, object, scripts, models, weights we are permitted to deliver, prompts, configuration, and documentation. “Load” means the scoped work. “Waste” means material screened out as out of scope. “Grade” means a written assessment of fitness against agreed tests. “Dispatch” means handover of the agreed artefacts. References to statutes include successor legislation. If these terms conflict with a statement of work, the statement of work prevails for that conflict only. If they conflict with the website terms of service, these terms prevail for paid work. Notices to us must be sent to tech@starlightporter.wiki and also to 911 Green Lanes, London, United Kingdom, N21 2QP if a formal contractual notice. Notices to the client go to the addresses on the statement of work.
Nothing in these terms creates a partnership, joint venture or employment. Subcontracting is permitted provided we remain responsible to the client for the subcontracted fraction and provided confidential material is protected. Assignment by the client without consent is void, except to an affiliate on written notice or to a purchaser of the relevant business. We may assign to an affiliate or to a purchaser of our business. Third parties have no rights under the Contracts (Rights of Third Parties) Act 1999 to enforce these terms, except that our affiliates and licensors may enforce intellectual property and confidentiality clauses. A variation must be in writing and designated as such. Email can satisfy writing. Clicking a website button does not vary a live statement of work.
2. Formation of contract
A quotation is an invitation to treat, not an offer, and expires on the date stated or after thirty days if silent. A contract is formed when we issue a written acceptance of a statement of work, or when we begin work after a clear written instruction that references these terms, whichever occurs first. Purchase order terms printed on a client form do not apply unless we sign them. Pre-printed limitation of client responsibility for data legality is rejected if it would require us to process data we reasonably believe is unlawful. The client warrants that the signatory has authority. If work begins while a statement of work is still being negotiated, time-and-materials rates in our latest written rate card apply until the statement of work is signed, and either party may stop that preliminary belt on written notice without liability except for payment of work already performed and non-cancellable costs.
The client acknowledges that AI systems are statistical. Formation of contract is not a promise of a particular scientific result on future unseen data. It is a promise to apply a professional screening method and to deliver the artefacts described.
3. Client obligations and delays
The client shall provide timely access to systems, people, data, brand assets, environments, and decisions. The client shall nominate a single intake owner who can bind the client on scope questions within two working days. If the owner is silent, we may treat the last written client position as the grade, or we may pause the belt. The client shall ensure that third-party suppliers cooperate. The client shall obtain licences for software we are instructed to integrate with. The client shall not schedule go-live marketing that assumes a date we have not accepted as a contractual milestone. Delays caused by the client move milestones by at least the duration of the delay plus a reasonable remobilisation period. Standing idle with a full team reserved may be charged if we warned that the bench would remain allocated. The client shall maintain backups of its own estates. The client shall not introduce production personal data into a shared evaluation notebook. The client shall complete UAT within the window in the statement of work; silence after two reminders five working days apart may be treated as deemed acceptance of that milestone except for defects later found that could not reasonably have been seen.
The client shall comply with export controls, sanctions, and anti-bribery laws. The client shall not require us to build a system whose primary purpose is unlawful surveillance, unlawful discrimination, or the evasion of United Kingdom regulatory duties. We may terminate for a material breach of this clause.
4. Our obligations and professional standard
We shall perform with reasonable care and skill expected of a competent United Kingdom AI software development practice. We shall keep the client informed of material risks discovered during crush and screen. We shall not guarantee the conduct of Apple, Google, cloud vendors, model providers, or regulators. We shall assign personnel we consider suitable; named individuals are not guaranteed unless the statement of work says so and even then substitution is allowed for illness, departure or skill mismatch with notice. We shall use the environments agreed. We shall not insert undisclosed cryptocurrency mining, advertising SDKs, or data exfiltration. We shall return or delete client data according to the privacy and termination clauses. We shall not publicise the client’s name without permission, except that we may list a generic industry and a load reference in an anonymised yard description.
Where we reasonably believe a requested feature would be unsafe, unlawful, or professionally indefensible, we shall say so in a grade note. If the client insists, we may decline that fraction without being in breach, and the remaining load continues if separable.
5. Change control
A change is any alteration to scope, tests, environments, volumes, languages, platforms, model providers, security grade, or timetable. The client shall raise a change ticket. We shall respond with impact on cost and time. Work on the change does not begin until written approval, except emergency security patches which we may apply and then document. Using a different foundation model because a provider withdrew an API is a change. Discovering that labels do not exist is a change. A verbal request in a workshop is not approval. Email from the nominated owner is approval if it clearly accepts the impact note. Repeated micro-changes may be batched weekly. If the client rejects a necessary change caused by a hidden constraint in client material, we may terminate the affected fraction and invoice for work done and proven wasted materials such as reserved GPU spend that cannot be cancelled.
6. Charges, expenses and taxes
Fees are as in the statement of work: fixed, capped time-and-materials, or retainer. Rates are in pounds sterling exclusive of VAT. VAT is added where applicable. Expenses for travel outside Greater London, specialised labelling houses, and cloud spend above an agreed cap are recharged at cost plus any handling fee stated. Invoices are due within fourteen days unless otherwise stated. Late sums bear interest at 8% above the Bank of England base rate under the Late Payment of Commercial Debts (Interest) Act 1998 if that Act applies, otherwise at 4% above base, plus reasonable recovery costs. We may suspend work for non-payment after notice. Disputed invoices must be challenged in writing within ten days with particulars; undisputed amounts remain payable. Set-off against our invoices is excluded except for amounts finally awarded by a court or agreed. Quotes that assume a volume of tokens, images or records are estimates; overrun caused by client-generated traffic is chargeable. Currency conversion for any foreign cost is at a commercially reasonable rate on the date incurred. The client shall provide a valid purchase order number if its accounts payable process requires one; failure to issue a PO is not a reason to withhold payment for accepted work.
If a fixed price was based on assumptions listed in the statement of work and an assumption fails, we may convert the remainder to time-and-materials or re-price. Withholding tax, if any, is the client’s matter except where the law makes us account for it; the client shall gross up if a deduction would leave us with less than the agreed fee.
7. Intellectual property
Each party retains pre-existing intellectual property. Tools, methods, yard codes, screening checklists, internal accelerators, and generic components we developed independently remain ours. Upon full payment, we assign to the client the intellectual property in deliverables created uniquely for the client under the statement of work, excluding pre-existing materials, excluding third-party components, and excluding model weights we are not legally able to assign. We grant a non-exclusive licence to use our pre-existing materials as embedded in the deliverables for the client’s internal business, including hosting by the client’s processors. The client shall not extract our accelerators to build a competing AI software development practice. Feedback the client gives about our method may be used by us freely. Third-party licences, including open source, are supplied in a notice file; the client must comply. Training data supplied by the client remains the client’s (or its licensors’). Models trained solely on client data are assigned as deliverables upon payment unless the statement of work uses a third-party training service whose terms retain weights. Outputs of a generative system are licensed as the deliverables clause allows; we do not warrant that a generated artefact is free of third-party claims. The client indemnifies us against claims arising from material it supplied. We indemnify the client against claims that our uniquely authored code, as delivered, infringes a third-party copyright, provided the client gives prompt notice, control of defence, and does not settle without consent; this indemnity does not cover combinations, client modifications, generated content, or infringement caused by following client designs. If infringement is likely, we may procure a licence, modify, or refund the relevant fraction less a reasonable use deduction, and that is the exclusive remedy for intellectual property infringement against us.
Moral rights are waived to the extent permitted. The client shall not remove copyright notices. Until payment, we grant only a limited evaluation licence. If the client uses deliverables in production before payment, such use is still subject to these terms and fees remain due.
8. Confidentiality
Each party shall keep confidential the other’s non-public information, including data samples, prompts, unpublished product plans, and pricing, and shall use it only to perform the contract. Exceptions: information that is public other than by breach, independently developed, already known, or required to be disclosed by law or a listing authority, in which case the disclosing party is notified if lawful. Confidentiality lasts for five years from disclosure, and indefinitely for trade secrets as long as they remain secret. Source code of undelivered accelerators is a trade secret. We may disclose to personnel and subcontractors under equivalent duties. Return or deletion is required on request after the engagement except for one copy kept for dispute or legal retention, isolated from product use. Public case studies require consent. A load reference number is not confidential. Injunctive relief is available because damages may be inadequate.
9. Data protection allocation
Each party shall comply with UK GDPR and the Data Protection Act 2018. For personal data in client materials, the client is controller and we are processor except where we determine purposes for our own staff administration or website. Processor terms: we process only on documented instructions, ensure confidentiality of persons who process, implement appropriate technical and organisational measures, not appoint subprocessors without a general or specific authorisation (general authorisation is given for hosting, email, standard cloud, and named specialists in the statement of work, with notice of material changes), assist with data subject requests at the client’s cost if volume is unreasonable, assist with security and DPIAs at professional rates if the assistance is substantial, delete or return on end of services, and make available information reasonably necessary to demonstrate compliance. International transfers follow UK approved mechanisms. The client warrants that instructions are lawful and that notices and bases exist. Security incidents are notified without undue delay after we confirm a personal data breach affecting client data. The client shall not instruct us to process in a way that ignores data minimisation. This clause is the Article 28 contract.
10. Security and information handling
We implement access control, encryption in transit for remote connections, segregated project spaces, and logging appropriate to the grade of data. The client shall not lower the security of a shared environment. Penetration tests against our core estate require written scheduling. The client may test systems we built in client environments. Credentials must be rotated on dispatch. We are not responsible for the client’s identity provider misconfiguration. If the client requires a named certification such as ISO 27001, that is a special term; we do not warrant that every subcontractor holds the same certificate. Vulnerability disclosure should be sent to the published technical email, not advertised exploit-style on public forums before we have a chance to patch. Payment card data must not be stored in systems we build unless a PCI scope is expressly priced.
11. Warranties and disclaimers specific to statistical systems
We warrant that for ninety days after dispatch of a fraction, that fraction will materially conform to the written acceptance tests when used as documented on supported environments. The remedy is repair, re-performance, or a refund of the non-conforming fraction, at our choice. This warranty does not cover client changes, third-party API changes, data drift, novel attack prompts, hardware failure, or use outside the documented envelope. We do not warrant uninterrupted or error-free operation. We do not warrant that a model will remain calibrated. We do not warrant non-infringement of patents unknown to us. Implied warranties of merchantability and fitness are excluded to the extent permitted. The client warrants the accuracy of information it supplies and that it has all rights needed. Both parties warrant they are not barred by sanctions from the transaction. Advice given in workshops is professional opinion, not a regulated legal, medical, credit or investment service. If a system we build produces content, the client must apply its own editorial or professional review before relying on it in a regulated act.
12. Liability
Nothing excludes liability for death or personal injury caused by negligence, fraud, or other non-excludable liability. Subject to that, we are not liable for loss of profit, revenue, anticipated savings, goodwill, data (except cost of reasonable reconstitution of data we corrupted by negligence, capped as below), or indirect or consequential loss. Our aggregate liability arising from a contract, whether in contract, tort or otherwise, is limited to the fees paid for the affected statement of work in the twelve months before the claim, or twenty-five thousand pounds, whichever is greater. The client’s exclusive remedies are as stated. The client shall mitigate. Claims must be notified with particulars within three months of the client becoming aware, and legal proceedings commenced within twelve months of the cause of action, except for non-excludable claims. This allocation reflects the fees, the statistical nature of the work, and the client’s control of data and operations after dispatch. The client shall take out insurance appropriate to its use of AI systems, including where it deploys them against consumers. We maintain professional insurance at a level we consider suitable for a practice of our size; a certificate may be provided on request, not as an increase of the cap.
13. Indemnities from the client
The client shall indemnify us against claims, damages, fines and reasonable legal costs arising from: client data and content; client instructions that we followed; the client’s use of outputs; the client’s breach of law including data protection, consumer, equality, and surveillance law; store listing statements the client approved; and third-party claims that training material the client supplied was stolen or unlicensed. We shall notify the client of claims and may participate in defence at our cost. This indemnity survives termination.
14. Term, suspension and termination
Each statement of work runs until dispatch of its fractions or earlier termination. Either party may terminate a statement of work for material breach not remedied within fourteen days of notice, or immediately if the breach is irremediable. Either party may terminate if the other becomes insolvent, enters administration, or ceases business. We may suspend for non-payment, security risk, unlawful instructions, or sanctions issues. On termination the client pays for work performed, committed non-cancellable costs, and licence fees due. Licences for unpaid work end. We shall deliver work-in-progress upon payment. Survival: intellectual property, confidentiality, data protection, liability, indemnities, governing law, and accrued payment. We may retain a copy of artefacts as required by law or for defending claims. Convenience termination by the client, if allowed in a statement of work, requires payment of a wind-down fee equal to the lesser of remaining authorised fees or six weeks of planned team cost, plus work done.
15. Non-solicitation
During the engagement and for six months after, neither party shall solicit the other’s employees who worked on the load, except through general advertising not targeted at them. A breach is compensated by a fee equal to six months’ gross pay of the person, as a genuine pre-estimate of replacement cost. This does not restrict hiring after an unsolicited application.
16. Force majeure
A party is not liable for delay caused by events beyond reasonable control, including cloud region failure, foundation model provider shutdown, epidemic, strike (excluding the party’s own workforce for more than fourteen days), act of government, or failure of a unique supplier that cannot reasonably be replaced. The affected party shall notify and mitigate. If the event continues for more than sixty days, either party may terminate the affected fraction without liability except for payment of work done.
17. Publicity, references and portfolio
We may describe the work in anonymised yard language using load references. Named publicity requires consent. The client shall not issue a press statement that attributes a scientific breakthrough to us without our review. Screenshots that reveal third-party personal data shall not be published by either party.
18. Export, sanctions and acceptable use of outputs
The client shall not export deliverables in breach of the United Kingdom, United States or EU export rules that apply to encryption or to AI items as those rules evolve. The client shall not use the systems to design weapons in breach of law, to exploit children, or to deploy unauthorised biometric identification in public spaces contrary to United Kingdom law. We may refuse support if we reasonably believe such use is occurring.
19. Employees, contractors and IR35
Personnel we supply are not client employees. The client shall not supervise them as employees. If legislation treats a contractor as employed by the client, the client shall not claim against us for that characterisation if it arose from the client’s working practices. We operate PAYE for our employees. Day rates do not include client-side benefits.
20. Acceptance procedure
We present a weigh note when a fraction is ready. The client has ten working days to accept or to reject with reproducible evidence against the tests. Minor defects do not justify rejection of the whole load; they go on a punch list with a repair timetable. Cosmetic issues outside the tests are changes. If the client puts the software into live operational use other than an agreed pilot, it is accepted. Deemed acceptance also occurs if the client withholds comments after the period. Rejection must not be used to renegotiate price. After acceptance, the warranty process applies rather than a reopening of scope.
21. Service levels for managed lanes
Unless a managed service schedule is attached, there is no uptime commitment after dispatch. If a managed lane is purchased, the schedule states hours (typically 09:00–18:00 UK time Monday to Friday excluding English public holidays), response targets for P1 to P3 incidents, and exclusions for client-side causes. Service credits, if any, are the exclusive remedy for missed targets and are capped at a percentage of the monthly managed fee. Credits are not damages. Monitoring tools may be required; if the client refuses them, targets lapse. Emergency out-of-hours work is billable unless the schedule includes it.
22. Open source and third-party models
Deliverables may include open source. Copyleft components will not be introduced into proprietary client code in a way that would require the client to publish its own source, unless the client approves that licence grade. Model provider terms are between the client and the provider if the client holds the account; if we hold the account as reseller, we flow down acceptable use. Token spend is the client’s if the client’s keys are used. We are not liable for a provider changing a system prompt, withdrawing a model, or adding watermarking. The client shall read those terms. Benchmarketing that violates a provider’s terms is forbidden.
23. Trials, proofs and unpaid screening
A short unpaid screening conversation does not transfer intellectual property in our questions or method. A paid discovery fraction produces a grade note that the client may use internally. Prototypes are not production. Data used in a trial remains subject to confidentiality and deletion. If a trial uses a public model, the client should assume prompts might be logged by the provider unless an enterprise endpoint is used.
24. Recruitment and additional roles
If the client asks us to introduce candidates beyond delivery of software, that is a separate recruitment service not covered by these development terms. Introducing a person who is later hired through other channels within six months may still trigger a fee if a recruitment schedule exists. Absent such a schedule, we have no duty to staff the client’s internal data science team.
25. Dispute resolution
The parties shall attempt good faith negotiation for fourteen days, then mediation in London under CEDR rules if both agree. Either party may still seek interim relief. Subject to that, the courts of England and Wales have exclusive jurisdiction. The governing law is the law of England and Wales. The United Nations Convention on Contracts for the International Sale of Goods is excluded. Each party submits to that jurisdiction. A party that unsuccessfully litigates a claim excluded by the liability clause may be required to pay costs on the standard basis.
26. Entire agreement and order of documents
The contract comprises the statement of work, these terms and conditions, processor details, and any security schedule. It supersedes prior negotiations. Misrepresentation claims are limited to fraudulent misrepresentation. Pre-contract presentations on the website, including metaphors of sorting yards, are illustrative of method, not additional warranties. Order of precedence: statement of work, these terms, website terms of service, privacy policy (for processing explanations). A purchase order is an administrative document only.
27. Notices, counterparts and electronic signatures
Notices are effective when received if sent by email with a copy by post for termination, infringement or payment default. Electronic signatures and counterparts are valid. The person clicking or signing warrants authority. Time is not of the essence except for payment and for dates expressly labelled as such in a statement of work.
28. Severance, waiver and rights cumulative
An unenforceable clause is modified to the minimum extent to make it enforceable. Waiver must be express. Rights are cumulative. These terms bind successors. They may be executed after work starts and still govern from the first day of performance. The client shall not register a domain, company name or social account that impersonates the yard. Our failure to issue a ticket number does not waive a fee.
29. Contact and version
STARLIGHT PORTER LTD, 911 Green Lanes, London, United Kingdom, N21 2QP, +44 7411 527869, tech@starlightporter.wiki, https://starlightporter.wiki. These terms and conditions were last updated on 18 August 2026. Continued instructions after that date on a new statement of work adopt this version unless a locked earlier version is attached. For site-only use, see the terms of service. For cookies, see the cookie policy. For personal data, see the privacy policy. For commercial intake, use contact.html.
Service fraction schedules
The following schedules apply when the named fraction appears in a statement of work. They add to, and do not replace, the general clauses. If a schedule and a general clause conflict on a technical matter unique to that fraction, the schedule prevails for that matter.
AI software development
AI software development under these terms means the design, construction, testing and handover of software systems that incorporate statistical or rule-based inference as a material component of a business process. It includes architecture notes, source artefacts agreed in the statement of work, build pipelines described in the handover, and operator guidance sufficient for a competent client team to run the first production lane. It does not include unlimited future invention, unrestricted staff substitution, or ownership of third-party model weights that remain licensed by their providers. The client must identify a product owner who can accept or reject a grade at each weigh point. Absence of an owner is a client delay, not a yard defect. Acceptance tests are written in operational language: a job that can be completed, a record that can be retrieved, an exception that can be seen. Aesthetic preference about a colour on a screen is not an acceptance test unless the statement of work priced a visual design fraction. If the client changes the job after crush, the change control clause applies. Security of the client’s wider estate remains the client’s duty except for components we operate under a documented managed service. Open source components are used under their licences; the client receives those licences with the handover and must not assume that copyleft obligations can be ignored because the yard assembled the belt. Documentation is delivered in English. Training workshops are not included unless listed as a fraction with a date and a headcount. Warranty for this fraction is limited to material non-conformance with the written acceptance tests for the warranty period in the general clauses. Performance of a model against live drift after handover is a monitoring topic, not an implied forever-accuracy promise.
Machine learning software solutions
Machine learning software solutions means supervised, unsupervised or reinforcement approaches selected after a screening of the available labelled and unlabelled material. The client warrants that it has lawful rights to provide training, validation and test data, including rights in personal data and in third-party licensed content. The yard does not warrant that a published research accuracy will appear on the client’s data. Evaluation metrics are agreed in the statement of work and are measured on a held-out set constructed without leakage. Leakage discovered after crush may require the load to be re-graded at additional cost. Feature stores, label taxonomies and annotation guides are deliverables only if listed. The client must not withhold known data quality defects. If labels are noisy, the grade will say so. Production serving, retraining cadence and drift alerts are included only to the extent written. A model file without a serving contract is not a complete fraction. The yard may refuse to deploy a model that cannot be monitored. Intellectual property in a model trained solely on client data is allocated in the intellectual property clause; third-party pretrained weights remain with their owners. The client shall not require the yard to strip copyright management information from training corpora. Export of model artefacts to a prohibited jurisdiction is forbidden. Human review remains the client’s responsibility for decisions with legal or similarly significant effects unless a managed human-in-the-loop service is purchased.
Intelligent mobile applications
Intelligent mobile applications means software for supported iOS and Android versions listed in the statement of work, possibly including on-device inference or a call to a graded backend. Store listing copy, privacy nutrition labels and permission justifications are prepared from facts the client supplies. The yard is not the data controller of end users unless a managed consumer product is expressly in scope. The client is responsible for developer account enrolment, store fees, signing keys unless escrowed, and responding to store review questions that only the client can answer. Offline behaviour, camera use, location and push notifications are off unless specified. Accessibility is designed to a standard named in the statement of work; if none is named, a reasonable professional effort against WCAG 2.2 AA for newly built screens is the default for public-facing client apps, subject to platform limits. Performance on obsolete devices is excluded. The yard does not promise that Apple or Google will approve a listing. Rejection by a store is a change event if it requires redesign beyond the original grade. Maintenance after handover is a separate retainer. Sideloading enterprise builds follows the client’s mobile device management rules. The client must not insert tracking SDKs that conflict with the privacy design without a written variation.
Generative AI app development
Generative AI app development means interfaces and orchestration that produce text, images, code suggestions or similar artefacts using a model. Outputs can be wrong, biased, stale or similar to existing work. The client shall not represent generated content as verified professional advice unless a separate verification fraction is in scope. Retrieval grounding, citation display, logging, rate limits, and refusal behaviour are included only as specified. The client is responsible for acceptable use toward its own users and for not feeding unlawful prompts. Provider outages, policy changes and price changes of model APIs are passed through as they occur; the yard is not an insurer of a foundation model vendor. The client must not use the service to attempt to extract model weights or to train a competing foundation model on outputs in breach of a provider’s terms. Secret prompts and evaluation sets we create remain our confidential methods unless assigned. The client owns its prompts and its business content. Hallucination is a known property of the material, not a unique defect of this yard. Safety evaluation is scoped as a red-team fraction if purchased; it is not an implied unlimited guarantee that no user can elicit a bad answer.
AI automation software
AI automation software means the connection of systems so that a repeated job moves without unnecessary human copy-paste, with exceptions remaining visible. The client must provide interface credentials, sandbox environments and a map of systems of record. The yard is not liable for the client’s choice to automate a process that is legally required to stay manual. Kill switches and audit logs are designed where the statement of work requires them. RPA-style fragile interface scraping is avoided unless the client accepts the maintenance grade in writing. Changes to a third-party user interface after handover that break an automation are a new load. The client remains responsible for authorisations inside each connected system. The yard will not store standing administrative passwords in shared chat histories. Volume assumptions in the statement of work cap the expected transactions; exceeding them is a scaling change. Automation that sends communications to data subjects must respect the client’s privacy notices and PECR where applicable.
Computer vision application
A computer vision application means software that assigns labels, detections or quality grades to images or selected video frames. The client warrants that it can lawfully capture and provide the images, including notices in workplaces and public spaces as required. Biometric identification of natural persons is out of scope unless a dedicated legal pack is signed. Camera hardware, lighting and lens choice affect the grade; the yard does not supply quarry or factory cameras unless listed. Sample diversity is the client’s duty. If the production distribution shifts, accuracy can fall; monitoring is required. False positive and false negative costs must be stated so thresholds can be set. The yard may refuse a load that is effectively covert surveillance. Human appeal for adverse outcomes is the client’s process unless we are hired to build that chute. Model cards and limitation statements are delivered as part of handover for this fraction.
Natural language processing app
A natural language processing app means classification, routing, extraction or search over text. Languages in scope are listed; unspecified languages are excluded. Dialect, sarcasm and mixed code reduce accuracy. The client must not require the system to be the sole arbiter of employment, credit or criminal matters. Evaluation sets must reflect real tickets, not only tidy demonstrations. PII redaction, if required, is a specified sub-fraction of intelligent data processing. The yard does not warrant that extraction will be complete on handwritten scans unless a vision plus NLP combined load is priced. Toxicity filters, if any, are heuristic. The client is responsible for downstream actions taken by staff who read the graded output.
Recommendation engine development
Recommendation engine development means ranking or suggesting items, actions or content. The client must disclose known fairness constraints, catalogue poisoning risks, and whether the engine may create filter bubbles that the client finds unacceptable. Popularity bias is a property of many datasets. Offline metrics are not a promise of lift in revenue. Online experiments, if any, need a traffic allocation the client controls. The client shall not require secret manipulation of rankings that would breach consumer protection or advertising rules in the United Kingdom. Explanations, if required by regulation or by the statement of work, are a specified output. Cold start behaviour is designed, not left as silence. Personal data used for ranking is processed under the privacy allocation in the contract.
Deep learning solutions
Deep learning solutions means neural methods selected when a simpler model failed the weigh or when the material is inherently high dimensional. Compute costs are estimated, not guaranteed; cloud invoices can move. The client provides or funds compute unless the statement of work includes a capped cloud budget. The yard may stop a training run that is wasting budget relative to the grade. Notebooks are not production. Reproducibility is targeted through recorded seeds, data versions and environment files to a reasonable scientific standard, not an academic forever-bit-identical promise on all GPUs. The client must not insist on a fashionable architecture that cannot be served under the operational constraints. Transfer learning uses third-party weights under licence. The yard is not liable for hidden training-data contamination inside a third-party base model.
Intelligent data processing
Intelligent data processing means ingestion, validation, matching, transformation and delivery of data so later fractions can run. The client remains controller of source systems unless otherwise written. Survivorship rules must be approved by the client; silent merge of legally distinct persons is forbidden. Lineage documentation is delivered to the depth specified. The yard does not become the client’s data protection officer by performing cleansing. Backups, disaster recovery and long-term archive of the client’s estate are out of scope unless purchased. Quality metrics are defined in the statement of work. Discovering that a source system cannot emit a field is a material fact that can pause the belt. The client shall not provide stolen databases. If we reasonably suspect unlawful data, we may suspend and notify as required by law.
30. Environments, access and client laboratories
Development, staging and production are distinct grades of environment. The client shall provide staging that resembles production in data shape, not necessarily in volume. Production access is limited to named people and time-boxed. We shall not use production as a scratch pad. If the client insists that we train on production personal data, a DPIA and a written exception are required. VPNs, SSO and hardware keys required by the client will be used if provided promptly; delay in issuing access is client delay. The client shall maintain a register of accounts issued to us and revoke them at dispatch. Shared passwords in documents are forbidden. Where the client’s laboratory network blocks package registries, the client shall provide an allow-list or an internal mirror, otherwise timelines move. Container images we supply will target a runtime listed in the statement of work. We are not required to support every orchestrator. Infrastructure as code is included only if listed. Cost of the client’s cloud account remains the client’s even if we typed the template. The client shall not demand that we disable logging in production to hide operator behaviour. If an environment is contaminated with malware, we may isolate our tools until the client certifies cleanliness.
Data in staging should be anonymised or synthetic where possible. If realistic data is essential, it should be a minimised extract. We may refuse to copy a full production dump onto a laptop. Remote desktops provided by the client must allow us to perform the work; a view-only terminal is not access. Time spent waiting on jump-host queues is billable if a reserved team is on the clock.
31. Testing doctrine
Unit tests, integration tests, evaluation sets for models, and user acceptance tests are different chutes. Coverage percentages in the statement of work are targets, not a scientific law. Flaky tests will be quarantined rather than allowed to block every dispatch. Load testing of a recommendation engine or a generative endpoint requires a volume profile from the client. We do not perform unrestricted destructive testing on production. Accessibility testing uses automated aids plus a sample of manual checks; it is not a full audit by a specialist charity unless purchased. Security testing by us is basic unless a penetration test fraction is in the statement of work. The client’s third-party tester must share a rules-of-engagement document. Test data creation is a labour fraction; the client often underestimates it. If the client’s users never attend UAT workshops, deemed acceptance mechanics apply. Visual regression is included only for agreed templates. We are not a device farm; a matrix of devices is listed or it is excluded. Model evaluation will report confidence intervals or error bars where sample size allows; a single accuracy number without context is not our preferred grade.
32. Documentation and knowledge transfer
Handover includes a system overview, how to run the tests we delivered, environment variables, and known limitations. It does not include a textbook on machine learning. Recorded walkthroughs, if purchased, are for internal client use, not for resale as a course. We may withhold internal wiki pages that describe our yard method. The client may internally copy handover documents. Translation into languages other than English is a change. If staff who received the transfer leave the client, a refresh workshop is a new fraction. We are not required to remain on chat channels forever after dispatch. A reasonable number of clarification questions by email during the warranty period is included; a new design conversation is not.
33. Accessibility, equality and public sector addenda
If the client is a public authority, additional transparency, FOIA assistance, and accessibility duties may apply. FOIA assistance is chargeable if substantial. We do not automatically accept Crown terms. Equality impact in an AI system is a shared design problem; the client must state protected characteristics risks it already knows. We do not warrant that a model is free of bias. We will document known evaluation gaps. Procurement frameworks, if any, apply only if we have signed them. TUPE is not expected to apply to a software development statement of work; if a later managed service is alleged to transfer staff, the parties shall discuss before the service starts. Transparency reports about model use, if required by a regulator, are the client’s publication unless we are hired to draft them.
34. Insurance, audit and ethical walls
We maintain public liability and professional indemnity insurance at levels we consider appropriate. The client may request a certificate. Policy terms govern. The client’s auditors may inspect artefacts of their project under confidentiality, not our entire company accounts, and not other clients’ files. Ethical walls between competing clients are implemented through access control, not through marketing promises. We may decline a new load that would create an unmanageable conflict. Prior work in the same industry is not itself a conflict. Independent development of similar generic components for two clients is permitted if client confidential material is not reused.
35. Subprocessors and specialists
Labelling companies, niche algorithm consultants, and cloud regions may be used. We remain responsible to the client for their performance as if they were us, except that a named foundation model provider is a third-party utility whose SLA is not ours. The client may reject a specialist on reasonable confidentiality grounds before they see the data. Once they have seen the data, switching mid-stream is a change. Flow-down of confidentiality is mandatory. Flow-down of unlimited liability is not; specialists are engaged on terms we can actually obtain in the market.
36. Records, tax and Companies Act matters
We keep accounting records as required by United Kingdom law. The client shall not require us to backdate invoices in a misleading way. If the client needs a particular narrative on an invoice for its internal cost centres, it must say so before the invoice date. We are a limited company. Our directors’ duties are to the company. Nothing in a statement of work makes a director personally liable except as English law already provides for fraud or wrongful trading. The website company name STARLIGHT PORTER LTD is the contracting brand for these terms. VAT registration, if required, will appear on invoices. Reverse charge, if applicable to a non-UK client, will be handled according to HMRC rules then in force; the client shall provide its VAT number.
37. Consumer-facing deployments and PECR
If software we build sends electronic marketing, uses cookies in a consumer app, or makes automated calls, the client is responsible for PECR compliance, consent ledgers, and suppression lists. We can implement technical controls that the client specifies. We are not the client’s marketing legal team. Dark patterns that obtain false consent are not a requested feature we will proudly grade. Cookie banners in a mobile WebView are designed only if listed. Push notification frequency caps are a product choice of the client.
38. Incident response for delivered systems
After dispatch, the client operates the system unless a managed schedule exists. The client shall notify us of suspected defects with logs. We shall respond during the warranty according to severity: a complete outage of a system we still have access to is treated ahead of a cosmetic issue. If we no longer have access, the client must restore access before the clock starts. A security incident in the client estate may require the client to notify the ICO; we assist with facts about our components. We do not speak to the press as the client’s spokesperson. Preservation of logs is the client’s duty in its environments. Forensic imaging, if required, is a specialist fraction.
39. Benchmarks, competitions and publicity of scores
The client shall not publish a benchmark that identifies us without context about the dataset, the date, and the hardware. We may require a disclaimer. Kaggle-style competitions using client data are a change if they expose confidential material. Academic publication of a method we invented requires agreement on authorship and on what remains trade secret. The sorting-yard metaphor on the website is branding, not a scientific claim that we operate heavy plant.
40. Escrow and continuity
Source escrow with an independent agent is available as a priced option. Absent escrow, the client’s protection is the handover of repositories and documentation upon payment. We do not promise to retain staff indefinitely. If we cease trading, ordinary insolvency law applies; the client is an unsecured creditor for unused prepaid fees except where the law grants better treatment. Prepaid managed fees for unused months after a lawful termination for our breach are refundable pro rata. For client breach, prepaid fees may be applied to damages.
41. Accessibility of these commercial terms
These terms are long because the work is technical and the United Kingdom legal environment is dense. A short statement of work should still be readable. If a clause here is never triggered, it still forms part of the allocation of risk. Questions before signature should be sent to the published email. We do not provide legal advice to the client. The client should instruct its own solicitors, particularly if it operates in financial services, health, education, policing, or children’s services.
42. Model monitoring, drift and retraining
After dispatch, data distributions move. A computer vision application that met the weigh in winter light may fail in summer glare. A recommendation engine will chase new popularity. A natural language processing app will meet new slang. Monitoring, alerting, and retraining are separate fractions unless included. If the client declines monitoring, the warranty does not cover drift. Thresholds should be reviewed when false positive costs change. We may recommend taking a model offline; the client decides. Automated retraining without evaluation is not our default grade because it can silently worsen the load. Champion-challenger designs are priced. The client shall keep a rollback artefact. Regulatory model risk management frameworks in banks or insurers, if applicable, are the client’s overlay; we map our artefacts to them only if that mapping is scoped.
Feature stores must not silently change definitions. Training-serving skew is a recognised failure mode and will be tested where we control both sides. If the client’s downstream warehouse team changes a column without notice, resulting defects are client-caused. Calendar effects, campaign spikes, and outages in upstream vendors should be listed as known seasonality. We are not liable for a black-swan event that no reasonable evaluation set contained, such as a novel product line that did not exist at crush time.
43. Human oversight, explainability and regulated decisions
United Kingdom equality law, consumer law, and sector rules may require meaningful human review of certain decisions. Building a button labelled “override” is not the same as staffing a review team. The client must resource the review chute. Explanations may be global (how the model generally works) or local (why this item ranked). Local explanations for deep learning solutions can be unstable; we will say so in the grade note. Counterfactual tools are a specific fraction. The client shall not advertise a system as “fully explainable” if the statement of work used a black-box model. For credit, insurance, employment or housing decisions, the client must take specialist legal advice; we will not pretend a generic NLP classifier is a compliant decision engine. Recording of review decisions is the client’s record-keeping duty unless we host that log under processor terms.
44. Dataset provenance, synthetic data and licensed corpora
The client shall disclose if a corpus was scraped, licensed, purchased, or generated. Synthetic data may still encode secrets from the generator. We may refuse a corpus with no provenance. Web scrape material can contain malware and personal data; handling it is a security and privacy event, not a casual download. Licensed data remains subject to its licence; we will not strip watermarks on request. Open data still requires attribution where the licence demands it. The client indemnifies us for provenance failures. If we create synthetic data as a deliverable, the method is ours until assignment on payment, and the synthetic rows are the client’s to use internally. Selling our synthetic generator as a product is not included. Differential privacy, if required, is a specialised fraction with accuracy trade-offs that the client must accept in writing.
45. Prompt libraries, evaluation harnesses and red teaming
Prompt libraries we author as generic accelerators remain ours; client-specific prompts about the client’s policies are assignable deliverables on payment. Evaluation harnesses that encode our method may be licensed, not assigned, if so listed. Red teaming is a bounded exercise with a written rules of engagement. It is not a promise that no future jailbreak exists. Findings are confidential. The client shall not require us to attack third-party systems without authorisation. Safety mitigations can reduce utility; the client chooses the grade. We may refuse to implement a mitigation that is theatre, such as a disclaimer nobody will read, as the sole control for a high-stakes domain. Continuous red teaming as a retainer is optional.
46. Accessibility of mobile and web surfaces we build
New web surfaces intended for public use will target WCAG 2.2 AA unless the statement of work names another standard. Intranets used by trained operators may be graded differently if the client documents the user group. Mobile native components follow platform accessibility APIs. Third-party widgets, including maps and model vendors’ chat windows, may not meet the same standard; we will flag them. Captioning of video is the client’s content duty. An accessibility audit by a specialist organisation is not included. If a disabled employee of the client cannot operate an internal tool, the client should raise it as a defect against the agreed standard during UAT, not six months later as a new theory of liability.
47. Support hours, languages and London time
Correspondence is in English. Business hours are 09:00 to 18:00 UK time on days that are not public holidays in England, unless a managed schedule says otherwise. The yard is in London. Remote work by our personnel does not change the governing law. Meetings outside hours are by agreement and may be billable. We are not a 24-hour network operations centre by default. On-call rotas are a priced fraction. If the client’s users are worldwide, the client must staff its own follow-the-sun support or purchase that pattern. Emergency contact numbers, if issued, are for P1 incidents, not for new feature ideas.
48. Deliverable formats and repositories
Source is delivered through a Git repository the client controls, or through an archive if the client has no repository. We do not use a personal cloud folder as the system of record. Binary models may be too large for Git; object storage is then used. Notebooks are converted to pipelines where production is in scope. Design files remain in the tool named in the statement of work. We are not required to supply editable source for third-party fonts. Container registries and artefact feeds are the client’s unless we host a temporary one. The final dispatch note lists hashes or tags of what was handed over. If the client deletes the repository, that is not our loss of the only copy after dispatch; the client must keep backups.
49. Warranties about malware and supply chain
We take reasonable steps to avoid introducing malware through our build chain, including using maintained dependencies and not installing unknown browser extensions on build agents we control. We do not warrant that the entire upstream open source ecosystem is free of compromise. A supply-chain incident in a widely used library is force majeure as to that library, and we will assist with patching as a change or under warranty if it is a straightforward version bump within the warranty period. The client shall likewise protect credentials. Typosquatting packages in a client-controlled registry are the client’s risk. We shall not commit secrets to Git. If a secret is committed by the client, rotation is the client’s job. Software bills of materials are delivered if listed in the statement of work.
50. Pricing assumptions for tokens, storage and labelling
Generative AI app development fees that exclude token spend will say so. If token spend is included up to a cap, overrun is billed monthly. Caching, batch APIs, and smaller models are used when they still pass the weigh. Labelling is priced per unit or per hour as stated; rework caused by a changed taxonomy is extra. Storage of video for computer vision can dominate cost; retention must be stated. We may delete contractor copies of bulk media after the evaluation set is built. The client should not assume that “AI” reduces cost in the first release; screening often reveals that the expensive part is the data, not the model. Fixed prices assume one primary cloud region. Multi-region active-active is a different grade.
51. Cooperation with regulators and law enforcement
If a competent United Kingdom authority lawfully requires information, we may disclose it. We will notify the client if lawful and practical. We will not destroy evidence. The client shall not instruct us to hide records that must be kept. If a regulator inspects a model, we will provide artefacts we hold, at professional rates if the inspection is not caused by our breach. We do not accept contractual clauses that require us to break the law. Whistleblowing by our staff is protected as UK law provides and is not a breach of confidentiality as against a disclosure to a prescribed person.
52. Ethical use, environmental impact and compute
Large training runs have environmental cost. We will not run unbounded experiments on the client’s budget. The client may request a rough compute estimate; it is not a scientific carbon audit unless purchased. We may recommend a smaller model that meets the tests. The client shall not require us to hide energy use in reports to a parent company. Ethical review boards, if the client has one, should be involved before crush for high-stakes loads. We may decline work whose primary purpose is deceptive manipulation of voters or of children. Ordinary commercial persuasion within advertising law is not automatically declined.
53. Transfer of third-party contracts and cloud accounts
Cloud accounts should be in the client’s name. If we temporarily hold an account, we will transfer it on dispatch and payment. The client shall not refuse the transfer then claim we hold them hostage. Domain names, store listings, and API keys follow the same pattern. Recurring cloud bills after transfer are the client’s. We are not a reseller of cloud credits unless a schedule says so. Unused reserved instances purchased at the client’s request are the client’s asset and liability.
54. Survival of metaphors and marketing language
Website language about hoppers, chutes, weighbridges and fractions describes a method of breaking complexity into usable outputs. It does not make us a minerals business, a construction contractor, or a carrier of physical aggregate. Technical schedules control. A judge should read “screened waste” as out-of-scope work and “graded output” as accepted deliverables. Load references are identifiers. Yellow inspection marks in the design system are branding. Nothing in the brand authorises unsafe workplace practices. The client shall not reprint our brand assets except as allowed for linking to the site.
55. Additional definitions used in statements of work
“P1” means a complete outage of a production function in scope with no workaround. “P2” means a severe degradation with a workaround. “P3” means a minor defect. “UAT” means user acceptance testing by the client. “SOW” means statement of work. “DPIA” means data protection impact assessment. “PECR” means the Privacy and Electronic Communications Regulations. “UK GDPR” has its ordinary meaning after Brexit adaptation. “Working day” means a day other than Saturday, Sunday or an English public holiday. “Greater London” means the administrative area. “Pilot” means a limited production use with a stated user cap and end date. “Champion-challenger” means running two models in parallel for comparison. “Leakage” means information from outside the legitimate feature set contaminating evaluation. “Drift” means a change in data or performance after dispatch. These definitions apply unless a statement of work redefines them for that load only.
56. Entire professional relationship after multiple loads
A master services arrangement may cover several statements of work. Each SOW is a separate load for limitation of liability unless the master says liabilities aggregate. Non-solicitation periods run from the end of the last SOW. Confidentiality continues per disclosure. A dispute on one SOW does not automatically suspend another unless non-payment is concerned and we have given notice. The client’s affiliated companies may be added only by written accession; otherwise an affiliate is a third party. Work done for an affiliate without a contract is still billable to the instructing client at rate card. These terms apply to all future SOWs unless a later version is stated in that SOW.
57. Notices regarding the website legal suite
The privacy policy, cookie policy, terms of service and these terms and conditions are distinct instruments. Website visitors who never buy anything are not bound to pay development fees. Clients who buy are bound to these terms even if they found us through the website. Copies may be printed. In the event of a PDF circulating internally, the version on https://starlightporter.wiki at the date of the SOW controls unless the SOW attaches a frozen copy. Deep links to legal pages are permitted. Scraping legal pages to train a public model that pretends to be STARLIGHT PORTER LTD is forbidden.
58. Construction against a party and negotiation history
These terms are a standard form for an AI software practice. They have been drafted to be used many times. Contra proferentem is not to be applied aggressively against us merely because we wrote the first draft; the client may negotiate a SOW. Handwritten amendments prevail over printed text only if signed by both. Auto-generated emails that quote a different limitation of liability do not amend these terms. A salesperson’s optimism about a metric is not a contractual warranty. The screening method described on about.html is our working practice, not an additional service level.
59. Further assurance and execution
Each party shall execute documents reasonably required to vest assigned intellectual property, including short-form assignments for registrable rights if any arise, which is uncommon for this type of software. Moral rights waivers by our employees are obtained as a matter of employment practice. Contractors we use are bound to assign. If a contractor refuses an assignment, we will replace the artefact or obtain a licence sufficient for the client’s use. The client shall likewise procure assignments from its own contractors who contribute to the load. Failure by the client’s designer to assign UI files is a client problem. Further assurance is at the requesting party’s reasonable cost if the request comes after dispatch and is not caused by a defect in our paperwork.
60. Closing operational note
The parties intend these terms to allocate risk in a way that allows a London AI software development yard to take on mixed, heavy, unclear loads, screen them, and dispatch usable systems without pretending that statistical software is a certified measuring instrument for every future day. Good faith cooperation at the weighbridge is expected. Gamesmanship around acceptance tests is not. Payment for graded work is expected. Silence is not a specification. If the load cannot be graded, we will say so rather than fill a hopper with theatre. That is the commercial bargain.
61. Training of client staff and safety of generated advice
Workshops included in a statement of work train the people who attend, not the entire future workforce of the client. Recordings, if allowed, are for internal refresh, not for resale. Staff who operate a generative AI app development layer must be told that outputs can be wrong. The client shall not present our workshop slides as a regulated qualification. If the client asks us to train hundreds of people, that is a volume change. We may refuse to certify that a named employee is “competent” in a statutory sense; we can only say they attended. Where a system can emit legal, medical or financial sounding text, the client must keep a professional in the chute or must not use the system for that act. We will write that limitation into the grade note. Ignoring it is a client operational choice and not a hidden warranty from the yard.
Train-the-trainer models are only in scope if listed. Translation of training into other languages is extra. Accessibility of training venues is the client’s duty for on-site sessions. Remote sessions require a working conferencing tool the client can operate. We are not liable for a participant who joins without audio and later claims they were not trained. Attendance lists are kept for a reasonable period as delivery evidence.
62. Source code quality, comments and internal style
Code style follows a professional standard we choose unless the statement of work names the client’s guide and the guide is provided before crush. We do not promise a particular comment density. Public website properties we build for ourselves may contain no code comments by design; client projects follow whatever the SOW says. Refactoring of unrelated legacy systems is out of scope. If the client’s review comments are taste rather than defect, they are changes. Pairing hours are billable. Pull request review by the client should happen inside the UAT window. A demand to rewrite a working fraction in a new language after acceptance is a new load. Dependency upgrades after dispatch are maintenance. We will not insert Easter eggs. We will not insert telemetry that phones home to us unless a managed service requires it and it is disclosed.
63. Brand, domain and store assets
The client supplies trade marks, domain control, store accounts, and brand rules. We will not invent a mark that we cannot assign. If the client’s brand rules conflict with accessibility or with platform rules, we will say so and the client chooses. App store screenshots that show personal data must be mocked. The name STARLIGHT PORTER LTD, the yard codes, and the visual universe of the public site remain ours. The client does not obtain a licence to copy this website’s layout for its own marketing merely because we built them a product. A small credit line is not required unless agreed. The client shall not register confusingly similar company names to pass off as the yard.
64. Multiple currency and overseas clients
Fees are in pounds sterling unless the SOW says otherwise. Overseas clients still accept England and Wales law if they sign these terms. Tax representation in another country is the client’s problem. If a local statute cannot be excluded, it applies to the minimum extent. Payment charges on international wires are the sender’s unless agreed. Sanctions screening may delay a start. We may require beneficial ownership information before we crush a load for a new overseas entity. Time zones do not expand support hours. English remains the contract language. A translation is a courtesy and yields to the English text.
65. Closing catalogue of excluded theatres
For the avoidance of doubt, we are not engaged as a construction contractor, miner, cement supplier, machinery dealer, warehouse operator, or safety trainer, even though the public brand uses aggregate metaphors. We are engaged as an AI software development practice. Excluded from a default SOW, unless added in writing, are: hardware procurement, physical installation, 24-hour operations, legal opinions, certified penetration tests, ISO certification of the client, recruitment of a permanent head of data, and unlimited generative content production. The usable fraction is the software and the method described in the SOW. Everything else is waste until it is graded in.
This clause exists because mixed piles often hide those extras. Screening them early is cheaper than litigating them late. If you need those extras, ask, pay, and put them on the ticket. If you do not, do not later claim they were implied by a photograph of a hopper or by the words “heavy clarity”. Heavy clarity is the opposite of implication by atmosphere. It is a weighed list of outputs, a named owner, and a dispatch that can be lifted.
66. Governance meetings and steering
A steering meeting is included only if the statement of work sets a cadence. Status notes can be short weighbridge tickets rather than slide theatres. The client’s internal politics are not billable as a separate product unless the client asks for facilitation and we agree. We may pause a meeting that has no owner in the room. Decisions must be written down. A decision that exists only in a chat thread that later disappears is a client record-keeping failure. We will not attend unlimited committees. If a programme requires a full-time engagement manager, that role is a named fraction.
Minutes we issue are delivery records, not a promise to perform extra items captured as “ideas”. Ideas go through change control. The sorting method on about.html is how we keep steering from becoming a second unsorted pile. If the client wants a different governance ritual, it must be written, priced, and staffed. Silence in a steering slot is not approval of a change, and enthusiasm in a steering slot is not a substitute for the owner’s email on an impact note.
67. Final commercial remainder
These terms and conditions, together with a statement of work, are the commercial belt. They should be long enough that a later dispute does not have to invent missing fractions. They should not be so vague that a photograph of limestone becomes a specification. STARLIGHT PORTER LTD will screen, grade and dispatch AI software development and the related fractions named in the SOW, from 911 Green Lanes, London, United Kingdom, N21 2QP, under the law of England and Wales, with notices to tech@starlightporter.wiki. That is the load. Everything else stays in the waste bin until someone pays to put it on the ticket.
68. Records retention for commercial files
We keep statements of work, invoices, and dispatch notes for the statutory accounting period and for so long as a warranty or dispute may reasonably arise. Source we assigned and handed over is the client’s to keep. Copies we retain for defence are isolated. The client should not assume we are a backup vendor. If the client needs a longer archive of model checkpoints, that storage is a priced fraction. Destruction certificates, if required by the client’s policy, are issued after deletion of live project spaces, not after every backup cycle in a cloud provider’s hidden redundancy layer, because that layer is not under our physical control.
Personal data in commercial files follows the privacy policy and the processor clause. Mixing those regimes is how organisations accidentally keep customer files forever “in case the model is retrained”. That is not our default. Retraining is a new load with a new data ticket. STARLIGHT PORTER LTD of 911 Green Lanes, London, United Kingdom, N21 2QP, reachable at tech@starlightporter.wiki and +44 7411 527869, will not treat a leftover spreadsheet as implied permission to run another deep learning solution. The belt starts when the next SOW says it starts.