In force

Privacy Policy

OnSiren is a safety network for licensed security professionals. This policy explains, in plain language, what personal data we collect, why we collect it, who we share it with, and the rights you have over it under UK data protection law.

Last updated
11 November 2026
Applies to
The OnSiren app, network and website

1. Who we are

OnSiren is operated by Onsiren Limited, a company registered in England and Wales (company number 16981806). For the purposes of the UK General Data Protection Regulation (UK GDPR) and the Data Protection Act 2018, Onsiren Limited is the data controller of the personal data described in this policy.

You can contact us about anything in this policy at privacy@onsiren.com.

2. Who the app is for

OnSiren is for working security professionals who hold a valid licence from the Security Industry Authority (SIA). A business can also invite people to use its own channels (see “Businesses you join”). You must be at least 18 to hold an SIA licence, and you confirm you are 18 or over when you join a business, so the app is not directed at, and must not be used by, anyone under 18. We do not knowingly collect data from children.

3. The data we collect

Your account

When you sign up, we collect your email address, which you confirm with a code and then use to sign in, and your SIA licence number. If you use an older version of the app, you sign up with your phone number instead, and confirm it with a code. We take your name, licence type and expiry date from the SIA register (see below). You choose a call sign: it, not your name, is what other officers on the network see. When you finish verifying your account, we ask for the one you did not sign up with: your mobile number, which you confirm with a code sent by text, or your email address, which you confirm with a code sent by email. You can then sign in with either.

When you sign up, we note where you are, to show you the channels near you. Each time you sign in, we record your device (its model, operating system and name), the app version and your IP address, and while you use the app we keep a note of the app version, with its build and update identifiers, up to date, to keep your account secure.

SIA licence verification

You type your SIA licence number when you sign up, and we check it against the SIA’s public register. We keep your licence number and what the register says about it: your name, licence type, status and expiry date. If the register can’t be reached at that moment, we let you carry on and mark your number as not yet checked.

Later, when you finish verifying your account, you photograph your licence card. An automated check confirms the photo shows a readable SIA licence card, our team can look at it, and it is the reference picture for your face check. The photo is stored securely and is accessible only to authorised staff. You can ask us to delete it at any time, and it is erased when you delete your account.

Face verification (biometric data)

When you finish verifying your account, we run a face-liveness check to confirm you are a real person and that you match the photo on your licence card. An AI model makes the comparison (see How AI processes your data). Biometric data used to identify a person is special category data under Article 9 UK GDPR, so we ask for your explicit consent in the app before any capture begins. We store the outcome of the check (pass or fail, and confidence scores). We do not create or keep a biometric template for ongoing identification, and we never use your face to identify you elsewhere in the product. The images captured during the check are stored securely, restricted to authorised staff, and erased on request or when you delete your account. You can decline, but we cannot verify your account without the check.

Location

OnSiren is built around where you are. With your permission, the app collects your exact location while you are using it, and we keep it to run the network and keep officers safe. On a public channel, the officers on the network around you see roughly where you are on the map, never your exact location. The only exception is an alert you send, which shows its exact location to the officers on the channels it reaches, including in their alert history. Our staff can see your exact location in our control console. On a business’s channel, the other people on that channel see you on a team map: roughly where you are, unless the business has set the channel to show exact positions. If we have set the business up to see this, it can also see which of its sites you are at, but not where you are on the site (see “Businesses you join”). On iPhone, sharing can carry on for a while after you leave the app; on Android, it runs only while the app is open, unless you turn on Roaming. Turning your radio off in the app doesn’t stop it. Sharing stops when you sign out, when you no longer have a channel, or when you turn off location for OnSiren in your phone’s settings.

You choose your channel from a list of channels near you, and it stays your channel until you pick another, unless you turn on Roaming. Other officers’ live positions shown on your map are held in your device’s memory only and are never written to its storage.

Roaming is off unless you turn it on in Settings. With it on, OnSiren moves you to the public channel for the area you travel into. If you allow location all the time, the app also uses your location when it is closed to do this, but only while Roaming is on, you have a public channel and your radio is on. These locations are kept like the rest of your location history. Each switch is recorded, and you get a note in the app with Undo. Turn Roaming off in Settings, or stop allowing location all the time in your phone’s settings, and location from a closed app stops.

We keep a history of your location at key moments: from your live location (at most once a minute), when you sign up, when you look for channels, and when you send or receive an alert. An alert you raise keeps the place you raised it.

If you look for a channel somewhere OnSiren doesn’t cover yet, we keep where you were and the name of the place, so we can plan where to open channels, and we may tell you when coverage starts near you. If you use a map tool, such as the nearest police station or transport, the app sends your location to find what’s nearby, and we don’t keep it.

