Built on transparency, not blind trust.

Privacy Principles

Samay Cyber Pulse is an enforcement tool, not a surveillance tool. The app does not collect message content, call logs, GPS or precise location, photos, files, or keystrokes, and it does not request location permission.

The Service is built to be Digital Personal Data Protection Act (DPDP), 2023 compliant from day one, with a named Grievance Officer and defined data retention limits. For the complete, legally binding detail of what is collected and why, see the Privacy Policy.

Data We Never Collect

The platform is architecturally incapable of collecting the following, on any deployment:

• Message content
• Call logs
• GPS or precise location
• Photos or files
• Keystrokes
• Browsing content beyond the domain queried

Security Overview

Security principles that hold across every deployment:

• Dedicated VPS. Every customer runs on isolated, per-tenant infrastructure — never shared compute or shared logs.
• DNS over HTTPS. DNS queries are encrypted end-to-end, closing the plaintext DNS gap most filters leave open.
• DNS over TLS. An additional encrypted transport option for environments that require it.
• Fail Closed. If enforcement can't reach the policy engine, access fails closed by default — never silently open.
• Bypass Resistant. Enforcement is designed to resist common circumvention techniques, not just default settings.
• Zero Trust. Every device authenticates independently. No implicit trust from network location or device ownership.

Architecture Overview

Enforcement runs at the DNS layer, between the worker's device and the open internet — not by installing a VPN client that inspects traffic, and not by enrolling the device into an MDM profile.

We build in small, verifiable increments rather than large, infrequent releases, and prioritize auditable, standards-based protocols over proprietary lock-in:

• Built on standard, auditable protocols — DNS-over-HTTPS and DNS-over-TLS — not a proprietary tunneling client.
• Per-tenant infrastructure isolation is a default, not a paid add-on.
• Deployment simplicity is treated as a security property, not just a convenience — every design decision is weighed against IT operational burden.

Deployment Model

No Mobile Device Management enrollment, no company-owned hardware, and no manual device inspections. Workers install the app on their own device and enforcement follows their assigned shift automatically.

Setup is measured in minutes per worker, not a rollout project — there is no fleet of devices to procure, image, or manage.

Cross-Platform Worker Deployment

Cyber Pulse supports both Android and iPhone devices as part of the enterprise deployment architecture. The worker application enables policy enforcement while respecting employee privacy. Organizations can deploy Cyber Pulse without requiring traditional Mobile Device Management (MDM), and deployment is designed to be lightweight, scalable, and suitable for Bring Your Own Device (BYOD) environments.

The Android and iPhone worker applications are deployment components of the Cyber Pulse Digital Workforce Governance platform — not standalone consumer applications.

Platform Support

The mobile applications are deployment endpoints of this flow — not standalone products — reinforcing that enforcement, policy, and reporting all live in the same enterprise platform regardless of which device a worker uses.

Release Philosophy

We ship in small, verifiable increments rather than large, infrequent releases, and we'd rather ship a smaller change we can stand behind than a larger one we can't. Every release is expected to preserve the privacy and architecture commitments on this page — those aren't configuration an update can quietly loosen.

For the actual version history — features, improvements, and fixes as they ship — see Product Updates.

Contact Security

To report a security concern or ask about our security practices, contact us directly at hello@samayinvotech.com.