This Privacy Policy explains how spanSense collects, uses, shares, and protects personal data when you use the spanSense platform and the spanSense Field companion app.
spanSense Ltd · Registered in England and Wales, company no. 17464577 · Registered office: 8 Howard Street, Reading, RG1 7XS
1.1This Privacy Policy applies to personal data processed by spanSense in connection with the spanSense web application and the spanSense Field companion app (together, the "Service"). It should be read alongside our Terms & Conditions.
1.2We process personal data in accordance with the UK General Data Protection Regulation and the Data Protection Act 2018.
2.1The data controller for personal data processed through the Service is spanSense Ltd (company number 17464577), trading as spanSense, whose registered office is at 8 Howard Street, Reading, RG1 7XS ("spanSense", "we", "us").
2.2You can contact us about privacy matters at [email protected].
3.1We collect the following categories of personal data:
| Category | Examples |
|---|---|
| Account data | Name, email address, role, organisation, password (stored as a salted hash) |
| Usage data | Login activity, actions taken within the Service, device and browser information |
| Inspection-related data | Inspector names recorded against inspections; site photographs, which may incidentally include images of people or vehicles present at a site |
| Communications | Messages sent to us via the Contact Us form or support email |
| Free tools account data | Name, email address, organisation (optional), password (stored as a salted hash), the free tool used to sign up, and the dates the account was created, confirmed and last signed in to |
3.2Structure and defect data (bridge condition scores, span details, BCI values, and similar) is not, in itself, personal data, unless it is combined with information that identifies a specific individual.
4.1We collect data you provide directly (for example, when registering an account or logging an inspection), and data collected automatically through your use of the Service (for example, login timestamps).
4.2Our free public tools (the BCI Calculator, Structure Model, Stock Map and Location Plan) can be used without an account. What you enter into them, such as structure models, defects, inspection details, imported structure lists and site locations, stays in your browser's local storage and is not sent to spanSense. The exceptions are a structure photo or a described model change in Structure Model, and a previous pro forma uploaded to the BCI Calculator, which are sent once to Google for reading when those options are used (clause 7.2) and are not kept. Location Plan looks up the place searched for or marked on the map: the search text or the point's coordinates go from your browser to the OpenStreetMap Foundation's search service (addresses, car parks and nearby cafes), to komoot's Photon service (place suggestions while typing), to postcodes.io (postcode suggestions and the nearest postcode) and to Wikimedia (photos of nearby places). A cafe's own photo is fetched from its website by spanSense's servers, which receive only that website's address; none of these lookups is kept by spanSense. An optional free tools account opens extra features in these tools. It is separate from Service accounts and gives no access to the Service. When you create one we email a link, sent through Resend, to confirm the address, and the account opens only once the link is used.
4.3The free tools count their use: each page visit, each calculation (a BCI scored, a structure list imported or a site located) and each file exported, with the tool and the date, the type of device and browser, the website that linked to the tool, and an approximate place (country, region and town) that Cloudflare works out from the IP address. No cookie is set and nothing is stored in the browser for this. Visitors are counted with a code made from the IP address and browser together with a random value that is replaced every month, so a visitor can be counted once in a month but not recognised from one month to the next, and the IP address itself is not stored. When signed in to a free tools account, the count is linked to that account.
| Purpose | Legal basis |
|---|---|
| Providing and maintaining the Service, including your account and inspection records | Performance of a contract with you or your organisation |
| Responding to support requests and messages sent via Contact Us | Legitimate interests (supporting our users) |
| Providing a free tools account: confirming its email address, signing you in, and recording the new account so we know who uses our free tools | Performance of a contract (providing the free account you asked for) and legitimate interests (understanding use of our free tools) |
| Counting use of the free tools (clause 4.3) to understand which tools are used and by which organisations | Legitimate interests (understanding and improving our free tools) |
| Monitoring for misuse, and maintaining the security of the Service | Legitimate interests / legal obligation |
| Improving the Service (e.g. understanding which features are used) | Legitimate interests |
| Complying with legal or regulatory obligations | Legal obligation |
6.1Most data recorded within the Service (structures, defects, spans, BCI scores) describes physical infrastructure rather than individuals. Where personal data does appear — for example, an inspector's name against a record, or a person incidentally visible in a site photograph — the Customer submitting that data is responsible for ensuring it has a lawful basis to do so and, where applicable, for informing the individuals concerned.
7.1We do not sell personal data. We share personal data only with the service providers who host and support the Service on our behalf ("sub-processors"), under contractual terms that require them to protect it, and only to the extent necessary to provide the Service.
| Sub-processor | Purpose |
|---|---|
| Render | Application hosting |
| Cloudflare | Domain, network and security services in front of the Service; every request passes through it and carries the device IP address, and it supplies the approximate place recorded with the free tools usage counts (clause 4.3) |
| Supabase | Our PostgreSQL database, and secure storage of uploaded photographs and files |
| Google (Gemini API) | Used only while the organisation's administrator has switched AI features on (off by default for new organisations): reading uploaded inspection documents, drafting conclusion text, and answering questions in the chat assistant. Sent for processing: uploaded document text; the structure register (names, locations, dimensions, inspection dates and condition scores); defect details and comments; inspection conclusions; inspector names; and chat messages. Google does not use this data to train its models, and logs prompts and responses for a limited period solely to detect misuse. Processing may take place outside the UK |
| Resend | Sending account emails (invitations and password-reset links); the recipient's name and email address pass through it |
| OpenStreetMap Foundation | Standard map imagery, address lookup when placing a new structure, and Location Plan's place, car park and cafe searches (the search text or map point); requests carry the user's device IP address |
| postcodes.io | Location Plan's postcode suggestions and nearest-postcode lookup (the typed text or map point); requests carry the user's device IP address |
| komoot (Photon) | Location Plan's place suggestions while typing (the search text); requests carry the user's device IP address |
| Wikimedia (Wikidata and Wikimedia Commons) | Location Plan's photos of nearby places; requests carry the user's device IP address |
| OpenFreeMap | Dark-mode map imagery; requests carry the user's device IP address |
| Esri | Satellite map imagery, requested by the user's browser and carrying the device IP address; and street-map imagery for report location maps, fetched by spanSense's servers and carrying no user data |
| Cloudflare (cdnjs), jsDelivr, unpkg and Google Fonts | Delivery of open-source code libraries and fonts to the user's browser; requests carry the device IP address |
7.2AI features are off by default for new organisations. Nothing is sent to Google for AI processing unless the organisation's administrator switches AI features on in the organisation settings, and they can be switched off again at any time. The public BCI calculator, which needs no account, sends the text of an uploaded previous pro forma to Google in the same way to fill in the form; spanSense does not keep the file or its contents.
7.3We may also disclose personal data where required by law, to protect our rights, or in connection with a merger, acquisition, or sale of assets (in which case we will take reasonable steps to ensure your data continues to be protected).
8.1Our sub-processors may store or process data outside the UK. Where this occurs, we take reasonable steps to ensure appropriate safeguards are in place, such as relying on providers' standard contractual clauses or adequacy arrangements recognised under UK data protection law.
8.2Google does not commit to processing data sent to the Gemini API in a particular country. Organisations that need AI processing to stay within the UK can keep AI features switched off.
9.1We retain personal data for as long as your account is active and the data is needed to provide the Service, and afterwards for a reasonable period to comply with legal obligations, resolve disputes, and enforce our agreements.
9.2On request, or on termination of an account, we will delete or anonymise personal data we no longer need to retain, subject to any legal retention requirements.
9.3A free tools account that is not confirmed is deleted after 30 days. A confirmed free tools account is deleted automatically after 24 months without a sign-in, or sooner on request (clause 12.3). Free tools usage counts (clause 4.3) are deleted after 24 months, and the monthly random value used to count visitors is deleted when its month ends.
10.1We use technical and organisational measures appropriate to the risk to protect personal data, including:
10.2No method of transmission or storage is completely secure, and we cannot guarantee absolute security. A fuller data security policy, covering our practices in more detail, is in preparation.
11.1The Service uses essential cookies/local storage strictly necessary to keep you signed in and to remember preferences such as dark mode. We do not use non-essential analytics or advertising cookies. The free tools usage counts in clause 4.3 use no cookie or browser storage.
11.2While an inspection is being edited on the website, an unsaved draft is saved to spanSense so it can be resumed later or on another device, with a backup copy in the browser's local storage on that device in case the connection drops. Drafts are visible only to the person who started them, within their organisation, and are deleted once the inspection is saved or the draft is deleted. The browser backup expires after 30 days.
11.3Signing in to a free tools account sets the same essential sign-in cookie, which lasts up to 30 days so the free tools stay signed in between visits. The free tools also keep their work, such as models and imported structure lists, in the browser's local storage on that device; clearing the browser's site data removes it.
12.1Subject to applicable law, you have the right to:
12.2To exercise any of these rights, contact us at [email protected]. Where your account is managed by an organisation (your employer), some requests may need to be made through that organisation as the relevant data controller for its own records.
12.3To delete a free tools account, email [email protected] from the address it was registered with, and we will delete it and confirm by reply.
13.1The Service is intended for use by professionals in the course of their work and is not directed at, or intended for use by, children.
14.1We may update this Privacy Policy from time to time. Material changes will be notified via email or an in-app notice before they take effect.
15.1For any questions about this Privacy Policy or how we handle personal data, contact [email protected].