Security

Security Policy

Last updated: January 21, 2026

At Octran Technologies, we take security seriously and are committed to protecting user information and maintaining a secure website environment.

1. Security Measures

We implement reasonable administrative, technical, and physical safeguards, including:

  • Secure hosting infrastructure
  • Limited access to sensitive data
  • Monitoring for potential vulnerabilities

2. Data Protection

Although we collect limited personal data (such as names and email addresses), we take appropriate measures to prevent unauthorized access, alteration, or disclosure.

3. Analytics and Third-Party Tools

We use third-party analytics tools that may collect non-personal usage data. These providers are selected based on industry-standard security practices.

4. No Account Credentials

Since user accounts are not supported, we do not store passwords or authentication credentials.

5. Incident Response

In the event of a data security incident, we will take reasonable steps to mitigate the impact and comply with applicable legal obligations.

6. User Responsibilities

Users are encouraged to:

  • Use secure networks when accessing the website
  • Avoid submitting sensitive personal information unnecessarily

7. Policy Updates

This Security Policy may be updated periodically to reflect changes in technology or regulatory requirements.

8. Contact

For security-related concerns, please contact:

Octran Technologies New Town, Kolkata 700165 West Bengal, India

MAKE THE CONTROL VISIBLE

A permitted source.
A reviewable next step.

An illustration of scoped controls. Consult the security text above for the current published description.

01

Source

Start inside the permission boundary.

Agree which sources belong in the workflow. Illustrative controls are not evidence of a security audit.

  • Permitted source
  • Workflow scope
  • Responsible owner
02

Proposal

Keep prepared work inspectable.

The product direction keeps a proposal and its supporting information visible together.

  • Prepared work
  • Supporting context
  • Visible reasoning
03

Review

Keep consequential actions with the team.

Important actions should respect the agreed review boundary. Current assurances belong in the published text and partner discussion.

  • Approval rules
  • Human review
  • Published description
Output A clear control boundaryNo certification, audit or deployment guarantee implied.