Frequently Asked Questions

Kyrospect is a privacy-first, verified time tracking and proof-of-work platform that helps remote teams, agencies, BPOs, and IT services prove what work actually happened — without invasive screen surveillance.

Proof of work in time tracking means adding reviewable context to logged hours. Depending on policy, that can include active and idle time, application or URL context, and periodic screenshots. It strengthens a billing record without making the record infallible.

Authenticity verification connects tracked time to trustworthy work signals — active vs idle patterns, app and URL context, screenshots, and session history — and then checks whether that activity looks genuinely human. The goal is to replace guesswork with reviewable evidence, not to spy on people.

Kyrospect can surface unusual or automation-like activity patterns for review. These signals are context, not proof of misconduct, and should be checked against the timeline, the role, approved tools, accessibility needs, and the employee's explanation.

No. Kyrospect is built for transparent, professional accountability. It only tracks activity when the user explicitly starts the timer. Users have full visibility into what is being tracked, and it includes privacy features like screenshot blurring to protect personal data.

Kyrospect is designed for agencies, BPOs and call centers, IT services and offshore delivery teams, consulting firms, freelancers, and any remote or hybrid team that needs accountability and billing clarity without resorting to surveillance.

Unlike legacy trackers that focus on simple screenshots, Kyrospect focuses on 'Authenticity Verification'. We provide deeper context, explicit fake-activity detection, and a modern, privacy-first interface that remote teams trust rather than resent.

Kyrospect reviews the overall pattern of a work session and compares it against what genuine human activity looks like. When a session looks automated or unnaturally regular, it raises a reviewable alert with supporting context instead of making an automatic accusation. We deliberately keep the exact detection signals confidential so they stay effective against evasion tools.

No. A flag is intended to create a review item, not an automatic penalty. Managers should inspect the surrounding context available under the workspace policy and speak with the employee before making any decision.

Kyrospect is designed to combine multiple signals and surface patterns that may be consistent with software automation, auto-clickers, or jigglers. No detector is perfect, so a signal must remain reviewable and must not become an automatic accusation.

Those can be legitimate, which is exactly why Kyrospect treats flags as review context rather than proof of wrongdoing. Managers can see the surrounding evidence and account for accessibility tools, remote desktops, or approved workflows before drawing any conclusion.

Kyrospect uses review levels (warnings vs higher-confidence signals), stores clear context with each alert, applies cooldowns so one event does not flood the dashboard, and never relies on a single signal in isolation. Activity, screenshots, timeline, and manager judgment are combined.

It protects the value of your data. If tracked hours feed payroll, client billing, or performance reviews, you need confidence that the activity behind those hours is authentic — otherwise every downstream decision is built on unreliable numbers.

Agencies can attach Kyrospect's verified work records directly to client invoices. If a client questions a bill, the agency can provide a transparent log of exact applications used, active time, and blurred screenshots proving the work was completed as billed.

When reporting or export is enabled for the beta release, agencies can prepare summarized proof-of-work records by person or project. Confirm current export formats during onboarding; raw employee telemetry should not be sent to a client by default.

Real-time visibility into time per task and per project lets you spot work drifting beyond the agreed scope early — while you can still renegotiate — instead of discovering an unprofitable project after the fact.

Yes. Kyrospect detects when a user is inactive (no mouse or keyboard input) for a specific threshold and stops the timer or prompts the user. This prevents 'margin leakage' where clients or agencies pay for away-from-keyboard time.

Yes. Freelancers use Kyrospect to produce trustworthy, client-ready records of their work — which protects them in disputes, justifies their rate with objective output, and lets them disconnect completely when the timer stops.

Screenshot review, correction, and deletion behavior depends on the workspace policy and current beta release. Confirm exactly who can remove an image and what happens to associated time before relying on that workflow for client billing.

Yes. Work is organized by project and session, so agencies and freelancers can separate time across multiple clients, report on each independently, and keep one client's data out of another's reports.

BPOs use Kyrospect to verify seat utilization, separate genuine active time from idle time, and produce client-facing reports that prove delivery — protecting margin on per-seat contracts and strengthening trust with the brands they serve.

