Privacy Policy

Eriqa ("we", "us", or "our") operates the platform available at eriqa.io (the "Platform"). Single sign-on with Google and Microsoft is supported. This Privacy Policy explains how we collect, use, disclose, and protect personal information when you use our Platform, and sets out your rights under applicable data protection laws including:

• The UK General Data Protection Regulation (UK GDPR) and the Data Protection Act 2018
• The EU General Data Protection Regulation (EU GDPR) 2016/679
• The Protection of Personal Information Act 4 of 2013 (POPIA) - South Africa
• US state privacy laws including the California Consumer Privacy Act (CCPA) as amended by the California Privacy Rights Act (CPRA)

Please read this policy carefully. By accessing or using the Platform you acknowledge you have read and understood this policy. If you do not agree, please discontinue use of the Platform.

1. Who We Are (Data Controller / Responsible Party)

Eriqa is the data controller (UK/EU GDPR), responsible party (POPIA), and business (CCPA) with respect to personal information processed through the Platform.

Contact details:
Email: privacy@eriqa.io
Website: eriqa.io

For South Africa: our designated Information Officer can be reached at privacy@eriqa.io.

For EU residents: if we are required to appoint an EU representative under Article 27 GDPR, their contact details will be published here.

2. What Personal Information We Collect

2.1 Account & Identity Data

When you sign in we collect data depending on the authentication method you use:

• Google SSO: Full name, email address, Google profile picture URL, and authentication session data. Signing in with Google requests identity information only (OpenID, email and profile) and grants no access to your Google Drive. Google Drive permissions are requested separately, and only when you use the relevant feature: read-only Drive access when you explicitly connect Google Drive for transcript ingestion, which we use solely to read the folders you designate, and per-file access requested at the point of export, limited to documents and presentations the Platform itself creates on your behalf. The delegated Google Drive workflow never modifies, moves, deletes or automatically shares your source files. A legacy service-account arrangement, used only where an administrator has manually set one up, may involve a folder you choose to share with us for read-only ingestion. Preview sign-in uses our managed authentication broker and does not itself grant Drive access. We do not request access to your Gmail or Google Calendar.
• Microsoft SSO: Full name, email address, Microsoft profile picture (if available), and a Microsoft OAuth access token and refresh token (to access your OneDrive/SharePoint on your behalf for transcript ingestion and report storage). The refresh token is stored securely in our database to enable background auto-ingestion without requiring you to remain signed in. When you sign in with Microsoft, a refresh token is also stored securely on our servers so your session can be renewed without asking you to sign in again every hour; it is never sent to your browser and is deleted if Microsoft reports it is no longer valid
• Email & password: Email address and a securely hashed password (we never store your password in plain text; passwords are hashed using PBKDF2-SHA256 with a unique random salt). If you enable two-factor authentication (2FA), we also store a TOTP secret and single-use backup codes, all protected at rest by our database encryption

Sales representatives: An account administrator may invite an individual sales representative to log in and access only their own performance, coaching, QA, and competency data. Reps activate their account through a secure, time-limited invitation link sent to their email address, after which they authenticate using any of the methods above (Google SSO, Microsoft SSO, or an email and password they set). We store the rep's name, email address, authentication credentials, and notification preferences for this purpose.

2.2 Professional & Client Data

The Platform processes call transcripts and related data that you or your organisation upload or link from Google Drive, Microsoft OneDrive/SharePoint, or upload directly from your device. This may include names, phone numbers, or other personal information contained in those transcripts. You are the data controller for any third-party personal information contained in transcripts; we process it solely as your data processor on your instructions.

Device uploads: Signed-in users may upload transcript files (.vtt, .srt, .txt, .json) or audio recordings (.mp3, .wav, .m4a, .mp4, .webm, .ogg, .aac, .flac) directly from their device into a private storage bucket. Uploaded audio files are transcribed by the speech-to-text sub-processors listed in section 4.1, then the transcript is analysed by the same pipeline as Drive- and dialler-sourced calls. The original uploaded file is retained for 30 days after successful processing and then deleted; the resulting transcript and analysis are retained per section 6.