Businesses you join

A business, such as a company whose sites you work at, can invite you to its team on OnSiren. You decide whether to accept. When you do, you confirm you are 18 or over, and we keep the time you did. You don’t need an SIA check to use a business’s own channels, and we collect no face or SIA card images for them. To use public channels you verify your SIA licence in your Profile.

Once you join, the business can see:

  • your name on OnSiren and the callsign you use on its channels;
  • whether your SIA licence was on the SIA register when you gave it to us and, if so, its sector and end date;
  • which of its sites and channels you are on, and what you can do there;
  • your mobile number or email address, if it invited you with it;
  • if we have set the business up to see this, which of its sites you are at, while you are on its channel with your radio on and your phone has sent your location in the last 5 minutes. It sees the site, not where you are on it;
  • if we have set the business up to see this, where you were when you sent an alert on its channel from one of its sites, while the alert is on the channel’s map;
  • the channel’s past alerts, without places;
  • the last three messages on each of its channels from the past day, as the filtered text officers see, with the callsign of who said them;
  • that you are on its channel with your radio on, when you are not shown at one of its sites.

If we have allowed a business to, the people who run it on OnSiren can also see your full name, your licence number and its end date, your email address and your mobile number, so it can contact its team and look up their licences on the SIA register. The end date is the last one we read. They can also download these details in a file, which the business then keeps. We record in the business’s log when someone opens these details, at most once every 10 minutes for each person looking. The log doesn’t say whose details they opened.

The business’s control room can talk on its channels. You see it as CONTROL. What it says is recorded and written out like other messages.

If we have allowed a business to use Alpha One, it can also read what was said on its channels in the last hour, as filtered text, to summarise it or answer its control room’s questions.

If a business you join turns on radio checks, Alpha One checks on you during its shifts, and the business sees whether each check was answered, never what you said.

If a business you join gives you site instructions, they show at the top of your brief. You can mark a task done or say you can’t do it, with a reason and, if you want, a short note, and mark a rule as understood. The business sees whether each instruction has reached your brief, when you acknowledged it, and each answer you give, with its time, reason and note, and it can download them. It can also mark a task done for you. Other officers see only that a shared task is done and when, never who did it, and never your reasons or notes. Leave health and other private details out of a note.

Alpha One uses your instructions and your own answers to tell you what is done and what is still open. If we have allowed a business to use Alpha One, its control room can ask Alpha One about them too, notes included. The business decides what it asks you and what it does with your answers, and we hold them for it. They stay until the business deletes them, and yours are deleted when you delete your OnSiren account, except anything the business has already downloaded or its Alpha One has quoted, which the business keeps. Our staff can read them to help the business, and we record when they do.

A business can choose to log when its members arrive at and leave its sites. If it does, we record that while you are on its channel and your phone is sharing your location, even with your radio off. If we have allowed a business to, it can log this whether or not you are on its channel, except while you are on another business’s channel. We record the site and the times only, never where you were on the site. If we stop hearing from your phone on a site, the log shows the last time we heard from you there. The business can see this log, export it and delete it. You can’t see it in the app: for a copy, ask the business, or email privacy@onsiren.com and we will pass your request on. It stays until the business deletes it, and it is deleted when you delete your OnSiren account.

A business can’t see where you are anywhere else, what you say or hear on public channels, or anything about other businesses you belong to. We do not tell one business about another.

The business decides what it does with what it sees and is responsible for that. Eagle Eye, the app it uses, does not keep your position. We keep our own record of your location, as described above. Our staff can open a business’s Eagle Eye to help it. When they do, they see what the business sees, and their visit is recorded.

You can leave a business at any time. When you leave, the business keeps its records of your time with it until it deletes them.

If a business gave us your number or email address

A business can ask us to invite you to its team. To do that, it gives us your mobile number or email address, and may also give your name and its own reference for you. We use them only to send the invitation, to recognise you if you accept, and to show the business whether you did.

The business is responsible for giving us your details and decides what happens to them; we hold them for it. They stay on the business’s records until it removes them, even if you never accept. We also keep a copy of each text message we send, including the invitation, in our message records, which our staff can see.

If you weren’t expecting the invitation, you can ignore it. To have your details removed, ask the business, or email privacy@onsiren.com and we will pass your request on. If you accept, the rest of this policy applies to you.

