01
Who We Are
The company behind Lakloud, and how to reach us about privacy.
Lakloud is the software studio operated by [Lakloud legal entity], a [entity type] registered in [jurisdiction]. Where this policy says “we”, “us”, or “Lakloud”, it means [Lakloud legal entity].
For the personal data described here, we decide why and how it is processed, except during a client engagement where we act on your instructions — see Our Two Roles.
We have not appointed a Data Protection Officer, as we are not required to. Privacy questions go to the address below and are handled by the people who run the studio.
- Legal entity
- [Lakloud legal entity]
- Entity type
- [Entity type and jurisdiction]
- Registration number
- [Registration number]
- Registered office
- [Registered office address]
02
Scope of This Policy
What it covers, and what it does not.
This policy applies to lakloud.com: the pages you read, the emails you send us, and the correspondence that follows.
It is deliberately narrow, because this site is narrow. There are no forms, no user accounts, no payments taken on the site, and nothing for you to log into.
Client project data
If you engage us to build software, we may process personal data held in your systems. In that situation you are the controller and we act as your processor — see Client and Project Data. The terms of that processing live in a Data Processing Agreement, not in this policy.
If you are not a client
You do not have to be a customer for this policy to apply to you. Reading the site or sending a single email is enough, and the rights described below are available to you either way.
03
Our Two Roles
Controller for this site, processor during an engagement.
Data protection law separates the party that decides why data is processed (the controller) from the party that processes it on someone else's instructions (the processor). We are both, depending on the context.
We are the controller of enquiry data
The emails you send us and our replies, our engagement and billing records, and the technical data generated when you request a page. We decide what is kept and why, and this policy is our notice to you about it.
We are a processor of client project data
Personal data inside a client's systems that we touch while building or maintaining software for them. The client decides what that data is and why it exists; we act on their documented instructions and delete or return it at the end of the engagement.
NoteThe distinction has a practical consequence. If you ask us to delete an email you sent, we act on it directly. If you ask us to delete personal data about you that sits inside a client's product we happen to have built, we will refer you to that client, because the decision is theirs and not ours to make.
05
What We Do Not Collect
Worth stating explicitly.
Much of what a privacy policy usually has to explain simply does not happen here. To be unambiguous about it:
- No analytics — there is no Google Analytics, no Tag Manager, and no other measurement tool running on this site
- No cookies, no advertising or tracking pixels, and no cross-site tracking of any kind
- No forms, accounts or passwords — there is nothing on this site to fill in or sign in to
- No payment data — the site takes no payments; client invoicing happens outside the site
- No data brokers — we do not buy personal data or enrich your details with purchased information
- No sale of personal data, and no sharing of it for cross-context behavioural advertising
- No newsletter or marketing list — we do not add you to a mailing list because you emailed us
- No special category data is requested at any point; please do not send us health, biometric, political, religious, or similar information
NoteWe also do not train machine-learning models on your messages or on client material, and we do not paste client confidential information into third-party AI tools.
06
How We Use Information
Every purpose, and no others.
- Answering your email — reading it, replying, and having the follow-up conversation.
- Scoping and proposing work — turning a brief into an architecture, an estimate, and a Statement of Work.
- Delivering an engagement — communicating with your team and doing the work we were contracted to do.
- Business administration — invoicing, accounting, and keeping the records the law requires us to keep.
- Security — keeping the site available and investigating misuse of it.
- Legal compliance — meeting our tax and regulatory obligations and responding to lawful requests.
NoteWe do not use your email to market to you beyond replying to it. If you write to us once and we do not end up working together, you will not hear from us again unless you get back in touch.
07
Legal Bases for Processing
Why each use is lawful under the GDPR and UK GDPR.
If you are in the European Economic Area, the United Kingdom, or Switzerland, we must have a lawful basis for each purpose. Ours are:
- Steps prior to a contract, and performance of a contract (Art. 6(1)(b)) — answering your enquiry, preparing a proposal at your request, and then delivering and invoicing an engagement.
- Legitimate interests (Art. 6(1)(f)) — keeping the site available and free of abuse, retaining correspondence so we have a record of what was agreed, and holding engagement records for the ordinary running of the business. We have weighed these against your rights and collect the minimum each requires.
- Legal obligation (Art. 6(1)(c)) — retaining financial and tax records, and responding to valid legal process.
Objecting to legitimate interests
Where we rely on legitimate interests you have the right to object, and we will stop unless we can show compelling grounds that override your rights. Write to us and say so; you do not need to give a reason for an objection to direct marketing.
08
Cookies and Browser Storage
A short section, because there is little to say.
This site sets no cookies and runs no analytics, so there is no consent banner to answer. In normal browsing it stores nothing in your browser at all.
Fonts and scripts are served from our own domain rather than a third-party CDN, so loading a page makes no request to any other company's servers.
NoteThe full detail — including the one technical entry the site can write if a page fails to load — is in our Cookie Policy.
09
Client and Project Data
When we process personal data on your instructions.
During an engagement we may be given access to systems containing personal data about your customers, staff, or users. We treat that data as yours throughout.
We process it only on your documented instructions, only for the purposes of the engagement, and only by people who need it. Our team and subcontractors are bound by confidentiality obligations that survive the engagement.
- Clients subject to the GDPR, UK GDPR, or a comparable regime should ask for a Data Processing Agreement before an engagement involving personal data begins
- We prefer to work against anonymised, masked, or synthetic data in development environments, and will ask for it wherever a project allows
- Access to production systems is requested only where necessary, used only for the engagement, and surrendered at handover
- At the end of an engagement we return or delete client data on request, subject to any retention the law requires of us
ImportantPlease do not give us access to live production data containing personal information without agreeing the basis for it in writing first. If personal data reaches us in a way neither of us planned, tell us and we will work with you to contain and delete it.
10
Who We Share Information With
The complete list of recipients.
We do not sell personal data and we do not share it for advertising. Data reaches a third party only in the situations below.
| Recipient | Why | Where |
|---|
| [Hosting provider] | Hosting and delivery of lakloud.com, including network-level protection against abuse | [Region] |
| [Email provider] | Hosts the mailbox that receives and stores the emails you send us | [Region] |
| Professional advisers | Accountants and, where necessary, lawyers — for tax, audit, and legal advice | [Region] |
| Subcontractors | Vetted specialists working on an engagement, bound by confidentiality obligations no less protective than ours | Varies by engagement |
Legal disclosure
We may disclose data where compelled by law or by a court or regulator, or where necessary to establish, exercise, or defend a legal claim. Where we are legally permitted to tell you first, we will.
Business transfer
If Lakloud is involved in a merger, acquisition, or sale of assets, data may transfer as part of that transaction. Any acquirer would remain bound by this policy or give you notice before changing it.
11
International Transfers
Where your data goes.
Our records are held in [country or region]. If you are elsewhere, emailing us involves transferring your data there.
Where a transfer from the EEA or UK requires a safeguard, we rely on the European Commission's Standard Contractual Clauses, and the UK Addendum where the UK GDPR applies, together with the additional measures appropriate to the small amount of data involved.
Our hosting provider may serve a page to you from a location near you. You can ask us for a copy of the transfer safeguards we rely on.
12
How Long We Keep Things
Retention periods, and what happens at the end of them.
We keep personal data only as long as it serves the purpose it was collected for, or as long as the law requires.
| Data | Kept for | Then |
|---|
| Enquiry that goes nowhere | Up to 24 months from your last message | Deleted from the mailbox |
| Enquiry that becomes an engagement | Kept with the engagement records | See below |
| Engagement records and correspondence | 7 years after the engagement ends | Deleted |
| Invoices and financial records | As long as tax and accounting law requires | Deleted |
| Client project data we process | Duration of the engagement | Returned or deleted at handover, on your instruction |
Why engagement records last as long as they do
Professional services carry a long tail of potential claims, and contract and limitation periods run for years after a project ends. Keeping the record of what was scoped, agreed, and delivered protects both sides if a question arises later.
Asking for earlier deletion
You can ask us to delete your emails at any time and we will, unless they have become part of a live engagement or we need them to defend a legal claim. Say so in an email and we will confirm when it is done.
13
Security
How the small amount of data we hold is protected.
We keep the attack surface small on purpose. A site with no forms, no database, and no accounts has very little to lose in the first place — the only personal data we hold is in our mailbox and our business records.
- The site is served over HTTPS, with traffic encrypted in transit
- The site has no database and stores nothing you send it
- Access to the mailbox that receives your emails is limited to the people who need it and protected by strong, unique credentials and multi-factor authentication
- Client systems are accessed only with credentials issued for the engagement, and access is surrendered at handover
ImportantNo system is perfectly secure, and email in particular is not a confidential channel. Do not email us credentials, API keys, personal data about other people, or regulated data. If something sensitive needs to reach us, ask and we will agree a proper method first.
14
If Something Goes Wrong
Breach notification.
If a personal data breach occurs and it is likely to result in a risk to your rights and freedoms, we will notify the relevant supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware of it.
Where the risk to you is high, we will tell you directly and without undue delay, describing what happened, what data was involved, what we are doing about it, and what you can do to protect yourself.
Where we are acting as a processor for a client, we notify that client without undue delay so they can meet their own obligations, rather than notifying regulators or individuals ourselves.
15
Your Rights
What you can ask us to do.
If you are in the EEA, the UK, or Switzerland, the GDPR and UK GDPR give you the rights below. We extend the substance of them to everyone who writes to us, wherever they are, because operating two standards for a handful of records would be pointless.
- Access — a copy of the personal data we hold about you, and an explanation of what we do with it
- Rectification — correction of anything inaccurate or incomplete
- Erasure — deletion, where we have no overriding reason to keep it
- Restriction — a pause on processing while a dispute about accuracy or legitimate interests is resolved
- Portability — the data you gave us, in a structured, machine-readable format
- Objection — to processing based on legitimate interests, and absolutely to direct marketing
How to exercise them
Write to [email protected] saying what you want. We respond within 30 days, and will tell you if we need longer because a request is complex. There is no charge unless a request is manifestly unfounded or excessive.
Verifying who you are
We may need to confirm your identity before acting, which normally means replying from the email address the data is associated with. We will not ask you for identity documents to answer a request about an email address.
Complaining
You can complain to your local supervisory authority — in the UK, the Information Commissioner's Office; in the EEA, the authority for your country. We would rather you raised it with us first so we have a chance to put it right.
16
US State Privacy Rights
California, and other states with comparable laws.
Residents of California and of other states with comprehensive privacy laws — including Virginia, Colorado, Connecticut, Utah, and Texas — have rights to know, delete, correct, and obtain a portable copy of their personal information, and to be free from discrimination for exercising them.
We honour these requests through the same channel and the same timescales as the rights above.
We do not sell or share your personal information
Under the CCPA and CPRA definitions, we do not sell personal information and we do not share it for cross-context behavioural advertising. There is accordingly no “Do Not Sell or Share My Personal Information” mechanism to offer — there is nothing for it to switch off.
Categories collected
In the twelve months preceding the date at the top of this page, we have collected identifiers (name, email address, IP address) and the content of any email you chose to send. We disclosed these for business purposes only, to the recipients listed under Who We Share Information With.
Sensitive personal information
We do not request or intentionally collect sensitive personal information, and we do not use or disclose it for purposes requiring a right to limit.
Authorised agents
You may use an authorised agent to submit a request. We will ask for written proof of their authority, and may ask you to confirm it directly.
17
Children's Privacy
This is not a service for children.
This site is aimed at businesses and the people who run them. It is not directed at children, and we do not knowingly collect personal data from anyone under 16.
If you believe a child has emailed us, tell us and we will delete the message promptly.
18
Automated Decision-Making
There isn't any.
We do not carry out profiling or automated decision-making that produces legal or similarly significant effects. A person reads every email and a person decides whether we take a project on.
19
Links to Other Sites
Where this policy stops applying.
The site links to our profiles on LinkedIn, GitHub, X, and Dribbble. Following any of those links takes you somewhere governed by someone else's policy.
Nothing loads from those services while you are on our pages, and we receive no notification that you followed a link. We are not responsible for their content or their privacy practices.
20
Changes to This Policy
How updates are made and communicated.
We may update this policy as the site or the business changes — for example, if we add a contact form or analytics. The “Last updated” date at the top always reflects the most recent revision, and any such addition will be described here before it goes live.
Where a change materially affects how we use data we already hold about you, and we have a way to reach you, we will tell you directly rather than relying on you to re-read this page.