Kerbline privacy notice

The short version

Kerbline is a communication and record-keeping tool for construction sites. Site teams send messages and photographs. Each photograph records the time our servers received it, and whatever time and location the sending device reported — so there is a contemporaneous record of what was done, made at the time rather than reconstructed afterwards.

In plain terms:

• Your employer's account details — the name, email address and billing information of the company that subscribes to Kerbline — are held by us, and we decide how they are used.
• Site content — the photographs, messages, location stamps and previously recorded voice notes held on a site — belongs to the construction company that runs that site. They decide what is collected and what happens to it. We hold and process it on their instructions.
• We do not delete a paying customer's evidence automatically. A completed site is archived and stays readable. If a subscription lapses, the record becomes read-only but remains accessible. Deletion happens when the customer asks for it. The one exception is a free trial that never became a subscription: its content is deleted 90 days after the trial ends, and we email the company before that happens.
• We do not sell your information, use your site content for advertising, or make automated decisions about you. If you accept cookies in the app, Google Ads tells us which of our adverts brought you to Kerbline; on our website, Google Ads and Meta do (see Cookies and browser storage).
• Some of our suppliers are outside the UK. Where that happens we use the safeguards UK data protection law requires.

If you want to know what we hold about you, or you are unhappy with something, the contact details are below and we will respond within one month.

Contents

Who is responsible for your information

