Independent. Not run by Lambeth Council or any council.

Run by DanceOnVibes Limited, a small independent London company. SafeWatch.Lambeth isn't monitored in real time. Please report responsibly and with realistic expectations.

If you or someone else is in immediate danger, call 999 now. SafeWatch is not an emergency service and does not replace them.

Privacy

Privacy Notice

This notice explains what SafeWatch.Lambeth collects, why, how we handle it, and your rights. It applies to the SafeWatch.Lambeth website at lambeth.safewatchhq.com. Version 1.3 · Last updated 24 October 2026.

Who is responsible for your data

SafeWatch.Lambeth is operated by DanceOnVibes Limited, registered in England and Wales (company number 17423769). Registered office: 167–169 Great Portland Street, 5th Floor, London, W1W 5PF.

Registered with the Information Commission (the ICO), registration number ZC249791. Privacy contact: the Data Protection Officer, DanceOnVibes Limited — contact page or email privacy@safewatchhq.com.

The two reporting flows

  • (a) Concern reports — no account needed to submit: you can send a concern report without signing in. We store the report content, your safe-contact preference, and any optional name, email and preferred contact method you choose to give. You are shown a reference and a one-time access code. To look the report up later you sign in and enter both. Reports may contain descriptions of third parties and are processed only for community safeguarding purposes, subject to Investigation Shielding and staff-only access.
  • (b) Community observations — no account needed: you don't need an account or to give your name. You can add an optional email if you'd like status updates. For location you can drop a pin on the map, or tap "Use my location" so your browser shares your device's location (your browser asks your permission first). Photos have EXIF/metadata stripped before upload. You are shown a reference and a one-time access code; adding a follow-up later needs you to sign in and enter both.

What we collect

  • Account details: name and email so you can sign in and we can administer your account. If you sign in with Google, we receive your email and basic Google profile from Google.
  • Report content: category, description, incident date, and a general area (free text, not an exact address). Reports may include personal accounts, observations, or concerns — including descriptions of third parties, processed only for community safeguarding.
  • Safe-contact preferences and optional contact details: how and whether we may contact you, and any optional name, email or preferred contact method you choose to give with a report. These are stored with the report.
  • Photos: optional community-observation photos. Metadata (including GPS) is stripped before upload, client-side and again server-side as defence-in-depth.
  • Location coordinates: on a community observation, either where you drop a pin on the map or, if you tap "Use my location", your device's location as given by your browser. The coordinates are stored with the report. The exact location is visible only to the SafeWatch team; public summaries show only broad areas. If we pass an observation to the police or the council, we give a street-level location only (see Information sharing).
  • Audit logs: a record of key actions that only our team can see (report created, lookups, referrals, staff access, moderation, consent). Stored without access codes, hashes, or sensitive narrative.
  • Basic technical data: the minimum needed to keep the service working and secure — sign-in session data, and short-lived server access logs that may include IP addresses. IP addresses are treated as personal data, used only for security, abuse prevention and essential service operation, and retained only for as long as needed.
  • Analytics (optional): if you enable analytics cookies, Google Analytics 4 sets its cookies (_ga and _ga_02E2CLNP8M) and records page-view statistics, which we see only in aggregated form. Google states that Google Analytics 4 does not log or store IP addresses. Analytics is off by default and loads only after you agree; you can withdraw consent at any time. See Cookies & website data.
  • Anonymous daily counts: how many times a day the 999/101 screen is shown after someone answers "yes" to the crime question, and how many residents were emailed a council reply. These are totals only: no names, accounts, IP addresses, cookies or what anyone typed. They appear on the public pilot numbers page.
  • Map tile requests: the community-observation map closed on 24 October 2026, so public pages no longer load OpenStreetMap map tiles (staff screens may still show a map of older reports).

