MetaPilot

This page explains, in short form, how MetaPilot handles data when you use it with Salesforce in Chrome. This policy is published by Nextooly, the developer of MetaPilot for Salesforce.

1. What MetaPilot Is

MetaPilot is a Chrome extension for Salesforce developers and administrators. It helps you work with Salesforce metadata, Lightning Web Components, Aura components, Apex classes, automation details, debug logs, and related developer workflows from your browser.

MetaPilot is designed to work only with Salesforce orgs that you choose to open or connect.

2. What MetaPilot Accesses

MetaPilot may access Salesforce information needed for the features you use, including:

• Org and user context, such as org ID, user ID, username, and profile.
• Salesforce session details, including the sid cookie of the org you are logged into.
• Metadata, Lightning Web Components, Aura components, and Apex classes.
• Salesforce objects, fields, and record data returned by features you run.
• Automation metadata, such as flows, process builders, workflow rules, validation rules, and triggers.
• Debug log file content that you choose to load or analyze.
• Any records returned by a feature you explicitly invoke.

MetaPilot does not collect or transmit this data to MetaPilot-operated servers. When MetaPilot communicates externally, it communicates directly between your browser and the Salesforce org you choose to use.

3. How Data Is Used

Salesforce data is used only to provide the developer and administrator features you request inside MetaPilot.

MetaPilot may read Salesforce data to display it, analyze it, format it, preview it, or prepare changes. MetaPilot changes Salesforce data only when you explicitly choose an action such as save, deploy, create, update, delete, refresh, or preview-host creation.

MetaPilot does not use Salesforce data for advertising, user profiling, resale, or unrelated analytics.

Limited Use compliance. MetaPilot's use of information received from Salesforce, and any access to user data through Chrome APIs, adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. We do not transfer user data except as necessary to provide or improve user-facing features, do not transfer user data for advertising purposes, and do not allow humans to read user data unless we have your affirmative consent for specific messages, doing so is necessary for security purposes, or doing so is required to comply with applicable law.

4. How Data Is Stored and Retained

Local extension data. Extension settings, saved analyses, selected org context, and similar extension data are stored locally in your browser using Chrome's built-in storage, chrome.storage.local. This data persists until you uninstall MetaPilot, clear extension storage, or use an in-extension control to remove it.

Session data. Salesforce session details, including sid cookie value and org domain, are kept in chrome.storage.session, which Chrome automatically clears when you close your browser. The session token is used only from your browser to call your Salesforce org directly. It is never transmitted to MetaPilot or any third party, and it is not persisted to disk beyond Chrome's session storage.

Salesforce data. Salesforce data you choose to load, analyze, edit, save, deploy, preview, or download stays in your browser memory and in the Salesforce org you choose to use. We do not operate a separate cloud service that stores your Salesforce data.

5. What MetaPilot Does Not Do

To be explicit:

• We do not sell, rent, share, or transfer your data to advertisers, analytics services, data brokers, or any third party.
• We do not send analytics, telemetry, crash reports, or usage metrics to any server operated by us or anyone else.
• We do not have a backend that receives your Salesforce data.
• The only external communication MetaPilot performs is directly between your browser and the Salesforce org you choose to use.

6. Permissions

MetaPilot requests only the browser permissions needed to function within Salesforce.

• Salesforce site access, also called host permissions, lets MetaPilot run on Salesforce domains and communicate with your selected Salesforce org.
• cookies is used to read your active Salesforce session cookies, including sid, so MetaPilot can call Salesforce APIs as the currently logged-in user. The cookie value never leaves your browser except in requests to your Salesforce org.
• storage is used to save local extension settings, selected org context, saved analyses, and similar local state.
• scripting is used to inject a small bridge script on Salesforce pages for session-backed features such as debug-log access. This bridge runs only on Salesforce pages and is not used to send data to MetaPilot-operated servers.

7. LWC Preview Host

For real Lightning Web Component previews, MetaPilot may ask you for permission to create a small Aura application named MetaPilotPreviewHost in your Salesforce org.

This preview host is created only after you confirm the action. It is used to render selected Lightning Web Components inside the real Salesforce Lightning runtime so you do not need to manually create an app, page, or tab for each preview.

MetaPilotPreviewHost is a standard Aura application that lives entirely inside your org. It contains no external endpoints, makes no outbound callouts, and can be deleted at any time from Salesforce Setup -> Lightning Components or via standard deployment tooling.

8. Your Data, Your Control

Stored extension data belongs to you and remains on your device unless you choose to save changes back to Salesforce.

• To remove locally stored extension data, uninstall the extension or clear your browser's site or extension storage for MetaPilot.
• To remove Salesforce metadata created or changed through MetaPilot, use Salesforce Setup, your normal deployment tooling, or MetaPilot itself where the relevant feature supports deletion.

9. Regional Rights

EU / UK (GDPR and UK GDPR). Where MetaPilot processes personal data, the legal basis is performance of a contract, meaning delivery of the functionality you request, and our legitimate interest in providing developer tooling. Because MetaPilot does not transmit personal data to our servers, you can exercise data-subject rights, including access, rectification, erasure, restriction, portability, and objection, directly by using the extension's controls, clearing browser storage, or uninstalling. If you still wish to make a request to us, contact support@nextooly.com.

California (CCPA / CPRA). We do not sell or share personal information as those terms are defined under the CCPA/CPRA. California residents have the right to know, delete, and correct personal information. Because we do not retain personal information on our servers, these rights are exercised locally as described above.

Other jurisdictions. Where local law grants additional rights, we will honor them on the same basis.

10. Children

MetaPilot is a developer tool intended for use by Salesforce administrators and developers. It is not directed to children under 13, or under 16 in the EEA/UK, and we do not knowingly collect data from them.

11. Changes

If this policy changes, we will update the Last updated date at the top.

For material changes, we may also notify users through an in-extension notice or the Chrome Web Store listing notes.

Continued use of the extension after an updated policy is posted means you accept the updated policy.

12. Contact

Questions, requests, or privacy concerns can be sent to support@nextooly.com.

We aim to respond within 7 business days.