Sales Copilot · Edra Labs LLP
Privacy Policy
Last updated: October 26, 2026
Sales Copilot ("the Extension"), provided by Edra Labs LLP, is a Chrome extension for Salesforce that syncs your meetings, emails and call transcripts, turns them into deal and account intelligence, and suggests CRM updates, follow-up emails and meeting briefs from a side panel on the Salesforce page. The Extension is a thin client: it renders the interface and talks to your Salesforce org, while the processing happens on our backend service. This Privacy Policy explains what data we collect, how we use it, and your rights.
1. Information We Collect
Account Identity and Sign-In
- We use Google Sign-In to verify your account and associate it with the Salesforce identity supplied by the Extension. We process your Google account identifier and email address, Salesforce user and organization identifiers, work email address, and Salesforce domain. We store verification and session information to authenticate requests and manage sign-in and sign-out. Access to Gmail and Calendar depends on the permissions you grant, which you can review in your Google Account and the Extension's settings.
- Your Salesforce session credentials never leave your browser. The session cookie and Aura token the Extension uses to call your own Salesforce org are held in local browser storage and are not transmitted to, or stored by, our servers. Our backend holds no Salesforce credentials and never connects to Salesforce directly — when it needs Salesforce data, it asks your browser to fetch it.
Salesforce Record Data
- The Extension reads Salesforce records — opportunities, accounts, contacts, contact roles, tasks and events, notes and attached files, and the field and picklist definitions of your org — and uploads them to our backend, where they are stored so the Extension's intelligence, search and suggestion features can be produced from them.
Google Account Data
- If you connect your Google account, our backend accesses your Gmail messages and Google Calendar events on a read-only basis, to match conversations and meetings to Salesforce opportunities. Message content, participants, subjects and event details are stored on our servers for that purpose.
- With your permission the backend can also create draft emails in your mailbox for follow-ups you ask it to write. It creates drafts only — it never sends email on your behalf.
- The connection is made by our backend, not by the Extension, and can be revoked at any time from the Extension's settings or from your Google Account.
Meeting Recordings and Transcripts
- If you connect Zoom, our backend reads your Zoom account identifier and email address to associate the connection with your Sales Copilot account. It uses recording metadata, meeting identifiers, titles and timestamps to retrieve available cloud-recording transcripts, retained AI Companion transcripts and My Notes transcripts accessible to your account.
- Transcript text and meeting metadata are stored so they can be matched to calendar meetings and sales records and used for summaries, briefs, suggestions and assistant answers. Relevant content can be sent to the AI providers described below. The Zoom integration does not join meetings, start recordings or edit your Zoom content.
- Availability depends on your Zoom account permissions, plan, transcription and retention settings. Disconnecting Zoom clears stored connection credentials and stops future sync through that connection; it does not automatically delete previously imported transcripts or derived insights. Removal in Zoom revokes access, and we clear stored credentials when we receive its deauthorization notification. Contact us to request deletion.
Other Connected Services
- If you connect Microsoft Teams, we process account identity and accessible meeting metadata and transcripts through Microsoft Graph. Availability depends on your organization's permissions and administrator consent. We use imported content for the same meeting and deal-assistance features described above.
- If you connect Atlassian, the assistant can search and read Confluence content and accessible attachments using your account's permissions. Relevant content and results can be processed by our AI providers. The hosted assistant can use an AI-provider credential vault to access this connection. Sales Copilot's configured Atlassian tools are for reading and searching.
Files, Assistant Conversations and Saved Preferences
- Files you upload or choose to use, including relevant email, Salesforce or Confluence attachments, may be stored in AWS object storage. We process their text, images and document structure to support the feature you request. Where configured, Modal processes document contents for extraction and OCR, and AI providers process extracted content or images.
- We store assistant messages, tool results and generated files so you can return to your work. Hosted assistant features can also store conversation state, working files and generated artifacts with OpenAI. If saved-memory features are enabled, preferences and instructions you ask the assistant to remember are stored separately from the conversation.
AI Processing and Research
- To produce summaries, risk assessments, briefs, suggested field values and chat answers, the relevant context — which can include the content of your emails, transcripts, notes and Salesforce fields — is sent to our AI providers (OpenAI and Anthropic) for processing.
- The results are stored on our servers alongside the records they describe. Conversations you have with the in-product assistant are stored so a thread can be reopened, and are deleted on the schedule in section 7.
- Research features can send search queries to AI-provider web-search tools and retrieve public pages. Queries can contain relevant work context from your request, including company or person names, and are processed by the provider for the requested research.
Product Analytics and Diagnostics
- We collect usage analytics through PostHog to understand which features are used and where they fail. Events are keyed to a pseudonymous identifier derived from a one-way SHA-256 hash of your Salesforce user id. Associated properties can include your Salesforce user alias, organization identifier and domain, extension version, feature usage and experiment settings.
- Product event tracking is designed to use operational metadata, such as counts, durations, identifiers and category labels, rather than email bodies, transcript text or chat messages. Automatic page-view capture and session recording are disabled in the extension's analytics client.
- We also collect error diagnostics, logs and traces to detect and fix failures. These can contain account and organization identifiers, user aliases, URLs, technical details and customer content. When backend AI-content capture is enabled, model prompts and responses can be included in telemetry sent to SigNoz.
2. How We Use Your Information
- Authentication: to verify your identity and apply account and role-based access permissions.
- Core features: to sync your CRM records, meetings, emails and transcripts, link activities to the right opportunity, and keep your workspace up to date.
- AI features: to generate summaries, deal and account intelligence, meeting briefs, suggested CRM updates, draft emails and answers to your questions.
- Product improvement: to measure feature usage and diagnose errors, using the limited event data described above.
We do not use customer content to train general-purpose AI models. We use business/API AI services under their applicable service terms and data controls. Provider storage, safety processing and retention depend on the service and feature used, as explained in section 7.
3. Data Storage & Security
- Application records are stored in a PostgreSQL database; files and generated artifacts may also be stored in object storage or hosted assistant services. Access follows account and role permissions. Authorized managers can view team members' work where team access is enabled, and authorized administrators can use administrative access.
- Access and refresh tokens for your Google and Zoom connections are encrypted before database storage. Our production encryption policy requires encryption of application databases and backups at rest and HTTPS with TLS 1.2 or higher at the public endpoint.
- Backend access uses short-lived signed session tokens. Renewal depends on a valid application session and Google verification; signing out ends the application session. We do not ask you to provide your Salesforce password.
- All communication between the Extension, our servers and third-party services uses HTTPS or secure WebSockets.
- Data is streamed back to the Extension over an authenticated, per-user connection and cached in your browser so the panel renders offline-tolerantly. Clearing browser data or uninstalling the Extension removes that local copy.
4. Third-Party Services
The Extension and its backend integrate with the following third-party services:
- Salesforce: to read and update your CRM data, using your own session, from your own browser.
- Google (Gmail & Calendar): to sync emails and meetings (read-only) and to create email drafts you request.
- Zoom: to read account identity, recording and meeting metadata, and available cloud-recording, AI Companion and My Notes transcripts.
- Microsoft: connected Teams account identity, meeting metadata and transcripts.
- Atlassian: connected account identity, Confluence search, pages and attachments.
- AWS: application hosting, databases, file storage, backups and secret storage.
- Modal, where configured: document-content extraction and OCR.
- OpenAI and Anthropic: to process AI features. Data sent to these providers is subject to the applicable business/API terms and data controls. OpenAI also provides hosted assistant sessions, file processing, web search and connected-tool access where enabled.
- PostHog: product analytics, limited to the event data described in section 1.
- Sentry: error diagnostics, extension logs and performance traces.
- SigNoz: backend logs, traces and metrics, including AI prompts and responses when content capture is enabled.
5. Google API Services — Limited Use
Sales Copilot's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Specifically, Google user data is used only to provide and improve the features described in this policy, is never sold, is never used for advertising, and is never used to train generalised AI or machine-learning models. Human access to Google user data occurs only with your explicit consent, for security purposes, to comply with applicable law, or where the data has been aggregated and anonymised.
6. Data Sharing
We do not sell, trade or rent your personal data, and we do not share it with advertisers. The service providers listed in section 4 process relevant data to provide the features and operate the service. Within your organization, authorized managers and administrators may access information according to their permissions, as described in section 3. We may disclose data where required by law.
7. Data Retention
- Synced Salesforce, email, calendar and transcript data, and the intelligence derived from it, are retained while your account is active.
- For classic assistant conversations, unpinned threads become eligible for cleanup after 30 days of inactivity, with cleanup performed when a new classic thread is created. Pinned threads and hosted assistant conversations do not follow that automatic cleanup path and can remain until deleted. You can delete conversations through the product or request deletion.
- Saved assistant memories are separate records. Deleting a conversation does not necessarily delete its saved memories; manage those in the product or include them in a deletion request. Files, extracted content and generated artifacts also need to be included in a data request.
- Connection credentials are cleared when you disconnect an integration. Disconnecting is separate from deleting data already imported into Sales Copilot.
- Our approved retention policy calls for application data to be deleted within 30 days of a verified deletion request or account closure. We follow an operational deletion procedure; this is not an automatic consequence of removing the Zoom app.
- Database backup copies can remain for up to 35 days after deletion. Removing the Chrome extension clears its local copy; a server-side deletion does not clear your browser.
- Diagnostic and service-provider records have separate retention periods: SigNoz logs and traces 15 days and metrics one month; Sentry records up to 90 days. PostHog events do not expire automatically and require a deletion request that includes the associated events.
- AI-provider retention varies by endpoint, hosted session, file type and applicable service terms. Some API safety records have a standard retention window, while stored sessions and files can remain until deleted or their configured expiry. Deleting a hosted conversation in Sales Copilot also requests deletion of its hosted session and tracked input-file copies; this does not imply immediate removal of all provider safety records or backup copies. Security, compliance and incident records can be retained where needed for legal obligations or security investigations. We explain any remaining copies when responding to your request.
8. Your Rights
- Disconnect services: use the Extension's settings to disconnect an integration and clear its stored connection credentials. You can also revoke permission through the provider. Microsoft does not offer an application token-revocation endpoint for this flow; use your Microsoft account or administrator controls to revoke its grant. Disconnecting a service does not delete data already imported into Sales Copilot.
- Delete data: you can request deletion of your account and its associated data by contacting us.
- Access data: you can request a copy of the data we store about you.
- Correct data or raise an objection: contact us about inaccurate information, restrictions on processing, or another applicable data-protection right. We verify your identity and authority before acting and explain any limits that apply to the request.
9. Chrome Extension Permissions
The Extension requests the following Chrome permissions:
- cookies: to read your existing Salesforce session cookie so the Extension can call your own org on your behalf.
- storage: to persist your session state, settings and panel navigation locally.
- alarms: to schedule periodic Salesforce syncs and token refreshes.
- scripting: to read your Salesforce user id from an open Salesforce tab.
- identity: to open Google's sign-in flow and return its result to the Extension.
- declarativeNetRequest: to adjust request headers so the Extension's own requests to Salesforce and our backend succeed. It does not block, redirect or inspect any other site's traffic.
The current extension requests required access to Salesforce domains and the configured
backend and sync-service domains, including *.nebulalabs.com and
*.nebulalabs.in. Its Salesforce interface is injected on Salesforce pages.
The manifest also declares optional HTTPS site permissions for features that require access
to another site; those permissions are not granted merely by installing the Extension and
require your approval when requested. Domain changes may require an updated extension.
10. Changes to This Policy
We may update this Privacy Policy from time to time. Changes will be reflected on this page with an updated "Last updated" date. We will provide additional notice and obtain consent where required before using previously collected data for a new purpose.
11. Contact Us
If you have questions about this Privacy Policy or wish to exercise your data rights, please contact Edra Labs LLP at support@aecopilot.ai.