Lawful bases for processing

  • Contract — Article 6(1)(b): creating and operating your account if you choose to have one.
  • Legitimate interests — Article 6(1)(f): running the service — receiving, reviewing and signposting reports, sending updates you asked for, safety moderation, keeping the platform secure and preventing misuse. We have weighed these interests against your rights and keep what we collect to the minimum needed.
  • Vital interests — Article 6(1)(d): where a report indicates a risk to life or safety, we may act or disclose to protect individuals.
  • Consent — Article 6(1)(a): for optional things: analytics cookies, optional contact details and status updates, and using your device location when you tap "Use my location". Your cookie choice is saved in your browser (sw_cookie_consent_v1). If you're signed in, we also keep a record for 24 months. You can withdraw consent at any time.
  • Legal obligation — Article 6(1)(c): only where a law or court order requires us to keep or disclose specific information.
  • Recognised legitimate interest (UK GDPR Annex 1): when we pass information to the police, the council or safeguarding services to help prevent or detect crime or to protect someone — including passing community observations to the Met's Safer Neighbourhood Team or Lambeth Council.

Please keep sensitive details out. Please don't include health information or other sensitive details (such as religion, ethnicity or sexuality) about yourself or anyone else unless it is genuinely needed to explain the concern.

Special category data. Some reports include special category data — for example health details. We rely on these conditions:

  • Sensitive details about yourself: your explicit consent (UK GDPR Article 9(2)(a)). You give it when you choose to include them, and you can ask us to remove them.
  • About a child, or an adult at risk, where consent can't be got: Article 9(2)(g) with the Data Protection Act 2018, Schedule 1, Part 2, paragraph 18 (safeguarding of children and of individuals at risk).
  • Possible crimes (for example domestic abuse, stalking or harassment, scams): Article 10 of the UK GDPR with the Data Protection Act 2018, Schedule 1, paragraph 10 (preventing or detecting unlawful acts).
  • Disclosures to the police, the council or safeguarding services: recognised legitimate interest (UK GDPR Annex 1).

Appropriate policy document. The Schedule 1 conditions above need an appropriate policy document. Ours is being finalised; you can ask for a copy at privacy@safewatchhq.com.

Safeguarding data — special category and vulnerable person data

SafeWatch.Lambeth processes personal data relating to children, vulnerable adults, and safeguarding concerns where necessary for substantial public interest. This includes concerns about domestic abuse, coercive control, stalking or harassment, exploitation, and the safety of children or people at risk.

  • Article 6(1)(f) — legitimate interests: recording, reviewing and signposting safeguarding concerns so that people at risk can get the right help.
  • Article 6(1)(d) — vital interests: where there is a risk to someone's life or safety.
  • Article 9(2)(a) — explicit consent: for sensitive details you choose to give about yourself.
  • Article 9(2)(g) — substantial public interest: only for a child, or an adult at risk, where consent can't be got — read with Schedule 1, Part 2, paragraph 18 of the Data Protection Act 2018 (safeguarding of children and of individuals at risk).
  • Article 10 — possible crimes: read with Schedule 1, paragraph 10 of the Data Protection Act 2018 (preventing or detecting unlawful acts).
  • Article 9(2)(f) — legal claims: where processing is necessary for the establishment, exercise, or defence of legal claims.

Such data is passed to authorised safeguarding partners — for example the police, the local authority, or a designated safeguarding lead — only when strictly necessary and proportionate. We share information only (a) through a deliberate staff referral with your consent, (b) where there is a serious risk to someone's life or safety, (c) where the law requires it, or (d) for community observations, as described under Information sharing. See our Safeguarding Policy for full details.

Information sharing — important

Reports are NOT automatically shared with the police, the council, or any other organisation. This is a core promise of SafeWatch.Lambeth.

We share concern reports only (a) through a deliberate staff referral with your consent, (b) where there is a serious risk to someone's life or safety, or (c) where the law requires it.

Community observations: we may pass what you describe (place, time, pattern, photos — never your email) to the Met's Safer Neighbourhood Team or Lambeth Council. We remove names and number plates and give a street-level location. If a report may name a person or has a photo, someone on our team reads it first and removes anything that identifies a person. If a number plate matters to a possible crime, our team may give it to the police directly — never to the council or anyone else. This is done by a person, never automatically. Lawful basis: recognised legitimate interest (UK GDPR Annex 1, crime), with Article 10 and the Data Protection Act 2018, Schedule 1, paragraph 10.

