01
Who we are
This site and the work described on it are operated by Portmund
Logistics, a software studio. Our legal and registered details
are Portmund Logistics Ltd, a company registered in England and Wales, company number 17201469, registered office 20 Wenlock Road, London N1 7GU.
Written notice under these terms reaches us at
[email protected].
02
What these terms cover
They cover your use of this website and any work we do for you
where there is no separate signed agreement between us. Where a
signed agreement and this page disagree, the signed agreement
wins. Your approved specification sits above both on anything it
describes.
03
Quotes and specifications
We do not price a project from a conversation. Work is quoted
against a written specification listing screens, data,
integrations, assumptions and the things deliberately left out.
A quote holds for the period stated on it.
An engagement starts when you approve that specification in
writing and any deposit named in it has been paid. Until then
nothing is booked and nothing is owed.
04
What we need from you
Builds stall on access far more often than on code. For the dates
in your specification to hold, we need:
- One named person who can make a decision
- Content, data and branding at the point the plan asks for them
- Access to the systems we have to integrate with
- Answers and sign-off within a reasonable time
If a stage waits on you, the remaining dates move by at least the
length of the wait. We will say so in writing when it happens
rather than at handover.
05
Changes to scope
You are allowed to change your mind. Anything outside the
approved specification is a change, and we price it and put it in
writing before we build it, so nothing appears on an invoice you
have not already agreed to. Adjustments that cost us nothing, we
simply make.
06
Fees and invoices
The fee, the payment schedule and anything billed separately are
set out in your specification. Invoices are payable by the date
printed on them. Quoted fees exclude any sales tax that applies,
which is shown separately.
If an account falls overdue we may pause work, and we will tell
you before we do it rather than after. Refunds are covered by our
refund policy.
07
Ownership of what we build
Once a piece of work is paid for in full, the custom code, design
and content we produced for it are yours outright. Accounts,
repositories, domains and hosting are set up in your name from
the start, so nothing has to be handed back later.
We keep ownership of the general tools, libraries and internal
components we bring with us and reuse across clients. You get a
permanent licence to use those as part of the delivered work, at
no extra cost. We do not claim anything you already owned.
08
Third party services
Most builds depend on services nobody in this contract controls:
app stores, payment providers, mapping, email delivery, hosting.
Their terms, fees, review decisions and outages are theirs. We
name the ones your project relies on before you approve it, and
we are not liable when one of them changes its rules.
09
Confidentiality and data
What you tell us about your business stays between us. We do not
name you as a client or show your work publicly without asking
first. This survives the end of an engagement.
Where we handle personal data belonging to your customers or
staff, we act on your instructions and only for the project.
How we treat personal data generally is set out in our
privacy policy.
10
Defects and support
If delivered work does not do what the specification says it
does, we fix it and you pay nothing. The length of the
post-launch window for that is stated in your specification.
The window covers defects. It does not cover new features,
changes forced by a third party service, or problems caused by
someone else editing the system after handover. Those are ordinary
chargeable work, and we will quote them.
11
Liability
Nothing here limits our liability for death or personal injury
caused by negligence, for fraud, or for anything else that cannot
lawfully be limited.
Beyond that, we are not liable for indirect or consequential
loss, lost profit, lost revenue or lost anticipated savings, and
our total liability for an engagement is limited to the fees you
have paid us for it. You are responsible for keeping your own
backups of live data once a system is in your hands.
12
Ending an engagement
Either of us can end an engagement in writing. You pay for work
completed and for work already committed at the point you tell
us. We hand over what exists: source, accounts, credentials and
whatever documentation has been written.
We do not hold a project hostage over a dispute. Accounts being
in your name from day one is what makes that promise real rather
than a sentence on a page.
13
Law and jurisdiction
These terms, and any dispute arising out of them, are governed by
the law of England and Wales, and the courts of England and Wales.
Before starting a formal dispute, both of us agree to raise the
problem in writing and give the other a fair chance to fix it.
14
Changes to these terms
We update this page when the way we work changes. The date at the
top is the version in force. The terms that apply to your project
are the ones published when you approved your specification, so a
later edit cannot move the goalposts on work already agreed.