Terms and conditions
Status of these terms
These terms and conditions govern use of the website at https://driveritics.study. They apply to a person who reads the pages, follows a link inside the site, or sends the enquiry form. They also apply to an organisation on whose behalf that person acts, to the extent the person had authority to act. They do not apply to a written agreement for actual software work, except that the website cannot be used to contradict a signed agreement by pointing at a general sentence on a public page. If a signed agreement and these terms both touch the same practical question about a piece of paid work, the signed agreement wins for that work. These terms remain the rules for the public site.
The shorter terms of service are a readable summary of the same subject. They are not a second, competing contract. If a summary sentence and a sentence in these terms cannot both be true, these terms prevail. The privacy policy and the cookie policy deal with personal information and with device storage. They are not overridden by a general sentence here. A question about what the form does with a name and an email address is answered in the privacy policy. A question about whether the site sets a cookie is answered in the cookie policy. A question about whether reading a service page creates a duty to build something is answered here.
These terms are published by the company as its website terms. They are not a quotation, a statement of work, a support policy with timings, or a schedule of fees. No fee is stated because no fee has been published. No date is promised because no date has been published. Silence is not a default price of zero, and it is not a default promise to start.
The company, and what is not stated
The company is DRIVERITICS LTD. The published address is Summit House, 4-5 Mitchell Street, Edinburgh, EH6 7BD, United Kingdom. The published email address is network@driveritics.study. The published telephone number is +44 7911 123456. Those are the identity facts the site relies on. The name includes “LTD”, which is the ordinary marker of a limited company in the United Kingdom. The site does not publish the registration number, the registered office as a separate legal formula beyond the address above, the names of directors, the share capital, or a VAT number. You must not invent them in a proposal, a press note, or a form that asks you to “confirm” a number the company has not given. If a process you are running requires a number the site does not show, ask the company. Do not copy a number from an unrelated record and attribute it to these pages.
The site does not state a year of incorporation, a number of employees, a list of offices beyond Summit House, or hours of business. A message sent outside a working day is not refused by these terms, and it is not guaranteed a reply the same day. The absence of hours is deliberate. It is not an invitation to treat the company as continuously staffed.
The practice described on the site is software publishing and IT engineering: proprietary software, enterprise SaaS products, prepackaged software, custom programs, web and mobile platforms, computer systems design, software architecture, cloud deployment, enterprise API integration, technical consulting, and maintenance after a release. That list is the scope. A phrase on a page that sounds broader is read back to the list. “Information technology services” is the collective name, explained later, and not a mandate to do any IT task a reader can imagine.
How to read the site
The homepage is arranged as a series of unequal divisions. That arrangement is a way of presenting the company. It is not a diagram of a system architecture, and the position of a sentence on the left or the right is not a ranking of services. The services page says the same thing in words: the list is not a ranking. A larger type size is compositional. It does not mean the company declines smaller or later items on the page. If you need a particular item, use its name. Do not infer priority from scale.
Headings are labels. They are not warranties. A heading such as “Published software. Engineered systems.” is a description of the practice, not a promise that any given system has already been published for you. A heading on a demonstration is a label of the kind of illustration it is — capability demonstration, representative workflow, technical approach, or illustrative scenario. Those labels are there so a reader does not convert an illustration into a case study. Ignoring the label and describing the block as a client result, in a tender or a conversation, would be a misuse of the site.
Internal links are part of the site. A link to a section of the services page is a link to that explanation. It is not a selection of that service as an order. The contact link is an invitation to write. It is not an offer that becomes a contract when you click it.
Where a page and these terms use the same words, the longer explanation here controls the legal reading of the website. Where a page is more specific about a fact — the address, the email, the telephone number — the page and these terms say the same fact. Neither is a licence to add facts that appear in neither.
Definitions
“Company” means DRIVERITICS LTD, identified by the address and contact details published on the site.
“Site” means the pages served at driveritics.study, including the homepage, the services page, the portfolio page, the about page, the contact page, the thanks page, and these legal pages, together with the styles, scripts, and images that belong to them. It does not mean a future application, a customer environment, or a piece of software the company may publish under another name.
“You” means the person using the site, and, where the context requires, the organisation that person represents. If you do not have authority to bind an organisation, you bind only yourself, and you must not state that the organisation has agreed to anything.
“Enquiry” means a message sent by the form, or an email or call to the published routes, in which a person asks the company something. An enquiry is not an order and not a statement of work.
“Form” means the enquiry form on the homepage and on the contact page, posted to contact.php, asking for a name, an email address, and a message, and carrying the hidden checks described in the privacy policy.
“Writing” and “written agreement” mean a document that identifies the parties, the work, and the fact that both sides intend to be bound, and that is agreed by a means more deliberate than browsing this site or pressing the form’s button. An email chain can become that writing if it is clear. A page of this site cannot.
“Product” means software the company publishes as a product: prepackaged software or an enterprise SaaS product with a defined surface. The site does not name a current product catalogue with versions and prices. A product, for these terms, is a category of work, not a SKU you can order by clicking.
“Custom software” means a program commissioned for a stated operation, including a web platform or a mobile platform when that is what was asked for. It is not a modification the site promises to make to unnamed third-party software.
“Systems design” means the architecture and engineering of a computer system: structure, boundaries, and the conditions of deployment. It is not a certification and not a drawing stamped for a regulated building.
“Demonstration” means a block on the portfolio page, or the capability demonstration on the homepage, which is labelled as illustration rather than as a client engagement. A demonstration has no customer, no metric, and no testimonial, because none has been published.
“Loss” includes loss of profit, loss of revenue, loss of data, loss of goodwill, and interruption of business, whether direct or indirect, except where these terms or the law say a particular head of loss cannot be limited.
Who may use the site
The site is aimed at organisations, and at people acting for organisations, who want to understand or enquire about software publishing and engineering. You may use it if you are able to form a contract for yourself or you are authorised to enquire for an organisation. You may also read it if you are simply a reader. Reading does not require an account and does not require you to accept a click-wrap beyond the fact that the terms are published for the site you are using.
The site is not directed at children. A child should not send the form. A parent who finds that a child has done so can ask the company to delete the enquiry, as the privacy policy explains.
If you are a consumer, with mandatory rights under the law that protects consumers, those rights are not taken away by a sentence here. The company does not use the site to sell to consumers as a shop. If, unusually, a consumer enquiry led to paid work, the consumer rules that cannot be waived would still apply to that work, and these website terms would not be used to strip them out. Most of the language here is written for business enquiry, because that is what the site is for.
You are responsible for the people who use your systems to access the site. If a colleague sends the form from your domain, you should assume the company will treat the message as coming from the address that was typed. The company does not operate a staff directory against which to check the sender.
The job of the website
The site has two jobs. The first is to say, in public, what the practice is and what it is not. The second is to receive an enquiry. Everything else — the seam, the photographs, the phase descriptions, the menu — serves those two jobs. The seam is a layout. It does not process your data beyond what the privacy policy describes. The photographs do not identify a delivery. The phase descriptions on the services page are a way of talking about how attention can move from context, to specification, to build, to deployment, to lifecycle support. They are not a methodology you can hold the company to, and they are not a promise that every brief uses every phase or uses them in that order.
The site does not host the software it talks about. You cannot log into a product here. You cannot download a package here. You cannot open a ticket with a published severity level. If a product exists or comes to exist, access to it would be a separate matter, with its own terms if it is offered as a service. Those terms are not these terms, and they are not hidden in a page of the marketing site.
No account, no shop, no software licence
The site does not create an account when you visit or when you send the form. There is no password to reset and no profile to delete, other than the correspondence described in the privacy policy. A third party that asks you for a DRIVERITICS LTD password is not using a mechanism this site provides.
Nothing is sold from the pages. There is no basket, no checkout, and no automatic renewal. A price mentioned in an enquiry by you is your figure, not the company’s acceptance of it. The company does not become obliged to match a budget you typed.
Visiting the site does not license any software. It does not license a product, a library, a script on the page beyond the right to have your browser run it in order to read the site, or a design. The script that runs the menu and the seam is part of the page. You may not extract it and ship it as your own product. You may let your browser execute it while you read.
Permission and its limits
The company grants you a limited, revocable permission to access the site for the two jobs described above: to read it, and to send a genuine enquiry. The permission is not exclusive. It is not transferable into a right to frame the site inside another site and present the frame as your product. It does not include a right to mirror the site, to train a model on a bulk copy of it and republish the output as the company’s words, or to use the pages as a source of leads to contact the company’s correspondents. The company does not publish a list of correspondents. Do not try to construct one.
You may quote a short passage for a fair purpose such as criticism, review, or a genuine question to the company, with a link and an acknowledgement. You may not reproduce a whole page as your own marketing. You may not remove the labels that mark demonstrations as demonstrations and then circulate the remainder as proof of work.
The permission ends if you misuse the site in the ways these terms forbid, or if the company withdraws the site. Ending the permission does not erase a written agreement that was actually made. It also does not require the company to keep serving pages to an address that is being used to attack the server.
Acceptable use
You will not use the site, the form, or the published addresses in any of the following ways. The list is practical rather than theatrical. It is aimed at the misuse that a public form and a public description of a software company actually attract.
You will not send a message that is unlawful, that defames a person, that incites violence, or that includes material you have no right to send. You will not use the form to deliver malware, to link to malware, or to test whether the mailbox will execute content. The message is read as text. It is not a channel for code the company has agreed to run.
You will not submit the form by automated means, in bulk, or with invented identities. The honeypot and the timing check exist because this happens. Circumventing them in order to deliver junk is a breach of these terms, not a clever use of a public page. You will not harvest the email address in order to build a spam list, and you will not register the company’s name as the sender of mail the company did not send.
You will not probe, scan, or test the site for vulnerabilities except where the law gives you a right the company cannot remove, and even then you will not do it in a way that degrades the site for everyone else. You will not attempt to bypass a control, to inject content into a page, or to overload the form. A genuine report of a fault can be sent to network@driveritics.study with enough detail to understand it and without a demand for payment as a condition of hearing the report. The company does not operate a public bug-bounty programme, and these terms do not create one.
You will not scrape the site at a volume or a frequency that impairs it. A normal browser, a normal link preview, and a search engine doing ordinary indexing are not the target of this sentence. A crawler that walks the form or replays submissions is.
You will not misrepresent the company. In particular you will not state that a demonstration is a client project, that a photograph is the interior of Summit House, that the company holds a certification or an award the site does not mention, that the company has a named partner, or that a technology vendor is the company’s standard when the site has refused to name one. You will not put the company’s name on a tender response as a subcontractor unless the company has agreed in writing to be named.
You will not use the site to send special-category personal information, card numbers, or passwords. If you do, you do so at your own risk and against the request in the privacy policy. The company will not have asked for them.
You will not attempt to make the site the place where a regulated activity is conducted — a financial promotion, a medical device claim, a gambling service — by posting that content into the form and treating the company’s reply as approval. A reply, if one is sent, is about the software enquiry. It is not a regulatory permission.
Enquiries
An enquiry can be made by the form, by email to network@driveritics.study, or by telephone on +44 7911 123456. The form is the route the site itself provides. The other two are the published direct routes. They reach the same company. They are not a promise that the same person will answer, because the site does not name individual staff.
A useful enquiry says who is writing, how to reply, and what is being asked. It helps if it says which part of the practice is in view: publishing, custom software, systems design, deployment, an API boundary, consulting, or maintenance. If you do not know, say what the organisation is trying to do. The company can then say which heading fits, or that none of them fits. A conclusion that the work is outside the practice is a valid answer. It is not a breach of these terms.
The company may ask questions before it can tell you whether it will propose written terms for work. Those questions are still part of the enquiry. They are not the start of the work. Time spent reading a message is not billable under these terms, because these terms set no fees. If a piece of advisory work is to be paid for, that is a consulting engagement and it needs its own writing. Do not assume that a long reply is a free specification you can hand to another supplier as the company’s work product. A short orientation is a reply. A specification is work.
The company may decline an enquiry without giving a detailed reason. Reasons can include fit, capacity, conflict, or a brief that asks the company to do something the site does not offer. A decline is not defamation and it is not a review of your organisation for anyone else to read. The company will not publish your enquiry.
You must not send an enquiry that pretends to be from someone else, and you must not intercept a reply meant for someone else. If you receive a reply that was clearly not for you, delete it and tell the company. Do not use its contents.
What the form means
Pressing the button sends the fields to contact.php. The script checks them. If they fail the checks, nothing is emailed and the page explains the failure. If they pass, the script asks the server to email network@driveritics.study. Only if that request is reported as successful does the site send you to the thanks page. The thanks page is a statement about that hand-off. It is not a statement that a person has already read the message, and it is not an acceptance of any offer that might have been inside the message.
If the mail path fails, the site says so. You should then use the email address or the telephone number yourself if you still want to make contact. A failed hand-off is not a refused brief. It is a failed transmission. The company may never have seen the text. Do not treat silence after a failure page as a commercial “no”. Treat it as an instruction to write directly.
An offer, if your message contains one — a proposal that the company do X for Y pounds by Z date — is not accepted by the act of transmission, by the thanks page, or by an acknowledgement that says the message was received. Acceptance of commercial terms happens only in the written agreement these terms keep pointing to. A sentence in an automatic mail-system notice, if one is generated by infrastructure the company does not control, is not the company’s acceptance either.
You are responsible for the accuracy of what you send. If you mistype your email address, the reply may not reach you. The company will use the address you provided. It does not undertake to discover a different one.
Software publishing
On this site, software publishing means preparing proprietary software or prepackaged software, including enterprise SaaS products, as products rather than as an open quantity of labour. A product has a surface that can be described: what it is for, what a release contains, and the fact that it is published as software an organisation runs. The services page says this. These terms fix the legal reading of that description for the website.
The description is not a catalogue. The site does not list named products, version numbers, licence metrics, or prices. You cannot accept an offer to buy a named product by sending the form, because no such offer is made. If you ask whether a product of a certain kind exists or could be published, the answer is an enquiry. It may be “not as a current catalogue item”, or it may become a conversation about whether publication or a custom build is the right shape. That conversation is not, by itself, a licence.
Publishing, as a category, is distinct from custom software. The homepage says a published product and a commissioned system are different briefs. These terms adopt that distinction. A reader must not collapse them. Asking for “a SaaS platform, but exactly our process, and we will own every line” may be a custom brief wearing a product word. The company is entitled to say which brief it is prepared to discuss. The website does not force every request into the product category because the visitor prefers that word.
Nothing on the site promises a particular availability of a product, a particular number of tenants, a backup interval, a support hour, or a data-residency location. Those are the sorts of terms a real product agreement would have to state. They are absent here on purpose. Do not fill the absence with an industry average and then attribute the average to the company. Do not fill it with a figure you once saw on another vendor’s page.
Intellectual property in a product, if a product is later offered, stays where the written product terms put it. These website terms do not pre-agree that a customer owns the product, and they do not pre-agree a licence scope. They also do not say that the company will accept a customer’s paper as the only paper. Negotiation of real terms happens off this website, in the writing that follows an enquiry the company is willing to take further.
A demonstration that mentions publishing an enterprise SaaS product is an illustration of that separation between a product surface and client-specific work. It is not evidence that a multi-tenant service is currently operated for a named sector, and it is not a reference site. Citing it as a reference would misrepresent the page.
Custom software
Custom software, on this site, means a program written for a stated operation. The operation is something the organisation can describe: who uses it, what it must take in, what it must produce, and which neighbouring systems it must respect. Web platforms and mobile platforms are included when that is the operation. The site says the work is written for the context in front of it, rather than relabelled from a generic package. These terms hold the company and the reader to that sentence. A request to “take your product and make it ours” is not, without more, a custom brief and not, without more, a publishing brief. It is an enquiry that still needs a shape.
The site does not publish a technology stack. It does not name a language, a framework, a database, a mobile store, or a cloud vendor as the company standard. A reader must not treat silence as a commitment to a stack the reader prefers, and must not treat silence as a refusal of a stack either. The choice, if work proceeds, belongs in the written agreement, where it can be matched to the operation. Putting a stack in the enquiry is useful information. It is not an instruction the company has already accepted.
A custom brief has edges. The services page says the useful boundary is the brief, and that an interface to software the organisation already runs is described as enterprise API integration rather than hidden inside the build. These terms adopt that edge. If you want the interface work included, say so. If the company proposes to treat it separately, that is a legitimate reading of the site, not a surprise exclusion invented after the fact. Hiding interface work inside a single vague sentence is how disputes start. The website’s position is that the edge should be visible.
Custom software is not a body-shop arrangement stated on this site. The site does not offer unnamed developers by the day, and it does not publish a rate card. Asking for “two developers for six months” without an operation is not a brief the pages have described. The company may still talk to you. It is not obliged by these terms to staff a seat.
Delivery method is not specified. The site does not promise a particular cadence, a particular workshop format, or a particular tool for tracking work. The phase names on the services page — context, specification, build, deployment, lifecycle — are a vocabulary. They are not a contractual waterfall and not a contractual iterative method. A written agreement can choose a method. These terms do not choose it for you.
Acceptance of custom software, ownership of the result, warranty periods, and what happens to pre-existing tools the company already had, are all matters for the written agreement. These terms do not pre-assign the copyright in a future program to you, and they do not pre-assign it away from you. They refuse to decide the question on a marketing page. Anyone who tells a third party that “DRIVERITICS LTD’s website says the customer owns the code” is misreading the site. Anyone who says the opposite with the same confidence is also misreading it. The site says the question is for a written agreement.
A representative workflow on the portfolio page describes enquiry, written scope, build, and handover as the shape of the work. It states that it is not a diary of a named engagement and that it does not imply a duration. These terms repeat that limit so it cannot be argued that the workflow page created a timetable.
Computer systems design
Computer systems design and software architecture, as published here, mean the structure of a system, the boundaries between its parts, and the conditions under which it is deployed. The work sits beside a product or a custom program. It makes the relationship explicit: what the system owns, what it asks of neighbouring software, and what must be true before a release is put into use. That is the whole of the website’s claim. It is a substantial claim. It is not a claim to be a certified designer of buildings, a signatory of structural calculations, or the holder of a security accreditation.
The site shows a bright equipment room as an illustration of a technical place seen through glass. The photograph is not a drawing of your estate and not a statement that the company operates a data centre. You must not attach your network diagram to that photograph and describe the combination as the company’s design. A design, if one is commissioned, will be a document agreed in the engagement, not a crop of a public image.
The technical approach on the portfolio page names three statements: what the system owns, which requests cross an interface, and which environment is the deployment target. These terms treat those three statements as the website’s definition of “technical content” for this topic. They are topics the company is prepared to discuss. They are not a completed design for any reader, and they are not a warranty that a particular boundary is safe, lawful, or sufficient for a regulated activity. If your system is in a regulated setting, the written agreement would have to face that setting. The website does not face it for you by using the word “enterprise”.
Systems design is not, on this site, a promise to audit a third party, to certify compliance, or to sign a report for a regulator. If you need that kind of artefact, say so in the enquiry. The answer may be that it sits outside the practice. That answer is consistent with these terms.
A design can reveal constraints you would rather not have. The company is not liable, under these website terms, for the existence of a constraint. A public page that talks about boundaries is not a representation that your current system already has clean ones.
Cloud systems and deployment
Deployment, as the site uses the word, is the work of putting a product or a custom system into the environment where it will run. That environment may be a cloud environment or the organisation’s own. The site refuses two embellishments. It does not name a preferred cloud vendor. It does not advertise an uptime figure. These terms make that refusal binding on the reading of the website. You cannot select a vendor by assumption. You cannot read an uptime percentage into the word “cloud”.
A deployment brief, if it becomes work, names the target, the release, and the handover. Those three nouns are on the services page. They are the minimum of what “deployment” means here. They are not a run-book. They do not include a standing offer to operate the environment after handover. Operation after handover is maintenance, or it is a different contract, and it is not implied by the fact that the company was willing to place a release.
The illustrative scenario on the portfolio page is labelled as a scenario: one deployment target, one interface, one handover, no volumes and no latency figures. The view through the glass is a photograph of roofs and water. The caption says it is not the view from Summit House and not evidence of a completed deployment. These terms adopt the caption. Using the image in a slide as “DRIVERITICS LTD’s production region” would be a false statement about the site.
The company does not, by publishing this page, become your cloud provider. It does not open an account for you with a hyperscaler. It does not accept a click-through of a vendor’s terms on your behalf. If a later agreement involves a vendor, the agreement will have to say who contracts with the vendor. The website does not say it is the company.
Security of a deployed system is likewise not fixed here. No control list, no penetration-test cadence, and no encryption standard is published. Those omissions are not an assertion that such matters do not matter. They are an assertion that they are not settled by a public page. A reader who needs a particular control must ask for it to be written down, and must be prepared to hear that it changes the brief.
Enterprise API integration
Enterprise API integration means connecting a published product or a custom program to software an organisation already operates, through interfaces that can be specified. The sentence is deliberately modest. It does not say that every system has an interface. It does not say that an interface, if it exists, is documented, stable, or licensed for the use you intend. It says the connection is a kind of work the company will discuss, and that the connection should be specified rather than assumed.
Specification is the point of the website’s approach. An interface has a direction, a meaning for each exchange, and a boundary around what it will not do. The portfolio’s technical approach treats the interface as one of the boundaries of a system, not as an afterthought. These terms do the same. A sentence in an enquiry such as “and integrate with everything we have” is not a specification. It is a request for a scoping conversation. The company may decline to treat it as a build instruction. That decline is aligned with the site.
The company does not warrant, via this website, that a named third-party product can be connected, that the third party will cooperate, or that the third party’s terms allow the connection. Those facts sit with the third party and with your licence. The website does not grant you a right in anyone else’s software. If an integration later requires a key, a certificate, or a paid API from someone else, obtaining it is not silently included by the word “enterprise”.
The portrait on the services page — a person walking toward a violet wall — is a colour and a place. It is not a diagram of an integration. Do not annotate it as one.
Failure of a third-party interface, a change in a third-party schema, or a withdrawal of a third-party API is not a breach of these website terms. There is no integration in existence by virtue of you having read the page. If a written agreement later covers a named interface, that agreement will have to say what happens when the other side changes. These terms do not guess that allocation.
Technical consulting
Consulting, on this site, is advice on a software or systems question: an architecture under consideration, a release that needs a second reading, or a boundary between a product and a commissioned program. It is not a substitute for the build, and it is not described as a retained panel. These terms keep both limits. You may ask for advice. The company may agree to give it, or not. If the advice is to be relied on, paid for, or issued as a report, that is an engagement and it needs writing. A conversational reply to an enquiry is not that report.
The services page asks you to say what decision you are trying to make. These terms treat that as a fair requirement of a consulting enquiry. An enquiry that says only “tell us what to do” does not yet identify a decision. The company can ask you to name one. It can also say that the question is really a build, or really a publishing question, and point you at those headings. Reclassification is not a refusal to help. It is the site working as it says it works.
Advice given only on the public pages — the distinctions between briefs, the insistence on edges, the refusal of invented metrics — is general. It is not advice about your facts. You may find it useful. You may not say that the company advised your board because you printed a page. Reliance of that kind is not invited. The liability section below deals with decisions taken only from general pages.
Consulting does not include legal advice, tax advice, or audit opinions. The company is a software publisher and an engineering practice, as the site describes it. It is not, on these pages, a law firm, an accountancy firm, or a registered auditor. Do not instruct it as one by the form.
Maintenance and lifecycle support
Maintenance is the work that follows a release: corrections, agreed changes, and the continuation of a product or a custom system through its working life. The site says the length of that support, and what it includes, is for a written agreement, and that the page sets no response time. These terms repeat the point because response times are exactly the sort of term readers otherwise invent. There is no four-hour response, no next-business-day response, and no “best endeavours” formula on this website. If you need one, it has to be written in an agreement the company actually accepts. Until then, there is none.
Maintenance is separate from the original build so the boundary stays visible. A sentence such as “including all future changes” in an enquiry does not create a perpetual support duty. The company can treat future change as a later brief. That treatment matches the site. It is not a trick. Perpetual duties are serious. They are not formed by a public page that expressly refuses to set them.
The lifecycle phase on the services page says maintenance is for the period and the changes a separate agreement names. These terms adopt that sentence as the definition of lifecycle support for the website. A period that is not named does not exist. A change that is not agreed is not included. A wish-list sent after a release is a new enquiry, unless an agreement already says otherwise.
The site also says no service level is stated. A service level, if one is later agreed, is part of that agreement’s remedy scheme. It is not imported from these terms, because these terms contain no service credit, no uptime credit, and no formula for calculating one. Do not draft a credit against the company by reference to “standard IT practice”. The company has not published a standard of that kind.
Ending a maintenance conversation is not the same as ending a licence to software you already have under a different agreement. These website terms do not terminate, and do not create, product licences. They only refuse to let the website become a silent support contract.
Information technology services
The phrase “information technology services” on this site means the practice as a whole: the publishing, the custom work, the systems design, the deployment, the integration, the consulting, and the maintenance already described. It is not a separate offer sitting behind the list, and it is not a promise to supply deskside support, device fleets, telecoms lines, or print management. If your enquiry is for those things, the company can say they are outside the published practice. That answer is consistent with the services page, which tells a reader who is unsure to describe the system rather than to invent a heading.
Using the broad phrase in a contract draft — “all information technology services required by the customer” — and then pointing at this website as the definition, would be a bad reading. The website defines the phrase narrowly, as the collective name for a stated list. These terms adopt the narrow definition. A wide drafting that tries to use the site as a catch-all is not supported by the site.
The same narrowness applies to words such as “digital”, “transformation”, and “platform” if they appear in your own paper. The company has not used them as obligations on these pages. Do not paste them into a scope and claim the website agreed.
Demonstrations and photographs
The portfolio page states that the company has not published named clients, project titles, testimonials, or performance figures. Each block is labelled. These terms make the labels operative. A capability demonstration is not a case study. A representative workflow is not a diary. A technical approach is not a delivered design. An illustrative scenario is not a completed deployment. You will not re-label them in your own materials. If you need a reference, ask. The answer may be that none is published. That answer is not a gap you may fill.
Photographs are illustrations of places and of people at work in general. Captions say when an image is not Summit House and not a client environment. Those captions control. The company does not warrant that a depicted room exists as a place you can visit, or that any person shown is an employee. You will not contact a person shown in a photograph as if the picture were an introduction. The pictures are not a staff directory.
The company does not grant you a right to use the photographs outside the act of viewing the site, except for a short quotation of a page with its images where the law of fair dealing clearly allows it and the labels stay intact. Using a photograph as the hero of your own proposal, stripped of the caption, is not fair dealing. It is a misuse of the site.
Metrics are not omitted by accident. The site says it does not publish them. You will not estimate a metric and attribute the estimate to the company. You will not tell a third party that results were “removed for confidentiality” when the truth is that no client result was published at all.
Separate written agreements
If the company is willing to do work, the work needs a written agreement. These terms do not set the minimum contents of that agreement as a form you can insist on, but they do say what the website will not silently supply. A written agreement is where parties, scope, price, timing, responsibilities, intellectual property, and any service level would have to be stated if they are to exist. Until they are stated there, they do not exist by inference from the site.
The company may propose its own paper or review yours. These terms do not oblige it to accept your paper unamended, and they do not oblige you to accept the company’s paper unamended. They only stop either side from claiming that the public website already closed the deal. A purchase order that arrives alone, referring to “the website” as the specification, is not acceptance of a contract on these terms for the delivery of software. It is, at most, another enquiry, unless a person at the company with authority confirms in writing that the order is accepted against a named scope.
Pre-contract discussions, including replies to the form, are not a duty of care to produce a buildable specification for free. They are conversations. If you want a paid discovery piece, that is consulting or an early phase of a build, and it should be named as such. The phase list on the services page is available as vocabulary for that naming. It is not a free project plan.
A written agreement can incorporate parts of the site by explicit reference, for example by saying that a demonstration is not a requirement. It can also say that the site is superseded. What it cannot honestly do is incorporate “all website claims” as if the site were full of numerical promises. The site’s claims are qualitative and limited. Incorporating them incorporates the limits too.
Intellectual property
The site’s text, the selection and arrangement of the pages, the seam mark, and the way the name DRIVERITICS is set out as a wordmark on the pages, are protected as the company’s materials to the extent the law provides. You receive the limited permission stated earlier, and nothing more. You do not acquire trade mark rights by using the name in an enquiry. The company does not, by these terms, claim a registration it has not published. It does claim the ordinary right to stop a person passing off another service as the company’s, and the ordinary right in the copyright of the pages.
The scripts and styles are part of the pages. They are not an open-source release. No licence file on the site grants a public licence to them. Do not remove a notice. Do not present the seam system as a library you authored.
Feedback you send — a suggestion about a page, a correction, an idea about how a brief might be shaped — may be used by the company to improve the site or to think about its practice, without a duty to pay you or to keep the suggestion secret, unless the message is clearly marked as confidential business information and the confidentiality section below applies. A suggestion is not a commission. The company is not obliged to implement it, and if it does, that implementation does not make you a joint author of the site.
Third-party materials, including typefaces served to your browser, remain the property of their owners. The site’s use of a font service does not assign those fonts to you. Your right to see them is the right your browser obtains when it loads the page, on the terms of that service, not a right to extract the font files and ship them.
Nothing in this section decides the intellectual property in software that might be built later. That decision is reserved to the written agreement, as the publishing and custom sections already say. Repeating it here is deliberate. It is the point readers most often try to settle by wishful reading.
Materials you send
You keep whatever rights you already have in the text and files you send. You grant the company a permission to use what you send for the purpose of reading the enquiry, replying, and, if you and the company later agree work, preparing that work. The permission lasts as long as those purposes require. It is not a permission for the company to publish your brief as a case study. The company will not do that without a separate agreement, and the site’s own refusal to invent case studies applies in that direction as well.
You confirm that you are allowed to send what you send. If you include another person’s personal information, you are responsible for having a proper basis to do so. The privacy policy tells you not to send special-category information casually. These terms add the contractual point: if the company suffers a claim because you sent material you had no right to send, you will be responsible for that claim to the extent it was caused by your sending it, subject always to the liability limits below and to any responsibility the law does not allow to be shifted.
The company may refuse a message that contains material it does not want to hold, including unlawful content. Refusal is not a breach. It is a protection of the mailbox.
Confidentiality of enquiries
The company will treat a genuine enquiry as confidential business correspondence. It will not post it on the site, and it will not use it as a public example. People inside the company who need to see it in order to answer may see it. A professional adviser who needs to see it for that answer may see it, under a duty of confidence. The company may also disclose it if the law requires, or if you ask it to.
This duty is the company’s duty under these terms. It is not a mutual non-disclosure agreement with a defined term, a defined residual category, or a schedule of exceptions drafted for a transaction. If you need that instrument before you will describe a system, say so. The company can consider it. Until it is signed, do not send information you would only send under a negotiated non-disclosure agreement. The form is not that agreement. A footer in your email that says “this message is confidential and may not be read” does not, by itself, rewrite these terms or create a negotiated NDA. The company may still read an enquiry in order to answer it. That is the point of the message.
The company does not owe confidentiality in an idea that is already public, that it already held, or that it receives from someone else without using your message. A general method described on the site — separating a product brief from a custom brief, for example — is public because the site published it. You cannot send it back and then claim the company must stop saying it.
Your duty, in return, is not to present the company’s reply as a public endorsement, and not to circulate a proposal that was clearly marked as a draft for you alone. A short reply that only points you to a page is not confidential. A detailed comment on your architecture may be. If you are unsure, ask before you forward it.
Liability
Nothing in these terms excludes or limits liability for death or personal injury caused by negligence, for fraud or fraudulent misrepresentation, or for any other liability that the law of Scotland, or the law of the United Kingdom so far as it cannot be disapplied, does not allow to be excluded or limited. Those liabilities sit outside every limit below. If a sentence and this paragraph conflict, this paragraph wins.
Subject to that, the site is information. You use it at your own judgment. The company is not liable for a decision made only by reading the public pages, where no written agreement for work was made. That includes a decision to delay a project, to choose a vendor, to announce a programme internally, or to cite the company in a tender. The pages are not a substitute for your own advice, technical or legal, on your facts.
Subject to the opening paragraph of this section, the company is not liable under these terms for loss of profit, loss of revenue, loss of anticipated savings, loss of data, loss of goodwill, or business interruption arising from the use of the site or the inability to use the site. The form may fail to send. The pages may be unavailable. A sentence may be updated. Those are incidents of a public website. They are not a delivery failure under a software contract, because these terms are not that contract.
Subject to the opening paragraph, the company’s total liability arising out of the use of the site, whether in contract, delict, or otherwise, is limited to one hundred pounds sterling. The figure is deliberately small because the site is free to read and the form is free to use, and because real work is meant to be governed by a written agreement with its own allocation of risk. If that figure is held to be unenforceable in a particular case, the rest of these terms still stand, and the liability that cannot be limited remains unlimited in the way the law requires.
You will not bring a claim under these terms for a matter that is actually a claim under a written agreement for work. That agreement’s remedies, if any, are the remedies for that work. These terms must not be used to stack a second claim about the same facts on top of a contract that was meant to be the whole deal, except where the written agreement itself preserves a right or where the law does not allow the stacking to be prevented.
The company does not accept liability for third-party sites, third-party software, or third-party interfaces that the website mentions only as categories. A category is not a recommendation of a vendor. A photograph of a room is not a recommendation of a landlord.
Availability of the site
The site is published on an as-available basis. The company may withdraw a page, correct a sentence, or suspend the form. It does not promise a particular uptime for the website, consistent with its refusal to promise an uptime for systems that are not even under contract. Maintenance of the website is not the “software maintenance” service described for customers’ releases. The two uses of the word must not be confused. One is the company looking after its own pages. The other is a service that does not exist until it is agreed.
The company is not responsible for the network between you and the server, for your browser, or for a font service that fails to load. The pages are built to remain readable if the typeface does not arrive. A missing font is not a defect in the information.
Stopping a correspondent
The company may stop answering a person who breaches these terms, who uses the form for abuse, or who continues to write after being asked to stop. It may do so without a public explanation. It will not, under these terms, be obliged to keep a channel open to a correspondent who is using it to harm the site or to misrepresent the company. Stopping a correspondent is not a statement to the world about that person’s business. It is a decision about the mailbox.
If the company has a written agreement with an organisation, that agreement governs the working relationship. These terms do not let either side walk away from that agreement merely by citing a website breach that has nothing to do with the work. A website breach and a project dispute are different things unless the facts make them the same.
Changes
The company may change these terms by posting a new version and changing the date. The date on this version is 12 October 2026. You should read the date when the terms matter to you. A change applies to use of the site after it is posted. It does not rewrite an enquiry already sent, except that the company’s handling of personal information remains subject to the privacy policy and to the law. It does not amend a written agreement for work.
A change that only corrects grammar or a cross-reference, without altering a rule, is still a change of version if the date moves. The company will not use a silent edit to introduce a fee or a service level. Fees and service levels are not introduced on this page at all.
Law and courts
These terms are governed by the law of Scotland. That choice follows the published address in Edinburgh. It is the law of the place the company has identified, not a clause copied from an unrelated template. The courts of Scotland have jurisdiction over a dispute about the use of the website. You and the company may still choose, in a later written agreement for actual work, a different governing law for that work. A different choice in a project contract does not silently re-govern the public website.
If you are a consumer and a mandatory rule of your place of residence gives you a right to sue in your home courts, or preserves a protection these terms cannot remove, that rule still applies. The company does not ask a consumer to waive a right the law says cannot be waived. The site’s commercial character does not, by itself, decide every cross-border question. It does decide the company’s stated law for business use of the site.
Before starting a court claim about the website, you should write to network@driveritics.study and describe the dispute. The company will consider a response. This request is not a condition that blocks a claim the law allows you to bring without notice, and it is not an arbitration agreement. There is no arbitration clause. There is no requirement to mediate. There is a preference for being told what is wrong before positions harden. A claim about personal information may also be taken to the Information Commissioner’s Office, as the privacy policy explains, and that route is not closed by this section.
General
If a court or another competent body holds that part of these terms is unenforceable, the rest continue. The unenforceable part should be read down to the minimum extent needed to make it enforceable, if the law allows that reading, and if it does not, it is severed. The liability cap, if it fails in a case, is severed or read down without pulling down the distinction between the website and a contract for work.
A failure or delay in enforcing a right is not a waiver. A waiver of one breach is not a waiver of a later breach. A waiver needs to be clear. Silence, including silence after an enquiry, is not a waiver and not an acceptance.
You may not assign your permission to use the site. The company may assign the site and these terms to a successor of the practice, and it will say so on the site if the identity of the publisher changes. An assignment of a future software contract is a different matter and belongs in that contract.
These terms, together with the terms of service, the privacy policy, and the cookie policy, are the whole of the public terms for the website. They supersede earlier public versions of the website terms. They do not supersede a written agreement for work. No person has authority to vary these terms by a casual email that says the website “doesn’t really mean” a limit that is written down. A variation of these terms happens by a new published version, or by a written instrument that identifies itself as a variation and is agreed by the company.
A person who is not a party to these terms has no right to enforce them, except that this sentence does not remove a right that a statute confers and does not allow to be removed. The company does not intend the site to create third-party rights in visitors’ customers or suppliers.
Notices about these terms can be sent to network@driveritics.study or by post to the Edinburgh address. The company may send a notice about the site by publishing it on the site, which is the appropriate route for a change to public terms. A notice about your enquiry may be sent to the email address you gave. Each side should use a method that is likely to be read. A notice is not effective merely because it was buried in an unrelated message.
Headings are for convenience. They do not limit the sections. The word “including” means “including without limitation” unless the context shows a closed list. A reference to a page is a reference to that page as published from time to time, including its limits. A reference to “writing” includes email. It does not include a browse of a page.
These terms are in English. A translation, if one were ever made, would be for convenience. The English text of the published page is the text that counts. The company does not publish a translation now.
The terms of service and these terms are meant to be consistent. The summaries there are shorter. They should not be read as extra promises. If you came to these terms from a service page, bring the limit on that service with you. The publishing section limits products. The custom section limits programs. The systems, cloud, API, consulting, and maintenance sections limit those words. The collective phrase is limited by the section that defines information technology services. None of those sections is optional colour. They are the point of publishing a long set of terms for a site that has chosen not to invent commercial numbers.
Phases are vocabulary, not a programme
The services page sets out five phases: context, specification, build, deployment, and lifecycle. Each is given a different width on the page. The widths are a visual device. They are not percentages of a fee, of a timetable, or of a team. A reader who adds the widths and treats them as a commercial split has misunderstood the page. These terms forbid that reading. No phase is priced. No phase has a duration. No phase is mandatory for every brief.
Context means understanding the setting and the constraint. It does not mean a paid discovery report. Specification means writing the edges of the work so that a product and a custom system are not described as the same thing. It does not mean a document you may take to another supplier as the company’s specification unless a written agreement says the document was commissioned and may be used that way. Build means programming, integration, and review against what was specified. It does not mean a commitment to a particular ceremony of review. Deployment means placing an agreed release and handing over what was specified. Lifecycle means maintenance for a named period and named changes. If a brief never reaches a later phase, the earlier conversation does not roll forward by inertia.
You may use the phase names in an enquiry if they help you speak clearly. Using them does not select a package. The company may answer that a brief needs only one of them, or that it needs a different order, or that it needs none of them because the request is outside the practice. That answer is allowed. The diagrammatic pressure of the page, with each phase wider than the last, is not a funnel you have entered by scrolling.
Spoken words, estimates, and old pages
A telephone call can start an enquiry. It does not vary these terms and it does not create a software contract. If something said on a call matters, ask for it to be put in writing. The company is not bound by a recollection of a call that was not confirmed. You are in the same position. Neither side should build a programme on an unconfirmed sentence.
An estimate given in a reply — a rough sense of whether a brief is large or small — is an estimate. It is not a quotation unless it says it is a quotation and it identifies a scope. A range is not a cap. A remark that something “sounds straightforward” is not a warranty that it will be. The site’s own refusal to publish numbers is undone if casual numbers in a mailbox are treated as published prices. They are not. A quotation, when one exists, will identify itself and the work it covers.
Pages change. A copy you saved, a print you made, or a snapshot in a search engine may be older than the page now published. The controlling text for the website is the text on the site at the time you rely on it, together with these terms as dated. If you need to rely on a sentence for a tender, quote the sentence, the page, and the date you read it, and do not add a metric that was not in the sentence. The company may correct an error when it sees one. A correction is not an admission that the previous sentence was a promise, and it is not a commitment to keep every historical wording available. The site does not promise a public archive of retired paragraphs.
Search snippets, link previews, and social-media cards can shorten a sentence until the limit disappears. A preview that shows “enterprise SaaS” without the surrounding refusal of uptime figures is not the company’s claim. The page is the claim. If you share a link, you do not control the preview, and you should not write a caption that restores a promise the page removed.
Records of these terms
You may print or save a copy of these terms for your own record of what you read. A saved copy is a record of a past version. It does not freeze the website. If you later rely on the site again, check the date at the top of the live page. The company may keep a copy of a version for its own file so that it can see what a page said on a given day. That internal copy is not a promise to supply every historical version on demand. If a real dispute makes a past wording relevant, the company will look for what it still holds. It will not reconstruct a page from memory and present the reconstruction as the archive.
The enquiry form does not ask you to tick that you have read these terms. Publication is how the terms are brought to a reader’s attention. A tick box that nobody reads would not make the position clearer, and the site does not pretend that a checkbox is a signature. If you send work on the assumption that a limit in these terms does not apply, you do so against the text. The safer course, when a limit matters to a transaction, is to say so in the written agreement rather than to hope the website was silent. On the points these terms address — no catalogue price, no uptime, no response time, no client metric, no implied licence, no staffed seat — the website is not silent.
These additions do not create new commercial offers. They close readings that would turn a careful public site into an accidental contract. The company would rather refuse a strained reading now than argue about it after money and time have been spent. That is why the terms are long, and why they keep returning to the same boundary: the site explains the practice; the written agreement, if any, is what binds the work.
Contact
Questions about these terms can be sent to network@driveritics.study, by post to DRIVERITICS LTD, Summit House, 4-5 Mitchell Street, Edinburgh, EH6 7BD, United Kingdom, or by telephone on +44 7911 123456. Say that you are writing about the website terms so the message is read as that, rather than only as a new brief. For personal information, use the route in the privacy policy. For a new piece of work, use the form or the same address, and expect an enquiry to be treated as an enquiry until a written agreement exists.