Back to Support

Security Statement

Our approach to protecting the confidentiality, integrity, and availability of customer data

Version 2.0 · Last Updated: 5/11/2026

SafeLogs is committed to protecting the confidentiality, integrity, and availability of customer data. This Security Statement describes our general approach to security. It is provided for informational purposes only and does not modify any contractual obligations.


1. Security Approach

SafeLogs maintains an information security program designed to apply reasonable administrative, technical, and organizational safeguards appropriate to the nature of the Services and the data processed.

Security controls are designed to reduce risk, not eliminate it entirely. SafeLogs regularly reviews and updates its security practices in response to evolving threats and industry standards.


2. Technical Safeguards

SafeLogs employs measures such as:

  • Encryption of data in transit (TLS 1.2 or higher for all communications)
  • Encryption of data at rest (AES-256 or equivalent for stored customer data)
  • Role-based access controls
  • Secure authentication mechanisms, including multi-factor authentication for administrative access
  • Logging and monitoring of system activity
  • Secure development and deployment practices
  • Regular dependency and vulnerability review
  • Automated security scanning of application code

3. Access Controls

  • Access to production systems is limited to authorized personnel
  • Access is granted on a least-privilege basis
  • Credentials are managed and reviewed periodically
  • Access logs are maintained and reviewed for anomalous activity
  • Access is promptly revoked upon personnel role changes or departure

4. Data Isolation

Customer data is logically isolated by account and organization. Customers cannot access data belonging to other customers. SafeLogs implements database-level controls to enforce tenant separation.


5. Infrastructure and Hosting

SafeLogs utilizes reputable third-party infrastructure providers that maintain industry-recognized security certifications. A current list of subprocessors is maintained at safelogs.in/subprocessors.


6. Incident Response

SafeLogs maintains internal procedures to identify, assess, and respond to security incidents. In the event of a confirmed security incident involving customer data, SafeLogs will notify affected customers in accordance with applicable agreements and law. SafeLogs classifies incidents by severity and responds within defined timeframes as outlined in our internal Security Incident Response Plan.


7. Business Continuity

SafeLogs maintains backup and disaster recovery procedures designed to ensure the availability and recoverability of customer data. Backup procedures are tested periodically.


8. Customer Responsibilities

Security is a shared responsibility. Customers are responsible for:

  • Securing their own devices and networks
  • Managing user access and permissions within their SafeLogs account
  • Using strong passwords and authentication practices
  • Ensuring appropriate operational controls within their organization
  • Promptly notifying SafeLogs of any suspected unauthorized access to their account

9. Security Assessments

SafeLogs conducts periodic internal reviews of its security posture and may engage third-party assessors as appropriate. Enterprise customers may request additional security documentation subject to a mutual non-disclosure agreement.


10. No Guarantees

While SafeLogs takes security seriously, no system can be guaranteed to be completely secure. This Security Statement does not create warranties, guarantees, or service level commitments.


11. Changes

SafeLogs may update this Security Statement from time to time. Material changes will be posted at safelogs.in/security with at least thirty (30) days' advance notice.


12. Questions

Security-related questions may be directed to:

Jet Innovative Media LLC d/b/a SafeLogs
Email: support@safelogs.in

Website: safelogs.in/security