Privacy policy
Privacy notice
This notice explains how the Coder Link website handles your information today. It describes what the site actually does in its current form, not what it might do later.
Last updated: 10 September 2026
What this website does
In its current form the site is a set of informational pages about the company and its services. There are no user accounts, no sign-in and no checkout.
The quote and contact forms
The forms on this site do not send your details to a server of ours. What you type is assembled inside your browser into a single message, and you choose whether to send it over WhatsApp or email. Anything that reaches us does so because you sent us that message, not because the website stored it.
Contacting us by WhatsApp or email
If you continue the conversation over WhatsApp or email, those services operate in their own environments under their providers' terms. What we see is the content of the message you sent us.
Analytics, cookies and your choice
This site uses Google Tag Manager, a Google service, to load measurement tags that we have approved. Loading it means your browser requests a file from Google’s servers, as with any file fetched from Google; on its own it does not set analytics cookies. The measurement tag we intend to use is Google Analytics 4, which helps us understand how the site is used — for example which pages are visited, the type of device and browser, and the general region a visit comes from. Google Analytics runs only if you choose “Accept analytics”. Until you make a choice, and whenever you reject it, analytics stays switched off. When you accept, Google Analytics sets its own cookies in your browser and sends usage data to Google, which processes it under Google’s own terms. We have not enabled advertising features, Google Ads or Google Signals.
Remembering your choice
Your analytics choice is saved in your own browser, in local storage under the name “cl-consent”, so that we do not ask on every page. It records only the choice and when it was made, and it is not sent to our server. This record does not contain your name, email address or other contact details. We ask again after 12 months. You can change your choice at any time from “Privacy settings” at the bottom of every page. If you withdraw your consent, the site removes the Google Analytics cookies it set in your browser. The site works the same whichever choice you make.
Technical data and hosting
This website is served over HTTPS from a private server operated by Coder Link. Like any web server, it records basic technical data in its ordinary operational logs — such as IP address, browser type and the page requested — which we use to keep the site available and secure and to investigate faults or abuse. We do not use those logs to build a profile of you.
Service providers we rely on
We keep the number of third parties small and name only the ones we actually use. Our server is rented from a hosting provider, so that provider necessarily operates the machine this site runs on. For disaster recovery we send encrypted backup archives to two offsite destinations: Google Drive and Cloudflare R2 object storage. Those backups are described in the sections that follow. For measurement we use Google Tag Manager and, only with your consent, Google Analytics 4 — both provided by Google, as described above. We use no advertising provider.
Google user data and our use of Google Drive
Coder Link uses Google Drive as one offsite destination for backups of its own servers. This is an internal infrastructure process. It is not a feature of this website and not a Google Drive integration offered to customers: no visitor to this site signs in with Google, and we never request access to a visitor’s or a customer’s Google Account. The Google Account involved belongs to Coder Link, and the only person who authorises it is a Coder Link administrator.
What Google access the backup process requires, and why
The backup software on our servers authenticates to that Coder Link Google Account using Google OAuth. The access it requests today is Google Drive access, and that authorisation is currently broad rather than restricted to files the application itself created. We state this plainly rather than describe a narrower permission than the one actually in force. In practice the process uses it for three things only: writing encrypted backup archives into a dedicated backup folder, reading back the size of a file it has just written so the upload can be verified, and checking how much Drive storage remains before an upload begins. It does not browse, read or modify unrelated files, and it is used for no purpose beyond backup.
What Google Drive receives, and what we never do with it
Backup archives are compressed and encrypted with AES-256 on our own server before they leave it, so what is stored in Google Drive is encrypted data and a checksum file, not readable content. We do not sell Google user data, do not transfer it to third parties other than as part of the backup process described here, do not use it for advertising, and do not use it to develop, improve or train artificial-intelligence or machine-learning models. Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Protecting the Google credentials, and withdrawing access
The OAuth credentials used by the backup process are held in a file readable only by the administrator account on the server that performs the backup. They are not present in this website, not in our published source code, and not shared outside the small group that administers our infrastructure. Because the authorisation belongs to a Coder Link Google Account, its owner can withdraw it at any time from the Google Account permissions page, which stops any further upload immediately. If you have a question about this integration, write to us at the address at the end of this page.
Keeping information
The website does not store form data in the first place, so there is no retention period to state for it. Messages that reach us over WhatsApp or email remain within those channels and our accounts on them. Backup archives are a separate matter: they are kept for as long as we need them for disaster recovery, older copies are removed on a rolling schedule at the object-storage destination, and copies held in Google Drive are deleted by us when they are no longer needed.
Security
The site is served over HTTPS. Backup archives are encrypted before they leave our server and are checked after upload to confirm they arrived intact, and the credentials that process uses are restricted to the administrator account on the machine that runs it. We handle what reaches us with reasonable professional care. No one can guarantee absolute security for communication over the internet, and we do not offer that guarantee.
Your choices
Analytics runs only with your consent, and you can change that choice at any time from “Privacy settings” at the bottom of every page. The site stores no form submissions, so beyond that there is little held about you to act on. If you have written to us and want to know what we hold from that conversation, or want it deleted, write to us: we will tell you what we have and act on your request. Where a legal right applies to you, contacting us is how you exercise it.
Links to other sites
Some pages link to services and products outside this website. Once you follow such a link you are on a site we do not control, and this notice no longer applies — that site’s own privacy terms do.
Changes to this notice
We may update this notice when the way the site works changes — for example if form submission to a server is enabled, or measurement tools are added.