Feature
Privacy
No message content, no call logs, no location tracking — enforcement only.
Quick Summary
Privacy in Cyber Pulse is an architectural constraint, not a setting: the platform never collects message content, call logs, GPS location, photos, files, or keystrokes, and only processes domain-level enforcement metadata.
Business Problem
Organizations need to govern internet access without taking on the legal, ethical, and trust liabilities of employee surveillance — and employees need assurance that a governance tool isn't secretly a monitoring tool.
Feature Overview
Privacy is not a setting within Cyber Pulse — it's an architectural constraint on what the platform is capable of collecting. The app does not collect message content, call logs, GPS location, photos, files, or keystrokes, and it does not request location permission. Only domain-level enforcement metadata is processed: which domains were queried, and whether each was allowed or blocked.
Business Benefits
No surveillance liability
Because the platform never collects message, call, or location content, organizations avoid the legal and trust exposure of an employee-monitoring program.
Employee trust
Workers can verify exactly what is and isn't collected, which supports adoption instead of resistance.
Compliance by architecture
Built to be DPDP Act 2023 compliant from day one, with a named Grievance Officer and defined data retention limits.
How It Works
No content collection
The app does not collect message content, call logs, GPS location, photos, files, or keystrokes.
No location permission requested
The app does not request location permission at any point.
Domain-level metadata only
Only domain-level DNS enforcement metadata is processed — which domains were allowed or blocked, and when.
Deployment
Same architecture, every deployment
Privacy constraints are built into the platform itself, not a configuration an administrator can loosen.
Documented in the Privacy Policy
The complete, legally binding detail of what is collected is published in the Privacy Policy.
Applies identically across devices
The same privacy architecture applies whether a workforce has ten devices or ten thousand.
At a Glance
FAQ
What does Privacy mean in Cyber Pulse?
It means the platform is architecturally limited to enforcement — it does not collect message content, call logs, location, photos, files, or keystrokes.
Why does this matter?
Because a governance tool that also monitors content or location creates legal, ethical, and trust risk that a pure enforcement tool does not.
Who benefits from this approach?
Both the organization, which avoids surveillance liability, and workers, who get a verifiable privacy guarantee.
How is this different from employee monitoring software?
Monitoring software observes and records behavior for later review. Cyber Pulse enforces policy automatically without observing content at all.
When does this apply?
At all times and on every deployment — privacy constraints are part of the platform's architecture, not an optional configuration.
Key Takeaways
- No message content, call logs, location, photos, files, or keystrokes are ever collected.
- Only domain-level DNS enforcement metadata is processed.
- Built to be DPDP Act 2023 compliant from day one, with a named Grievance Officer.
- The same privacy architecture applies at any deployment scale.
Related Features
Policy Engine
The unified governance framework that applies Site, Shift, Break, and Department policies automatically, across the entire organization.
Learn more →BYOD Governance
Apply policy on personal devices without MDM enrollment or device ownership.
Learn more →DNS Policy Engine
Block or allow access at the DNS layer, before a connection is ever made.
Learn more →Related Resources
Ready to Build a More
Productive Workforce?
See how Samay Cyber Pulse enforces internet policy automatically, across every shift, without owning a single device.