Privacy Policy
Effective date: September 27, 2026
This Privacy Policy explains how the OrgWise for Salesforce browser extension (“OrgWise,” “the extension,” “we,” or “us”) accesses, uses, stores, and shares information.
Information the extension accesses
- Salesforce authentication information: OrgWise accesses the active Salesforce session cookie so it can make Salesforce API requests as the signed-in user. The extension does not ask for or store the user’s Salesforce password.
- Salesforce identity and organization details: The extension may retrieve the user’s name, username, Salesforce user ID, organization name, organization ID, environment type, and organization URL to verify connections, display the active context, and let the user select saved organizations.
- Salesforce metadata and access information: The extension retrieves accessible object, field, relationship, List View, Report, folder, sharing, permission, group, role, profile, and related metadata needed for query assistance and user-requested access analysis.
- User-cloning information: When the user chooses Clone User, OrgWise reads the selected source user's available profile fields and assignments and uses the user-reviewed destination values to create a user and selected assignments in the chosen destination organization.
- User-entered content: This includes natural-language requests and SOQL written, generated, saved, or executed through the extension.
- Query results: Salesforce records returned by a query are displayed in the extension and may be copied or exported only when the user chooses to do so.
- AI provider credential: If the user connects Groq, the Groq API key is stored locally in browser extension storage.
How information is used
Information is used only to verify Salesforce connections; display selected users and organizations; discover accessible schema; generate, validate, and execute user-requested SOQL or SOSL; display and export results; analyze List View, Report, folder, sharing, and record access; provide saved-query and query-history features; and clone a user and selected assignments when the user explicitly requests that action.
AI processing and third-party services
When Google Search assistance is selected, OrgWise sends the user’s prompt with Salesforce query-related keywords to Google Search, reads the resulting query suggestion, and closes only the temporary Google window created by OrgWise. Salesforce session cookies, Salesforce passwords, and query results are not sent to Google.
When Groq is connected and selected, OrgWise sends the user’s prompt and a limited, prompt-relevant subset of accessible Salesforce object, field, and relationship metadata directly to the Groq API. The extension does not intentionally send Salesforce session cookies, Salesforce passwords, or query results to Groq. The user’s Groq API key is sent only to Groq for authentication.
Use of third-party services is also governed by their applicable policies, including the Google Privacy Policy, Groq Privacy Policy, and Salesforce Privacy Statement.
Local storage and retention
The Groq API key, provider selection, interface preferences, connected Salesforce organization names and URLs, up to 50 saved SOQL entries, and up to 20 query-history entries per Salesforce organization may be stored locally in the browser profile. Salesforce passwords, session cookies, and query-result datasets are not stored in extension storage. Local information remains until the user clears or removes it, disconnects Groq, uninstalls the extension, or clears browser extension data. OrgWise does not operate a separate server database for this information.
Data sharing
OrgWise does not sell or rent personal data or use it for advertising, creditworthiness, or unrelated purposes. Information is transmitted only to Salesforce to fulfill requested Salesforce API operations, to Google Search when the user selects Google query assistance, to Groq when the user connects and selects Groq, or when required by law.
Security
OrgWise validates query-editor operations and blocks modification commands entered as SOQL or SOSL. The separate Clone User feature creates a destination user and selected assignments only after user initiation and review. All Salesforce actions remain subject to the signed-in user’s Salesforce permissions. Requests use encrypted HTTPS connections. No method of transmission or storage is completely secure, so users should use dedicated AI credentials and follow their organization’s security policies.
User choices and deletion
Users can clear saved SOQL and query history, remove saved Salesforce organizations, disconnect Groq to remove its locally stored API key, clear the extension’s storage through browser settings, or uninstall OrgWise. Salesforce access is controlled by the user’s existing Salesforce permissions and sessions.
Children’s privacy
OrgWise is a business productivity extension and is not directed to children under 13.
Changes to this policy
This policy may be updated when OrgWise functionality or data practices change. The effective date at the top of this page will identify the latest revision.
Contact
For privacy questions or requests, email mahesh.cs724@gmail.com or use the support contact listed on the OrgWise for Salesforce store page.