Communications

  • Radio transmissions. Your voice transmissions are relayed live to the officers on your channel, recorded, and turned into text for the channel’s written log. Officers on the channel and our staff can play recordings back. If you speak another language, we detect it, translate the text into English and keep your original words too.
  • Channel chat. Messages you type, and photos you send with any caption. Photos are checked automatically for unsafe content before they are stored. If the check can’t run, for example during a fault, the photo goes through without it. We can also switch the check off for a channel, or for everyone. You can’t switch it off yourself. A photo the check rejects is never stored.
  • Alerts you send or receive, including where you raised them, your answers, any voice note (which we transcribe, and translate into English where needed) and any photo you attach, which is checked in the same way. A voice note is uploaded while the alert counts down, so we keep it even if you cancel the alert.
  • Channel activity. When you join or leave a channel, the officers on it can see that, and we keep a record of the channels you have been on. When you acknowledge a channel briefing, your call sign appears in the channel chat as a radio check. Channels you mark as favourites are visible only to you.
  • Reports and blocks. If you report a message, we keep your report and our team reviews the message. If you block someone, their messages are hidden from you and our team is told who you blocked, whether from channel chat or direct messages, and in channel chat which message, so it can check it. We keep that record after you unblock, until either account is deleted. If someone blocks you, our team may review that message.

Alpha One

Alpha One, the assistant in the app, is optional. If you use it, we keep your conversations with it, by voice or text. To answer you, it can look at information in the app that you could see yourself, such as your alerts, your channel’s messages, your notifications, and which officers are near you (as a rough distance and direction, worked out from their approximate positions, never an exact position). If you allow it, Alpha One also remembers useful facts about you. You can see and delete them, or switch Alpha One off, in Settings → AI & your data. Turning Alpha One off doesn’t stop the checks on what you send.

Safety check

Safety check is an optional wellbeing check-in. If you use it, we keep how you said you were feeling, anything you chose to add, and Alpha One’s reply. This is information about your health, so we ask for your explicit consent first. Only you can see it. You can change how often it asks, see or delete your history, or turn it off, in Settings → Safety check.

Notifications

We keep your device’s notification tokens so alerts can reach you, a record of the notifications we send you and whether they reached your phone, whether the app is open or in the background, and your notification settings. If you have been away from your channel, we may send a notification naming the officers who spoke. You can turn this off in Settings → Notifications → Channel chatter.

Device and diagnostics

Crash and error reports help us fix faults. They are tagged with a pseudonymous user ID, your call sign, and the app version (with its build and update identifiers), not your name, location, or contact details.

The app also records your screen while you use it, and logs the screens you open and the actions you take, linked to your account, your call sign and your channel. We use these recordings to find faults and improve the app. Sign-in codes, your email address, your phone number, your licence details and the camera during your identity check are hidden from recordings, and the Safety check screens are not recorded. Anything else on your screen can appear in a recording, including the map with other officers’ approximate positions, channel messages and photos. The app doesn’t currently let you turn this off. You have the right to object: email privacy@onsiren.com.

Usage statistics

The app also tells Google Analytics how it is used, so we can see how people find OnSiren and how officers use it. It sends the screens you open, the sign-up and sign-in steps you finish (including whether your licence check went through, or why it didn’t), when you first use the radio, Alpha One or Radio Check, and when you share an invite to OnSiren and through which app. With these it sends your account type, the sector your SIA licence covers, your phone’s model, operating system and language, the app version, a rough area Google works out from your IP address and, on Android, how you came to install the app. Google links all of this to a random ID for the app on your phone, which changes when you sign out. It never receives your name, phone number, email address, call sign or licence number, your phone’s location, or your messages, photos, alerts or anything you say to Alpha One. If you agree to Advert measurement, Google also uses these statistics and your phone’s advertising ID to measure our adverts. Otherwise we don’t use them for advertising, and Google never receives your advertising ID. The app doesn’t let you turn the statistics off. You have the right to object: email privacy@onsiren.com.

We advertise OnSiren on Google, Meta (Facebook and Instagram) and TikTok. If you agree, the app tells Meta and TikTok that this phone installed OnSiren, signed up, finished setting up and first used the radio, and lets Google use the usage statistics described above, so we can see which adverts bring officers to OnSiren.

This uses your phone’s advertising ID, your IP address and information about your device, which Google, Meta and TikTok may use to match the phone to one of their adverts. We don’t let Google use it to personalise the adverts you see. None of them receives your name, phone number, email address, call sign or licence number, your phone’s location, or your messages, photos, alerts or anything you say to Alpha One.

This is optional, and nothing in the app depends on it. We only do this with your consent, which you give on the sign-up screen or in Settings, Privacy, and on iPhone through Apple’s tracking prompt. You can change your mind at any time in Settings, Privacy, or on iPhone in Settings, OnSiren, Allow Tracking. It does not affect anything sent before you changed your mind.