Yes. Managers can see active vs idle context across the floor and spot under-utilized seats before they quietly eat into margin, using evidence rather than assumptions.

Yes. Tracking is tied to work sessions rather than fixed office hours, so it fits day, night, and rotating shifts across locations and time zones.

You can generate summarized proof-of-work and utilization reports per team or per client, giving the brands you serve confidence that contracted hours were genuinely worked — without exposing raw, sensitive telemetry.

Yes. Authenticity alerts, long idle gaps, and unusual sessions are grouped into a manager review queue so supervisors can focus attention where it actually matters instead of scrolling through raw logs.

Kyrospect replaces constant check-ins and 'are you online?' pings with passive, transparent work records. Managers get the visibility they need from trends and evidence, so they can stop interrupting deep work to ask what people are doing.

Yes. Because tracking follows work sessions rather than a fixed schedule, distributed teams across different time zones are all captured fairly, and managers see when work actually happened.

Yes. Kyrospect is designed for transparent monitoring — team members can view their own activity, screenshots, and trends. Shared visibility is what turns monitoring from surveillance into accountability.

Handled transparently, it does the opposite. The damage comes from hidden, opaque monitoring. When employees know exactly what is tracked, can see their own data, and understand the rules, monitoring becomes a shared system rather than a threat.

It reduces the need for them. When work records are automatic and reviewable, people spend less time writing 'here's what I did today' updates to prove they worked, and more time actually working.

Indian IT services firms use Kyrospect to attach verifiable evidence to every hour billed to US, UK, and EU clients. Instead of asking overseas clients to trust an invoice on faith, they provide reviewable activity context — which closes the trust gap that stalls contracts.

Yes. You can share summarized weekly or per-sprint reports showing active hours, work context, and proof of work — enough for the client's finance and procurement teams to satisfy their own compliance without seeing raw telemetry.

The gap in offshore delivery is usually evidence, not quality. By making work visible and verifiable, Kyrospect turns billing from a trust argument into an evidence-backed conversation, which protects renewals and rates.

Yes. Whether you run fixed-bid projects, time-and-materials, or dedicated/staff-augmentation models, Kyrospect produces the verified records clients increasingly expect for dedicated offshore resources.

Consultants capture work sessions automatically and turn them into a clean narrative of focused work, context, and outcomes — so a 38-hour invoice is backed by evidence the client can understand, not just a number to defend.

Yes. Time is organized by project and engagement, so partners can see utilization across clients, identify which engagements consume more resources than they pay for, and forecast capacity with real data.

A consistent weekly proof-of-work summary shows clients what was worked on and where time went, replacing vague retainer anxiety with confidence — which reduces disputes and improves renewals.

Privacy-aware screenshot controls are designed to reduce unnecessary exposure through blur and policy settings. The exact blur behavior available in a beta workspace should be demonstrated and tested before sensitive work is captured.

Data is encrypted in transit and at rest. Kyrospect follows a privacy-by-design approach — sensitive content is blurred at the point of capture rather than collected and secured later — which reduces both privacy risk and data-breach liability.

Kyrospect is designed to support privacy principles such as transparency, data minimization, access control, and defined retention. That does not make every customer deployment automatically GDPR compliant; lawful purpose, notices, agreements, configuration, and employee rights remain the customer's responsibility.

No. Kyrospect does NOT use keyloggers or record continuous video of the screen. We only track overall activity volume (not the specific keys pressed) and take periodic screenshots, strictly avoiding invasive surveillance techniques.

Access is role-based. Employees can see their own data, managers see their team within policy, and sensitive screen content is blurred before storage. Visibility is governed by clear roles rather than a free-for-all.

No. Tracking only runs during active work sessions that the user starts. Kyrospect is built to capture work context, not personal browsing, private messages, or off-the-clock life.

Yes. Screenshot capture and its frequency are policy controls. Teams that only need activity context and authenticity signals can run Kyrospect without storing screenshots at all.

Kyrospect is designed to support compliance with major workplace data regimes — GDPR in the EU, the DPDP Act in India, and US state laws like CCPA/CPRA — through transparency, data minimization, role-based access, and Data Processing Agreements. Final compliance always depends on how your organization configures and communicates monitoring.

