Security begins with separation, control and traceability.
CyberSaathi’s public product layer should be cleanly separated from operational applications, APIs, data, credentials and non-production environments.
Environment Separation
Keep the public website, production APIs, staging systems, development services and operational data isolated from one another.
Controlled Access
Use application authentication, licensing and access controls appropriate to the deployed CyberSaathi environment.
Traceability
Preserve relevant audit records and operational history so system actions can be reviewed where the product supports it.
Configuration Isolation
Maintain separate production and non-production credentials, databases, Firebase configuration and API secrets.
Data Minimization
Use only the data required for the authorized purpose and avoid placing sensitive case information in public website forms.
Secure Maintenance
Treat dependency updates, backups, logs, deployment review and credential rotation as ongoing operational responsibilities.
Keep operational endpoints out of normal public navigation.
The brand website can describe the architecture without publishing sensitive implementation details, credentials, internal paths or environment configuration.
cybersaathi.in
Marketing, trust, legal and demo request pages.
api.cybersaathi.in
Production service layer, separately protected.
staging.cybersaathi.in
Non-production testing with separate configuration.
docs.cybersaathi.in
Future documentation with appropriate access policy.