Google, Meta and TikTok are separate companies that may handle this data outside the UK, under their own terms.

App updates

Each time the app starts, and from time to time while you use it, whether or not you’re signed in, it checks OnSiren’s update service for fixes to the version you have installed, or for an instruction to withdraw one. The check sends your device’s IP address, a random identifier that the app’s update software creates and keeps on your phone, the platform (iPhone or Android), the identifiers of the app’s build and update, including any update that failed to start on your phone, and the technical details your phone adds to any web request. If the app crashed while starting last time, it also sends the error message, up to about 1,000 characters, which could include anything the message contained. The random identifier lets us send a new fix to a small share of phones first, so a fault can’t reach everyone at once. We don’t link it to your account. The identifier stays on your phone until you delete the app or clear its data. If your phone’s backup includes the app’s data, the identifier can come back when you reinstall the app or move to a new phone.

The update service runs on Amazon CloudFront, part of Amazon Web Services (AWS), and keeps no log of these checks. Its firewall, AWS WAF, keeps a small sample of recent requests, including what each one sends, and our staff can look at that sample for about three hours, to protect the service and to find faults. If a check fails, or a fix goes wrong on your phone, our crash reports note it (see “Device and diagnostics”). We rely on our legitimate interest in keeping the app working and secure. The app doesn’t let you turn these checks off. You have the right to object: email privacy@onsiren.com.

Feedback

If you send us feedback, we keep what you write or say, your call sign, your channel, the area you were in (a place name your phone works out, not your exact location), and your phone model and app version.

Rank badges

When rank badges are switched on, acknowledging your channel briefings builds the standing on your profile, and officers near you can see your rank badge. Your rank always shows to other officers; there is no setting to hide it.

Network launch

If you ask for a reminder before the network launches, we keep that. At launch, we record the first officers to transmit on each channel (call sign, channel and time) for the launch prize, and our staff can play that transmission back.

4. Our website, our field team and contacting us

Reserving a call sign

You can reserve a call sign through the Clocked challenge, and until 7 October 2026 you could also reserve one on our website. When you reserve one, we collect your phone number, which you confirm with a code, the call sign, and your email address if you give it, which you also confirm with a code. We note your IP address and browser details to stop abuse, and whether you reserved on our website or through Clocked, so we can see which works better. When you join the app with that phone number, your reservation carries over.

Meeting our field team

Members of our field team meet security officers in person. If you talk to one of them, they may note your name, phone number, email address, employer, SIA licence number, notes about the conversation and where you met, and send you a Join OnSiren link by text or email. When you check your licence on that link, we keep what the SIA register says about it, with your IP address and browser details. If you then join, we link that record to your account. We use this to send you the link, to check your licence when you use it, and to credit the team member who helped you. Your licence number stays on that record; it is not copied into our contact list.

Messages we send you

If you use the app, your email address signs you in: each time you sign in with it, we email you a one-time code. We also use the email address you give us to send you service messages about what you signed up for or asked us for, and about significant changes to this policy. If you use the app, that means messages about your account and our terms. If you reserved a call sign on onsiren.com or through the Clocked challenge, it means messages about your reservation, such as when it is ready to activate. If you asked our field team for a Join OnSiren link, we text you the link, and email it too if you gave us an email address. After that we send you service messages only after you use the link (you check your licence on it, go to an app store or sign up), to help you get started. These are not marketing, and we add no open or click tracking to them. Your Join OnSiren link is personal to you, so we record when you use it (see “Our contact list”).

If you are in our contact list (see below), we may also send you marketing emails and texts about OnSiren without you signing up for them. Unlike service messages, marketing emails carry open and click tracking. You can stop marketing emails at any time with the unsubscribe link in any of them, and marketing texts by following the opt-out instruction in any of them: replying STOP, or the opt-out link. In the current version of the app, you can also switch marketing emails and marketing texts off, and back on, in Settings → Privacy, and the app tells you this when you give us your email address or your mobile number. Older versions of the app don’t have these switches.

Every service or marketing email we send has an unsubscribe link; using it stops both. It does not stop one-off emails you ask for, such as a code to sign in or to verify your email address, the Join OnSiren link our field team sends at your request, or the confirmation of a reservation you have just made; those carry no unsubscribe link. Nor does it stop an account notice: an email telling you about action we have taken on your app account, such as suspending it. We send account notices even if you have unsubscribed, switched marketing emails off in the app or marked one of our emails as spam. They never contain marketing, and they carry no unsubscribe link and no open or click tracking.