Yes. We provide DPAs so your organization can document the legal basis and processing terms for employee data, which is a standard requirement under GDPR and similar regimes.

India's Digital Personal Data Protection Act emphasizes clear notice, consent where required, and data minimization. Kyrospect's transparent, employee-visible model and privacy-by-design capture align with those principles — collect only what is needed for the stated purpose.

In most jurisdictions you must inform employees that monitoring takes place, usually in writing at hire and in the handbook, specifying what is monitored and why. Kyrospect reinforces this by being overt and employee-visible by design, but you should confirm the specific notice rules in your region.

A workspace should define retention before collecting workday data. Be aware that in the current beta a retention window can be configured but is not yet enforced by automatic deletion — that enforcement is still being built, so document any deletion steps that need operational handling in the meantime.

The beta is Windows-first. Desktop release and signing support can change, so confirm the operating-system version currently available to your invited workspace before planning a rollout.

The agent installs like a standard desktop app and pairs to your workspace via a secure device code, so team members can get set up quickly. Installation follows normal desktop permissions for your operating system.

The desktop agent is designed to stay lightweight, but actual CPU, memory, battery, and network impact depends on the device and enabled capture policy. Test it with representative workloads during the evaluation period.

Yes. The Kyrospect desktop agent securely caches your activity data locally when your internet connection drops. Once you reconnect, it automatically and securely syncs the data to your cloud workspace, ensuring no billable time is lost.

Screenshot frequency is a configurable policy. Admins choose an interval that fits their needs (or disable screenshots entirely), so capture matches your actual proof-of-work requirements rather than a fixed setting.

Yes. Kyrospect's anti-cheat engine is designed to flag synthetic activity from hardware and software jigglers and auto-clickers for manager review. The exact detection methods are kept confidential so they stay effective as new evasion tools appear.

Yes. The agent identifies the active application to provide a breakdown of where time was spent (e.g., 'Figma', 'VS Code', 'GitHub'). This helps teams optimize their workflows and provides concrete proof of work.

Webcam snapshots are not part of the published beta plans. If identity verification is considered in the future, it would require separate product disclosure, explicit governance, and a proportionate legal and employee review.

None today. Export is not built yet. What exists is the in-product record: tracked time, activity context, session timelines and team views that you and your employees can review in the dashboard. Export is on the roadmap and is the most requested gap beta teams raise.

Not yet. There is no PDF or CSV export in the beta product. If a billing or payroll process depends on scheduled exports, that dependency is not met today — plan around the in-product views, or tell us during your beta application so it weighs on our sequence.

The intent is a summary of active hours, work context such as apps and URLs, session timelines and optional privacy-aware screenshots — the work being paid for, not raw telemetry. To be clear, this is the design of a planned capability, not something you can generate today.

Yes. Client-facing reports are summarized and privacy-aware by design. You share the confidence — hours, context, and proof — without dumping every screenshot, URL, or minute of raw data.

Yes. Managers get real-time team and project dashboards showing active time, trends, app usage, and review items, so they can act on what needs attention today instead of waiting for end-of-week reports.

Hubstaff is a mature time tracker focused on screenshots and activity percentages. Kyrospect adds an authenticity layer — explicit fake-activity detection and reviewable evidence — with a privacy-first, employee-visible model designed so teams trust it rather than resent it.

Time Doctor leans on detailed activity and distraction tracking that can feel heavy-handed. Kyrospect focuses on verifying that work is genuine and proving it cleanly, with Smart Privacy Blur and transparency built in rather than bolted on.

ActivTrak is oriented toward broad workforce analytics and behavior monitoring. Kyrospect is purpose-built around verified proof of work and authenticity for billing and accountability use cases, with a stronger privacy posture.

Screenshots without context are easy to game and create privacy and legal risk. Kyrospect treats screenshots as one privacy-safe signal among many — combined with activity context and authenticity checks — so the evidence is both more trustworthy and less invasive.

Many teams can start with a clean cut-over rather than importing old activity data. Founder-led onboarding helps define the scope, but any employee, project, or historical migration depends on the source quality and current beta tooling.

Yes. Accepted teams can evaluate the platform for up to 60 days without a credit card. Track Basic remains free; paid beta plans begin only after plan confirmation.

