Safety & Trust

How we try to keep the network safe

Trust should be shown, not just claimed. Here is how RAKSHA approaches verification, safeguarding, privacy and moderation — and where our limits are.

RAKSHA does not replace emergency services and a community response is not guaranteed. In a life-threatening emergency, always call 112 or 999 first.

What "verified" actually means

An identity check confirms a submitted document. It does not certify anyone’s character or future conduct — so we pair it with conduct rules, moderation and reporting.

1

Submit a document

Provide a government-issued photo ID (passport, driving licence, or National Age Card) during sign-up.

2

Manual review

A RAKSHA team member reviews your document during published support hours — not an automated guess.

3

Approval or appeal

Once approved, you can access community alerts. If a check fails, you can appeal or resubmit.

4

Retention & deletion

Documents are retained only as long as needed for verification and handled per our privacy policy.

The controls behind the network

The safeguards that shape how alerts, responders and data are handled.

Identity verification

Every account completes an identity check before accessing community alerts. Documents are reviewed manually, stored according to our retention policy, and re-verification may be requested. Failed checks can be appealed.

Responder eligibility

Responders must meet minimum age and residency requirements, accept the code of conduct, and may be periodically re-approved. Background checks are applied where lawful and appropriate.

Responder conduct

No pursuit, no confrontation, no weapons, no entry into private property, no transporting of users, and no medical treatment beyond a responder’s competence. Support is non-confrontational only.

Safeguarding

Specific rules protect minors and vulnerable adults, with mandatory escalation, grooming prevention, restricted contact, and post-incident review built into how the network operates.

Alert triage & escalation

Alerts are guided towards emergency-service escalation where needed. False, accidental, and duplicate alerts are handled, and dangerous scenes are flagged for 112/999 rather than community response.

Privacy controls

Your location is captured only when you trigger an SOS and shared with approved nearby members for that alert — never tracked continuously. Access to incident records is limited and kept only for defined retention periods.

Abuse & moderation

Block and report controls are built in. Reports are reviewed, accounts can be suspended, appeals are possible, and repeat-abuser and law-enforcement request processes exist.

Responder safety

Responders can decline any alert, hide their availability, receive risk context, share status, avoid unsafe areas, and are always guided to call 112/999 rather than intervene in danger.

How your data is handled

Incident records are encrypted in transit and at rest, with role-based access.
Your location is captured only when you trigger an SOS — there is no continuous or background tracking.
Identity documents and location data are kept only as long as needed, with defined retention periods.
A Data Protection Impact Assessment (DPIA) is part of our pre-launch governance.
You can request access to, correction of, or deletion of your data under GDPR.

Detail on lawful bases, processors, international transfers and data-subject rights lives in our Privacy Policy.

Who is behind RAKSHA

RAKSHA Ireland is operated by an accountable team based in Dublin. Our legal entity details, registered address, named safeguarding lead and data-protection contact are published as we move through beta and towards public launch.