Data protection law distinguishes between a controller (who decides why and how personal information is used) and a processor (who handles it on the controller's instructions). Kerbline sits in both roles depending on the information concerned.

We are the controller for account data. This means the information our business customers give us in order to have a Kerbline account: the names and contact details of the company's Owner and of the people who run its Sites, billing and payment information, registration and security information, and correspondence with us about queries, complaints or support.

We are a processor for site content. This means the material created inside a site: photographs and the location and time recorded with them, messages, albums, the names of the people who sent them, voice notes recorded before 17 September 2026, and the records built from that material such as applications, evidence packs and reports.

Voice notes are no longer collected, and nothing is transcribed. Kerbline stopped recording voice notes on 17 September 2026. No audio is sent to any transcription service, by us or by anyone on our behalf, and nothing in the product converts speech to text. Voice notes recorded before that date are not deleted — they remain stored and remain yours, under the same retention terms as the rest of your site content. They are no longer played back or transcribed inside the product, and any transcript made before that date is no longer displayed or included in exports.

For site content, the construction company that runs the site is the controller. They decide who joins a site, what is recorded there, how it is used and when it is deleted. We hold and process that content on their instructions under a written contract.

Contact details

Post

Email

What information we collect, use, and why

To provide the service

• Names and contact details
• Account information
• Photographs and video recordings
• Messages sent by site users, voice recordings sent before 17 September 2026, and the location data attached to photographs
• If you turn on notifications: for each device you turn them on for, the notification address and keys your browser gives us, the name of your browser, and whether you have message preview turned on for that device

We record the location the sending device reports at the moment a photograph is sent, which is not necessarily where or when it was taken. It is reported by the device and accepted as given. We do not track anyone's location continuously or at any other time.

To operate customer accounts

• Names and contact details
• Payment details, including card or bank information
• Account information, including registration details
• Information used for security purposes

To help new customers get started

During a free trial we show the company’s Owner a short Get started list and an example site of made-up sample data. The list ticks itself off from things that have already happened in the account: when the first site was created, when someone first joined it, when a photo request was first answered and when a report was first exported. We also record when the Owner hides the list or removes the example site. We use only these dates, never what any message or photo says, and we look at them across trial accounts to see where new customers get stuck.

To comply with legal requirements

• Name
• Contact information
• Financial transaction information
• Any other personal information required to comply with a legal obligation

To deal with queries, complaints or claims

• Names and contact details
• Account information
• Correspondence

If you ask for a sample evidence pack

Our website lets you ask for a sample evidence pack without signing up. When you do, we collect:

• Your work email address, and your company name if you give it
• Whether you ticked the box asking for occasional Kerbline updates, and the wording that box showed you
• The language the page was in, which page and which button you used, and when you asked
• Your IP address and your browser's identifying string, which we use to stop the form being used to send the sample to people who did not ask for it

We use your email address to send you the sample, and we tell ourselves about your request so that we can reply to you personally if we choose to. We do not send you anything else automatically. We will only send you marketing emails if you ticked the box, which is unticked until you tick it, and every one of those emails will tell you how to stop them. You can also stop them at any time by emailing hello@kerbline.co.uk.

Lawful bases and data protection rights

Under UK data protection law we must have a "lawful basis" for collecting and using personal information. The list of possible lawful bases is in the UK GDPR, and there is more on the ICO's website.

Which lawful basis applies may affect your rights. In brief, you have:

• The right of access — to ask for copies of your personal information, and for details of where we got it and who we share it with. Some exemptions apply.
• The right to rectification — to ask us to correct information you think is inaccurate, or complete information you think is incomplete.
• The right to erasure — to ask us to delete your personal information.
• The right to restriction of processing — to ask us to limit how we use your personal information.
• The right to object to processing — to object to our processing of your personal information.
• The right to data portability — to ask us to transfer information you gave us to you or to another organisation.
• The right to withdraw consent — where we rely on consent, to withdraw it at any time.

If you make a request we will respond without undue delay and in any event within one month.

Where your request concerns site content, the construction company that runs the site is the controller and the request should go to them. We will help them respond and will pass on any request that reaches us by mistake.

To make a request, use the contact details above.

Our lawful bases

Providing the service

• Contract — we need the information to enter into or carry out a contract with you. All rights may apply except the right to object.
• Legitimate interests — our business customers are construction companies who use Kerbline to keep an accurate record of work carried out on their sites. Site workers join at their employer's request, so we do not have a direct contract with every person whose information appears in the service. We rely on legitimate interests to provide the service to those users.

  The benefit is a clear and reliable record of what was built, by whom and when. That protects workers as much as employers, because disputes about work carried out are common in construction and an accurate record resolves them fairly rather than on memory.

  We keep the impact proportionate. We collect only what makes the record useful: the person's name, the photographs and messages they choose to send, and the location their device reports when a photograph is sent. We do not track location continuously. We do not use anyone's information for profiling or automated decision-making, and we do not sell it. If you accept cookies, we use Google Ads cookies (on our website and in the app) and Meta cookies (on our website only) to measure whether our adverts lead to trial sign-ups; we do not use them for remarketing or personalised adverts. Our customers decide what is kept and for how long, and any individual can contact us to ask what we hold or to raise a concern.

Operating customer accounts

• Contract — we need the information to enter into or carry out a contract with you. All rights may apply except the right to object.

Helping new customers get started

• Legitimate interests: we need to know where new customers get stuck so we can make Kerbline easier to start. We use only the dates above, never to decide anything about a person or to advertise to them. They are kept as account information, for the period described under How long we keep information.

Legal requirements

• Legal obligation — we need the information to comply with the law. All rights may apply except the right to erasure, the right to object and the right to data portability.

Queries, complaints and claims

• Legitimate interests — when someone raises a query, complaint or claim we need to look into it properly. That means keeping a record of the correspondence and, where relevant, looking at the account or site records the query concerns.

  The benefit is that people get a fair answer based on what actually happened rather than on assertion. That applies to individuals as much as to us: someone raising a concern about how their information has been handled, or about work recorded on a site, is better served by us being able to check the record than by us having nothing to check.

  The impact is limited. We look only at information relevant to the matter raised, we keep it no longer than we need to resolve it and to meet any legal time limits that follow, and we do not use it for anything else. Anyone can ask what we hold about them or ask us to stop using it, and we will explain our position if we cannot.

Sample evidence pack requests

• Legitimate interests: sending you the sample you asked for, keeping a record that you asked, and replying to you about it. The benefit to you is getting what you asked for; the impact is limited to the details listed above, and we do not use them for anything else unless you also agreed to updates.
• Consent: sending you occasional updates, only if you ticked the box. You can withdraw your consent at any time, and withdrawing it does not affect the sample or anything we sent before.

For more on our use of legitimate interests, contact us using the details above.

Where we get personal information from

• Directly from you
• From our business customers, who invite their own staff and site workers to join a site and may enter their names when doing so

How long we keep information

Once a customer has paid for a subscription, we do not delete their records on any schedule or timer, and there is no setting that causes them to expire. There is one exception, for free trials that do not become subscriptions, and it is set out below. (The short-lived working records used to send notifications are deleted automatically, as described under Notifications below; they are not records of the site.)

Site content. When a site is completed it is archived. An archived site stays readable — the photographs, messages and records remain available to the customer who owns them. If a subscription lapses, the account becomes read-only: nothing new can be added, but the existing record remains accessible.

Site content is deleted when the customer who controls it asks us to delete it. Because the construction company running the site is the controller of that content, the decision to delete is theirs, and they are responsible for setting their own retention periods in line with their obligations.

Free trials are the exception. Where a free trial ends and no subscription begins, including a trial that ends without a card being added, we keep the site content created during that trial for 90 days from the end of the trial, and then delete it. A subscription whose first payment is never made counts as one that did not begin. This differs from the position for paying customers, whose records we do not delete at all unless they ask us to. The deletion is carried out by a scheduled process in Kerbline. At least 14 days before it, we email the company's Owner with the date it will happen, and nothing is deleted until that email has been sent; if it is sent later than 14 days before the end of the 90 days, the deletion waits until 14 days after it. The deletion removes the trial's sites and their content, and the organisation's record in Kerbline with them; it does not delete anyone's sign-in account. The customer can ask us to delete it sooner, and can export it at any time before it is deleted. If a subscription begins before the deletion, the ordinary position above applies to that content permanently and the 90-day period has no further effect.

Account data. We keep account information for as long as the account is open, and for up to 12 months after it closes, to deal with any questions or disputes that follow. Financial records — invoices, payment records and related correspondence — are kept for six years from the end of the relevant accounting period, as required by UK tax law. We carry these deletions out ourselves as part of a periodic review rather than automatically, which is why nothing in Kerbline expires account data on a timer.

Correspondence. The conversation that follows a query, complaint or support matter — the emails and messages we exchange with you to resolve it — is kept for as long as needed to resolve the matter and to meet any legal time limits that follow, and then deleted when we next review what we hold.

Enquiries you send us. When you use the contact form on our website — to raise a data protection complaint, report a bug, ask about the product, or anything else — we keep a record of what you sent, so that we can deal with it and, where it matters, show that we did. We keep a general enquiry for up to 12 months, and a data protection complaint for up to three years, because that record is our own evidence that we received your complaint and handled it properly, which we may need to rely on for longer than an ordinary enquiry. These are the outside limits we work to; we delete them during a periodic review rather than on an automatic schedule.

Sample evidence pack requests. We keep a request for up to 12 months, to deal with any reply or question that follows. If you agreed to updates, we keep the record of that agreement for as long as we send you updates, and for 12 months after you ask us to stop, so that we can show you agreed and that we stopped. These are the outside limits we work to; we delete requests during a periodic review rather than on an automatic schedule.

Notifications. If you turn on notifications, we keep the notification address your browser gave us for that device until you turn notifications off on it, sign out of it or delete your account, or until the notification service tells us the address no longer works. If someone else turns on notifications on the same device, their address replaces yours.

The records behind notifications are deleted automatically. So that notifications can be sent, we record for every message and photo request which conversation it was in, who sent it and when — never what it said — and, for each device notified, whether the notification was delivered. We delete these records after seven days. While you have a conversation open, the app also tells our server so that you are not notified about messages you are already reading; that note lapses within a minute and is deleted within a day. Apart from the free-trial deletion described above, these are the only things Kerbline deletes on a timer. They are working records for sending notifications, not site content, and the messages themselves are unaffected.

If the app crashes. Nothing is sent to us. The details are written to your own device's console so that you can read them out to us if you choose to get in touch, and they go nowhere else.

If you report a bug from inside Kerbline. We receive what you type, the screen you were on, and your browser's identifying string. You may also attach a screenshot. A screenshot shows whatever was on your screen, so if you were looking at the Chat or Photos screen it will contain messages and photographs. Kerbline shows you the image and tells you this before it is sent, and you can send the report without it. Screenshots are held in the same private storage as the rest of your files.

How long we keep bug reports. Until the fault is fixed and any follow-up is closed. We delete them by hand when reviewing open reports; we do not run an automatic expiry on them. (A screenshot attached by someone in a free trial that never became a subscription is deleted with the rest of that trial's content.)

Evidence pack verification records. When someone produces an evidence pack, we record a short entry for it — a checksum of the pack's contents list, how many items it held, when it was produced, and internal references to the pack, the site and the organisation. It contains no site content: no photograph, no message, no caption, no name, no location. Anyone holding the pack can check that entry at the address printed on its cover, without signing in, which is the point of it. We keep it for as long as the organisation's account exists, and it deliberately outlives the deletion of the content it describes, so that a pack already in someone else's hands can still be shown to be genuine. It is deleted when the site or the organisation is deleted.

Who we share information with

This section covers two different things, and the difference matters. Most of it is about companies we have chosen and have a contract with, who handle information for us. The last part is about two organisations we have no contract with at all, which your own browser contacts directly on two particular screens. We have kept them apart rather than running them into one list, because what we can promise about them is not the same.

Data processors

These are companies we have a contract with. They process personal information on our instructions and only for the purposes we set, they are bound by obligations at least as strict as our own, and we remain responsible to you for what they do with it. The same list, with what each one handles, is kept on our sub-processors page.

• Supabase Pte. Ltd. — database and file hosting Singapore company; our data is stored in the United Kingdom Hosts our database and file storage, including all site records, photographs, messages and retained voice notes. Supabase serves stored files through Cloudflare, Inc. as their own sub-processor. Supabase also sends the email that account security depends on — your sign-up confirmation, any re-send of it, and password resets. Those messages go to the address on your account and contain no site content. Every request the app makes to Supabase carries a short identifier for the version of Kerbline you are running, which appears in Supabase's request logs. It identifies the code, never you.
• Cloudflare, Inc. — backup storage United States company; the backups are stored in the European Union Since 20 September 2026, keeps a nightly copy of every file in our file storage, including every photograph, so that they can be recovered if the originals are lost. The copies are held in Cloudflare R2 storage restricted to the European Union, encrypted in transit and at rest. We keep the last 30 nightly copies, so a file deleted from Kerbline stays in the backup for up to 30 days before it is removed.
• Anthropic Ireland, Limited — artificial intelligence services Anthropic’s US-based infrastructure, and the text may also be processed in other regions. We contract with Anthropic Ireland, Limited (Ireland), Anthropic’s contracting entity for UK customers Translates messages in a site’s chat between the languages people on that site read. The message text is sent to Anthropic; names, email addresses, photographs and location data are not, though a message can contain anything its sender typed. Group chats and direct messages are not translated. Anthropic’s documented policy is to delete what we send, and the translation it returns, within 30 days, keeping it for longer only where it is flagged under Anthropic’s usage policy (up to 2 years) or where the law requires it. By default, Anthropic does not use data sent through its commercial API to train its models. The translation is then stored on the message permanently, alongside the original and labelled as automatic, with a record of which model produced it and when — the original is never replaced. Messages sent before that person joined can also be translated on request, including on a completed site, and translations continue to be produced for anyone who still has access to the site, including those who have moved on from it.
• Plus Five Five, Inc. (Resend) — email delivery United States Delivers the account emails described under Supabase above — sign-up confirmation and password resets — and the messages sent by the contact and demo-request forms on our website. Resend never receives site content.
• Stripe Payments Europe, Limited — payment processing Republic of Ireland and United States Processes subscription payments and holds the card and billing information used for them. When a free trial starts, we create a customer record at Stripe with the company name and the Owner's email address, so that the trial can be run and a card added later. No card is needed to start a trial. We do not store full card details ourselves. Stripe has two roles. It processes some data on our behalf, and for card details, fraud prevention, anti-money-laundering and identity checks it acts as an independent controller: it decides for itself how that data is used, under its own privacy policy.
• Railway Corporation — application hosting United States company; our backend runs in the European Union (the Netherlands) Hosts the Kerbline backend application. The backend holds the credentials used to read and write the database, so site content passes through this infrastructure whenever the service is used. It also runs the nightly backup job, so each stored file passes through it on the way to the backup copies described under Cloudflare.
• Vercel Inc. — application hosting United States Hosts the Kerbline web application and marketing site. The application runs in your browser and sends requests to our backend; Vercel serves the application code rather than storing site content.

Push notification services

Only if you turn on notifications, and they are off until you do. A notification cannot be sent to a phone or computer directly. It has to go through the push service run by the company that makes your browser, and your browser chooses which one — we do not. These companies are listed separately because they are not our processors in the sense above: we have no contract with them and cannot give them instructions. We send them only what is described here.

They cannot read your notifications. Each notification is encrypted on our server, using a key that only your device holds, before it is sent. The push service carries it without being able to read it — including the text of the message, when the notification contains it.

What a notification contains. When your device decrypts it, it contains the name of the site or group, the name of the person who sent the message, and the text of the message, shortened if it is long — in your language where a translation already exists when the notification is sent, otherwise as it was written. For a photo it says "Photo"; it never contains a photograph. A photo request says who asked for a photo, not what they asked for.

Message preview is on unless you turn it off, and you can turn it off for each device. In Kerbline, go to You, then Notifications, then Show message preview. With it off, that device's notifications contain only the site or group name and the sender's name — for example "Marek sent a message" — and the text of the message is not sent to that device at all.

What the push service does see: the notification address it issued to your browser, which it can link to that device; that a notification was sent to it and when; its size; and an identifier for Kerbline. That is the information any notification from any app gives the service.

Notifications appear on the lock screen. The site or group name, the sender's name and — unless message preview is off for that device — the text of the message appear on your screen when a notification arrives, including on a locked phone, where anyone who can see the phone can read them. On a phone that other people can see or pick up, such as a shared site phone, turn message preview off. You can also turn notifications off in Kerbline or in your device's settings at any time.

• Apple Inc. — Apple Push Notification service United States Used when Kerbline is added to the Home Screen of an iPhone or iPad, and by Safari on a Mac.
• Google LLC — Firebase Cloud Messaging United States Used by Chrome, and by most other browsers on Android, including Samsung Internet and Edge on Android.
• Mozilla Corporation — Mozilla Push Service United States Used by Firefox.
• Microsoft Corporation — Windows Push Notification Services United States Used by Edge on Windows.

Third parties your browser contacts directly

Two features work by having your own browser make a request straight to another organisation. They are listed separately from the processors above because none of the promises in that paragraph apply to them: they are not our processors, we have no contract with either of them, we give them no instructions, and we send them nothing ourselves — the request goes from your device to theirs without passing through us, so we cannot bind them on your behalf. Each one receives your IP address, as any web request does, along with what is described below. Neither is used for tracking, and neither is contacted from any other screen.

• OpenStreetMap Foundation — map tiles Registered in the United Kingdom; tiles served worldwide by Fastly, Inc. (United States) Supplies the background map, but only when you open the map view of a photo gallery. Nothing is requested until you do, and nothing at all if you never open it. The request tells OpenStreetMap which map squares you are looking at, and that is the point to understand: those coordinates reveal the area you are viewing to within roughly 400 metres, which on a site gallery is the site itself. It also receives the address of the Kerbline page making the request. Around 18 requests are made when the map opens, and more each time you pan or zoom. The Foundation's privacy policy states that data from tile requests is excluded from its guarantee that personal data is held in the UK and the Netherlands.
• Have I Been Pwned — password checking Superlative Enterprises Pty Ltd, Queensland, Australia; hosted in the United States and served through Cloudflare, Inc. Checks whether the password you have chosen appears in a known data breach, so we can warn you before you use it. This happens only when you submit the signup or password-reset form, and only if your password has already passed our own checks — nothing is sent while you are typing. Your password itself is never sent. Your browser hashes it and sends only the first five characters of that hash, which are not enough to work out what the password was. The service returns every leaked hash starting with those five characters and your browser does the comparison itself, and we ask for that response to be padded with decoy entries so its size gives nothing away either.

Others we share personal information with

• Professional or legal advisors
• Organisations we are legally obliged to share personal information with

Sharing information outside the UK

Where necessary we transfer personal information outside the UK. When we do, we comply with the UK GDPR and make sure appropriate safeguards are in place. The safeguard each company relies on is the one set out in its own data processing agreement with us, and is listed below and on our sub-processors page.

Scroll the table sideways to see every column.

Where necessary, our data processors may also share personal information outside the UK with their own sub-processors — for example, Supabase delivers stored files through Cloudflare, Inc. When they do, they comply with the UK GDPR and make sure appropriate safeguards are in place.

The two third parties your browser contacts directly are set out separately, because we cannot put a transfer safeguard in place for a request we do not make. We have no contract with either organisation, and the request goes from your browser to them without passing through us.

Scroll the table sideways to see every column.

The push notification services are set out separately too, and for a similar reason. Unlike the two above, our server does send each notification to one of them — but which one is decided by your own browser, not by us, so we have no contract with any of them and no transfer safeguard we can put in place. They may process the notification outside the UK. This only happens if you turn notifications on, and what they carry is encrypted so that they cannot read it.

Scroll the table sideways to see every column.

How we keep information secure

We take the security of site records seriously, because the value of the service depends on the record being trustworthy.

• Separation between organisations. Every customer's data is separated at the database level. For information your browser requests directly, the database itself enforces the separation. For operations our server performs on your behalf, the server checks your membership of the site before it acts. We test both by attempting access we should not have, rather than by inspection alone.
• Private file storage. Photographs, retained voice notes, profile and site pictures, and any screenshot attached to a bug report are held in private storage. They are not publicly addressable and are served only to authenticated users with a right to see them. An exported evidence pack is not stored at all — it is assembled when you ask for it and sent straight to your browser, so no copy is kept on our side.
• Encryption. Information is encrypted in transit. Files and database contents are encrypted at rest by our hosting providers.
• Authenticated access. Every route that returns or modifies your information requires authentication, and we test new routes without credentials against realistic data before release. There is one deliberate exception: the address printed on an evidence pack cover, which anyone holding the pack can open without signing in. It answers with a checksum, a count and a time, and with nothing else — see evidence pack verification records above.
• Evidence integrity. The account that sent a photograph or message, and the name and role that account held at that moment (on that Site: Owner, Manager, Member or Guest; on or before 5 October 2026, possibly the earlier names Office staff, Site worker or Admin), are recorded when it is sent and cannot be changed afterwards — not by the sender, not by the Owner or any Manager, and not by us. The text of a message cannot be changed once sent. A record cannot be deleted afterwards either, by anyone including us, except through a deletion the controlling customer asks us to carry out or the published trial-data cleanup. Location and time information is captured from the original file before any processing.

No system is perfectly secure, and we do not claim otherwise. If we become aware of a breach affecting personal information we will act on it, notify the ICO where the law requires it within 72 hours, and tell affected individuals and customers where the risk to them is high.

Our access to your information

Running Kerbline means our own systems can reach the information inside it. The part of the service that does work on your behalf — sending a message, building an evidence pack, running a report — connects to your organisation's database with an administrative key that the in-app permissions do not restrict. In plain terms: that key can read any site's messages and photographs, and a person operating Kerbline can therefore reach them. We are saying this directly because the rest of this notice would otherwise leave you to assume we cannot, and that would not be true.

What we do with that reach is deliberately narrow. We look at site content only where it is necessary to operate the service — to investigate a fault, recover data, or keep the service running — where you have asked us for support that needs it, or where the law requires it of us. We do not read your messages or open your photographs as a matter of routine, and never to build a profile of you, to advertise to you, or to train anything.

Cookies and browser storage

Our website and the app ask whether you accept cookies for our adverts. Until you choose, and if you reject, no advertising cookies are set and nothing is loaded from Google or Meta.

If you accept, we load Google’s tag for Google Ads (provided by Google Ireland Limited and Google LLC). It sets cookies, such as _gcl_au and _gcl_aw, that tell us which of our Google adverts brought you to Kerbline and whether you went on to start a free trial. Google receives the address of the page, the advert’s click identifier and technical details of your browser, and uses that information as a controller under its own privacy policy. We do not send Google your name, your email address or anything from your sites. The lawful basis is your consent.

On our website only, if you accept, we also load the Meta Pixel, Meta’s advertising tag (provided by Meta Platforms Ireland Limited). It sets cookies, such as _fbp and _fbc, that tell us which of our Facebook and Instagram adverts brought you to Kerbline. It reports three things: that you viewed a page, that you asked for our sample evidence pack, and that you clicked a button to start a free trial. Meta receives the address of the page, the advert’s click identifier, your IP address and technical details of your browser. We do not send Meta your name, your email address, your company’s name or anything from your sites, and we do not use Meta’s “advanced matching”. Meta collects this information jointly with us and then uses it as a controller under its own privacy policy. The lawful basis is your consent. The app does not load the Meta Pixel.

Your choice is kept for six months in a cookie called kerbline_consent, shared between kerbline.co.uk and app.kerbline.co.uk so that you are asked once. On our website a second cookie, kerbline_meta, records that you accepted after we added Meta; if you accepted before that, or only in the app, the website asks you again. You can change it at any time with “Cookie settings” at the foot of any page on kerbline.co.uk, or in the app under You, then Help, then Cookies. Rejecting after accepting removes the Google Ads and Meta cookies that our pages can reach, and from the next page you open nothing more is loaded from either.

We use browser storage in three ways, none of them for tracking. Your sign-in session is held in local storage so you stay signed in between visits. Photographs you take while offline are held in a queue on your device until they can be sent, so nothing is lost on a site with poor signal. If you work on more than one site, the app remembers which one you were last viewing so it opens where you left off.

If you turn on notifications, your browser also keeps a notification subscription for Kerbline, and signing out removes it. The app also remembers, on that device, whether you have closed the offer to turn notifications on, so that it does not keep asking; whether you turned notifications off on that device, so that they stay off; and whether message preview is on for that device.

The language you choose is remembered in your browser, on kerbline.co.uk and in the app. Once you have an account it is also stored on your account, so it follows you to any device.

Apart from the Google tag and the Meta Pixel described above, which load only if you accept, we use no third-party analytics, advertising or tracking on our website or in the app, no third-party scripts and no embedded social media. The Get started dates described under To help new customers get started are kept by Kerbline as part of your account information, not by an analytics or advertising company. Our fonts are served from our own servers rather than loaded from Google.

There are two exceptions, and neither happens on an ordinary visit. If you open the map view of a photo gallery, your browser requests map images from OpenStreetMap, which tells them the area of the map you are looking at. If you submit the signup or password-reset form, your browser sends the first five characters of a hash of your chosen password to Have I Been Pwned to check it against known breaches. Both are described in full under who we share information with. Apart from these, the only other companies your browser contacts are the ones that run Kerbline for us: when you sign in and use the app, it gets its data and photos from Supabase and from our servers at Railway, and paying takes you to Stripe's own checkout page. None of them puts a script on our pages, and all three are listed under who we share information with.

People under 18

Kerbline is a business tool supplied to construction companies for use on their sites. It is not marketed to or aimed at children.

We recognise that some site workers — apprentices in particular — may be under 18. Where that is the case, the construction company that runs the site decides who joins it and is the controller of the content created there. We ask our customers to make sure anyone they invite understands what the service records and why.

If you are under 18 and using Kerbline, the same rights set out in this notice apply to you. If you want to know what is held about you or you are unhappy about something, you can speak to your employer or contact us using the details above and we will help.

How to complain

If you have concerns about our use of your personal information you can complain to us:

Email: privacy@kerbline.co.uk
Post: 1 Martins Cottages, Church Lane, Bulphan, Upminster, RM14 3TS, United Kingdom

If your complaint is about site content, we will tell you which of our customers controls that record and pass your complaint to them.

If you remain unhappy after raising a complaint with us, you can complain to the Information Commissioner's Office.

ICO address:
Information Commissioner's Office, Wycliffe House, Water Lane, Wilmslow, Cheshire, SK9 5AF

Helpline: 0303 123 1113
Website: https://www.ico.org.uk/make-a-complaint