If an email we send you bounces for good, or you mark one as spam, our email provider tells us and we stop sending you service and marketing emails at that address. One-off emails you ask for and account notices still reach you after a spam report, but not at an address that has bounced for good.

Our contact list

We keep one contact record for each person who uses the app, reserves a call sign, gives their details to our field team, fills in one of our forms or is added from a list we import. It holds your name, email address and phone number where we have them, any call sign you reserved, where you came to us from, your licence sector (never your licence number), how far you have got (for example whether you checked your licence through your Join OnSiren link, went to an app store or finished signing up), which email topics you have switched off, and whether you opened or clicked our marketing emails: those contain a small tracking image and links that pass through our servers, so we can see when they are opened and which links are clicked. When you fill in one of our forms, we also keep the time, your IP address and browser details as a record of your choice. We group these records into lists and score them to decide which messages are relevant to you. The record holds no biometric data and no location.

Asking for access for an organisation

If you ask us for access on behalf of a police force or another emergency service, a local authority, a business improvement district (BID) or another public body, we keep your name, your job title, your email address, your organisation, the areas you cover and anything else you send us about the request. We use them to check your request, to reply to it and to keep a record of what we decided, and we email you to confirm we have it. We keep your IP address and browser details to stop misuse of the form. A security check (Google reCAPTCHA) runs when you send the form. Our team is told about the request in Slack: the type of organisation (or the force, for a police request), the areas and the request’s reference, but never your name or your email address. We keep your request for as long as we need a record of who asked for access and what we decided, and you can ask us to delete it at privacy@onsiren.com.

The Legal Hub

The question box in our Legal Hub answers from our published documents. While AI answers are switched off, it searches them in your browser, and what you type isn’t sent to us or kept.

While AI answers are switched on, we send your question with our published documents to an AI model that Amazon Web Services runs for us in London or elsewhere in the EU (Amazon Bedrock), to write the answer. If you ask a follow-up, we send the question before it and its answer too. A security check (Google reCAPTCHA) runs when you ask. We keep each question and answer, without your IP address, so we can see what people ask and improve our documents. Don’t put personal details in a question: use the Request Centre instead.

If you send a request through the Legal Hub’s Request Centre, we use what you send to deal with it and to reply: the kind of request, how you’re connected to OnSiren, your name and email address if you give them, the details you write, and any incident reference, area or date.

When you send the form, a security check (Google reCAPTCHA) runs and we give you a reference. We email you to confirm we have your request, and that email doesn’t repeat what you wrote. We keep your request with our replies and a record of how we handled it, such as when we checked who you are and the dates the law gives us to reply. We reply to the email address you gave. Our team is told about each new request in Slack: its kind, its reference, the date we must reply by and whether you gave an email address, but never your name, your email address or what you wrote. If you don’t give an email address, we can’t reply, but we still read your request.

Sending us an enquiry

If you send us a message through the form on our contact, media or Eagle Eye pages, we keep your name, your email address, what your message is about and what you write. If you give them, we also keep the company or publication you work for and, for a business enquiry, your phone number. We use them to answer your enquiry and to keep a record of it, and we email you to confirm we have it, with a reference to quote. A security check (Google reCAPTCHA) runs when you send the form. We don’t keep your IP address or browser details. Our team is told about each new enquiry in Slack: what it’s about, its reference and whether you gave an email address, but never your name, your email address or what you wrote. Sending an enquiry doesn’t add you to our contact list or sign you up to marketing. We keep your enquiry with our replies for as long as we need a record of it, and you can ask us to delete it at privacy@onsiren.com.

To offer an organisation a data sharing agreement, we email a private link to the person it names, and keep their name and email address with the offer. If the agreement is accepted online, we keep a record of the acceptance: the agreement and the version accepted, a fingerprint of everything offered, the name and role of the person who accepted it, the time, their IP address and the browser they used, and we email a copy to the address we sent the offer to. Our team is told in Slack which organisation accepted, but not who. We keep the record as evidence of what was agreed, for as long as the agreement applies and afterwards while the law needs it, including after a newer version replaces it.

The Legal Hub keeps every edition of its documents that it publishes, with the date it was published and what changed. You can read them from its list of documents.

Using our Martyn’s Law Guide

Our Martyn’s Law Guide at www.onsiren.com/martyns-law is free and needs no account or email address. When you search for your venue, we send what you type to Google (Google Places) to suggest matching places. We don’t send anything about you with it. When you pick a suggestion, we also send what you typed to OpenAI, which searches the web for public information about the venue, such as its published capacity. We show you what it found, with a link to each source, for you to check. When you pick a suggestion, your browser also loads a 3D map of the venue straight from Google, so Google receives your IP address, details of your browser and the venue’s location.

