📘 Vigilo — Help & User Guide
📘 What is Vigilo?

A digital safety management platform covering all aspects of workplace safety — replacing spreadsheets and manual follow-ups with a single system.

📋 Observations — report, assign & verify
🔐 Permit to Work — digital approvals & LOTO
⚠️ HIRA — ISO 45001 5×5 risk register
🚨 Incidents — RCA workflow, LTIFR/TRIFR
🔍 Inspections — mobile checklists & auto-score
⚖️ Legal Compliance — traffic-light register
✅ Corrective Actions — cross-module CA hub
🎓 Training & Skills — plans, sessions & passport
🏆 Appraisals — goal setting & performance review
🌿 ESG & BRSR — SEBI BRSR, GRI & TCFD reporting

🔍 Observations — Workflow
  1. Observe — Any user records an observation (safety, quality or general) with description, severity & photo.
  2. Assign — Safety Manager assigns an Action Owner and sets a target date.
  3. Rectify — Action Owner fixes the hazard, uploads a "after" photo and submits.
  4. Verify — Safety Manager reviews the fix: Approve (closes it) or Reject (sends back for re-work).
  5. Archive — Closed observations move to the archive for record-keeping.

Severity levels: High · Medium · Low


🪪 Permit to Work (PTW) — Workflow

A Permit to Work is a formal written document that authorises high-risk work. No work should begin until an approved permit is in hand.

  1. Raise — Requestor fills the permit (work type, location, dates, hazard assessment, risk controls, PPE, isolation, emergency procedure) and clicks Submit for Approval in one step. Save as Draft keeps a partial permit to finish later.
  2. Approve / Reject — Safety Manager (or Manager) reviews the permit and pins the authorised work location on a map.
    • Approve — Work is authorised. Approved By and timestamp are recorded.
    • Reject — Permit is rejected with comments. Requestor must revise and resubmit.
  3. Pre-Work Checklist — On site, the Requestor completes the work-type checklist and confirms the actual start time; this activates the permit. Their device location is checked against the approved work location — a large gap is flagged (not blocked).
  4. Close — When work is complete, the permit is closed. Site restoration and final sign-off details are captured.

A permit can also be Cancelled by the Requestor (or Manager) at Draft or Submitted stage if the work is no longer required.

Draft → Submitted → Approved → Active → Closed

Work Types requiring a Permit:

🔥 Hot Work 🚪 Confined Space ⚡ Electrical ⛏ Excavation 🏗 Lifting & Rigging 🪜 Work at Height ⚠ Breaking Containment 📋 General High-Risk

👥 Roles & Responsibilities
Role Observations Permits to Work
Observer Reports observations Creates & submits permits
Action Owner Submits rectifications Creates & submits permits
Safety Manager Assigns, verifies & closes Approves, rejects & closes permits
Manager Full access Full access, invites users, manages billing
Vigilo
All modules — 18 tools, one platform
Safety Operations
📋 Observations 🔐 Permit to Work 🔒 Lockout / Tagout 🚨 Incidents 🔍 Inspections & Audits ✅ Corrective Actions
Risk & Compliance
⚠️ HIRA ⚖️ Legal Compliance 🔁 Change Management
Reporting
📈 Executive Overview 🌿 ESG & BRSR Reporting Add-on
People & Culture
🎓 Training & Skills 📊 Training Need Analysis Add-on 👁️ Behaviour Based Safety 🏆 Performance Appraisals 💬 Grievances Add-on 🪪 Employee Screening Add-on 🧭 Induction Training Add-on
Compare all modules → Start free →
Pricing Help
Sign in Request a demo Get started
Effective: 1 June 2026

Privacy Policy

How Vigilo collects, uses, and protects your data.

This Privacy Policy describes how Vigilo ("we", "us", or "our"), operated by Safety Desk (safety-desk.com), collects, uses, and safeguards information when you use our workplace safety management platform. By accessing or using Vigilo, you agree to the practices described in this policy.

1. Information We Collect

Account and organisation information

  • Organisation name, domain, and logo
  • User names, email addresses, job titles, and designations
  • Employee ID numbers and PIN credentials (for field worker login)
  • Subscription and billing details (processed by Razorpay — we do not store card data)

Safety and operational data

  • Safety observations, hazard reports, and incident records
  • Permit-to-work entries, inspection checklists, and audit findings
  • HIRA assessments, corrective actions, and compliance records
  • Training records, assessment attempts, and performance appraisals
  • Photos and documents uploaded as evidence or attachments

Usage data

  • Browser type, IP address, and pages visited (for security and diagnostics)
  • Error logs and application crash reports

2. How We Use Your Information

  • To provide, operate, and improve the Vigilo platform
  • To send automated alert emails and system notifications you have configured
  • To process subscription payments and manage your account
  • To respond to support requests and enquiries
  • To detect and prevent fraud, abuse, and security incidents
  • To comply with applicable laws and regulations

We do not sell, rent, or share your data with third parties for marketing purposes.

3. Data Storage and Location

All application data and uploaded files are stored on Amazon Web Services (AWS) infrastructure located in the ap-south-1 (Mumbai, India) region. Your data does not leave India except as described in Section 4 below.

4. Third-Party Services

We use the following sub-processors to deliver our service:

  • Amazon Web Services (AWS) — cloud hosting, database (RDS PostgreSQL), and file storage (S3). Data residency: ap-south-1, India.
  • Brevo (Sendinblue) — transactional email delivery. Email content is transmitted to Brevo's servers solely for the purpose of delivery.
  • Razorpay — payment processing. Razorpay handles all card and payment data; we receive only transaction status and identifiers.

Each sub-processor is bound by its own data protection obligations and is not permitted to use your data for any other purpose.

5. Data Retention

We retain your organisation's data for the duration of your active subscription. Upon account termination or cancellation, we retain data for 30 days to allow for recovery, after which it is permanently deleted from all systems. You may request earlier deletion by contacting us.

6. Security

We implement industry-standard security measures including:

  • TLS 1.2+ encryption for all data in transit
  • Encrypted storage for sensitive credentials
  • Role-based access controls so users only access data within their organisation
  • Regular automated database backups

No system is completely secure. In the event of a data breach that affects your organisation, we will notify you within 72 hours of becoming aware of it.

7. Your Rights

As an account holder you have the right to:

  • Access — request a copy of the data we hold about your organisation
  • Correction — request correction of inaccurate data
  • Deletion — request deletion of your organisation's data
  • Export — export your data in CSV or PDF format at any time from within the platform

To exercise any of these rights, contact us at the address below.

8. Cookies

Vigilo uses session cookies strictly necessary for authentication. We do not use advertising or analytics tracking cookies.

9. Applicable Law

This policy is governed by the Information Technology Act, 2000 and the Information Technology (Reasonable Security Practices and Procedures and Sensitive Personal Data or Information) Rules, 2011 of India.

10. Changes to This Policy

We may update this policy from time to time. Material changes will be notified to your account's registered email address at least 14 days before they take effect. Continued use of the platform after that date constitutes acceptance of the updated policy.

Contact Us

For privacy-related queries, data access requests, or to report a concern:
Email: contact@safety-desk.com
Website: www.safety-desk.com

Delete this record?

This action cannot be undone.