Privacy Policy

What CodeLocator reads

CodeLocator reads a page only when you start a pick on it, by clicking the toolbar icon or pressing the shortcut, and only in that tab. When you click an element, it reads:

• the address of the page, for example http://localhost:4200/volunteers;
• a short description of the element: its tag, id and classes, a few attributes such as aria-label or placeholder (up to 200 characters each), its own text (up to 80 characters) and up to 10 of its parent elements;
• the component that renders it, as your app's framework reports it in development mode: its name and tag, and for Next.js apps where in your source it was created.

// one pick, sent to the bridge on 127.0.0.1
{ "pageUrl": "http://localhost:4200/volunteers",
  "component": { "className": "VolunteerCardComponent", "selector": "app-volunteer-card" },
  "element": { "tag": "button", "classes": ["btn", "btn-primary"],
               "attributes": { "type": "submit" }, "text": "Register",
               "path": ["app-volunteer-card", "div", "button"] } }   // shortened

It does not read form values you typed, passwords, cookies, your browsing history or pages where you did not start a pick.

Where it goes

The extension sends a pick only to the CodeLocator bridge, a small program you install and run on the same computer. The extension talks to it at 127.0.0.1, an address that never leaves your computer. The bridge uses the pick to find the matching file and line in your project, reading your project's files on your disk, and then opens that line in your editor.

Nothing is sent to a server, to us, or to any third party. The extension and the bridge have no accounts, no analytics, no ads and no tracking. (This website does count visits; see This website.)

What it keeps

Why it asks for each permission

• activeTab and scripting: to add the element picker to the tab where you start a pick, and nowhere else.
• sidePanel: to show the file, line and styles of your pick next to the page.
• storage: to keep the settings and counts listed above in Chrome on your computer.
• nativeMessaging: so the Connect button can start and stop the bridge on your computer.
• Access to 127.0.0.1: to talk to the bridge on your computer. No other address is contacted.

How the data is used

The data is used only to find and open the source of the element you picked, and to show you your own Time saved counts. It is never sold, never shared or transferred, never used for advertising, and never used to decide credit or lending. CodeLocator's use of this data follows the Chrome Web Store User Data Policy, including its Limited Use requirements.

How to delete it

• Press Reset counts on the Time saved page to delete the counts.
• Remove the extension in chrome://extensions to delete everything it stored in Chrome.
• Run codelocator setup --remove and npm uninstall -g codelocator, then delete the .codelocator folder in your home folder, to remove the bridge and its files.

This website

This website uses Google Analytics to count visits and see which pages people read, so the site can be improved. Google Analytics sets cookies and receives your browser's usual information, such as the page address, your approximate location and your device type. It is handled by Google under the Google Privacy Policy. You can block it with your browser's privacy settings or Google's opt-out add-on.

This applies to the website only. The CodeLocator extension and the bridge use no analytics and send nothing to Google or anyone else.

Changes and contact

If this policy changes, the new version will be posted on this page with a new effective date.

Questions: yassin_mohamed310@outlook.com