If you save a report, we keep the venue’s name, address and type, your answers, your working notes, your checklist and any sources found for you, with each earlier version you saved. A cookie lets this browser get back to your report for 30 days (see our Cookie Policy), and a private edit link lets you get back from another browser. Your report stays on our servers until you or we delete it. It doesn’t expire when your browser’s access ends. You can delete it from the report at any time. If you can’t get back to it, email privacy@onsiren.com with its private edit link or its web address and we’ll delete it.

A team guide you share shows only the venue’s name, address and type and our general guidance, never your answers, notes or checklist. Anyone with its link, and its password if you set one, can read it until you withdraw it or delete the report. Our staff can open saved reports to deal with privacy requests, problems and misuse. Please don’t put other people’s personal details in your notes. The guide uses your IP address only in scrambled form, for up to an hour, to limit how often it can be used, and doesn’t keep it with your report.

Taking our radio course

Our free radio course at www.onsiren.com/learn is open to anyone and doesn’t need an OnSiren account. To sign in, you give us your email address and we email you a code. A security check (Google reCAPTCHA) runs when you ask for a code. The first time, we also ask for your name, which goes on your certificate, and whether you’d like news about OnSiren. That box is unticked unless you tick it.

We keep your email address, your name, whether you asked for news and when, which videos you’ve watched and how far you got, your quiz answers and scores, and your certificate. A cookie keeps you signed in (see our Cookie Policy). The videos are streamed by Mux. If you accept analytics on our cookie banner, Mux also collects viewing statistics, such as how much of a video is watched and how well it played, with the video’s name but nothing about who you are.

When you pass, we issue a certificate with your name and a certificate number. Anyone with its link or QR code can see your name, the certificate number, the course and the date on our verification page, and download the certificate. Its digital badge holds your email address only in scrambled form, so someone who already knows your address can check the badge is yours. If you choose to add it to LinkedIn, we open LinkedIn with the certificate’s details filled in. If you asked for news, we may email you about OnSiren, and you can ask us to stop at any time. Our staff can see the list of learners, with each person’s progress, scores and certificate. We keep your course record until you ask us to delete it or we delete it. To delete it, email privacy@onsiren.com from the address you used. That removes your progress, quiz results and certificate, and your certificate’s link stops working.

Contacting us

If you email us or send us a request, we use what you send and your contact details to reply and to deal with it. We keep that correspondence while we need it for that purpose, and to show how we handled it.

6. How AI processes your data

Some OnSiren features use AI. The companies that provide it are listed under Who we share it with.

  • Speech to text: radio transmissions, and voice notes on alerts and broadcasts, are turned into text, and translated into English where needed, so the channel has a written record everyone can read.
  • Checks: photos you attach are checked for unsafe content, and an AI model checks your licence card photo and compares your face with it to confirm your identity. Messages are also screened against a list of abusive words.
  • Briefings and summaries: your channel briefing is put together automatically from alerts, broadcasts, channel activity and public information, and no AI writes it. When you tap Summarise, AI writes a short summary of your briefing or of your channel’s chat. A summary you ask for is private to you.
  • Channel history: AI picks out notable events from your channel’s radio transcripts and keeps them as the channel’s history, which briefings and Alpha One can draw on.
  • Alpha One, if you use it: answers your questions by voice or text and can help draft an incident report. While you talk to it, your voice goes straight from your phone to OpenAI. Where it offers to prepare something for you, such as an alert, nothing is sent or changed until you confirm it.
  • Safety check, if you use it: AI writes Alpha One’s reply to your check-in.
  • Legal Hub answers, when switched on: AI writes the answer to a question in the Legal Hub from our published documents (see Our website, our field team and contacting us).

AI output is informational. Two things happen automatically and affect your account: the identity check, which uses AI, and the limits the app applies if you don’t finish verifying in time. If either affects you and you think it’s wrong, email privacy@onsiren.com and a person will review it. Decisions to suspend or remove an account are made by people.

7. Who we share it with

Other officers on the network. That is the point of OnSiren: your call sign, approximate location, alerts and voice transmissions reach the licensed officers around you. A public alert can also reach a business’s channels, if it has set them to receive alerts in that area, including people on those channels who have no SIA licence.

Businesses you join. A business you join sees what “Businesses you join” sets out, and nothing about the other businesses you belong to. The other people on its channels get your call sign, alerts and voice transmissions, and see you on a team map.