Shared issues are an example of (a): a combined report is sent by our team only for residents who ticked the consent box. It contains no names, addresses or emails (where residents agreed, it includes their council reference numbers) and gives totals rather than personal details — see Shared issues.

No Wrong Door. SafeWatch.Lambeth follows a "No Wrong Door" principle: we help record your concern and route it to the correct official service, rather than turning you away for choosing the wrong route. Routing is not automatic — it happens only through the referral steps above.

How long we keep information

  • Account data: account lifetime plus 6 years after account closure.
  • Concern reports and access code hash: 6 years after case closure, then deleted or anonymised.
  • Safeguarding flags: 6 years after case closure.
  • Community observation reports: 6 years after triage closure.
  • Community hub messages and contributor-flow data: 24 months, then deleted or anonymised.
  • Safe Circle check-ins: 12 months after the last check-in.
  • Consent records (signed-in people only): 24 months from the most recent consent decision or update.
  • Photo and video uploads: photos are removed from reports when the report is deleted; stored copies are cleared in our regular manual reviews.
  • Audit events: 6 years.
  • Referrals: 6 years after case closure.
  • Optional contact details given with a report: kept with the report for the same period, unless removed sooner (for example after an account deletion request).
  • Look-up and submission-limit records (used to block guessing of access codes and floods of reports): up to one month. Submission limits store only a one-way hash of your connection's IP address combined with a secret value and the date, never the IP address itself.
  • Data-rights requests: kept for 6 years as a record of how we handled the request.
  • Forum posts (including original text), community requests, contributor profiles, trade reviews and concerns, local listings, and case action plans: not deleted automatically — reviewed and deleted manually at least every 12 months once no longer needed.

The full schedule, including deletion and anonymisation procedures, archiving exceptions, legal holds, and the responsible person, is set out in our Data Retention Policy. Records are deleted by scheduled retention purges or in our regular retention reviews once these periods end. We do not keep data for longer than is needed. Records subject to pending litigation, a statutory investigation, or a legal hold are retained until the hold is lifted.

Your rights

Under UK data-protection law you have the right to:

  • access your personal data;
  • rectify (correct) it where it is inaccurate;
  • erase it, subject to the limits below;
  • restrict processing;
  • data portability (receive it in a machine-readable form);
  • object to certain processing; and
  • withdraw consent at any time where we rely on it.

If you have an account, your Account page lets you download a copy of your data as a file, and has a "Delete my account" button. When you use it, we remove your name, email and contact preferences from the reports linked to your account, log a deletion request, and email you to confirm. Report content needed for safeguarding is kept, but no longer linked to you. Our support team then completes the closure of your account within one month — the sign-in account is closed by our team, not instantly.