Public list prices currently start at ₹250 per paid Tracking seat and ₹50 per HRMS seat. Approved beta teams receive first-year prices from ₹50 for paid Tracking and ₹10 for HRMS, while Track Basic stays free. The pricing page is the source of truth for current plans and terms.

No card is required for the initial evaluation period. A payment method is required only when a team confirms a paid beta plan after evaluation.

Request access from the beta page. Selected teams receive founder-led onboarding and paid beta pricing protected for their first 12 months.

Founder-Led Setup means our founding team will personally help you integrate Kyrospect into your agency or BPO workflow, configure your policies, and help you present the tool to your team to ensure high adoption and trust.

Lead with a transparency conversation before anything goes live: explain what is tracked, why, who sees it, and what it will never be used for. Give employees access to their own dashboards on day one. Most rollout backlash comes from surprise and secrecy, not from monitoring itself.

Tell employees before monitoring begins. Specific notice, consultation, agreement, or consent requirements vary, but transparency is the baseline for a defensible and trustworthy rollout.

Frame the data as a shared resource, not a weapon: employees see their own data, it is used to fix systems and protect billing rather than to punish, and leaders are held to the same standards. Buy-in follows when people see the tool working for them, not just on them.

Show them their own dashboard, walk through exactly what is and isn't captured, and reiterate the prohibited uses. Most concern fades once people see that the data matches what you told them and that personal and sensitive content is protected.

The beta is centered on employee records, the team directory, organization roles and reporting lines, plus onboarding, leave, and attendance workflows as they are released. Track Basic is included. Payroll is not included yet.

No. The ₹10 per-employee monthly beta price covers released HRMS capabilities except payroll. We state the exclusion clearly so teams can evaluate the current product rather than a future promise.

Yes. Track Basic is included and provides clock-in and clock-out, active time, idle time, total tracked time, shift start and end, and daily or weekly summaries without paid screenshot capture.

Yes. HRMS and Track Basic can be used without purchasing an advanced Tracking seat. Paid Tracking is optional for roles that need screenshots, app, URL, window, or location context.

Yes. Tracking is available as a standalone product. Track Basic is free, while paid Tracking seats add the review context listed on the pricing page.

The connected model is designed around one employee identity shared across HR and Tracking. During onboarding, teams should still clean duplicate source records and agree which system owns each field before importing data.

Kyrospect uses role and team scope to control access. Exact permissions should be reviewed during beta onboarding so each workspace reflects its reporting structure and least-privilege requirements.

Self-service availability depends on the field and the beta module currently enabled. Stable identity or employment fields may require review, while lower-risk profile fields can follow simpler workflows.

Onboarding workflows are part of the HRMS beta roadmap and are released progressively. Accepted teams receive a clear view of what is live for their workspace before they adopt the process.

Employee lifecycle and access closure are core design goals. Because the product is in beta, confirm the exact offboarding steps available before relying on Kyrospect as the sole control for a high-risk exit.

Document capabilities may be enabled progressively during beta. Teams should confirm current availability, supported file types, access rules, retention, and export before moving sensitive records.

Yes. The HRMS is designed around a shared employee directory with organization roles and reporting lines, subject to workspace access settings.

Organization roles and reporting lines are part of the HRMS foundation. The beta team will help confirm how your current structure maps into the available model.

Leave and attendance modules are released progressively during beta. Track Basic already provides time and shift context; policy workflows should be confirmed for the specific beta release your workspace receives.

Founder-led onboarding can help plan the migration, but import scope depends on data quality and the beta tooling available. We recommend migrating only useful, owned fields and keeping a reconciled source copy.

Historical records should remain attributable after access is closed, subject to retention and privacy requirements. Exact archive and deletion behavior should be confirmed during onboarding.

Multi-assignment requirements vary significantly. Share contractor, multi-entity, concurrent-role, or rehire scenarios during beta discovery so the team can confirm current support rather than forcing an inaccurate structure.

A connected HR and Tracking platform is designed to use role and team context for consistent policies. Any automated inheritance should be previewed and tested before applying it broadly.

During the first-year beta offer, Workforce is ₹60 per seat per month for HRMS plus 10-minute Tracking, and Workforce+ is ₹80 for HRMS plus 5-minute Tracking. Published list prices are shown beside the discount on the pricing page.