Service providers (processors). These providers process data on our behalf, under contract, and only on our instructions:

  • Amazon Web Services: hosts OnSiren in its London region (eu-west-2): our servers, database, cache, logs and file storage, including licence card and face-check images, radio and alert audio, and photos. Through Amazon Bedrock it also runs the AI models we use, including Anthropic’s Claude, for the identity check, photo checks, translation, summaries, Alpha One’s typed chat and Safety check replies, and Legal Hub answers while they’re switched on. Bedrock may run these models in other AWS regions in the EU. Anthropic does not receive this data. Amazon SES, in the same London region, sends our emails, such as sign-in and email verification codes, Join OnSiren links, call sign reservation confirmations, service messages, marketing emails and the emails we send about requests and agreements. Amazon CloudFront delivers our app updates, normally from AWS locations in North America and Europe, and the images in our emails and our brand images from AWS locations worldwide. AWS WAF, its firewall, checks the requests to our update service.
  • OpenAI (EU endpoints): turns channel radio, and voice notes on alerts and broadcasts, into text; runs Alpha One’s voice conversations, for which your phone connects to OpenAI directly while you talk; reads some briefing summaries and the welcome tour aloud; and searches the web for public information about a venue in our Martyn’s Law Guide.
  • Deepgram (EU endpoint): turns channel radio into text when we choose it instead of OpenAI.
  • Apple: notifications and push-to-talk on iPhone.
  • Google Firebase: notifications on Android, crash reports, and the app’s usage statistics (Google Analytics), as described under The data we collect. If you agree to Advert measurement, Google also uses those statistics to measure our adverts, under its own terms.
  • PostHog (EU): app analytics and screen recordings, as described under The data we collect. On this website, if you accept analytics cookies, it also counts visits, notes where people click and scroll, and records each visit so we can play it back (see our Cookie Policy).
  • Twilio: text messages: sign-in codes, codes for reserving a call sign, the links our field team sends, marketing texts, and replies such as STOP with our automatic answers to them.
  • Slack: our team’s internal notifications, for example when someone reserves a call sign (with the phone number and email partly hidden), asks for coverage where we have none yet, or sends feedback (the notification doesn’t include the feedback itself). It also tells the team when an organisation asks for access (without the requester’s name or email address) and when someone sends a request through the Request Centre (its kind, its reference, its reply date and whether an email address was given, never the person’s name, email address or what they wrote), and when someone sends an enquiry from our contact, media or Eagle Eye pages (what it’s about, its reference and whether an email address was given, never the person’s name, email address or what they wrote). When an organisation accepts an agreement, it tells the team which organisation and the agreement’s reference, never the name or email address of the person who accepted.
  • Google reCAPTCHA: security checks when you sign up or sign in to the app, ask for a sign-in code for our radio course, reserve a call sign, ask for access on our law enforcement page or our page for BIDs and local authorities, send a request through the Request Centre, send an enquiry from our contact, media or Eagle Eye pages, ask a question in the Legal Hub while AI answers are on, or use a Join OnSiren link.
  • Cloudflare: a Turnstile security check on Join OnSiren links.
  • Google Maps Platform: maps in our staff console, which can show an officer’s last known position, and place names for coverage requests; and, on our website, venue search and the 3D venue map in our Martyn’s Law Guide.
  • Mux: streams the videos in our radio course and, if you accept analytics cookies, collects viewing statistics for them.
  • Google Sign-In: identity provider for the admin console. Staff only; officers never see it.
  • Google Tag Manager: tag management container for analytics on this site. The container loads only after you accept analytics cookies. Nothing loads if you decline.
  • Google Analytics: aggregated visitor analytics (GA4) on the landing site, consent-gated, with Google Signals off and ads personalisation off. Google states that GA4 does not log or store visitor IP addresses. Analytics data is processed by Google in the United States under an approved UK transfer mechanism (see our Cookie Policy).

Services your phone contacts directly. The app’s map comes from OpenFreeMap, a community map service: your phone asks it for map images, which shares your IP address and the area you are looking at. When the app shows a street or place name for a location, your phone asks Apple (on iPhone) or Google (on Android) to name the spot.

The SIA public register: we check your licence number against the register the SIA publishes. This is a lookup of public data, not a disclosure of your account.

Authorities: we may disclose data where the law requires it or where it is necessary to protect someone’s life or safety.

We never sell personal data.

8. International transfers

We keep processing in the United Kingdom and the European Economic Area wherever we can. Our servers and AI models run on AWS in London and elsewhere in the EU, and OpenAI, Deepgram and PostHog process through their EU services.

