01
Tenant isolation
Tenant identity derives from the authenticated session, authorization is role aware, and PostgreSQL row-level security provides defense in depth.
Varajen Time security
Endpoint time intelligence with enterprise boundaries.
Varajen Time extends the platform's tenant, role and audit model to enrolled Windows devices, browser attribution and telemetry ingestion.
Visible trackingTenant isolatedAudit ready
Transparent by design
Important: This page describes product controls and does not claim an unlisted third-party certification or guarantee that all risk can be eliminated.
Built for accountable operations
Every signal keeps its context.
Varajen Time connects collection, policy, coverage, review and deployment controls so teams can understand both the metric and the evidence behind it.
02
Endpoint trust
Tenant-scoped enrollment, device revocation, signed installers, signed update manifests, SHA-256 verification and encrypted local queues protect the endpoint workflow.
- Revocation blocks later endpoint uploads
- HTTPS manifests are signature and hash verified
- Pending queues use Windows user-scoped protection
03
Idempotent ingestion
Device identifiers and monotonic sequence numbers let accepted records be processed idempotently, reducing duplicate telemetry during retries.
04
Screenshot protection
Screenshots are disabled unless policy enables them, captured only in the signed-in session, protected locally, stored encrypted and accessed through tenant-scoped links.
05
Honest health reporting
Connection, tracking and component health remain separate. A working heartbeat with failed browser attribution is degraded, not healthy; missing telemetry remains unknown.
- Last heartbeat and upload time
- Pending queue and component state
- Coverage percentage and reasoned gaps
06
Responsible deployment
Customers provide legally sufficient notice, establish a lawful basis, configure retention, restrict access and follow applicable labor and privacy requirements.
Varajen Time