Learn the language of Digital Workforce Governance.
Definitions and answers — grounded in how the platform actually works. For the complete guide to the category, see the Digital Workforce Governance pillar page.
Blog
Updates, announcements, and product thinking will be published here, organized by category. See the Blog for the category structure — nothing published yet, check back soon.
Knowledge Base
Setup, concepts, and terminology, organized by topic. See the Knowledge Base — most topics already link to real coverage; standalone articles are still being written.
FAQ
Does Samay Cyber Pulse require MDM?
No. It works without Mobile Device Management enrollment or company-owned hardware — enforcement runs on the worker's own device.
Does it work on personal phones (BYOD)?
Yes. The app runs on the worker's own Android or iPhone device; there's no device ownership requirement.
What data does it collect?
Only DNS enforcement metadata (domains queried, allowed/blocked, timestamps) and the account/device data needed to operate the Service — never message content, call logs, GPS location, photos, files, or keystrokes.
Is it DPDP Act 2023 compliant?
Yes — the Service is designed to comply with the Digital Personal Data Protection Act, 2023 from the ground up.
Does enforcement apply outside work hours?
No. Enforcement is tied to a worker's assigned shift and pauses automatically during scheduled breaks and off-shift time.
What happens if the device can't reach the policy engine?
Access fails closed by default — enforcement never silently opens up when it loses connection.
For more, organized by topic, see the full FAQ Center.
Glossary
Digital Workforce Governance
The practice of automatically governing enterprise internet access based on business policies, work schedules, and operational requirements, while preserving employee privacy.
Why it matters: It replaces a written acceptable-use policy nobody can verify with automatic, schedule-aware enforcement.
Digital Workforce Governance guide →Enterprise Internet Governance
The broader discipline of managing how an enterprise's workforce accesses the internet — policy, schedule, and role — as a governed resource rather than an unmanaged one.
Why it matters: It's the umbrella discipline Digital Workforce Governance is a specific, automated implementation of.
Digital Workforce Governance guide →Policy Engine
The framework that combines Site, Shift, Break, and Department policies into a single, automatically enforced set of rules for each worker.
Why it matters: It's the foundation every other policy type (Site, Shift, Break, Department) is built on.
Policy Engine →Private DNS
A DNS resolution path dedicated to a specific customer's policy configuration, rather than a shared public resolver.
Why it matters: It's what makes per-tenant, per-organization policy enforcement possible at the DNS layer.
DNS Policy Engine →DoH (DNS-over-HTTPS)
An encrypted transport protocol for DNS queries that closes the plaintext gap most filters leave open.
Why it matters: It means enforcement doesn't depend on inspecting unencrypted traffic.
DNS Policy Engine →DoT (DNS-over-TLS)
An additional encrypted DNS transport option, alongside DoH, for environments that require it.
Why it matters: It gives enforcement a second standards-based, encrypted transport path.
DNS Policy Engine →MDM (Mobile Device Management)
Software that enrolls and centrally manages company-owned or company-controlled devices.
Why it matters: Digital Workforce Governance is explicitly designed as an alternative for workforces where this model doesn't fit.
Compare: Cyber Pulse vs. MDM →BYOD (Bring Your Own Device)
A model where employees use personal devices for work, requiring governance tools that don't depend on device ownership or enrollment.
Why it matters: Most front-line and distributed workforces are BYOD by default, not by choice.
BYOD Governance →Compliance
The ability to demonstrate that a policy is actually enforced, not just documented.
Why it matters: A written policy with no enforcement trail doesn't satisfy modern audit or client due-diligence expectations.
Analytics →Operational Governance
Governing how day-to-day operations run — schedules, roles, sites, departments — through automatically applied policy rather than manual oversight.
Why it matters: It's the operational counterpart to Digital Workforce Governance's internet-access focus.
Policy Engine →Employee Privacy
The principle that internet-access enforcement should never require observing message content, calls, location, or other personal content.
Why it matters: It's the boundary that separates governance from employee monitoring.
Privacy →Shift Policy
An internet-access policy that activates and deactivates automatically based on a worker's assigned work shift.
Why it matters: It ties enforcement to the actual work schedule instead of a fixed clock.
Shift Policies →Whitepapers
Deeper research on workforce governance and compliance. See the Whitepapers page for what's planned — nothing published yet. Looking for a structured evaluation or deployment guide instead? See Buyer Guides.
Case Studies
Customer case studies will be published here as deployments complete. Nothing to show yet — check back soon.