This is a training tool. Not surveillance.

Mehak Learning exists to find where your team is losing time to skills they haven't been taught yet, and to teach them. The daily check-ins and work samples feed that, and nothing else.

It is not a monitoring product. There is no screen recording, no keystroke logging, no location tracking, and no measurement of how long anyone was at their desk. We have deliberately not built those things, and we don't intend to.

Check-in text, uploaded work samples, skill scores and skill reports must not be used for discipline, termination, demotion, pay decisions, or discrimination of any kind.

That includes using them as evidence in a performance-management process, ranking employees against each other, or building a case against someone. A skill score is a statement about what a person hasn't been trained in yet. It is not a performance rating, and treating it as one both misreads it and breaks these terms.

It also poisons the data. The moment your team believes their check-ins might be used against them, they will write bland answers, and the tool stops working for everyone.

If we find an account being used this way, we may suspend it. Where we reasonably can, we will raise it with you first.

Before you start an observation week, your team must know it is happening and what it is for. The onboarding flow asks the firm owner to confirm this, and it is a real commitment, not a checkbox to click past.

Your firm is responsible for informing your employees and for obtaining any consent your jurisdiction or your own employment agreements require. See the Data Processing terms.

Work samples are optional, and they should be sanitised before they are attached. Do not upload:

• ✕Privileged material — attorney–client communications, attorney work product, or anything covered by a comparable professional privilege.
• ✕Medical or health records, or anything covered by HIPAA or a similar regime.
• ✕Regulated client data you do not have clear authority to share with a third-party service — including material under a confidentiality agreement, protective order, or client engagement terms that forbid it.
• ✕Personal data about clients or third parties: names, addresses, account numbers, identification numbers.
• ✕Credentials of any kind — passwords, API keys, access tokens.

Every upload requires the employee to confirm they have removed client names and confidential information, and we run an automatic pass that strips obvious email addresses, phone numbers and SSN-like patterns. Treat that as a safety net, not a substitute for judgement — it cannot recognise a client's name or a privileged paragraph.

Uploaded text is sent to an AI provider for analysis, which is exactly why this list matters. If you are unsure whether something can be shared, describe the work in the check-in instead of attaching the document.

Don't use the service to:

• ✕Break the law, or help someone else do so.
• ✕Access another firm's data, or attempt to.
• ✕Probe, scan or overload the service, or work around its rate limits and access controls.
• ✕Resell or repackage the service without a written agreement with us.
• ✕Upload malware, or content that is harassing or abusive toward a colleague.

Security researchers are welcome — email aqeek@mehaklearning.com before testing anything and we will work with you.

Check-ins are written by the employee, and they choose what to say and whether to attach anything. If someone on your team doesn't want to take part, that is a conversation for your firm to have — but nobody should be penalised for it, and we would rather you have that conversation than quietly enrol someone who hasn't been told.