People stay in charge. Facts stay checkable.

Employees share what really happens at work, so they need to know who will read it. Here is how Lontra handles data, access and decisions, and what to bring to your security review.

Your region
Customer data is hosted in the US or in Europe, chosen per customer.
Audits in progress
SOC 2 and ISO 27001 audits are in progress. We share the current status during security review.
HR decides
HR reviews and can correct every summary and score. Nothing is decided automatically.
Every finding has a source
Summaries and scores link to the exact words behind them, so anyone reviewing can check them.

How the work comes together

  1. Scope the use

    Write down the business purpose, data types, participants, reviewers and intended action. Bring employment, privacy and security stakeholders into the discussion.

  2. Check the configuration

    Confirm the intended processing and retention. Walk through role access, a participant enquiry, a correction and campaign closure before inviting real participants.

  3. Record what was agreed

    Assign a named owner, record the controls and open items, and set a point to revisit the design when the audience or use changes.

Participation and transparency

Use an invitation that states the purpose of the campaign, what participation involves and how a person can raise a concern. Let people know what to leave out and where to go for sensitive issues. Use your existing reporting channels for grievances, emergencies and safeguarding matters.

Access across participants, managers and HR

Agree who can open source responses, summaries and any exports. Test named accounts from each role, including a manager outside the intended scope. Check whether small groups, recognizable examples or direct quotes could identify someone before sharing findings more widely.

Data flows and retention

Review the actual deployment with privacy and security stakeholders. Map data from invitation and conversation through processing, review, export and deletion. Ask where each component processes data, who provides it, and what is kept in logs and backups. Agree how long to retain each data type and what the exit process covers.

Review and challenge

Read summaries alongside the examples and context that support them. Distinguish an employee’s account from a reviewer’s inference. Preserve relevant disagreement and avoid conclusions about groups whose perspectives are missing. Define how a participant can raise a correction and who will respond.

Procurement and security review

Bring the security questionnaire or policy requirements that apply to your organization. Use the planned deployment to check the controls, data flows, contractual responsibilities and evidence your teams require. Include your HR sponsor in that conversation so the review stays tied to the intended use.

Questions that come up

Does Lontra make employment decisions?

No. Lontra prepares summaries, scores and briefs. HR and managers review them, can correct them and remain responsible for any decision that affects an employee.

Are employee responses anonymous?

They are confidential, not anonymous. You decide who can see each person’s summary and quotes. Before sharing results for a small group, check that no detail could identify someone. Say exactly this in the invitation.

Where is data hosted, and for how long?

Customer data is hosted in the US or in Europe, chosen per customer. Retention is set per deployment; we share retention settings and sub-processors during security review.

Is Lontra SOC 2 or ISO 27001 certified?

Not yet. Both audits are in progress, and we share the current status and supporting documents during security review.

What should our security and privacy teams bring?

Your intended use, countries, roles, information categories, retention requirements and any mandatory supplier questionnaire. We will go through them against your planned deployment.

Bring one performance question.

See the product on a question like yours, and what a first campaign could involve.

Book a demo