Method Library material: Account owners and admins may upload sales material (documents, whole folders from their device, or dictated and typed notes) into the Method Library. Files and notes are stored in a private bucket for that account. Dictated audio, including messages spoken into Eriqa's chat, is transcribed and then discarded straight away; only the text is kept, and chat dictation is placed in the chat box for the person to check before sending. When a folder is updated from a device, Eriqa compares file fingerprints to find changes. When Eriqa reads a company record from a client's own connected CRM, it keeps that company's name and industry so library suggestions can match the sector. Each time Eriqa, Ask Eriqa or a connected AI tool quotes a library document, Eriqa records which document and version, the tool, the person and the time, so owners can see where each document is used. If a seller asks Eriqa to check a draft against the Library, the draft is sent to our AI provider with zero data retention and is not stored; only claims with no approved support are kept as unmet requests. When someone asks Eriqa's chat (or a connected AI tool) to build training material, that client's skill scores, objection summaries and approved library excerpts are sent to our AI provider with zero data retention to write it; the result is shown to that person and is not stored unless they save or export it. People can save material created in the chat to their own Google Drive (when signed in with Google) or Microsoft OneDrive (when signed in with Microsoft); Eriqa uses their sign-in permission only to write that one file. Material added to the Library from the chat goes in as waiting for approval, owned by the person who added it. If someone schedules a workflow in the chat (for example weekly training needs or 1:1 preparation), Eriqa stores the schedule and each prepared result for that person; results are deleted after 90 days.

Client setup progress: For newly created clients, Eriqa records which setup items have been completed or left for later, including the client profile, people, frameworks, scorecards, conversation sources, integrations and Method Library. This checklist is held separately for each client and is visible only to authorised people in that account.

Saved Eriqa conversations: Eriqa stores the questions and answers a signed-in person chooses to keep in their conversation history, together with their folders and selected context. This history is private to that person, held separately for each client, and is not shown when they switch to another client. The account deletion and retention rules in section 6 apply to saved conversations.

Coaching evidence documents: Managers and representatives using the Act coaching area may attach supporting documents to a coaching action, such as a call plan, scorecard or development note. These documents are stored in a private bucket and are visible only to the manager and representative attached to that coaching action. A document remains attached to the coaching action and is retained with your other coaching data; deleting the coaching action removes the document link. We do not use these documents to train AI models.

Dialler integrations: When your organisation connects its sales dialler or phone system (such as Orum, Kixie, FrontSpin, ConnectAndSell, Aircall, Dialpad, JustCall, Zoom Phone, Zoom Contact Center, or a dialler connected via Zapier/n8n), the Platform receives call data directly from that system. This may include call audio recordings, call transcripts, the calling representative's name, email address and agent ID, the phone numbers dialled, call timestamps, durations, dispositions, and queue or campaign names. Where the dialler provides its own transcript (for example Zoom, Aircall AI, Dialpad Ai, or JustCall AI), we ingest that transcript directly; otherwise audio recordings are transcribed by the speech-to-text sub-processors listed in section 4.1. Call data is stored in our database infrastructure (Supabase). Your dialler provider remains a separate controller/processor under your agreement with them.

CRM integrations (optional): Where an individual user connects their own CRM account (currently HubSpot or Salesforce), the Platform reads records from the CRM account that user belongs to in order to match a conversation to the right person, company and deal, and to show what has already been recorded against them. The data read may include contact names, email addresses, phone numbers, job titles, company names and web domains, deal names, stages, amounts and close dates, CRM record owners, and existing conversation, note and task activity on those records. The Platform may also store versioned structured facts extracted from a conversation, including action items, competitors, problem statements, stakeholders, renewal dates, commercial details and evidence from the assigned scorecard. Missing information is recorded as not obtained or not assessed rather than inferred. This connection is read-only: the Platform cannot create, change or delete anything in your CRM through it. Where the Platform identifies a possible CRM update from a conversation (for example an agreed follow-up or a blank qualification field), that suggestion is held inside the Platform and is only ever acted on after a person reviews and approves it. Where the person in a conversation is not yet in HubSpot or Salesforce, the Platform may suggest adding them as a new contact (and their company), using only the name, job title, company, phone number and email address recorded for that conversation; it is created only after a person reviews, edits if needed and approves it, and approved changes are made through a separate write connection set up by your organisation. Existing activity is read specifically so that the Platform does not duplicate an entry your dialler or notetaker has already logged. Where an organisation works for several clients (for example an agency), a manager may instead connect a CRM for one specific client; that connection is used only for that client's conversations, never for another client's or the organisation's own, and CRM data is never shared between clients. The connection itself is held encrypted on our servers and is never exposed to the browser. Your CRM provider remains a separate controller/processor under your agreement with them, and a user may disconnect their CRM at any time in Settings, which deletes the stored connection.

