How Earken works
- Interview
- A relaxed ~20-minute voice conversation in the browser with Earken, an AI interviewer. It's planned from everything already known, so nobody is asked the same thing twice.
- Distil
- Afterwards Earken turns the conversation into structured knowledge pages, sourced facts and open questions — not a transcript.
- Spread
- Each conversation suggests who to talk to next, with their interview already prepared. One person leads to the next until the whole organisation is covered.
- Ask
- Anyone in the project can ask questions in plain language and get answers with links to the pages they came from.
Your journal
- What it is
- A private notebook you keep by talking. Every week or so you have a 10–15 minute voice check-in with Earken; afterwards it organises what you said into your notebook: what's happening now, your threads, goals, people, decisions, patterns and open questions.
- Starting
- Go to earken.com/journal and press “Start your journal”. Sign in with an email link or Google, and your journal is ready. Your first check-ins are free.
- A check-in
- Press “New check-in”, allow the microphone, and talk. Earken asks questions and follows your lead. End it whenever you like; everything said so far is saved.
- Talk more about…
- After each check-in Earken suggests a few things to pick up next time, each with a line on why. Choose one to go deeper on it, or start a fresh check-in. Dismiss any you don't want.
- Reminders
- Earken can email you a gentle weekly reminder. Turn it off or pause it in Settings.
- Ask your notebook
- Ask questions in plain language — “What did I decide about the course?” — and get answers from your own check-ins.
- Your AI assistant
- Create a key in Settings to let Claude or another assistant use your notebook as context. Only keys you create can reach it; revoke one any time.
- Deleting it
- Delete your journal from Settings. It's gone from Earken at once and from our backups within 7 days.
- Who can read it
- Only you. Earken staff, your company and its consultancy can't open it — they see only that it exists, its owner's email and the credits it uses. This holds for journals set up at work too. Use a personal email for your journal: whoever runs a work email account could sign in as you. See Security & privacy below.
For interviewees
- Getting in
- Click the button in your invitation email — it signs you in. Or go to app.earken.com and sign in with the same email address (email link or Google).
- Before you start
- Find a quiet spot. Headphones help. Allow microphone access when your browser asks.
- During the conversation
- Just talk. Choose “Take turns” if you'd rather press a button when you've finished answering. “Skip topic” moves on; “End interview” finishes and saves.
- Dropped call?
- Everything said so far is saved. Open the link again and press Reconnect.
- Afterwards
- Your conversation is added to the knowledge base for the people running the project — the organisation's leadership and its consultancy. Your colleagues don't see it.
For AI agents and developers
- What agents can do
- Set up interviews, get a one-click link for each person to hand over, wait for the conversations, then read the distilled results — summary, knowledge pages, sourced facts, transcript — or ask questions, and interview whoever Earken suggests next.
- API keys
- Consultancy owners create keys under “API keys & agents” on their dashboard (reaches all their projects). Admins of a project bought directly create project-only keys under Settings. Keys are shown once; revoke them any time. Spending uses the same credits.
- Three ways in
- REST API at app.earken.com/api/v1, an MCP server at app.earken.com/api/mcp (for Claude and other agents), and a small command-line tool. Agent-readable docs: app.earken.com/llms.txt.
- Links and email
- Each interview link opens that one interview — no sign-in, and nothing else is reachable with it. Links expire after 14 days; the API can mint a fresh one. Earken sends no invite email unless asked to — the agent delivers the link. Campaigns (larger groups) are always emailed by Earken.
- Webhooks
- Set a URL to be told when interviews start, finish distilling or fail. Each call is signed so you can check it came from Earken.
Security & privacy
- Every client is sealed off
- Each client project's data sits in its own compartment. Every request is checked against who you are, and AWS itself blocks access across clients — each request runs with credentials that can only reach that one client.
- Tested, not assumed
- Automated tests sign in as one client and try to reach another's pages, interviews and knowledge through every route. Releases only ship when every attempt is refused.
- The AI sees one client at a time
- When Earken plans, distils or answers a question it only ever loads that project's knowledge. Nothing from one client is used in another's interviews or answers.
- Encrypted and hosted in the EU
- All traffic is encrypted (HTTPS). Data is stored encrypted at rest on Amazon Web Services in Ireland.
- No audio kept
- Earken keeps the text transcript to build the knowledge base. We don't store audio recordings.
- Our AI suppliers
- Voice conversations run live on xAI (Grok Voice); planning, distilling and answers use Anthropic (Claude). Neither trains on this data, and both delete it within 30 days. Zero-retention terms are available for enterprise clients.
- No passwords
- Sign-in is by one-time email link or Google, so there are no passwords to leak.
- Journals are private
- A journal can only be read by the person who keeps it — check-ins, transcripts, notebook, summaries and answers — and by AI assistants they connect with their own key. Not Earken staff (not even for support), not their company or consultancy: not in the app, “View as”, exports, reports, the API, emails or webhooks. Others see only that it exists, its owner's email and the credits it uses.
- Each journal has its own key
- Every journal is encrypted with its own key, and AWS logs every time it's unlocked. Our servers must unlock the text so the AI can write the notebook, so we promise no person at Earken can read it — not that it's technically impossible.
- Who can see what
- Transcripts stay with the consultancy team running the project (and Earken support when helping you). The client's admins see the knowledge base, which describes people by role, and a short neutral summary of each conversation — not what anyone said word for word. Colleagues see only their own conversations.
- Your data, your call
- Clients own their content. Consultancies can permanently delete a client project themselves; or ask us and it's gone within 24 hours, including past versions (and from our disaster-recovery backups within 7 days). Other data is kept 30 days. Full details: Privacy Policy and Terms.
- Coming: redaction mode
- An optional mode that strips names and specific figures from transcripts before they reach the AI, for sensitive organisations.
Other guides: For consultancies · For client project admins · Process maps · Credits
Running a consultancy and interested in Earken for your clients? Email support@amplifygis.com.
FAQ
My sign-in link didn't arrive
Check spam, then try again from the sign-in page. Links work once and expire after 24 hours. You can also sign in with Google if your email is a Google account.
The interviewer can't hear me
Check the browser has microphone permission (the icon in the address bar), then reload and start again.
Can I correct something in the knowledge base?
Mention it in your next conversation, or ask an admin to invite the person who knows — Earken updates pages when new conversations correct them.
Which browsers work?
Recent Chrome, Edge, Safari or Firefox, on a laptop or phone.
Need help?
Email support@amplifygis.com — include your project or consultancy name and we'll get back to you.