Privacy policy
This policy explains what happens to personal information when someone uses the website at https://driveritics.study. It is written against the pages that are actually published: a company site for a software publisher and IT engineering practice, with an enquiry form, a telephone number, an email address, and no customer account, shop, or analytics programme. It does not describe a product dashboard, a newsletter list, or a staff directory, because this website does not have those things.
Who this policy is about
The people this policy is written for are visitors to the website and anyone who sends an enquiry. That includes someone writing about software publishing, an enterprise SaaS product, custom software, computer systems design, cloud deployment, an API boundary, technical consulting, or maintenance. It also includes someone who only reads the pages and does not write. A reader who does not use the form gives the site almost nothing, and this policy says so plainly rather than implying a profile is built in the background.
The company behind the site is DRIVERITICS LTD, at Summit House, 4-5 Mitchell Street, Edinburgh, EH6 7BD, United Kingdom. The published contact routes are the email address network@driveritics.study and the telephone number +44 7911 123456. This policy does not name a separate data-protection officer, a company registration number, or a group of affiliates, because those details are not published on the site. Privacy messages should use the same email address as other enquiries, with a subject line that says the message is about personal information, so it can be read as such.
Who is responsible
For the enquiry form and for the pages of this website, DRIVERITICS LTD is the controller. That means the company decides why the enquiry is collected and how the site is set up to handle it. The site’s own code is simple on this point: it receives the form, checks it, and attempts to pass a valid message to the company mailbox. It does not hand the message to an advertising network, and it does not place it in a marketing platform.
Other organisations may be involved only in the ordinary sense that a website has to be hosted and an email has to travel. This policy does not name a hosting company or an email provider, because the site does not publish one. If a host stores the files that make the pages appear, or carries the email that the script asks the server to send, that host is acting so the site can function. The company does not use that relationship to add a second purpose, such as measuring an audience or building a list of prospects.
If a later written agreement for software work creates a different role — for example if the company were to process personal information inside a system it builds for a customer — that agreement would have to say so. This website policy does not do that work. It covers the site, the form, and the correspondence that starts here. It is not a data-processing schedule for a product or a custom system.
What the site is
driveritics.study is a corporate website. It describes software publishing and development, enterprise SaaS products, custom software programming, computer systems design, software architecture and engineering, prepackaged software, cloud systems and deployment, custom web and mobile platforms, enterprise API integration, technical software consulting, and software maintenance. The portfolio pages are labelled demonstrations. They are not client case studies and they do not contain customer names or performance figures. The about page states the address and the limits of what the site claims. The contact page and the end of the homepage carry the same form.
There is no login, no shopping cart, no payment page, no comment thread, and no area where a visitor creates a profile. Photographs illustrate places and working contexts. The site does not name the people in them or attach an enquiry to a picture.
Because the site is informational, most of a visit does not require the company to hold a file about the visitor. The moment that changes is the moment a person chooses to send a message, or to email or telephone the company directly. Direct email and telephone sit outside the form, but they are still correspondence with the company, and the same purposes apply: to read the enquiry and to reply.
The enquiry form
The form asks for three things a person fills in: name, email address, and message. Name and email are single lines. The message is a longer note. The site asks for at least a short paragraph, and it refuses a message that is empty or only a few characters, because a blank note cannot be answered. There is a maximum length so a single submission cannot be used to push an unbounded amount of text through the script.
The name is used so a reply can address the person who wrote. The email address is used as the route back. The message is the enquiry itself. The company does not ask the form for a job title, a company registration number, a budget, or a file upload. If you put those things in the message because they help explain the brief, they arrive only because you wrote them, not because a field demanded them.
You should not use the form to send information you are not free to share. In particular, do not include passwords, payment card numbers, or special-category information such as health data, unless there is a specific reason you have chosen to include it and you accept that the mailbox will then hold it. The form is built for a software enquiry, not for a medical or financial record. If such information appears in a message, the company will treat it as part of that message and will not use it for any other purpose, but the safer course is not to send it.
The form is submitted by the ordinary POST method to contact.php on this site. There is a check in the browser, if scripts run, and a check on the server in every case. The server check is the one that matters if the browser check is skipped. A message that fails the server check is not emailed. The page explains what was missing, and the name, email, and message you typed are shown again so you can correct them. That redisplay happens in the response to your browser. The failed attempt is not written to a database by this site’s code.
Fields you do not fill in
The form carries three extra fields that are not part of the enquiry you are asked to write. One is a honeypot, labelled as a website field and hidden from normal use. It is there so automated submissions that fill every box can be refused. A person using the form in the ordinary way leaves it blank. If it is filled, the message is rejected and is not sent to the mailbox. Do not put your real website address in that field. If you want the company to know a web address, put it in the message.
Another field records a time, set when the page loads, so a submission that arrives immediately can be refused as likely to be automated. A person who reads the page and then writes will pass that check. If scripts do not run, the time may be absent, and the server does not punish that absence, because a browser without scripts should still be able to send a genuine note. A third field records whether the form was sent from the homepage or the contact page. It is included in the email so the company can see which page was used. It is not a tracking identifier that follows you across other sites.
These fields are about abuse of the form, not about building a profile. They are not dropped as cookies. They travel with the single submission. If the submission is rejected, the site’s code does not keep them. If the submission is emailed, the time and the page source are in that email along with your name, address, and message.
What a successful send does
If the server accepts the message, it asks the machine that runs the site to send an email to network@driveritics.study. The email contains the name, the email address, the message, the page the form was on, and the fact that it came from the website. The reply address on that email is the address you typed, so a person at the company can answer you. The site redirects to the thanks page only when that send is reported as successful. The thanks page says the message was handed to the mailbox. It also says that opening the thanks page directly does not itself send anything, so the page cannot be mistaken for proof if you did not submit the form.
The site does not add your details to a separate list when the email is sent. There is no second copy written by the script into a database, a spreadsheet, or a customer-relationship tool. What exists, if the send works, is the email in the company mailbox, and whatever ordinary record the mail system keeps of mail it has transmitted. From that point the enquiry is correspondence. It may be read by the people at the company who deal with new work. It may be forwarded inside the company if more than one person needs to see the brief. It is not sold, and it is not used to feed an advertising audience.
A reply, if one is sent, will normally go to the email address you gave. If the company needs to ask a question before it can say whether the brief sits with publishing, custom software, systems design, or another part of the practice, that question is still part of handling the enquiry. Sending the form does not create a contract. The contact page and the homepage both say so, and this policy repeats it so that a message is not misunderstood as an order.
If the message is not sent
If the server cannot hand the message to the mailbox, the site does not pretend that it has. You will see a page that says the message was not sent, and you will be given the email address and the telephone number so you can write or call directly. The name, email, and message you typed are shown again in the form on that page so you can try once more or copy the text into your own email programme. The script does not store that failed attempt in a database.
A refusal for a different reason — a missing name, an email address that is not valid, a message that is too short, a filled honeypot, or a submission that arrives too quickly — also does not result in an email. The page lists what needs to change. Those refusals are there to keep the mailbox usable. They are not a score about you, and they are not kept as a behavioural record by the site’s code.
What the site does not collect
The pages do not run a web-analytics product. They do not embed an advertising pixel. They do not set a cookie to remember a consent choice, because they do not load a consent banner and they do not set non-essential cookies. The cookie policy explains that in more detail. They do not use local storage or session storage to keep a history of what you read. They do not offer social plug-ins that would send your visit to another company. Fonts are requested from Google Fonts so the pages can use Encode Sans Semi Condensed and Rubik. That request is a connection to Google’s font service when your browser loads the type. The site does not receive a report of that connection back into a company database. If you prefer not to make that connection, your browser will fall back to a system typeface and the pages remain readable.
The site does not collect account credentials, because there are no accounts. It does not collect payment details, because nothing is sold through the pages. It does not ask for a date of birth, a government identifier, or a precise location from your device. It does not read your contacts, your photos, or your files. The only file-like thing you can send is the text of the message.
Calls and emails you send yourself are received at the published number and address. They are not collected by the website script. This policy does not say that calls are recorded.
Hosting and ordinary server logs
A website is served by a computer. Computers that serve websites commonly write a line when a page is requested: a time, an address of the machine that asked, the page that was asked for, and a short description of the browser. This site’s own pages do not add a second log for marketing. The company has not published a named logging product or a retention period for host logs, and this policy does not invent one. If the host keeps such lines, they exist so the site can be operated, faults can be seen, and abuse can be investigated. They are not used by these pages to build a visitor profile or to retarget advertising.
An internet address can be personal information when it can be tied to a person. The company does not use host logs, if they exist, to identify casual readers. If a log line were needed to deal with an attack on the form or the server, it might be read for that purpose. That is a security purpose, not a commercial one.
The enquiry email is different from a server log. It is content you chose to send, addressed to the company, and it is kept as correspondence rather than as a technical trace.
Why information is used
An enquiry is used to read what you asked, to decide which part of the practice it belongs to, and to reply. It may be used to keep a record of that correspondence so the company can remember what was asked and what was answered. If the conversation continues into a written agreement for software work, the enquiry may be kept with the papers for that work, because it is part of how the brief was first described. The site itself does not carry out the project. It only starts the conversation.
Information is also used, in the narrow way described above, to refuse abusive or empty submissions and to keep the form available to genuine writers. That use is limited to the checks in the script: length, the shape of the email address, the honeypot, and the short-time check.
Information is not used to make automated decisions about credit, hiring, or access to a service. It is not used to train a public model. It is not used to enrich a data broker’s file. It is not combined with information bought from another source. The company does not match the form against a social network.
Legal bases
Under UK data-protection law, a controller needs a lawful basis for each purpose. For an enquiry, two bases are the ones that fit, and which one applies depends on what you asked.
If you write because you want the company to consider a piece of work — a product question, a custom system, a design, a deployment, an integration, advice, or maintenance — the message is a step you have asked the company to take before any contract exists. Using the message to respond to that request is covered by the basis that applies to steps taken at your request with a view to a contract. The form does not itself make the contract. It lets the company understand the request.
If you write with a question that is not really a request for work — a correction to a page, a privacy question, a complaint about the site — the company still needs to read and answer. That use rests on legitimate interests: answering people who contact a published business, and keeping a record of what was said. The same interest covers the limited checks that keep the form from being filled by automated junk. Those interests are weighed below.
The company does not rely on consent as the basis for the enquiry form. There is no unticked box you must tick to “agree to processing” before the message can be sent. Sending the message is the request. Consent would be the wrong tool here, because a pre-ticked box or a buried sentence would not be a real choice, and because the company should be able to answer an enquiry even if a later conversation is difficult. Where consent is the right basis for something else — and nothing on this site currently asks for that kind of consent — it would be asked for separately, and it could be withdrawn.
The company does not rely on a legal obligation as the reason for running the form. If a later legal duty required a record to be kept — for example an accounting record if a contract and a payment followed — that duty would apply to that later record, not to every visitor who only read a page.
Legitimate interests
The legitimate-interest basis requires a real interest, a use that is necessary for it, and a balance against the person’s rights. The interest here is ordinary and limited: a business that publishes a telephone number and an email address must be able to receive and answer messages, and a form that stands in for those routes must be able to reject obvious abuse. The use is necessary in the plain sense that the company cannot reply to a message it is not allowed to read, and it cannot keep the form useful if every automated post is delivered.
The balance takes account of what is actually collected. A reader who does not write is not placed on a list. A writer sends a name, an email address, and whatever they chose to say. The information is not used to advertise to other people, and it is not published. The effect on the writer is that the company can answer and can keep the thread. That is the effect a person expects when they use a contact form. It is not a hidden consequence. On that balance, the company considers the legitimate-interest basis appropriate for correspondence that is not already covered as a pre-contractual step, and for the abuse checks on the form.
You can object to a use that rests on legitimate interests. How to do that is set out with the other rights below. An objection to the company reading an enquiry you have just sent may simply mean the company cannot continue the conversation. An objection does not require the company to pretend a message was never received if it needs the message to show what happened.
How long information is kept
The site’s code does not set an automatic deletion date, because it does not keep its own database of enquiries. The email, once sent, lives in the mailbox and in the correspondence that follows. The company keeps that correspondence for as long as it needs it to handle the enquiry, to continue a conversation that you are still in, and to have a record of what was asked and answered if the matter is later disputed. If the enquiry leads to a written agreement, the papers for that agreement — which may include the original note — are kept for as long as the agreement and any ordinary record-keeping that follows it require. This policy does not invent a fixed number of years for every note, because the site has not published a single retention schedule and different messages have different lives.
A message that fails validation is not emailed and is not stored by the script. A message that the mail system refuses is shown back to you and is not stored by the script. Host logs, if the host keeps them, are kept according to the host’s operation of the server. The company does not publish a separate period for those logs and does not treat them as a mailing list.
If you ask the company to delete an enquiry, the company will do so unless it needs to keep the message for a reason the law allows — for example to show what was agreed if a dispute is underway, or to comply with a duty that actually applies. The rights section explains how to ask.
Security
The form is a normal web submission. The script removes line breaks from the name and the email address so those fields cannot be used to add extra email headers. It checks that the email address is shaped like an email address. It limits how long each field may be. It refuses the honeypot and the too-fast submission. Those are modest protections against abuse of the form. They are not a certification, and the site does not claim a security accreditation.
You should send the form only over the website as published. Do not email passwords or card numbers to the mailbox. Once a message is in the mailbox, the company is responsible for handling it as correspondence: not forwarding it casually outside the company, and not posting it on the site. No website can honestly promise that email or a server can never be interfered with. The company takes the care that fits a correspondence mailbox. It does not operate the form as a vault for secrets.
If the company becomes aware that an enquiry email has been disclosed to someone who should not have it, and that disclosure is likely to result in a risk to people, the company will consider the duties that UK law imposes in that situation, including telling the people affected and the Information Commissioner’s Office where the law requires it. This policy does not predict a breach. It records the approach.
Transfers outside the United Kingdom
The company is established in Edinburgh and the mailbox is the published address at driveritics.study. The site does not add a United-States analytics tool or an advertising transfer. Email and hosting can still involve infrastructure that is not physically in the United Kingdom, depending on how the mailbox and the server are provided. The company has not published the name of those providers on this website, and this policy does not invent a list of countries or a set of transfer contracts that have not been stated.
What can be said accurately is this. The enquiry is sent so the company can read it. It is not sent to a public social network. It is not placed on an advertising exchange. The font request, if your browser makes it, goes to Google’s font service and is governed by that service’s own handling of the connection. The company does not receive a copy of that font request into its mailbox. If a future change to the site introduced a tool that transfers personal information in a new way, this policy would need to be updated before that tool was used to describe the site honestly.
Children
The website is a business site about software publishing and engineering. It is not directed at children, and the form is not provided as a service for children. The company does not knowingly collect information from a child through the form. If you are a parent or guardian and you believe a child has sent a message, write to network@driveritics.study and the company will delete the enquiry unless there is a compelling reason, which is unlikely for this kind of site, to keep it.
Marketing
The form is not a signup to a newsletter. Sending an enquiry does not opt you in to marketing email. The company does not operate a marketing list from this website. A reply to your enquiry is not marketing. If the company ever wanted to send messages that are marketing rather than a reply to something you asked, it would need a proper basis for that, and this site would have to say so. It does not do that now. You will not be asked to untick a pre-ticked marketing box, because there is no such box.
Your rights
UK data-protection law gives people rights over personal information. They are not absolute. Some apply only in some situations. The following sections say what each right means for this website and this company, and how to use it. A request should be sent to network@driveritics.study. It helps to use a subject line that says it is a privacy request, to say which right you want to use, and to use the email address you used on the form so the message can be found. The company may need to ask for enough information to be sure it is dealing with the right person, and it will not ask for more than it needs for that check.
The company will respond within the time UK law allows, which is generally one month, and it will say if it needs more time for a complex request. There is no fee for a reasonable request. If a request is manifestly unfounded or excessive, the law allows a fee or a refusal, and the company would explain that rather than ignore the message.
Access
You can ask whether the company is processing personal information about you and, if it is, ask for a copy of that information and for certain details: the purposes, the categories, the recipients, the retention approach, and the existence of your other rights. For this site, that will usually mean the enquiry email and the correspondence that followed it. It will not mean a browsing history, because the site does not keep one. If host logs exist and can be tied to you, a request can cover those too, to the extent the company actually holds them and can find them without a disproportionate search. The company will not hand over information that is entirely about someone else. Where a document can be partly shared, it will separate the parts if that is practical.
Correction
You can ask for inaccurate personal information to be corrected, and for incomplete information to be completed where that is relevant to the purpose. If your email address was mistyped and the company is writing to the wrong place, say so. If a later reply has misunderstood your name, say so. The company will correct correspondence it still holds. It will not rewrite history by pretending an earlier email said something it did not say. A correction can sit beside the original where that is the honest record.
Erasure
You can ask for erasure in the situations the law describes. The ones most likely to matter here are: the information is no longer needed for the enquiry or the record of it; you object to a legitimate-interest use and there is no overriding reason to keep it; or the information has been used unlawfully. If the enquiry became part of a contract or of a record the company must keep, erasure can be refused for that part, and the company will say why. If the message was never stored because it failed to send, there may be nothing to erase. The company will tell you that rather than invent a deletion.
Restriction
You can ask the company to restrict processing in certain cases: while accuracy is being checked, where the use is unlawful but you prefer restriction to deletion, where the company no longer needs the information but you need it for a legal claim, or while an objection is being considered. Restriction means the company keeps the information but stops using it except for limited reasons, such as defending a claim or protecting another person’s rights. For a live enquiry, restriction may mean the company pauses the conversation until the question is resolved.
Portability
The right to data portability applies to information you provided, where the basis is consent or a contract, and where the processing is automated. An enquiry email is information you provided. Where the basis is a step toward a contract, portability can apply to what you sent. The company can provide that text in a common format, which in practice means the message itself. Portability does not require the company to hand over its own notes about whether it wants to take on a brief. Where the only basis is legitimate interests, portability does not apply, though access still can.
Objection
You can object to processing that is based on legitimate interests. The company will stop unless it can show a compelling reason that overrides your interests, or unless it needs the information for a legal claim. Objecting to the handling of a message you want answered is likely to end the conversation, and the company will say so. You also have a right to object to direct marketing. The site does not send direct marketing. If you ever received a marketing message that claimed to come from this site, treat it as unauthorised and tell the company.
Automated decisions
The site does not make a decision about you by automated means that produces a legal effect or a similarly significant effect. The form’s checks — whether an email address is valid, whether a message is long enough, whether a hidden field was filled — only decide whether that one submission is emailed. They do not decide whether you are offered work, credit, or access to anything else. If a check refuses a message, you can write directly to the mailbox or telephone the company. There is no score, and there is no review queue beyond reading the message a person actually sends.
Complaints
You can complain to the company first, at network@driveritics.study. You can also complain to the Information Commissioner’s Office. The ICO’s address is Wycliffe House, Water Lane, Wilmslow, Cheshire, SK9 5AF. The helpline is 0303 123 1113. Complaints can be started at https://ico.org.uk/make-a-complaint/. You do not have to contact the company before you contact the ICO. This policy is written for the United Kingdom because that is where the published address sits. The company does not claim to be established in another country in order to choose a different regulator.
How to reach the company
Privacy requests and questions about this policy go to network@driveritics.study. You may also write to DRIVERITICS LTD, Summit House, 4-5 Mitchell Street, Edinburgh, EH6 7BD, United Kingdom, or telephone +44 7911 123456. Please say that the contact is about personal information so it is not read only as a new project brief. The contact page of the website can be used for the same purpose. Do not send copies of identity documents unless the company has asked for a specific check and has explained why.
Related pages: the cookie policy describes the cookies this site does and does not use. The terms of service and the terms and conditions describe use of the website. They do not replace this policy on questions of personal information.
Changes to this policy
If the site starts to collect information in a new way — for example if a real analytics tool, a new form field, or a customer login were added — this policy would be updated to describe that change before it was presented as the current practice. The date at the top of the page is the date of this version. Older versions are not kept on the site as a public archive. A change that only clarifies wording, without a new use of information, may be made by updating the page and the date. A change that introduces a new use would be described in enough detail that a reader can see what is different.
Reading the site after a change means you see the policy as it stands. It does not, by itself, change the basis on which an old enquiry was collected. An enquiry already sent continues to be handled for the purposes stated when it was sent, unless the law requires something else or you and the company agree a different handling.