Notetaker integrations: When your organisation connects a meeting notetaker (such as Fireflies, Google Gemini for Google Meet, Microsoft Copilot for Teams, Granola, tl;dv, Read.ai, Fathom, or Otter), the Platform pulls the meeting transcript directly from that provider's API. We prefer provider-supplied transcripts and only download the audio/video recording as a fallback when no transcript is available. You control which call types are ingested (Discovery, Demo, Outbound, etc.) through the ingestion filter in Settings - meetings outside that filter are never pulled. Where the Eriqa Recorder has already captured the same meeting for the same representative in the same time window, the notetaker copy is automatically suppressed to avoid duplicate ingestion. Google Meet (Gemini) and Microsoft Teams (Copilot) are connected through Google's or Microsoft's own consent screen, separately from signing in to Eriqa. That consent grants read-only access to your Meet conference records and transcripts (and the transcript documents Meet saves to your Google Drive), or to your Teams online meetings and their transcripts. The resulting access is held encrypted on our servers, is used only to pull meetings that pass your ingestion filter, and is deleted when you disconnect. The notetaker provider remains a separate controller/processor under your agreement with them.

Eriqa Recorder (browser extension and desktop app): Where your organisation enables it, an individual sales representative may install the Eriqa Recorder to capture the audio of their own sales calls (for example on Google Meet, Microsoft Teams, Zoom, or a softphone) directly from their device. When active, the Recorder captures the representative's microphone and the tab/system audio of the other party, buffers the recording locally on the representative's device in short encrypted chunks, and uploads those chunks to the Platform's private storage bucket. Only representatives whose account administrator has issued a pairing code and who have approved recording analysis (see "Representative approval" below) can upload. The Recorder does not capture video, screen contents, keystrokes, or any other application data, and it does not run in the background outside of an active call. Local buffer chunks are deleted from the device as soon as they are successfully uploaded (or, for any chunks that fail to upload, within 24 hours). The uploaded audio is then handled on the same terms as any other device upload: transcribed by the speech-to-text sub-processors listed in section 4.1, retained for 30 days as the original file and per section 6 for the resulting transcript and analysis. Your organisation is responsible for configuring the Recorder in a manner that is lawful in the jurisdictions where its representatives and call participants are located (including any two-party consent requirements) - see the Terms of Service section 4.

Coaching sessions (Act): Where your organisation switches on coaching sessions, a manager may record an in-person or online coaching 1:1 from a representative's coaching plan using their browser microphone, write a short debrief, or paste or upload meeting notes, and a representative may add their own written reflection. A manager must confirm the representative has been told before a recording can start. Recordings are sent in short pieces to be transcribed by the same speech-to-text sub-processors used for call recordings (Groq first, with AssemblyAI and OpenAI as fallbacks, see section 4.1); the audio is discarded as soon as each piece is transcribed and is never stored. The transcript, debrief and notes are stored against the coaching plan, are visible to the representative's managers only (the representative sees their own reflections and commitments), are never scored or analysed as a sales conversation, and are deleted when a manager deletes the session or the coaching plan.

Representative approval: For connected dialler sources and the Eriqa Recorder, an individual sales representative's calls are only transcribed and analysed after that representative approves recording analysis in their own settings. Calls received before approval are held unprocessed for up to 14 days and then deleted (see section 6). Consent changes are recorded in an audit log.

2.3 Usage & Technical Data

• Access request information (email, organisation name)
• Pages visited, features used, and actions taken on the Platform
• Cancellation feedback you choose to give (a reason and optional comment), used to improve the service
• Browser type, device type, and operating system
• IP address and approximate location (country/region)
• Session tokens and authentication state stored in your browser's local storage
• Server-side product events (page-level signup, checkout started/completed) used for marketing pipeline reporting
• Free trial usage: the number of conversations analysed during the trial, the trial start and end dates, the paid rep count and monthly or yearly plan you selected for after the trial, any changes you make to that selection, and when and why the trial converted to a paid subscription. We use this only to run the trial, show your progress, send trial reminder emails (for example when 80% of the allowance is used and when the subscription starts) and charge your latest selected plan when the trial ends

