W3Copy logo W3Copy

Privacy Policy · W3Copy

We copy code.
Not your data.

W3Copy runs entirely inside your browser. It never phones home, never reads your personal information, and never collects anything about you. Its only job is adding a copy button to W3Schools code blocks.

Zero data collection w3schools.com only No trackers · No analytics

Last updated: October 3, 2026

Overview

W3Copy ("the extension", "we", "our") is a Chrome extension that adds a sleek, always-visible one-click copy button to every code block on w3schools.com. It is designed to make copying tutorial code fast and frictionless. This policy covers the extension only — it does not apply to W3Schools or any other third-party website.

The short version: W3Copy runs 100% locally inside your browser. It has no server, no analytics, and no mechanism to send anything about you to anyone. The sections below explain each permission individually so you can verify this yourself.

Data we collect

None. The extension does not collect, transmit, store remotely, or sell:

  • Your name, email address, or any personally identifiable information
  • The code you copy — it goes directly to your clipboard, nowhere else
  • Your browsing history, even within w3schools.com
  • Analytics, usage events, crash reports, or diagnostics
  • Keystrokes, form inputs, or clipboard contents (beyond the moment of copy)
  • IP address, device identifiers, or location data

The extension contains no remote code, no third-party SDKs, no ads, and makes zero outbound network requests of its own. It works fully offline once installed.

Permissions explained

Chrome Manifest V3 requires extensions to declare every permission upfront. W3Copy requests only a single API permission. Here is exactly what it is used for — and what it is never used for.

storage

Saves your extension preferences — such as whether W3Copy is enabled or disabled — in Chrome's built-in local storage on your own device. This is the only data ever written. It contains nothing about you personally, only a simple on/off toggle. It stays on your device and is never transmitted anywhere.

No permission is used to read page content for any purpose other than injecting the copy button UI, and nothing is ever sent off your device.

Site access scope

The extension's content script is restricted to a single host pattern:

content_scripts → matches

https://www.w3schools.com/*

Content scripts run only on pages under www.w3schools.com. W3Copy has no access to any other website — your bank, email, social media, or any other domain — and Chrome enforces this boundary automatically. The extension is completely inactive on all other sites.

Where your settings live

The only data written by the extension is a minimal preference object stored via Chrome's built-in chrome.storage API on your local device. This value is never synced to any external server — it exists purely to remember whether you have enabled or disabled the extension between browser sessions.

Uninstalling the extension removes all stored preferences automatically. We have no access to it at any time.

Third parties

We do not share, sell, rent, or trade any information with any third party — because we collect nothing to begin with. W3Copy embeds no advertising networks, analytics libraries, crash-reporting tools, or external SDKs of any kind. The only external resource that loads during normal use is W3Schools itself, which is governed by W3Schools' own privacy policy.

Children's privacy

W3Copy is a developer-utility extension intended for use with the W3Schools learning platform. It does not knowingly collect information from anyone, regardless of age — consistent with every other section of this policy. Because we collect no data whatsoever, there is no risk specific to younger users.

Changes to this policy

If this policy changes — for example, because a future version of the extension introduces a feature that alters how data is handled — this page will be updated and the "Last updated" date at the top will reflect the change. Material changes will also be noted in the extension's Chrome Web Store release changelog.

Continued use of the extension after a policy update constitutes acceptance of the revised terms. You can review all historical versions of this file in the GitHub repository.