Security

Keeplore security

Keeplore stores interview transcripts and the rules taken from them in a database in Frankfurt. Interview text is sent to Anthropic in the United States to run the interview and write the rules. Keeplore does not use your data to train AI models. Nothing reaches your AI agent until a manager approves it. You can delete an interview and its rules in one click.

This page is for the person who has to approve Keeplore: IT, security, a Head of Support or Operations. It says what Keeplore does today and what it does not. Where this page and your signed order differ, the order wins. The legal texts are the privacy policy, the data processing agreement and the terms.

What data Keeplore handles

What Keeplore does not collect: Keeplore has no integrations with email, Slack or calendars, on purpose. It only uses what people say in the interview.

Interviewees are asked not to share passwords or personal details about customers. The interviewer is instructed to steer away from them, and the rule extraction is instructed not to include them. Those are instructions to an AI, not a filter. Treat them as a safeguard, not a guarantee.

Who is responsible for the data

For interview data, your company is the controller and Keeplore is the processor under the data processing agreement. For account and website data, Keeplore is the controller. If an employee wants their data deleted, they ask their employer, and the employer can do it in one step.

Where data is stored and who the subprocessors are

The database is in Frankfurt. The application is set to run in Frankfurt (Vercel region fra1). Some other providers are in the United States, and the table says which.

The complete subprocessor list is in the data processing agreement. Two things to know:

• “EU-hosted” does not mean no data leaves the EU. Interview text goes to Anthropic in the United States. Account sign-in data is handled by Clerk in the United States. Invitation emails go through Resend in the United States.
• Transfers. The agreement says Keeplore relies on the EU Standard Contractual Clauses with each subprocessor and, where available, the EU-US Data Privacy Framework.

The agreement says Keeplore gives at least 30 days' notice of a new subprocessor, and you may object on reasonable data protection grounds.

How AI is used on your data

Keeplore uses Anthropic's Claude models in three places:

1. The interview. The employee's name, role, team and the conversation so far are sent to Claude so it can ask the next question.
2. Rule extraction. The transcript is sent to Claude, which proposes rules with quotes. A rule is dropped if its quote does not appear in what the employee said.
3. Agent answers. When your agent calls the query API, Claude receives the question and your approved rules (condition, action and reason) and picks the ones that apply. Employee names are not sent in this step. If no rule applies, the answer is empty.

Training. The privacy policy says Keeplore does not sell personal data, use it for advertising, or use interview data to train AI models. The agreement lists “no use of customer data to train AI models” among its security measures.

Human check. Every rule is pending until a manager approves, edits or rejects it. The terms say AI output can be incomplete or wrong and that you are responsible for reviewing rules.

Spending cap. AI use has a monthly cap per company. When it is reached, Keeplore pauses until the next month and keeps your data.

Who can access your data

Inside your company

• Access is by company workspace, through Clerk sign-in.
• There are two roles. Company admins can add interviews, approve and edit rules, delete interviews and create or revoke API keys. Other members cannot do any of those things.
• Every write action in the dashboard checks that the person is an admin of the company that owns the data.

Keeplore staff

• The staff admin panel is open only to an allow-list of staff accounts. Anyone else, signed in or not, gets a “not found” page.
• Every change staff make in the panel is recorded with who made it and what changed. This covers access level, trial and AI limits, notes, API key revocation and banning a user. Viewing is not logged.
• In the panel, staff see each interview's role, status and rule counts. They do not see employee names or transcripts there. They do see company and user names and emails, member lists, and the first characters (prefix) of API keys.
• The privacy policy says staff access customer data only when needed to support that customer.
• The panel is not the only way in. The founder runs the database and the product, so the real limit on staff access is the policy and the agreement, not only the panel.
• There is no “view as customer” feature today.

The employee being interviewed

• The employee gets a private link. There is no password.
• The link is a random token. Keeplore stores only a hash of it, so Keeplore cannot show the link again. A company admin can replace the link at any time, which disables the old one.
• Whoever holds the link can open that interview. Links do not expire on their own. Send them to the employee only, and replace one if it was sent to the wrong person.
• Before the first message, the employee sees a notice: managers at their company will see the answers, each rule keeps their name as its source, don't share passwords or personal customer details, and they can ask their company to delete the interview. The server refuses to save any message until the employee has agreed, and records the time of consent.
• The interview is rate limited to 10 employee messages a minute, and to 40 answers in total.

API keys

• A company admin creates a key in settings. It starts with lore_ and is shown once.
• Keeplore stores a SHA-256 hash of the key, a name, a short prefix and the dates it was created, last used and revoked. It cannot show you the key again.
• Revoking a key stops it working straight away. Staff can also revoke a key from the admin panel, and that is logged.
• Keys are tied to one company and can only read that company's approved rules.
• The query endpoint allows 60 requests a minute per key. Both endpoints require a valid, unrevoked key.
• Treat a key like a password: keep it in your agent's secret store, use one key per agent, and revoke it when the person or system that held it moves on.
• Keys are all-or-nothing today. There are no read-only scopes and no expiry dates.

Retention and deletion

• Delete an interview. An admin clicks “Delete handover”. This permanently removes the interview, its messages and all its rules.
• When you leave. The terms say Keeplore will export your approved rules on request and delete your data within 30 days of the end of the agreement.
• Deletion has limits. Deleting an interview does not remove the log of questions your agent asked, or the AI usage records (token counts and cost). The usage records do not contain interview text. The question log holds whatever your agent sent.
• Employee requests. An employee asks their employer to delete their interview. The employer can do it in the dashboard.
• Full account erasure is a manual process today.

Website visits

Website visits are counted without cookies. Nothing is stored on a visitor's device, so there is no cookie banner.

What Keeplore does not have

Keeplore is a two-founder Dutch company. Today it has no SOC 2 report and no ISO 27001 certificate.

If your security review needs one of these, ask. We would rather tell you now than lose you in procurement. Questions: privacy@keeplore.dev.