Some providers process data outside the UK and the EEA, or may do: Twilio, Slack, Cloudflare, Mux, Google (reCAPTCHA, staff sign-in, maps, Tag Manager and Analytics), Apple and Google for notifications and place names, and OpenFreeMap. Amazon CloudFront normally delivers our app updates from AWS locations in North America and Europe, the United States included, and it delivers the images in our emails and our brand images from AWS locations worldwide. Where a provider processes data outside the UK, we rely on safeguards recognised by UK GDPR: UK adequacy regulations, or the UK International Data Transfer Agreement / Addendum to the EU Standard Contractual Clauses, so your data has equivalent protection wherever it is processed. You can ask us for a copy of the safeguards we rely on.

9. How long we keep it

We keep personal data no longer than necessary for the purposes set out in this policy. Operational records, such as alerts, transcripts, recordings and location history, are kept for safety and audit purposes, and account data is kept while your account is active.

Reports saved in our Martyn’s Law Guide, and radio course records, are kept until you or we delete them. They aren’t linked to an OnSiren account.

You can delete your account at any time from the app. When you do, we erase the personal data we hold about you, apart from:

  • alerts you raised, which stay in the incident record with your call sign, where you raised them and what you sent, so the record stays complete;
  • our staff’s audit log of actions taken on your account;
  • records from a conversation with our field team, apart from the link to your account;
  • anything we hold under a mobile number that is not the one on your account, such as a call sign reservation, an entry to the Clocked challenge or texts we sent to it: tell us the number at privacy@onsiren.com and we will delete it;
  • a business’s own records of you, such as the invitation it sent, until it deletes them: ask the business, or email privacy@onsiren.com and we will pass your request on;
  • some copies in our team’s internal notifications, and data held by our analytics and crash-reporting providers.

If any of your records have to be kept for a legal reason, such as an open investigation, you can’t delete your account until they no longer need to be kept, and the app tells you so. You can also ask us to delete specific data at any time. See Your rights.

10. Your rights

Under UK GDPR you have the right to:

  • Access the personal data we hold about you;
  • Rectify data that is inaccurate or incomplete;
  • Erase your data (the “right to be forgotten”);
  • Restrict or object to processing, including processing based on legitimate interests;
  • Port the data you gave us to another service in a machine-readable format;
  • Withdraw consent at any time where processing is based on consent (such as the biometric check), without affecting processing that happened before you withdrew.

You have the right to object to direct marketing at any time, including any profiling for it. To stop our marketing emails, use the unsubscribe link in any of them; to stop marketing texts, reply STOP; in the app, switch either off in Settings → Privacy; to object to all of it at once, email privacy@onsiren.com.

Some of this you can do yourself in the app: Settings → AI & your data shows what Alpha One remembers about you and lets you delete it, and Settings → Safety check lets you see and delete your check-ins. For anything else, use our Request Centre or email privacy@onsiren.com. We respond within one month.

You don’t need an OnSiren account to use these rights. If you’re shown or mentioned on OnSiren, for example in an alert or a broadcast, you can ask us what we hold about you, ask us to correct it or add your side of events, or ask us to delete it, through the Request Centre or by email. We may need to check it’s you first. Sometimes the law lets us hold information back, for example to protect other people or to avoid harming the prevention or detection of crime. If we can’t do what you ask, we’ll tell you why where we can.

If you are unhappy with how we handle your data, you can complain to the UK regulator, the Information Commissioner’s Office, at ico.org.uk. We would appreciate the chance to resolve it with you first.

11. Deleting your account

You can delete your account at any time, in the app: tap your call sign on the map to open your profile, then go to Settings → Account → Delete my account. The app asks you to confirm twice. Deletion removes your personal data as described in How long we keep it, unless some of your records have to be kept for a legal reason. You do not need to email us or give a reason. If you prefer, you can also request deletion at privacy@onsiren.com.

12. Security

We protect your data with technical and organisational measures appropriate to its sensitivity: encryption in transit, access controls, audit logging across the network, and the data-minimisation choices described above, such as keeping other officers’ live positions out of persistent storage on your device. Authorised staff can access an account when they need to support or test the service, and we keep a log when they do. No system is perfectly secure, but if a breach ever puts your rights at risk we will notify you and the Information Commissioner’s Office as the law requires.

13. Changes to this policy

When we change this policy we will update the date at the top and, for significant changes, tell you before they take effect: in the app or, if you don’t use the app, by email where Messages we send you allows us to send you service messages. We keep earlier versions of this policy, and we’ll send you the one that applied on any date you ask about. Continued use of OnSiren after a change means the updated policy applies.

14. Contact

Questions about this policy or your data: privacy@onsiren.com. For anything else, see www.onsiren.com/contact.

Cookies

We use cookies to understand how our website is used and improve your experience. These analytics cookies are optional: nothing is set unless you accept. For more information, please see our Cookie Policy.

Privacy Policy | OnSiren