Privacy policy

1. Data controller

The data controller responsible for your personal data is:

This policy covers this Website, your EpiSensor account, and the parts of the EpiSensor Edge application that talk to episensor.com: licence checks, feedback reports, and the daily usage summary described in sections 2.9 and 2.10. Data that stays inside your own Edge installation, such as sensor readings and device configuration, is yours and is never sent to us by Edge.

2. Data we collect

We collect and process the following types of personal data:

2.1 Website analytics

We use Plausible Analytics to count visits to the public pages of this Website. Plausible is hosted in the EU, sets no cookies, stores nothing in your browser, and does not track visitors across websites.

Each page view sends the address of the page, the site that referred you (never the page you came from), and the country, browser, operating system and device type that Plausible works out from your request. We remove the query string and the fragment from the address before it is sent, except for the campaign tags (utm_source, utm_medium, utm_campaign, utm_content, utm_term and utm_id) that we put on links in our own advertising, and only when each one is a short lower-case word. So a search you run, a link someone sent you, or a code in an address never reaches Plausible.

Some actions are counted as named events. Each event carries only values from a fixed list that we publish in our code, never free text:

• clicks on a few tagged buttons, such as Download in the menu, the buttons at the end of a page (which of the buttons), and asking how a directory score is worked out;
• opening an email or phone link (which of the two, whether it sits in the page footer or the page itself, and whether it is our sales, support or general address or number), copying our phone number or email address with its copy button (which of the two and which of those three, never what was copied), a document on this site (the address of the document, its type from a fixed list such as datasheet, user guide or whitepaper, the product family it belongs to, and where on the page the link sits), and a link to another website (the name of that website only, never the full address);
• opening, starting and submitting an enquiry form (the name of the form, whether it opened in the page, in a side panel or full screen, which kind of button opened it, such as the menu, the top of a page or the end of a page, and, when you came from a System Builder plan, a guide, an article or a directory, which of those kinds of page, never its name), and, once the form is stored, whether it was a sales enquiry and the answers you chose from the form's fixed lists: what you came to talk to us about, your role, the number of sites as a range, when you plan to start and the kind of partnership, and, for a request for missing documentation, the product and the type of document, never what you typed into it, such as your name, company, message or the words you gave under "Something else". We also count viewing a form step (the name of the step from a fixed list), attempting to submit a validated form, and a form error (the error category, such as validation, rate limit, server, unconfirmed response, timeout or network, never the error message or field values);
• using System Builder (where you opened it from, the number of each step you answer, and reaching a recommendation or a question for an engineer, with the name of that route and whether it is a recommendation or a review), reading a plan it built (the goal you chose from its fixed list, a band for the number of lines, and whether any point needs an engineer's review), sharing a plan by copying its link or printing it (which of the two, that it was a System Builder plan, and its goal, never the link), asking for a quote for a plan, and being sent to it from a tool, guide or solution page (which kind of page);
• using an engineering calculator, filling it from a preset, copying its result, or printing or downloading a calculation sheet (the name of the tool only, never the values), reading a Knowledge Base article to the end, and following a link from an article to another page on this site (the address of that page);
• searching or filtering a listing (which listing, a band for the number of results such as "1-9", and whether you searched or filtered), never the words you searched for;
• reading a pricing section (which product), using the Configure button on a hardware page or the Choose hardware link (the product code for Configure, and where on the page it sits), choosing a measurement filter above the hardware list (which filter), configuring a product (the product code), adding an item to the basket (the product code and where you added it), viewing the basket (the number of lines in it) and choosing how to pay (card, quote, purchase order or bank transfer);
• starting checkout (the currency), and requesting a quote, placing an order by purchase order or by bank transfer, or completing a card payment (the currency and the word "card" only), never the amount or the order;
• what you see on the downloads page (for example signed out, or access approved), asking for download access, and starting a software download (the platform and the version);
• being emailed a sign-in code and completing sign-in (whether from a page or a panel, whether the newsletter box was ticked, and whether it was the first sign-in for that email address, never the address), subscribing to the newsletter from an article, a tool or sign-in (which of the three), and starting or submitting a job application (the role only).

Any value that looks like an identifier, such as an email address, an order number or a long code, is discarded in your browser before anything is sent. Plausible uses your IP address only to work out whether a visit is a repeat visit that day, and does not store it. We do not send Plausible your name, your email address, your company, an order number or amount, the words you search for, or anything you type into a form.

Analytics run only on episensor.com. Our staging site is not measured, and account, sign-in, administration and API pages are excluded. On the page you return to after a card payment, the only thing sent is the one event above, with a fixed page address, so the payment reference in that page's address is never sent.

2.2 Contact form submissions

When you submit a contact, configuration, demo, or partner enquiry form on our Website, the form is processed through EpiSensor's own website infrastructure. We collect the information you voluntarily provide, which may include your name, email address, company name, phone number, role, project details, the content of your message, and any files you attach. This data is used solely to respond to your enquiry and route it appropriately.

With each submission we also record the page you sent it from, the page that referred you, which button or directory listing the enquiry came from, the time, your IP address, and your browser's user-agent string. The IP address and user agent serve only to spot abuse of the forms, and are deleted 30 days after submission.

If you are signed in to your EpiSensor account when you send a form, we also record that account's email address with the submission, so that the next form you open while signed in can be filled in with details from your own earlier enquiry, and never with details someone else typed next to your address. It is deleted with the enquiry, and when you ask us to erase your data.

2.3 Customer support data

When you contact our support team (e.g., for warranty or technical issues), we may collect your name, email address, company name, device serial numbers, and details of your support request. This data is used to provide and improve our support services.

A support request becomes a ticket: the messages between you and our team, any files either side attaches, the severity and category, and the record of who changed what and when. You can reply by email, and your reply is added to the ticket. If you sign in with the same address you can read the ticket in your account. Where your address belongs to a company account, the other people in that account can see the tickets, orders and licences of the account as a whole. Section 2.5 explains how an address comes to belong to one.

2.4 Job applicants

When you apply for a role on our careers page, or send us a speculative application, we collect the information you provide in the application form: your name, email address, phone number, location, links to your LinkedIn profile or portfolio, the message you write, and your CV. We may add our own notes and a rating as we review your application. We do not record your IP address or browser details with your application.

We use this data to assess your application, to contact you about it, and, if you are successful, to prepare an employment contract. The lawful bases are taking steps at your request prior to entering into a contract, and our legitimate interest in recruiting for our team.

Applications are kept for 12 months from the date you apply so that we can come back to you if a suitable role opens. You can ask us to keep your details on file for longer, or to delete them at any time, by emailing careers@episensor.com and quoting your application reference. Once the retention period has passed, the application and CV are deleted.

2.5 Account access, policy acceptance and newsletter updates

When you request a sign-in code, we use your email address to send the code and may briefly record your IP address to protect the service against abuse. We use Cloudflare Turnstile on this request to distinguish ordinary visitors from automated abuse. The check connects your browser to Cloudflare, which processes technical request data such as your IP address, browser characteristics, and the result of the security check on our behalf. We receive only the short-lived verification result and do not use Turnstile for advertising or cross-site analytics. By signing in you accept our Terms & Conditions and Privacy Policy, as the sign-in form states. When you enter the code, we keep the time of acceptance, the versions of the documents you accepted, the source of the acceptance, and the IP address used. This gives both you and EpiSensor a clear record of the agreement.

If you fill in your account profile, we keep the name, job title, company and phone number you enter, and the photo you upload if you choose to add one. Where we hold a company account for your employer and have recorded that company's email domains, your address joins that account automatically the first time you sign in. An administrator can also add or remove an address by hand. A company account is what lets you and your colleagues see the same orders, licences and tickets, and everyone in it can see the names and email addresses of its other members.

If you separately choose to receive EpiSensor updates, when you sign in or from the sign-up at the end of a Knowledge Base article or engineering tool, the subscription becomes active only after you enter the code we send to that address. The sign-up uses the same Turnstile check as a sign-in, and its code subscribes the address without signing you in. We keep your email address, any name you provide, the time and source of your opt-in, the time and method of verification, and your subscription status. When you subscribe as you sign in, we also keep which version of the wording beside the updates checkbox you agreed to, so that we can show what you signed up for. We use this information only to send occasional product and company updates. Newsletter delivery is handled by an email service provider acting on our behalf. Every newsletter includes a way to unsubscribe, and opting out does not affect account access.

2.6 Orders, payments and licences

When you buy from our shop or accept a quote, we keep our own record of the sale: your email address, your company name, the destination country, the items and quantities, the prices and currency, any purchase order number and notes you add, the status of the order, and the identifiers that link it to the payment.

Payment is taken by Stripe. Card details are entered on Stripe's own checkout pages and never reach our servers. Stripe collects your billing details, and for physical goods your delivery address, and holds them under its own privacy policy. From that, we keep only what is needed to explain an invoice later: the VAT or other tax identifiers you gave, whether the sale was treated as tax exempt, and the country, city and postcode of your billing address. Street address lines stay with Stripe.

Orders are copied into EpiSensor's own ERP system, which we host ourselves rather than with a third party, as draft customer, quotation and sales order records, so that the order can be fulfilled, delivered and invoiced. Where a sale includes software, the licence we issue records the Gateway serial number it is bound to, the number of licensed devices, and the expiry date.

The lawful bases are performance of our contract with you, and our legal obligation to keep accounting and tax records.

2.7 Software downloads and the Edge application

Some Edge releases are public and some are released to approved customers and partners. When you ask for download access, we record your email address and whatever else you add: your name, company, job title, and what you plan to use Edge for. We record the decision on your request, who made it, and when. Each file downloaded is logged with the release and file, the time, whether it came from the Website, the Edge application, or the automatic updater, and the email address you were signed in with, where you were signed in. We use this to enforce access to pre-release builds and to know which versions are in the field.

When you sign in to the Edge application with an email code, we keep a record of that session: your email address, the name, platform, architecture and version the application reports for the device, the IP address the sign-in came from, and when the session was created, last used and expires. Only a hash of the session token is stored, so our records cannot be used to sign in as you. You can see your Edge sessions, and revoke any of them, from your account.

The lawful bases are performance of our contract with you and our legitimate interest in controlling access to pre-release software and in keeping accounts secure.

2.8 Returns and warranty claims

When you raise a return, we record your email address, the Gateway serial number and the serial numbers of the products being returned, your description of the fault, the return address you give us for the goods, your acknowledgement of the warranty terms, any files you attach, and the progress of the return through to completion. Every return is linked to a support ticket, which is handled as described in section 2.3.

The lawful bases are performance of our contract with you and compliance with our warranty obligations.

2.9 Edge feedback reports

The Edge application has a feedback form for bug reports and feature requests. Nothing is sent unless you fill it in and press send.

What we receive is the contact email address you enter, whether the report is a bug or a feature request, the title, your description, the steps to reproduce if you add them, and up to three attachments (PNG, JPEG, WebP, text, log or JSON files, 5 MB each and 8 MB in total). If you turn on the option to attach recent Edge logs, Edge takes the most recent log lines, caps them, and removes common credential patterns in your browser before they are uploaded. That redaction is automatic and cannot catch every secret, which is why the option is off until you choose it.

The form also offers to share system information. It is on by default, and you can turn it off before you send. When it is on, the report carries a snapshot of the installation: the Edge, front-end and build versions, the branding and hardware profile, the Gateway serial number, the licensed node count and the number of configured devices, the kinds of network connection in use (ethernet, Wi-Fi, cellular or WireGuard), which kind carries the default route, and whether the connection looks constrained, the names of the enabled integrations and how many are disabled, whether a restart or configuration change is pending, and, for the application itself, whether it is running on the web, desktop or mobile, its language, theme and window size, and the Edge page you were on when you sent the report. It does not include credentials, IP addresses, Wi-Fi network names, sensor readings, or any history of what you did in Edge. Because the snapshot carries the Gateway serial number, we can normally match a report to the customer who bought that Gateway.

A report becomes a support ticket in our support system and is handled exactly like any other ticket (section 2.3): our team is notified, we reply to the address you gave, and if you sign in to episensor.com with that address the ticket appears in your account. Feedback reports are not published and are not used for marketing.

The lawful bases are your consent, given by choosing to send the report and choosing what to attach to it, and our legitimate interest in fixing faults and improving Edge.

2.10 Edge usage summaries and licence checks

Once per day, the Edge application can send us a short usage summary. It contains a daily identifier, the Edge version, the front-end version, the build profile, whether the application is running on the web, desktop or mobile, the deployment mode, the language, and whether the browser reports a constrained connection, such as mobile data or a slow link. We store those values with the date and time the summary arrived.

The daily identifier is a one-way hash of the installation's own random identifier and the date, so it changes every day. It lets us avoid counting the same installation twice on one day, and it does not let us connect one day to the next, or a summary to you, your company, your account, your Gateway serial number, or your licence. The summary contains no name, no email address, no serial number, no licence key, no IP address, no sensor data, and nothing about your site, your devices, or what you did in Edge. The sending address is used in the moment to rate limit the endpoint and is not written down with the record. The summaries tell us which versions and platforms are in real use, so that we know what to support, what to test against, and what we can retire.

The summary is on by default. You can turn it off at any time in the Edge application under Display settings, and during first-run setup. Some builds never send it at all. We rely on our legitimate interest in maintaining and improving software that is already in the field, on the basis that a summary cannot be traced back to you. Because nothing in a summary identifies you, we cannot find, export or delete an individual summary on request; turning the setting off stops any further summaries being sent.

Separately, a Gateway running Edge checks its licence with episensor.com about once a day, sending its licence key, its Gateway serial number, and its Edge version. We answer from the licence record created when the licence was issued, and we do not keep a record of the check itself.

2.11 Records of email sent and received

We keep an operational record of the email we send you and of the email you send to our support address. For a message we send, we record the address it went to, its subject line, which template produced it and whether it was delivered. For a message that arrives at support, we record the sender's address, the subject line, and what happened to it: matched to an existing ticket, opened as a new one, or held back because the sender could not be authenticated.

These records exist so that we can answer what happened to a message. The content of a support email becomes a ticket message and is handled as described in section 2.3.

The lawful basis is our legitimate interest in running an order and support service we can account for.

2.12 Optional analytics and advertising

Alongside the cookieless Plausible measurements described in section 2.1, we offer two independent cookie choices. Google Tag Manager, from Google, loads the optional tools only after you accept at least one category. Before you choose, or if you reject both categories, none of these optional tools loads.

• Analytics: Google Analytics shows us which pages and features are used and how visitors move between them. Its first-party cookies recognise your browser across visits. Google receives a page address and referring site sanitised as described in section 2.1, the page title, time, browser details and cookie identifier. It receives your IP address to derive approximate location and the same named events and limited values described in section 2.1. We do not send it anything you typed into a form, email addresses, order numbers or amounts, or search text. Its advertising features, Google signals, run only if you also accept advertising, as described below.
• Analytics: Microsoft Clarity records clicks, scrolling and pointer movement to help us identify confusing pages. Strict masking hides all page text and form fields in recordings. Cookies can connect pages into a visit and recognise returning browsers. Clarity reads the page address directly, so a search term included in an address can reach Microsoft. It never runs on basket, checkout or order confirmation pages.
• Advertising: Google signals, part of Google Analytics, lets Google match the visits Google Analytics records with the Google accounts of visitors who are signed in to Google and have turned on ads personalisation. We use it for aggregated reports of our visitors' age range, gender and interests, and to build audiences so that our adverts can be shown on Google's services, on any of your devices, to people who have visited. Google does this with its own cookies on its own domains; it does not tell us who you are. You can also turn ads personalisation off in your Google account at My Ad Center. Its processing is described in the Google Privacy Policy.
• Advertising: the LinkedIn Insight Tag measures visits and advertising conversions, provides aggregate audience reports and lets us create audiences for LinkedIn advertising. LinkedIn receives the page address, referrer, IP address, browser details and timestamp, and may use cookies and pseudonymous browser identifiers to match visits with LinkedIn accounts. We do not send it form contents or contact details. Its processing is described in the LinkedIn Privacy Policy.

These tools run only on episensor.com. They are excluded from staging, account, sign-in, administration and API pages. On the page you return to after a card payment, only Google Analytics is eligible to run, after analytics consent, with a fixed page address and title. No Google Ads tag is currently enabled.

We rely on your consent for these optional tools (Article 6(1)(a) GDPR). Accept all and Reject all are equally available. Settings lets you choose analytics and advertising separately, both off by default. You can change or withdraw your choice using Cookie settings in the footer at any time. A Global Privacy Control signal keeps advertising off; you can still choose analytics. The Website works without optional tracking. Section 7 describes cookies, stored choices and withdrawal.

2.13 Personal promotional emails

For personal promotional emails, we keep the recipient address and name, the staff accounts responsible for that contact, the message, its campaign and format, approval details, and a record of the Gmail send. An individual random key connects the signature image and website link to that message. The key does not contain your email address.

When an email image is requested or its website link is followed, we record a count and the first and latest request times. Mail privacy services may load images without you reading the email, and security tools may follow links automatically. These records therefore indicate image and link requests, not proof that you read the message or visited personally. We keep known automated requests separate. We do not keep IP addresses or browser identifiers in these campaign records, set tracking cookies, or attach the key to your subsequent browsing on the Website.

You can use the “Stop these emails” link in any such message, or reply asking us to stop. This stops further personal promotional messages to that address. While we still hold the message, the link also unsubscribes that address from our newsletter. If you unsubscribe from the newsletter, we also stop personal promotional emails to you while you remain unsubscribed. Service emails about your orders and account are not affected.

3. Legal basis for processing

We process your personal data on the following legal bases under the GDPR:

• Consent: where you have given clear consent for us to process your personal data for a specific purpose, including the optional analytics and advertising tools in section 2.12.
• Contractual necessity: where processing is necessary for the performance of a contract with you or to take pre-contractual steps at your request.
• Legitimate interests: where processing is necessary for our legitimate interests (e.g., improving our products and services, or understanding aggregate Website use through Plausible), provided these are not overridden by your rights and freedoms.
• Legal obligation: where processing is necessary for compliance with a legal obligation to which we are subject.

Where section 2 names the basis for a particular kind of data, that is the basis we rely on for it.

4. Data sharing

We do not sell your personal data to third parties. We may share your data with:

• Service providers: third-party services that help us operate our business. These providers are bound by data processing agreements and process data only on our behalf. The main ones are Stripe for payments and invoicing, Resend for sending and receiving our email, Plausible Analytics for website analytics, Cloudflare Turnstile for protecting sign-in-code requests from automated abuse, and FedEx, which receives a destination country and postcode, and never your name or address, when the shop quotes a delivery rate.
• Analytics and advertising providers (section 2.12): Google for Google Tag Manager, Google Analytics and Google signals (Google Privacy Policy); Microsoft for Clarity (Microsoft Privacy Statement); and LinkedIn for advertising measurement and audiences (LinkedIn Privacy Policy). These providers receive data only when the relevant optional category is accepted.
• Channel and sales partners: we may share personal information with our channel partners and sales partners for operational purposes, such as order fulfilment and confirming what hardware or software you have purchased. Please note that you may receive marketing communications from these partners based on your relationship with them.
• Legal requirements: where we are required to disclose data by law, regulation, or legal process.

5. Data retention

We retain personal data only for as long as necessary to fulfil the purposes for which it was collected:

• Contact form submissions: retained for up to 2 years from the date of submission, or longer if an ongoing business relationship exists. The IP address and browser details recorded with a submission are deleted after 30 days.
• Customer support data: a ticket and its attachments are deleted 3 years after the ticket is closed. Open tickets are kept for the duration of the customer relationship.
• Edge feedback reports: kept as support tickets, on the same clock.
• Personal promotional campaigns: tracking stops 90 days after a message is prepared for sending. Campaign message records are deleted after 180 days from preparation, or from import for unsent drafts. Contact records and their staff associations are removed 180 days after the last import once no retained campaign messages refer to them. When a message record is deleted, we keep only a hash of its random key and a hash of the recipient address, so that its “Stop these emails” link keeps working; these hashes are deleted 2 years after the message record is deleted, or at once if you ask us to erase your data. We retain a minimal suppression record to honour requests to stop; after an erasure request, or a request made through the link of a deleted message, this contains a hash of the address rather than the address itself.
• Records of email sent and received: the operational record described in section 2.11 is deleted 1 year after the message was sent or arrived.
• Edge usage summaries: deleted once they are more than 400 days old.
• Orders, invoices, and licence records: kept for as long as tax and company law requires us to keep accounting records. These are not deleted on request.
• Returns and warranty claims: kept for the duration of the customer relationship, as evidence of what was returned, repaired or replaced under warranty.
• Download access decisions and download logs: kept while your account exists, and deleted if you ask us to erase your data.
• Edge sign-in sessions: a session expires 180 days after you last used it, and 400 days after it was issued at the latest. The record, including the sign-in IP address, is deleted 30 days after the session expires or is revoked.
• Job applications: retained for 12 months from the date of application, or longer if you ask us to keep your details on file. You can request deletion at any time by emailing careers@episensor.com.
• Access codes: expired and used sign-in-code records, including their IP addresses, are deleted after one day.
• Policy acceptance: retained as evidence of the agreement until you ask us to erase your customer data, subject to any legal obligation to retain it.
• Newsletter subscriptions: retained while you are subscribed. If you unsubscribe, we keep the minimum subscription status needed to honour that choice until you resubscribe or ask us to erase it.
• Website analytics: Plausible retains aggregated, non-personal data only. No personal data is stored.
• Analytics and advertising: Google Analytics keeps event data for 14 months, and its cookies expire after 13 months. Microsoft Clarity keeps recordings for 30 days and heatmaps for up to 13 months. LinkedIn retains advertising information under its own privacy and retention rules, linked in section 2.12.

6. Your rights

Under the GDPR, you have the following rights regarding your personal data:

• Right of access. You may request a copy of the personal data we hold about you.
• Right to rectification. You may request that we correct any inaccurate or incomplete data.
• Right to erasure. You may request that we delete your personal data, subject to certain conditions.
• Right to restriction. You may request that we restrict the processing of your data in certain circumstances.
• Right to data portability. You may request to receive your data in a structured, commonly used, machine-readable format.
• Right to object. You may object to the processing of your personal data where we rely on legitimate interests.
• Right to withdraw consent. Where processing is based on consent, you may withdraw that consent at any time.

To exercise any of these rights, please contact us at info@episensor.com from the email address the data is held under, or tell us which address it is.

The limits are worth stating plainly. An erasure request removes your enquiries and the files you attached to them, your support tickets and their attachments, your Edge feedback reports, your job applications and the CVs attached to them, our notes on them and the record of changes to them, your access codes and policy acceptance, your profile and profile photo, your signed-in website sessions, so that you are signed out everywhere, your Edge sign-in sessions, your download access and download history, our record of the email we sent you and of the email you sent to support, personal promotional messages and their image/link request records, promotional contact records and their staff associations, your newsletter subscription, and your place in a company account. Where you sent an enquiry while signed in under someone else's address, the enquiry stays with them, but the record that it came from your account is removed. It also removes every entry holding your email address in the records of our retired partner and affiliate programmes: old contact and access requests, partner codes, affiliate records and affiliate payouts, promotion codes, and the licence list those programmes kept, which is separate from the licence records described in the next sentence. It does not remove orders, invoices, licence records or support-plan records, or the records we keep in our own accounting and fulfilment systems, which we are required to keep as accounting records, or the record of a return, which is our evidence of what was repaired or replaced under warranty. It cannot reach an Edge usage summary, because nothing in a summary identifies you.

7. Cookies

The strictly necessary episensor_session cookie keeps your basket, sign-in and checkout together. It holds an identifier for the session on our server, cannot be read by browser scripts, and expires after 14 days without a visit. We do not ask for consent to this necessary cookie. Plausible sets no cookies.

Optional cookies are used only after you accept their category. Provider cookies can vary with browser restrictions and whether you have an account with the provider.

We remember your category choices in local storage under episensor.consent for 183 days, then ask again. A change to the optional providers or consent wording also asks again. LinkedIn may use a pseudonymous first-party identifier, li_adsid, for advertising measurement after advertising consent.

You can withdraw through Cookie settings in the footer. We clear accessible first-party tracking cookies and reload the page to stop tools already running. We cannot delete cookies on a provider's own domain; you can remove those in your browser's settings. Withdrawing stops future optional collection and does not undo processing that took place with your earlier consent.

Your browser also stores things for this Website outside of cookies. While you are checking out, the details you have entered are kept in the browser tab you are using, so that a second attempt is recognised as the same attempt rather than a second order; they are gone when you close the tab. Any display preferences you have set for the site, such as language and currency, are read from the same browser storage. While you sign in on the sign-in page, which runs no analytics, the browser tab keeps a short note of up to four steps (that a sign-in code was sent, that you signed in, that you chose the newsletter) for at most 30 minutes, so that the next page you open can count them in our analytics without the address of the sign-in page, if your analytics choices allow it. The note holds no email address, is deleted as soon as that page has read it, and is gone when you close the tab. None of these is used to identify you or to follow you between websites, and clearing your browser's site data removes them.

The booking calendar on the Book a call page is provided by Google Calendar. It loads only when you choose to show available times, and Google may then set its own cookies under the Google Privacy Policy.

8. International data transfers

Where personal data is transferred outside the European Economic Area (EEA), we ensure that appropriate safeguards are in place, such as Standard Contractual Clauses approved by the European Commission, to protect your data. Google, Microsoft and LinkedIn may process the measurements described in section 2.12 outside the EEA, including in the United States. Their linked privacy notices describe the applicable transfer safeguards, including Standard Contractual Clauses and the EU-US Data Privacy Framework where applicable.

9. Data security

We implement appropriate technical and organisational measures to protect your personal data against unauthorised access, alteration, disclosure, or destruction. However, no method of transmission over the Internet or electronic storage is completely secure, and we cannot guarantee absolute security.

10. Changes to this policy

We may update this Privacy Policy from time to time. Any change is posted on this page with a new version and effective date at the top. The next time you sign in after a change, we record that you accepted the new version.

Changes in the version effective 1 October 2026:

• Section 2.13: stopping personal promotional emails through their link also unsubscribes you from the newsletter, and a newsletter unsubscribe also stops personal promotional emails. Section 5 says how long we keep the hashes that let the link of a deleted campaign message keep working.

• Google signals, the advertising features of Google Analytics, is now on, and runs only if you accept advertising. Section 2.12 explains what it does and how to turn it off; section 4 names Google as its provider.

Changes in the version effective 29 September 2026:

• Optional analytics and advertising now require separate consent choices. Sections 2.12 and 7 explain the banner, withdrawal, Global Privacy Control and LinkedIn Insight Tag. Sections 3, 4, 5 and 8 reflect these choices and providers.

Changes in the versions effective 28 September 2026:

• Section 2.13 explains personal promotional email measurement, its limitations, and how to stop these messages. Section 5 gives the retention periods.

• Google Analytics now sets its two cookies, _ga and _ga_<id>, so that it can recognise a browser across pages and visits. Sections 2.12, 3, 4, 5 and 7 say so, and section 2.12 says how to refuse them until we add a choice to the Website.

Changes in the version effective 22 September 2026:

• Section 2.1 now lists every event our analytics can count and the values each one carries, and says that the campaign tags on our own advertising links are kept.
• Section 2.12 is new. It describes Google Analytics, Google Ads and Microsoft Clarity, which we run without cookies, and how to object.
• Sections 3, 4, 5, 7 and 8 name those providers, the basis we rely on, their retention, and where their data is processed. Section 7 now sets out every cookie in a table.
• The Book a call page now loads the Google Calendar booking page only when you ask for it.

11. Contact

For any questions or concerns about this Privacy Policy or our data practices, please contact us at info@episensor.com:

You also have the right to lodge a complaint with the Data Protection Commission (DPC), Ireland's supervisory authority, at www.dataprotection.ie.