Privacy policy

Midcall is a service published by Pertinence RH & Stratégie (hereinafter "we"). This policy describes the personal data we collect through the midcall.ai website, the app.midcall.ai application and the Midcall Chrome extension, and how we use it. Sections 2 to 7 cover the website; section 8 covers the application and the extension. Data controller: Pertinence RH & Stratégie, edward@midcall.ai.

Demo booking: when you book a demo, the scheduling is operated by our processor Cal.com (Cal.com, Inc.). The data you enter (name, work email address, company, chosen slot, and any information you add freely) is processed by Cal.com on our behalf and passed to us to organize and follow up on the meeting.

Emails: if you write to us at edward@midcall.ai, we keep your message and your contact details for as long as it takes to handle your request.

Analytics: with your consent, we use Google Analytics 4 to measure site traffic (page views, source, device). This data is pseudonymized.

Organizing demos and sales follow-up: performance of pre-contractual measures at your request.

Responding to your messages: legitimate interest.

Analytics: consent (revocable at any time via "Manage cookies" in the footer).

The data is accessible only to authorized staff of Pertinence RH & Stratégie. Our processors: Cal.com, Inc. (scheduling), Google Ireland Ltd (analytics, if consented), Lovable Labs Incorporated (website hosting). Some of these providers may transfer data outside the European Union; such transfers are governed by the European Commission's standard contractual clauses.

The processors specific to the application and the extension are listed in section 8.

Prospecting and meeting data: 3 years after the last contact. Emails: for as long as it takes to handle the request, then archived for 1 year. Analytics data: 14 months maximum.

You have the rights of access, rectification, erasure, restriction, objection and portability over your data. To exercise them: edward@midcall.ai. You may also lodge a complaint with the CNIL, the French data protection authority (cnil.fr).

See the details in the "Cookies" section below and in the "Manage cookies" panel accessible from the footer. Strictly necessary cookies: storing your consent choices and your theme preference (light/dark), exempt from consent. Analytics cookies (Google Analytics 4): set only if you accept them. Booking cookies (Cal.com): set only when the booking module loads, which you trigger deliberately.

Beyond the marketing website, Midcall provides an application (app.midcall.ai) and a Chrome extension that, during a Google Meet video call, transcribe the conversation live and offer the sales rep advice, then a summary.

8.1 Audio is not recorded. During a coaching session started from the application or the extension, the audio (the rep's microphone and the meeting tab's sound) is transmitted encrypted to our servers, transcribed to text on the fly, then discarded. Midcall creates and keeps no audio recording: no audio file is produced or stored, and the stream only lives in memory for the few seconds the transcription requires. Only the text produced by the transcription is retained. When the meeting assistant is used, the capture is not performed by our servers but by our provider Recall.ai, on its own infrastructure; Midcall only receives the text transcript. The recording conditions applicable to that capture are those of our data-processing agreement with that provider; for every meeting, Midcall instructs it to delete the recording no later than five (5) days after the capture.

8.2 When capture happens. The extension listens to nothing until the user starts a coaching session. Capture ends when the user ends the coaching, closes the application tab, or leaves the meeting; in that last case, the extension closes the coaching after a short resumption window, meant to absorb network drops. Returning to a meeting whose coaching was in progress may resume it automatically. The user stops the coaching at any time from the surface that started it: the banner shown in the meeting or the extension window for a coaching started by the extension, the session screen for a coaching started from the application. When the meeting assistant is used, it joins the video call as a participant, under a name that identifies it. Ending the session stops Midcall's transcription and analysis; removing the assistant from the video call is up to the meeting organizer, who can exclude it like any other participant.

