Wingman — Privacy Policy
- Last updated:
- 2026-05-14
- Data controller:
- Selectra
- Contact:
- [email protected]
Wingman is an internal Chrome extension distributed by Selectra to its own sales agents. It is not offered to the general public. This policy explains what the extension processes, where data goes, and how long it is kept.
1. Who uses the extension
The extension is installed on the workstations of authorised Selectra sales agents. End customers do not interact with the extension; however, their voice is captured as the incoming audio of the call the agent is handling (see Section 3).
2. What the extension does
On first use, the agent signs in to Selectra Conversa — Selectra's internal back-office application — through Google Workspace SSO. The resulting per-user access token is stored locally in the agent's browser and used to authenticate every subsequent call into Conversa.
When the agent explicitly clicks Démarrer l'écoute during a call handled in the Zoho CRM tab, the extension:
- Captures the audio of the active tab (the customer's voice, transmitted by Vonage WebRTC) and the microphone (the agent's voice).
- Requests a short-lived speech-to-text session from Selectra Conversa, which mints a single-use Gladia WebSocket URL on the agent's behalf. The extension opens that WebSocket directly to Gladia and streams the audio for real-time transcription. Audio bytes do not transit through Selectra's servers.
- Periodically sends the resulting text transcripts to Selectra Conversa, which forwards them server-to-server to OpenAI to classify the conversation state and returns a suggested commercial response.
- Displays the suggestion as an overlay on the Zoho CRM page, visible to the agent only.
Capture stops automatically when the agent clicks Arrêter l'écoute or when the agent closes the tab.
3. Personal data processed
| Category | Source | Purpose |
|---|---|---|
| Agent voice | Local microphone | Transcription, suggestion generation |
| Customer voice | Vonage call audio in the Zoho tab | Transcription, suggestion generation |
| Textual transcript of the call | Derived from the audio | Suggestion generation |
| Agent identity (name, email, Google user ID) | Google Workspace SSO via Selectra Conversa | Per-user authentication, audit logging, per-user revocation |
| Per-user OAuth access & refresh tokens | Issued by Selectra Conversa after SSO | Authenticating the extension's calls to Selectra Conversa |
| Browser User-Agent string | Agent's browser, attached to the OAuth session row | Help admins identify sessions when revoking |
| Agent preferences (department, theme, optional commercial context) | Agent's browser / Workspace policy | Local UX state and prompt customisation |
| Cached playbooks (situations, scripts) | Selectra Conversa | Reducing network traffic during calls (1 h soft TTL) |
No identifiers tying the transcript to a specific customer record (name, phone number, CRM ID) are collected by the extension. The only directly identifying information processed is the agent's own Google Workspace identity. The extension does not read the Zoho CRM DOM beyond the Vonage call-state indicators.
No third-party API keys (Gladia, OpenAI) are stored on the agent's workstation. They reside exclusively in Selectra Conversa's server environment and are not accessible from the extension.
4. Where data is sent
- Selectra Conversa — Selectra's internal back-office, operated by Selectra and hosted on AWS in the EU . Conversa is the central control point: it authenticates the agent, returns playbooks, forwards transcripts to OpenAI server-to-server, and mints one-shot session URLs for Gladia. Audio is not stored or proxied through Conversa; only request metadata is logged (see Section 5).
- Gladia SAS (France) — speech-to-text processor. Audio is streamed directly from the agent's browser to
api.gladia.ioover WSS using a single-use session URL minted by Conversa. The Gladia API key never leaves Conversa's server environment. Privacy terms: https://www.gladia.io/privacy - OpenAI, L.L.C. (USA) — large-language-model processor. Transcripts are forwarded from Selectra Conversa (server-to-server, not directly from the agent's browser) to
api.openai.com. The OpenAI API key never leaves Conversa's server environment. Privacy terms: https://openai.com/policies/privacy-policy - Google LLC — identity provider via Google Workspace SSO. The agent's
@selectra.*email, display name, and Google user ID are exchanged at sign-in. No Google service is called during a live call. Privacy terms: https://policies.google.com/privacy
5. Retention
- On the agent's workstation: no audio or transcript is written to disk. Transcripts live only in memory for the duration of the call and are discarded when the call ends. The agent's OAuth access token (1 h lifetime) and refresh token (30 d lifetime) are persisted in
chrome.storage.localuntil sign-out or expiry. Cached playbooks expire after 1 h. - On Selectra Conversa: no audio and no transcript content is persisted. Per-call request metadata (agent's user ID, timestamps, anonymous Gladia session ID, OpenAI token usage counters, user-agent string) is retained in application logs for 30 days. Per-user OAuth token hashes (never plaintext) are retained in the database until the agent signs out, an administrator revokes them, or the user is deleted.
- At Gladia and OpenAI: retention is governed by the processors' policies and the contractual agreements in place with Selectra. Zero data-retention is requested where the processor supports it.
6. Legal basis (GDPR)
Processing is carried out for the legitimate interest of Selectra in improving the quality and efficiency of its commercial interactions, and, where applicable, on the basis of the employment relationship between Selectra and its sales agents. Call-recording notice obligations owed to end customers are handled by Selectra through its standard call-opening script, outside the scope of this extension.
7. Security
- Per-user authentication via Google Workspace SSO. Access tokens rotate every hour; refresh tokens expire after 30 days; both are bound to the agent's Selectra Workspace account and can be revoked individually by a Conversa administrator with no impact on other agents.
- No third-party API keys (Gladia, OpenAI) live on the agent's workstation — they reside exclusively in Selectra Conversa's server-side environment, encrypted at rest with the application key, and rotatable from Conversa's admin interface without redeploying the extension.
- All network traffic uses HTTPS / WSS.
- The extension requests only the permissions strictly required to operate:
offscreen,tabs,storage,identity, microphone access, and host access to Gladia and to Selectra Conversa.
8. Your rights
Agents and customers may exercise their GDPR rights (access, rectification, erasure, objection, portability) by contacting [email protected]. Because Selectra does not retain audio or transcript content, requests targeting that content are forwarded to the relevant processor. Requests targeting the metadata Selectra holds (agent identity, OAuth sessions, call metadata logs) are honoured directly by Selectra.
9. Changes to this policy
Material changes will be communicated to agents through Selectra's internal channels and reflected in the version timestamp above.