Trust
Trust is decided before the first invitation.
A useful review starts with the real data flows: what is collected, who can see it, where each service processes it, how long it is kept, and who decides. Lontra prepares the material. Decisions that affect a person remain human.
Human decision
AI output prepares a review. It does not trigger an employment decision on its own.
Evidence and interpretation
A dated statement, a summary, and an inference should remain distinguishable and open to challenge.
Tested access
Test the access matrix with the pilot’s actual accounts and views before inviting participants.
Clear notice
The invitation explains purpose, use of responses, recipients, and the route for questions or refusal.
Documented flows
The application region alone does not describe model, voice, authentication, email, or observability processing.
Retention by data type
Transcript, summary, memory, signal, log, and backup each need an agreed period and exit procedure.
What Lontra does
- ✓Structures conversations within the scope defined for the campaign.
- ✓Prepares summaries and questions for human review.
- ✓Connects useful findings to their source and date where the workflow supports it.
- ✓Helps people examine group trends without turning them into an individual verdict.
Keep these boundaries visible
- •Does not make automated employment decisions.
- •Does not predict whether a person will leave or provide an individual score to use as a verdict.
- •Does not infer emotion from voice, tone, or pace.
- •Does not promise absolute anonymity or determine the customer’s legal compliance.
Close the review pack before the pilot
Use this list as the agenda with security, privacy, legal, and the business sponsor. Each answer should name the data flow, the control owner, and the evidence reviewed.
01
Data map, purposes, and controller / processor roles
02
Architecture, regions, and encryption examined for each store and connection
03
Sub-processor register with purpose, data, region, retention, and transfer mechanism
04
Role, view, export, and administrator-exception matrix tested with pilot accounts
05
Retention schedule and deletion procedure covering each copy and derivative
06
Access, correction, objection, challenge, and identity-verification procedure
07
Participant notice, minimisation rules, and handling of unexpected information
08
Incident contacts, contractual timelines, and launch decision criteria
FAQ
Does Lontra make HR decisions?
No. Lontra prepares material for accountable people. It does not trigger a decision affecting an employee on its own.
Can managers see raw conversations?
The deployment plan must keep raw conversations out of manager views and apply a minimum of five respondents to collective HR analysis. Test the access matrix with the pilot’s actual accounts.
Does all data stay in the European Union?
The application service deployment configuration targets Google Cloud europe-west1. It does not prove the region of a running instance or the regions used by AI models and other sub-processors. Those flows must be reviewed separately, so Lontra does not describe all processing as EU-only.
Is Lontra ISO 27001 or SOC 2 certified?
This page makes no ISO 27001 certification or SOC 2 report claim. Review the controls and evidence that are current for the project.
What happens if someone shares sensitive information?
The reflective conversation path applies pre-storage redaction for certain categories and languages. The mechanism is not exhaustive. It supplements, rather than replaces, minimisation, participant instructions, output review, and a process for unexpected content.
Can an employee directly inspect and correct a file in the product?
This page does not present direct employee access to a memory or file as a delivered feature. Define the process for access, correction, challenge, and deletion with the customer before the pilot.
What happens to an audio recording?
In the recorded-interview flow, the recording is encrypted before storage and deleted after transcription. The transcript and its derivatives need a separate agreed retention schedule.
What should be reviewed before launch?
The relevant teams should approve the precise pilot’s flows, sub-processors, access, retention, individual rights, incident handling, and participant notice.
Rolling out across countries, or want to look at your case together? Book a thirty-minute conversation.
30 minutes. Your problem, your teams, your measure.
Less theater. More humans.