You can also exercise these rights through the data-rights request page (you'll need to sign in), or — with or without an account — by emailing privacy@safewatchhq.com. We respond within one month.

Two things we state transparently: (1) erasure of data already shared via a lawful and necessary referral may be limited where the disclosure was lawful and necessary; and (2) fully anonymous community observations cannot be traced back to a requester, so we cannot locate an anonymous report by anything other than its reference.

If you are mentioned in a report

Concern reports, community observations, forum posts and community requests can describe other people. If you are mentioned, we hold what the person wrote about you (and sometimes a photo), and we use it only to review the concern, signpost help, keep the site safe and, where described above, pass it to the police, the council or safeguarding services. We got this information from the person who wrote the report, not from you.

We don't usually tell people that they have been mentioned. Doing so could put the reporter or someone else at risk, or harm a police or safeguarding enquiry (UK GDPR Article 14(5), and the Data Protection Act 2018, Schedule 2, paragraph 2 — crime). We keep it for the periods in "How long we keep information".

You still have the rights listed above. Email privacy@safewatchhq.com and we'll tell you what we can. If public content on the site names you and you think it's untrue or harmful, use Content that names you.

Anonymous community observations

We stopped taking new community observations on 24 October 2026. Crime, drug activity, anti-social behaviour and camera problems now go straight to the police or the council. Observations sent before then are kept and deleted under the retention schedule below, and the rest of this section still applies to them.

  • No name, email or account is required.
  • If you give an email, it is stored with your report so our team can send you status updates when the report's status changes. It is never published. It is kept with the report until the report is deleted under our retention schedule. If you give no email, we cannot send you updates.
  • If you are signed in when you submit, a confirmation with your reference (never your access code) is sent to your account email. Otherwise no confirmation email is sent. Either way, please note the reference and access code shown on screen.
  • To add a follow-up you sign in and enter the reference (shown once at submission) together with the one-time access code.
  • Photos have location and other metadata removed before upload, and again server-side as defence-in-depth.

Shared issues — combined reports to the council

On Shared issues, signed-in residents can start an issue about a place or council service, or flag an existing one ("this affects me too"). When enough neighbours have flagged an issue, our team sends one combined report to Lambeth Council through its official routes, by hand. Nothing is sent automatically.

  • What we keep: which account flagged which issue, your answers (whether you reported it yourself, how it affects you), an optional council reference number, an optional note for our team, and whether you want updates. If you start an issue, we keep that your account started it.
  • What the council receives: totals only — how many residents flagged it, between which dates, how many say they reported it themselves, and how many chose each impact (numbers under 3 are shown as "fewer than 3"). Never your name, address, email or note. Your council reference number is included only if you tick the box to share it.
  • Lawful basis: your consent to be counted in the combined report (you tick a box for every flag), and our legitimate interest in running the service and keeping it safe and free of duplicates and abuse.
  • Withdrawing: you can withdraw your flag at any time from the issue. It stops counting straight away. A combined report that has already been sent can't be recalled. It contains no names, addresses or emails. Where residents agreed, it includes their council reference numbers.
  • Updates: if you ask, we email your account address when the issue moves on (for example when the report is sent or the council replies). You can turn this off from the issue.
  • Public view: issue titles, the street, estate or block, the ward, a short description, rounded totals ("fewer than 5", "10+"), updates, the council's reply as sent, its commitments, and rounded answers to "is it fixed?". Who flagged an issue, and exactly when, is never shown.
  • "Is it fixed?": when the council says work is done, we may ask the residents who flagged it. Your answer is stored with your flag and only rounded totals are published.
  • Ward briefings: each month we publish a summary per ward and send the same copy to every ward councillor. Resident numbers from 1 to 7 are shown as "fewer than 8" and others are rounded to the nearest 5. Briefings contain no personal data.
  • Retention: your flags are kept while the issue is active and deleted within 12 months after it is resolved or closed. If you delete your account, your flags are deleted and you are unlinked from any issue you started.

Help & Support pages — zero collection

The public "Help & Support" section is a signposting resource only. Those pages collect no personal data and contain no forms. If you have enabled analytics cookies, standard anonymous page-view analytics may run like the rest of the site; no personal data is collected on these pages. You can read them without signing in.

Children, young people and vulnerable individuals

SafeWatch.Lambeth is a service for adults and requires users to be 18 or older to create an account (see our Terms of Use). Before 18 October 2026 the minimum age was 16; accounts opened before then are not changed. If we find that someone under 18 has opened an account after that date, we may close it. We do not knowingly collect personal data from children under 16. If we become aware that we have received personal data from a child under 16, we will delete it where required by law, except where it must be retained under a safeguarding lawful basis.

Adults may report safeguarding concerns about children or vulnerable individuals. Where a safeguarding concern is submitted by an adult or an authorised referrer (for example a parent, carer, or support worker acting on someone's behalf), the data is handled under the safeguarding lawful bases set out above. SafeWatch is not a statutory safeguarding route — for urgent safeguarding concerns, contact the appropriate statutory service or, in an emergency, call 999. See our Safeguarding Policy for details.

Area-level, not address-level

Public community views show only verified notices and aggregated trends — never individual reports, exact addresses, raw case details, or anything that identifies a reporter, household, or accused person. Reports under Investigation Shielding are excluded from all public surfaces entirely.

Where a community observation includes map coordinates, the exact location is visible only to the SafeWatch team; public summaries show only broad areas. If we pass an observation to the police or the council, we give a street-level location, not the exact pin.

International transfers

SafeWatch.Lambeth is hosted on the Base44 platform, which uses cloud infrastructure providers. This means some processing of personal data may take place outside the UK. Where it does, we rely on appropriate safeguards, such as the UK International Data Transfer Agreement or the UK Addendum to the EU Standard Contractual Clauses, or on UK adequacy regulations where they apply.

The third parties described in "Who we share data with" below — Google sign-in (only if you use it), and Google Analytics (only if you enable it) — may also process limited technical data outside the UK.

If you are in the EU/EEA, your data transfers to the UK under the European Commission's adequacy decision for the UK (Commission Implementing Decision (EU) 2025/2574 of 19 December 2025, valid until 27 December 2031); no additional safeguard is required while adequacy holds.

Who we share data with — sub-processors and third parties

To operate the service we work with the following third parties. We share only what is necessary for each to perform its function:

  • Base44 platform (processor): hosts and operates the app — authentication, database, file storage, and transactional email. All app personal data is processed here. Base44 uses cloud infrastructure providers (see International transfers).
  • AI assistants for our staff (processor, via the platform): the SafeWatch team can use AI assistants provided through the Base44 platform to help them prioritise reports, review forum content, trade reviews and community requests, draft the monthly public digest and keep track of data-rights deadlines. The assistants can only read what that staff member is already allowed to see, and only suggest. A person makes every decision, and no decision about you is made by automated means alone (UK GDPR Article 22). The AI model provider processes this text to give the assistant's answer, on the platform's instructions. Our hosting platform, Base44, says in its help pages that on its plans below Enterprise (we are on one of these) app data, including what people submit through forms, can be used to train AI models, with no setting to turn this off. We are asking Base44 to confirm in writing that SafeWatch.Lambeth data is excluded, and will update this notice when it answers.
  • Wix / Base44 image CDN (processor): serves and resizes content images. Image bytes and image URLs are processed; no other personal data is shared.
  • Google (identity provider and analytics): acts as a controller for the 'Continue with Google' sign-in step (your email and Google profile, as returned by Google). Separately, Google Analytics 4 runs only if you enable analytics cookies (see above).
  • OpenStreetMap (functional third party): no longer used: the community-observation map that loaded its tiles closed on 24 October 2026.
  • Email delivery (processor, via the platform): sends receipts, confirmations and data-rights acknowledgements to your account email, and status updates to an email you chose to give with a community observation.

We do not sell your data to anyone. We do not use third-party advertising or marketing trackers. A full sub-processor inventory is maintained internally and reviewed as part of our compliance programme.

Complaints about how we use your data

If you're unhappy with how we've used your personal information, tell us first: email privacy@safewatchhq.com with "Data protection complaint" in the subject, or use the data-rights request page.

We'll acknowledge your complaint within 30 days, look into it properly, and tell you what we found and what we've done about it without undue delay. You can also complain to the Information Commission (the ICO), ico.org.uk, at any time.

Right to complain to the Information Commission

If you are not satisfied with our response to a privacy concern, complain to us first at privacy@safewatchhq.com; we'll acknowledge within 30 days. You can also complain to the Information Commission (the ICO) at ico.org.uk (telephone 0303 123 1113).

Privacy questions

For any privacy or data-protection matter, contact our privacy contact, the Data Protection Officer, DanceOnVibes Limited, at privacy@safewatchhq.com or write to 167–169 Great Portland Street, 5th Floor, London W1W 5PF. See also the privacy contact page.

    We only use the data needed to keep SafeWatch.Lambeth working and secure. With your permission we'd also use Google Analytics, which sets cookies and sends Google how you use the site, so we can improve it. It's off unless you accept, never runs on report or look-up pages, and we use no advertising cookies. See our Cookies notice and Privacy Notice.