How Vigilo protects customer data — technically and operationally.
This Data Security Policy describes the technical and organisational measures that Safety Desk ("we", "us", "our"), operator of Vigilo (www.safety-desk.com), implements to protect customer data processed through the Vigilo platform. This document is intended for customers, procurement teams, and data protection officers conducting security due diligence.
Vigilo is hosted entirely on Amazon Web Services (AWS), one of the world's leading cloud infrastructure providers. AWS holds the following certifications independently of Vigilo:
Data centre region: ap-south-1 (Mumbai, India).
All customer data — including the database, file storage, and application servers —
is stored and processed exclusively within India. No data is transferred outside
India without explicit customer consent.
| Layer | Method | Status |
|---|---|---|
| Data in transit (browser ↔ server) | TLS 1.2+ via AWS CloudFront CDN | Enabled |
| Database at rest (RDS PostgreSQL) | AES-256 via AWS RDS encryption | Enabled |
| File storage at rest (S3) | AES-256 via AWS S3 SSE | Enabled |
| User passwords | PBKDF2-SHA256 with salt (Django default) | Enabled |
| Worker PINs | PBKDF2 with salt via Django hashers | Enabled |
Every user in Vigilo is assigned one of five roles that strictly controls what they can see and do:
All database queries are scoped by organisation. It is technically impossible for a user in Organisation A to access any data belonging to Organisation B. This isolation is enforced at the application layer on every request.
There is no open public registration for employee accounts. All users must be invited by a Manager within the organisation. Invitations expire after 7 days.
An email address can be registered with only one organisation. If an invitation is sent to an email already registered with a different organisation, the invitation is blocked and no account transfer occurs.
| Control | Implementation |
|---|---|
| CSRF protection | Django CsrfViewMiddleware — enforced on all POST requests |
| XSS prevention | Django template auto-escaping on all user-supplied content |
| SQL injection prevention | Django ORM with parameterised queries — raw SQL is not used |
| Clickjacking protection | X-Frame-Options: DENY header via Django middleware |
| HTTPS enforcement | HTTP requests redirected to HTTPS via CloudFront |
| Session security | Secure, HttpOnly session cookies; session invalidated on logout |
| Secrets management | All credentials stored as environment variables — never in source code |
| File upload validation | File type and size validated on upload; stored in private S3 bucket |
We target 99.9% monthly uptime. The platform is monitored continuously. Scheduled maintenance windows are communicated to customers at least 24 hours in advance and are scheduled outside business hours (IST).
All customer data is stored and processed within AWS ap-south-1 (Mumbai, India). This includes the PostgreSQL database, all uploaded media and documents, and application logs. Transactional emails are delivered via Brevo (EU-based); email content is transmitted to Brevo solely for the purpose of delivery and is not retained by them beyond delivery.
| Sub-processor | Purpose | Data location |
|---|---|---|
| Amazon Web Services | Application hosting, database (RDS), file storage (S3) | India — ap-south-1 (Mumbai) |
| Brevo (Sendinblue) | Transactional email delivery (alerts, invitations) | European Union |
| Razorpay | Payment processing (subscription billing) | India |
| GoDaddy | Domain name registration only | USA (domain metadata only — no customer data) |
Each sub-processor is contractually bound to process data only as instructed and to maintain appropriate security standards.
In the event of a confirmed security incident or data breach:
Vigilo operates in accordance with the Information Technology Act, 2000 and the IT (Reasonable Security Practices and Procedures and Sensitive Personal Data or Information) Rules, 2011 of India. For customers subject to GDPR, we are prepared to enter into a Data Processing Agreement — see our DPA.
For security enquiries, to request a signed copy of this policy, or to report a
vulnerability responsibly:
Email: contact@safety-desk.com
Subject line: Security — [your company name]
We aim to acknowledge all security reports within 1 business day.