Privacy Policy

Last updated 1 November 2026

This policy explains how Earken ("we", "us"), operated by AMPLIFY GIS MAPPING SERVICE - SOLE PROPRIETORSHIP L.L.C., a company registered in Abu Dhabi, United Arab Emirates (Abu Dhabi economic licence CN-4910769), handles personal data when you use earken.com and app.earken.com (the "Service").

How your data moves through Earken — and how each part protects it. 100 seconds.

1. Our role

  • Account data (your name, email, sign-in details, usage of the Service): we are the controller.
  • Interview content (what people say in interviews, transcripts, the knowledge base built from them): we process this on behalf of the organisation or consultancy that runs the project, who is the controller. We act as their processor and follow their instructions.
  • Journal content (what you say in your journal check-ins, their transcripts, and the notebook, summaries and answers built from them): if you keep a journal for yourself, we process it only to provide the Service to you, and you decide what happens to it. A journal inside a project run by an organisation or consultancy is private to you as well: they cannot read it (see section 4).

2. What we collect

  • Contact and account data: name, work email, role, organisation, who invited you.
  • Interview content: the text transcript of each voice conversation, and the knowledge pages, facts and summaries produced from it.
  • Journal content: the text transcript of each journal check-in, and the notebook, summaries and answers produced from it.
  • Usage data: which features are used, credit consumption, timestamps, technical logs (IP address, browser) for security and debugging.
  • We do not store audio recordings. Audio is streamed live to our voice supplier to run the conversation (see section 5).

3. Why we use it

  • To provide the Service: run interviews, build and show the knowledge base, answer questions, send invitations and sign-in links.
  • To bill and manage credits.
  • To keep the Service secure, prevent abuse, and fix problems.
  • To provide support when you contact us.

We process personal data in line with the UAE Personal Data Protection Law (Federal Decree-Law No. 45 of 2021) and, where they apply, the EU and UK GDPR. Our bases are performance of a contract, our legitimate interests in running and securing the Service, and — for interview content — the basis chosen by the controller. Interviewees are asked for their consent to recording at the start of every conversation.

We do not sell personal data, use it for advertising, or use interview content to train AI models.

4. Who can see interview and journal content

For interviews in a project:

  • Transcripts and verbatim quotes: the consultancy team running that project.
  • The client project's admins: the knowledge base built from the conversations, which describes people by role, and a short summary of each conversation. Other members see only their own conversations.
  • Earken support staff, only when needed to provide support or keep the Service secure (never journal content).
  • Our sub-processors below, only to provide the Service.

Journals are private to the person who keeps them. A journal's content — check-ins, transcripts, notebook, summaries and answers — can be read only by its owner, and by AI agents the owner connects with a key they create. Earken staff cannot read it, not even for support, and neither can the organisation, consultancy or admins of any project it sits in: not in the app, in previews, exports, reports, the API, emails or webhooks. They can see only that the journal exists, its owner's email and the credits it uses. Each journal is encrypted with its own key, and every use of that key is logged by AWS. Our servers unlock the text only to run the Service for its owner — for example, so the AI can write the notebook — and our sub-processors receive it only for that purpose.

Each client project is kept separate from every other. See Security.

5. Sub-processors

SupplierWhat forDataLocation
Amazon Web ServicesHosting, database, file storage, email delivery (SES)All Service dataEU (Ireland)
Anthropic (Claude)Planning interviews, turning transcripts into knowledge, answering questionsInterview transcripts and knowledge base of one project at a timeUnited States
xAI (Grok Voice)Running the live voice conversationLive audio, the interview plan, the spoken conversationUnited States
PostHogUsage analytics (see Cookies)Pages visited and features used, with project names and ids removed; no names, emails or contentEU (Germany)
Google"Continue with Google" sign-in (if you choose it)Name, emailGlobal

Anthropic and xAI do not train their models on data sent through their commercial APIs, and delete it within 30 days (they may keep it longer only where required to investigate abuse). See Anthropic: model training, Anthropic: data retention and xAI: API security. Where data is transferred outside the UAE, EU or UK, we rely on the suppliers' contractual data-protection commitments, including Standard Contractual Clauses where applicable.

6. How long we keep it

  • Client knowledge base and interview content (transcripts, knowledge pages, facts, people records): kept until deletion is requested by the client, its consultancy or the person concerned. Once requested, we delete it permanently — including all past versions — within 24 hours. It then leaves our encrypted disaster-recovery backups within 7 days, as they expire; those backups can't be read except to restore the service. Consultancies can also delete a client project themselves at any time.
  • Journal content: kept until its owner deletes the journal (in its Settings) or asks us to. It is then deleted permanently, including all past versions, straight away, and leaves our disaster-recovery backups within 7 days.
  • Everything else — account data after an account is closed, technical logs, superseded page versions: 30 days.
  • Billing records (credit history and spend totals): as long as UAE tax law requires.
  • Our AI suppliers keep request data for up to 30 days on their side, as described in section 5.

7. Security

Encryption in transit and at rest, per-client isolation enforced in our code and by AWS access controls, passwordless sign-in, and automated isolation tests. Details: Security.

8. Your rights

Depending on where you live you can ask to access, correct, delete, export or restrict use of your personal data, and object to processing. For interview content we will pass your request to the organisation that runs the project and help them respond. Your journal is yours: you can delete it yourself at any time in its Settings, or ask us. Contact support@amplifygis.com. You can also complain to the UAE Data Office or your local data protection authority.

9. Cookies and analytics

We use one essential cookie to keep you signed in. We also measure how Earken is used — which pages are visited and which features are used — with PostHog, hosted in the EU:

  • If you accept analytics cookies, PostHog sets a cookie so it can recognise a return visit from the same browser.
  • If you decline, or haven't chosen yet, we count visits without cookies or local storage, using a daily-rotating anonymous identifier.
  • Either way we never send PostHog the content of conversations or the knowledge base, your name or email, or the names of projects and organisations — page addresses are stripped of them first. We don't record sessions or use analytics for advertising.

You can change your choice at any time with “Cookie settings” at the bottom of every page.

10. Changes and contact

We will post updates here and tell account owners about significant changes. Questions: support@amplifygis.com.