2.4 Communications

If you contact us by email, complete a request-access form, or apply to join the Modern Selling community, we retain the contents of that communication and any personal information you include. For a cohort decision-sheet request, this may include your work email address and, if you choose to provide them, your name and company. We use these details to send the requested brief and respond to that enquiry. For a Modern Selling community application or invite request, this includes your email address and LinkedIn profile link; we use these only to review the request, record it in our CRM (Attio), send the welcome email with the community link once approved, and respond. The request does not by itself subscribe you to marketing emails.

3. How We Use Your Personal Information

4. Sharing Your Personal Information

We do not sell, rent, or trade your personal information. We share it only as described below:

4.1 Sub-processors / Service Providers

• Supabase - database, authentication, and serverless functions. Data may be stored in the EU or USA (subject to appropriate transfer safeguards). See Supabase's privacy policy at supabase.com/privacy.
• Google LLC - OAuth authentication, Google Drive integration, Google Meet notetaker access (including Google Docs and Google Slides files the Platform creates on your behalf via the Drive file-level scope). Data is processed under your Google account terms. See Google's privacy policy.
• Microsoft Corporation - OAuth authentication (Microsoft SSO), OneDrive and SharePoint integration for transcript ingestion and report storage, including PowerPoint files the Platform creates on your behalf when you export a report, Microsoft Teams notifications (via incoming webhook or, after you sign in to Microsoft from Settings, the Microsoft Graph API to list your teams and channels and post messages to the channel you select; the resulting Microsoft access is stored encrypted against your Eriqa login and deleted when you disconnect), and the Eriqa Microsoft Teams bot (where an account administrator switches chat coaching on and a representative adds Eriqa in Teams, we store that representative's work email and their private Teams chat reference, and send their after-conversation coaching, including short quotes from their conversation, to that chat only, via the Microsoft Bot Framework), and Microsoft Teams Phone integration (the Microsoft Graph CallRecords API is used to pull PSTN call records and recordings for transcription and analysis using application-only credentials authorised by a Microsoft 365 global admin granting tenant-wide consent on first connect - Eriqa does not act on behalf of any individual Microsoft user for Teams Phone). Data is processed under your Microsoft account terms. See Microsoft's privacy statement.
• Anthropic PBC - AI model provider for call transcript analysis and report generation. Transcript data is sent to Anthropic's API for processing; Anthropic does not use customer data for training. See Anthropic's privacy policy.
• TypeSafe - provider of the Jev decision model. We send conversation transcript text to Jev to check whether a live person was reached before scoring. TypeSafe processes and may retain this text under its own API terms; it is not used to train models on your behalf and is never shown to other customers. See TypeSafe's documentation.
• Trigger.dev Ltd - background task orchestration for report generation and call ingestion workflows. See Trigger.dev's privacy policy.
• Netlify Inc. - web application hosting and content delivery. See Netlify's privacy policy.
• Resend Inc. - transactional email delivery for account credentials, password resets, invitations, login confirmations, billing notices, and automated knowledge/report emails sent by Eriqa. See Resend's privacy policy.
• OpenAI, L.L.C. - AI model provider, called directly through our own OpenAI API account, used for the in-product and marketing chat assistant ("Eriqa"), background structuring of approved Method documents, conversation facts, training packs and scheduled workflow notes, and, as a last-resort fallback, to transcribe call recordings (speech-to-text) when the primary transcription providers are unavailable. API data is not used to train models; we request that it is not stored (store disabled) and it is retained by OpenAI only as its API terms allow. Eriqa sends only the client context selected by the person asking, such as conversations, approved Method Library material, CRM information or coaching. Any audio processed on the fallback path is handled under OpenAI's API terms. See OpenAI's privacy policy.
• Groq, Inc. - AI inference provider used as the primary engine to transcribe call recordings (speech-to-text) via the Whisper model. Audio recordings are sent to Groq's API for transcription (including Act coaching session recordings, where switched on); Groq does not use customer data for training. See Groq's privacy policy.
• AssemblyAI, Inc. - speech-to-text provider used as a fallback to transcribe call recordings (including speaker separation / diarisation) when the primary transcription provider is unavailable. Audio recordings are sent to AssemblyAI's API in the United States for transcription; AssemblyAI does not use customer data for training. See AssemblyAI's privacy policy.
• Slack Technologies, LLC - team messaging used to notify the Eriqa support team when a new company user signs up, a chat with Eriqa is escalated or a lead is captured. A new-user alert contains the person's name, work email, inferred company name and verified sign-in provider. Where an account administrator connects the Eriqa Slack app and switches it on, Slack is also used to send each representative a private message with their after-conversation coaching. To do this we look up the representative's Slack user by their work email address and send the coaching text (including short quotes from their conversation) to that representative only. Where the Eriqa Slack app is installed, a signed-in Eriqa manager can also ask Eriqa a question in Slack (a direct message, an @Eriqa mention or /eriqa). The text of that question is processed only to answer it: it is matched against that account's Eriqa data and sent to our AI model provider to produce the answer, it is not used to train AI models, and it is not stored beyond our operational logs. To link a Slack user to their Eriqa login, the person signs in to Eriqa and confirms the link; the Eriqa for Slack service, which we operate, then stores their Slack workspace ID and Slack user ID alongside their Eriqa account, user ID, email and role, and uses that link to decide who may ask questions and to deliver their private messages. Anyone can remove their own link, and account owners and administrators can remove links on their account, under Settings, Integrations. An account owner or administrator connects Slack from Settings, Integrations. The Eriqa for Slack service handles the Slack install and holds the Slack credentials; Eriqa itself stores no Slack tokens. When a workspace is connected, Eriqa gives that service a read-only Eriqa key for the account, and records the Slack workspace ID and name, who connected it and when. Disconnecting or uninstalling revokes that key and removes the record. See Slack's privacy policy.
• Firecrawl, Inc. - public website crawling and scraping service used to build the client context profile when you add or refresh a customer record. Only the customer's own public website URLs are sent to Firecrawl; no transcript or call data is ever shared with this sub-processor. See Firecrawl's privacy policy.
• Exa Labs, Inc. - public web search used by the optional Prep research feature, which an account administrator must switch on. When someone prepares for a conversation, only the buyer's company name is sent to Exa to find recent public news; no transcript, conversation, contact or CRM data is ever sent. Results are kept with their source link and date for 7 days, then searched again if needed. Exa processes data in the United States. See Exa's privacy policy.
• Stripe, Inc. - embedded subscription checkout, recurring billing, invoices, saved payment methods, tax calculation and, for supported transactions, tax filing and remittance, fraud and dispute handling, and transaction-level customer support. Stripe processes your name, email address, billing address, payment details, selected service level, paid rep count, billing cadence, currency, Eriqa account identifier and Eriqa user identifier. We do not store full card numbers. See Stripe's privacy policy.
• Notetaker providers (optional). Where your organisation connects a meeting notetaker, transcript and meeting metadata is pulled from that provider's API. The active notetaker sub-processors are: Fireflies AI, Inc. (policy), Google LLC for Gemini / Meet artifacts (policy), Microsoft Corporation for Copilot / Teams artifacts (policy), Granola, Inc. (policy), tl;dv GmbH (policy), Read AI, Inc. (policy), Fathom Video, Inc. (policy), and AISense, Inc. (Otter.ai) (policy). Each notetaker provider remains a separate controller/processor under your agreement with them.
• CRM providers (optional). Where an individual user connects their own CRM account, the Platform reads records from that CRM. The active CRM sub-processors are HubSpot, Inc. (policy) and Salesforce, Inc. (policy). The per-user connection is read-only; approved changes, such as adding a new contact, are made through a separate connection your organisation sets up. No transcript or call recording is sent to the CRM provider, and your CRM provider remains a separate controller/processor under your agreement with them.

4.4 Pseudonymisation Controls (Regulated Industries)

Account administrators can enable per-account pseudonymisation of transcripts under Settings → Privacy & Compliance. When enabled:

• Standard - Email addresses, phone numbers, payment card numbers, IBAN, NI/SSN, postcodes, URLs, IP addresses and dates of birth are replaced with stable tokens before any transcript is sent to AI sub-processors.
• Strict - In addition, person names and organisations are replaced with stable tokens. Designed for regulated industries pursuing ISO 27001 / SOC 2 readiness.
• The original (unredacted) value can be configured to be kept, quarantined in a service-role-only encrypted vault, or shredded (irreversibly discarded) after redaction.
• All un-masking events (where an authorised user reveals the original value behind a token) are recorded in an append-only audit log retained for at least 90 days. The log is visible to the account owner and Eriqa administrators.
• Detection runs entirely inside our own infrastructure - no additional third-party sub-processor is introduced by enabling these controls.

4.2 Legal Requirements

We may disclose personal information if required by law, court order, or to protect the rights, property, or safety of Eriqa, our users, or the public.

4.3 Business Transfers

If Eriqa undergoes a merger, acquisition, or asset sale, personal information may be transferred. We will notify you via email and/or prominent notice on the Platform before such a transfer.

4.5 Internal Read-Only Support and Design Access

A small number of authorised Eriqa administrators can open a read-only preview of an individual sales representative's own dashboard. This exists so we can support accounts and review the representative experience without asking anyone to share their sign-in. The preview cannot create, change, approve or delete anything, it is limited to one representative at a time, and every use is recorded in an append-only administrator audit log. It is not available to customer managers or any other customer user.

5. International Data Transfers

Personal information may be transferred to and processed in countries outside your home country, including the United States. Where we transfer data outside the UK or EEA, we rely on one of the following safeguards:

• An adequacy decision by the UK Secretary of State or the European Commission
• Standard Contractual Clauses (SCCs) approved by the relevant authority
• Other lawful transfer mechanisms permitted under applicable law

South Africa: Where we transfer personal information outside South Africa, we ensure the recipient is subject to a law, binding corporate rules, or binding agreement that provides an adequate level of protection substantially similar to POPIA.

6. Data Retention

We retain personal information for as long as necessary to provide the Platform and fulfil the purposes described in this policy, unless a longer retention period is required by law.

• Account data - retained while your account is active. When an account reaches the end of its life (for example, a trial or beta place expires and the read-only period ends), the account is permanently deleted 30 days later: all conversations, reports, coaching and client data are then removed and cannot be recovered. An administrator may schedule deletion earlier; once that date passes, deletion happens automatically. For beta invitations we keep the invited name, work email, company and invite status for as long as the related account exists, or until we withdraw an unaccepted invite.
• Client records - deleting a client from your organisation marks them as pending deletion. Pending clients are hidden from the Platform and their data is retained for 30 days in case the deletion is reversed; after that they are treated like any other deleted data.
• Transcript and report data - retained for the duration of your contract and deleted upon termination or on request.
• Call recordings (dialler integrations and Eriqa Recorder) - audio recordings ingested from connected diallers or captured by the Eriqa Recorder are stored for the duration of your contract and deleted upon termination or on request, alongside the transcript they produced. Local buffer chunks on a representative's own device are held only until successful upload and, if upload fails, are automatically discarded from the device within 24 hours.
• Coaching sessions (Act) - coaching recordings are never stored as audio; the transcript, debrief notes and reflections are kept for as long as the coaching plan exists and are deleted when a manager deletes the session or the plan, or when the account is deleted.
• Unapproved representatives' calls - where a representative has not approved recording analysis, their calls are held unprocessed (not transcribed or analysed) and automatically deleted after 14 days, or immediately where the representative declines.
• Access request data - retained for 6 months from the date of the request.
• Legal hold - data may be retained longer where required by legal obligation or dispute resolution.

7. Cookies and Local Storage

The Platform uses browser local storage to maintain your authentication session and theme preference. This storage is strictly necessary for the Platform to function and does not require consent under the ePrivacy Directive / PECR.

Saved answers: When you save an answer from the Ask me anything dashboard, the answer and its associated client name are stored locally in your browser under the key di_ama_saved_v1. This data stays on your device, is not transmitted to our servers, and can be removed at any time by clearing your browser's local storage.

Analytics cookies: The Platform does not set any third-party analytics or session-replay cookies. Marketing pipeline events are captured server-side from explicit actions (signup, checkout) and tied to your email address only. You can request deletion at any time by contacting us at privacy@eriqa.io.

Google's and Microsoft's authentication scripts may set their own cookies governed by their respective cookie policies.

Eriqa Recorder extension storage: Where a representative installs the Eriqa Recorder browser extension, the extension uses browser-managed local storage on that representative's own device to hold: a stable per-install device identifier (di_recorder_device_id), the pairing token issued by the Platform when the extension is paired to their account, the current recording policy for their organisation, and short encrypted audio buffer chunks queued for upload. Buffer chunks are deleted from the device once uploaded (or, if upload fails, within 24 hours). No transcript, meeting content, or personal data of call participants is stored on the device outside of these buffer chunks. Uninstalling the extension clears all of the above from the device.

8. Security

We implement industry-standard technical and organisational measures to protect personal information against accidental loss, unauthorised access, disclosure, alteration, and destruction - including TLS encryption in transit, access controls, and regular security reviews.

No method of transmission over the internet or electronic storage is 100% secure. If you become aware of a security incident affecting your account, please notify us immediately at privacy@eriqa.io.

9. Your Rights

9.1 UK and EU Residents (UK GDPR / EU GDPR)

You have the right to:

• Access the personal data we hold about you (Art. 15)
• Rectification of inaccurate or incomplete data (Art. 16)
• Erasure ("right to be forgotten") in certain circumstances (Art. 17)
• Restriction of processing in certain circumstances (Art. 18)
• Data portability - receive your data in a structured, machine-readable format (Art. 20)
• Object to processing based on legitimate interests (Art. 21)
• Withdraw consent at any time where processing is based on consent (Art. 7(3))
• Lodge a complaint with the Information Commissioner's Office (ICO) in the UK at ico.org.uk, or your local EU supervisory authority

9.2 South African Residents (POPIA)

Under POPIA you have the right to:

• Be notified when we collect personal information about you
• Access and request a copy of your personal information
• Request correction or deletion of your personal information
• Object to the processing of your personal information
• Submit a complaint to the Information Regulator of South Africa at inforegulator.org.za

To submit a request under PAIA (Promotion of Access to Information Act) for access to records we hold, please contact our Information Officer at privacy@eriqa.io.

9.3 California Residents (CCPA / CPRA)

California residents have the right to:

• Know what personal information we collect, use, disclose, and sell/share
• Delete personal information we have collected about you (subject to certain exceptions)
• Correct inaccurate personal information
• Opt out of the sale or sharing of personal information - We do not sell or share personal information for cross-context behavioural advertising.
• Limit use of sensitive personal information (we do not use or disclose sensitive PI beyond purposes permitted under CPRA)
• Non-discrimination - we will not discriminate against you for exercising your privacy rights

To exercise CCPA rights, submit a verifiable consumer request to privacy@eriqa.io. We will respond within 45 days (extendable by a further 45 days with notice). You may designate an authorised agent to make a request on your behalf.

Shine the Light: California residents may also request information about personal information disclosed to third parties for their own direct marketing purposes (Cal. Civ. Code § 1798.83). We do not disclose personal information for direct marketing by third parties.

9.4 All Users - Exercising Your Rights

To exercise any of the rights above, please contact us at privacy@eriqa.io. We will respond within the timeframe required by applicable law (generally 30 days for UK/EU/POPIA, 45 days for CCPA). We may need to verify your identity before processing your request. We will not charge a fee unless your request is manifestly unfounded or excessive.

10. Children's Privacy

The Platform is not directed to individuals under the age of 18 (or the applicable digital age of consent in your jurisdiction). We do not knowingly collect personal information from children. If you believe we have inadvertently collected such information, please contact us immediately at privacy@eriqa.io and we will delete it promptly.

11. Third-Party Links and Integrations

The Platform integrates with Google and Microsoft services and may contain links to third-party websites. This policy does not cover those third parties. We encourage you to review their privacy policies before sharing personal information with them.

12. Changes to This Policy

We may update this Privacy Policy from time to time. When we make material changes, we will notify you by email or by prominent notice on the Platform at least 30 days before the changes take effect (or such longer period as required by law). The updated policy will display the revised "Last updated" date at the top. Your continued use of the Platform after the effective date constitutes acceptance of the revised policy.

13. Contact Us

If you have any questions, concerns, or complaints about this Privacy Policy or our data practices, please contact us:

Email: privacy@eriqa.io
Website: eriqa.io

If you are a UK resident and are not satisfied with our response, you may escalate your complaint to the Information Commissioner's Office (ICO).

If you are an EU resident, you may contact your local data protection authority. A full list is available at edpb.europa.eu.

If you are a South African resident, you may contact the Information Regulator of South Africa.