8.3 Data processed. Transcripts of the exchange, and the analyses derived from them: advice shown during the call, summary, call score. Participants: names detected in the meeting interface; participant email addresses, including those of counterparts outside the organization, the teammates' addresses entered by the user, the guests' addresses provided by the calendar when it is connected, and, in meeting-assistant mode, those provided by the video-conferencing platform for each speaker. These addresses are used to tell the team apart from the prospect, to attribute what was said, and, if a CRM is connected, to find the contact's record. When the user connects their organization's CRM (HubSpot, for example) and explicitly asks for it, the Service reads the contact's record there (identity, job title), their company, open deals and latest notes, in order to propose a pre-filled meeting preparation sheet, a proposal the user reviews and can edit before anything is saved. The connected CRM is a service of the Client, not a Midcall subprocessor: access tokens are encrypted server-side and revocable at any time from the settings, and Midcall only writes to it on an explicit user action (sending a summary). The meeting label is also kept. Account-follow-up sheet per prospect account: context, goals, figures mentioned, decisions and stakeholders, built from the successive calls with that account to keep the coaching continuous; this sheet is shared within the client organization, so a rep taking over an account inherits what their colleagues learned. Sales method possibly chosen for a call, and tracking of the topics covered. Questions asked to the search assistant when the user queries their call history. Transcripts replayed for internal quality control: our teams replay real conversations to measure the quality of the advice produced by the AI and compare product versions. Account data: email, name, organization, licenses. Session tokens kept locally by the extension. Calendar, only if the user connects it (Google or Microsoft): upcoming meetings, title, times, participants; the corresponding access tokens are encrypted server-side and revocable at any time from the settings.

8.4 Informing participants. In the web application and in the extension window, starting a coaching session is conditioned on a checkbox the user must tick: they attest that they inform the other party that the exchange is transcribed and analyzed by an artificial-intelligence assistant. A standard notice is offered to them. A timestamp is recorded with the call's summary; it corresponds to the opening of the session and is an element of traceability, not proof on its own. The extension's other start paths (button shown in the meeting, keyboard shortcut, context menu, automatic resumption after leaving and rejoining the meeting) do not ask the question again: they reuse, for the same meeting and for a limited time, the attestation given previously, or start the call as unattested. It is the responsibility of the user, and of the organization employing them, to inform participants and obtain their consent where the law requires it. Midcall does not record audio and uses this data only for transcription, advice and the summary.

Exercise of rights by a non-user participant. Anyone who took part in a call can exercise their rights (access, rectification, erasure, objection) with the client organization that used the Service on that call: it is the data controller. A request sent to edward@midcall.ai is forwarded to that organization and handled with it; Midcall, acting as processor, carries out deletions on its instruction. For a request to succeed, it must make it possible to identify the call concerned (date, organization or counterpart): conversations are not indexed by person.

8.5 Who accesses the data. Calls, transcripts and summaries are accessible to the user who produced them, to the administrators of their organization as part of team management, and to Midcall's teams for operation, support and quality control. Partitioning between organizations is enforced at the database level.

8.6 What we do not do. We do not use your data to train any artificial-intelligence model, and we contractually require our AI providers not to use it for that purpose either. We do not sell or rent your data. We do not implement any emotion-recognition system within the meaning of Article 3 of Regulation (EU) 2024/1689: no emotion is inferred from voice, faces or any biometric data. The AI does interpret the meaning of what is said, a hesitation, a reluctance or an interest expressed by the words themselves, as a reader of the written summary would. We do not build, keep or use any voiceprint that would allow a person to be recognized, and we do not process any images: the video stream the browser requires opening to capture a tab's sound is cut immediately and never read. No one is identified by their voice. When words are attributed to a named person, the name comes from the information displayed by the video-conferencing platform (participant list, active-speaker indicator), never from voice analysis. When several people speak on the same audio stream, telling speakers apart may rely on acoustic separation performed by our transcription provider; on our side it only produces anonymous, temporary labels ("Prospect 1", "Prospect 2"), valid for the duration of the exchange.

This English version is provided for convenience only. In the event of any discrepancy, the French version available at midcall.ai/confidentialite prevails.