Use the HRMS product page, pricing page, and your beta onboarding scope as the current sources of truth. Beta capabilities evolve, so older blog posts or screenshots should not override the current release description.

Kyrospect does not position automation as a replacement for accountable human decisions about hiring, pay, promotion, discipline, or termination. Any future assistance in these areas should be explainable, reviewable, and subject to explicit governance.

It should not. Productivity depends on role, quality, outcomes, constraints, and collaboration. Device or activity signals can add context, but compressing them into an automatic verdict creates false certainty.

Conversational assistance is a possible product direction, but this website does not promise an unreleased bot. Any announced capability will appear on the current product or release page with its scope and limitations.

Lower-risk uses include finding approved policy information, summarizing a case for human review, drafting routine communication, and routing requests. Access controls, source citations, and a clear escalation path remain essential.

Yes. The interface should make automation clear, avoid pretending to be a human, and provide a simple route to a responsible person when the question is sensitive or the answer is uncertain.

That depends on the approved service terms and configuration. Organizations should require a clear answer on model training, subprocessors, retention, and opt-out before sending employee or customer data to any AI service.

It means a person has the context, time, authority, and accountability to inspect an automated output and change or reject it. A ceremonial approval click is not meaningful human review.

AI can help structure or edit a manager's draft, but the manager must verify every fact and own the judgment. Sensitive data, unsupported inferences, and generic generated praise or criticism should be removed.

Candidate screening is high impact and can reproduce bias in data or job design. Any automated screening requires qualified legal review, job-related validation, accessibility consideration, monitoring, and a meaningful human challenge path.

Ask what exact function is automated, what data is used, whether customer data trains shared models, how errors are measured, what explanations are available, how outputs are monitored, and how data can be deleted or exported.

Do not paste credentials, confidential customer material, sensitive employee records, health information, investigations, payroll data, or proprietary documents unless the organization has explicitly approved that tool and use.

No. Any system can misclassify accessibility tools, remote desktops, approved automation, or unusual work patterns. Signals should create a reviewable question, not an automatic accusation.

Disclosure is useful when people reasonably need to know how material guidance was produced. More importantly, the organization should identify the accountable reviewer, verify facts, and explain the limits of automation.

Provide a visible correction and appeal route, explain the relevant input and decision, preserve the employee's context, and route the case to a person authorized to change the outcome.

It can assist with trend summaries if the use is approved, access-controlled, and verified. Summaries should distinguish observation from inference and link back to the underlying evidence.

AI will change parts of HR work, especially search, drafting, routing, and analysis. Accountability, employee relations, judgment, policy design, and trust still require capable people.

Cover approved tools, confidential data, customer work, required output review, attribution, prohibited decisions, incident reporting, and concrete examples drawn from real jobs.

Start with a low-consequence, reversible workflow. Define a baseline, keep human review, test difficult cases, collect feedback from affected users, and stop or narrow the pilot when risks outweigh value.

It is a systematic difference in errors or outcomes that can arise from data, labels, proxies, model design, deployment, or human use. Testing must examine the complete workflow, not only the model.

The AI & Future of Work learning path contains field guides on use-case prioritization, human review, employee policy, vendor evaluation, performance feedback, and workforce analytics guardrails.

There is no universal yes-or-no answer. Requirements depend on jurisdiction, worker status, device ownership, data collected, purpose, notice, consultation or consent rules, and how the data affects employment decisions. Use transparent, proportionate settings and obtain qualified local advice before rollout.

Transparent time records can help employees document overtime, scope changes, and work that is otherwise invisible. They provide useful evidence, not an indisputable performance verdict, and should remain visible and correctable by the employee.

Surveillance is covert, continuous, and invasive (e.g., hidden keyloggers, constant video recording). Activity tracking is overt, intermittent, and collaborative. Kyrospect is an activity tracker: employees control the timer, see their own data, and can delete private screenshots.

Kyrospect's idle detection system acts as a safety net. If you step away from your keyboard for a predetermined amount of time (e.g., 5 minutes), the agent will automatically pause the timer or prompt you upon return to either keep or discard the idle time.