Yes. All of the plugin’s JavaScript and CSS ships inside the plugin itself — nothing executable is loaded from a remote server. But to display the live, interactive diagrams, the bundled loader connects to scrollchart.com at runtime for diagram DATA:
- It fetches each diagram’s metadata from scrollchart.com/api/diagram (cached locally on your server so repeat page-views do not hit the network). Only the diagram slug you embedded is sent.
- It loads the interactive diagram view in an iframe from scrollchart.com/embed-frame/ .
- It sends a view ping to scrollchart.com/api/ping . The ping sends the diagram slug and the URL of the page the diagram is embedded on. We use this to show authors where their diagrams are being used and to periodically check that the embed is still live on that page. No cookies are set and no visitor-identifying data (no IP stored long-term, no user agent, no fingerprint) is collected. Note that a page URL can itself contain information placed there by the site (for example a username or token in the path or query string); if that is a concern for a particular page, do not embed a Scrollchart diagram on it.
- Periodically (at most once every 15 minutes per diagram) it asks scrollchart.com/api/diagram-rev whether a diagram’s content has changed, so your cached copy stays fresh. Only the diagram slug and your site host are sent. This is a lightweight read; no visitor data is involved.
- Attribution. The plugin registers your site with ScrollChart, and may add one short paragraph containing a single link to one page on your site. Only your site host is sent, and no visitor data is involved. You can always contact us at https://scrollchart.com/contact if you wish to disable this functionality.
In the editor (admin) screens, when you are picking or creating a diagram:
- The catalogue browser loads the list of available diagrams from scrollchart.com/api/catalog.json . This is a read-only request; no data about you, your site, or your content is sent. The result is cached on your server for an hour.
- When a logged-in editor uses the optional Generate with AI button, the editor’s typed prompt, and an email address only if the editor chooses to enter one, are sent from your server to scrollchart.com/api/generate.php , which returns a generated diagram. This happens only when an editor actively clicks Generate; it never runs for site visitors and never runs on the front end. If you do not use the AI generator, no prompt data is ever sent.
- When you design or save your own diagram in the editor, the diagram’s content (the chart type, labels, values and styling you set) is sent to scrollchart.com/api/user-diagram so it can be stored and given a reusable ID you can re-open and edit later. Listing and deleting your saved diagrams use the same endpoint. This runs only when you actively design, save, or manage a diagram in the editor.
- To link your saved diagrams to your site (so only your site can edit them), the plugin registers your site with scrollchart.com/api/site-register , sending your site’s home URL and the installed plugin version, and receiving a per-site key it stores locally. This happens on activation, on plugin update, and the first time the editor loads if a key is not yet present. The version is sent only so we know which plugin features your site can use; it is not used to identify you. When the plugin is deleted, it sends a one-time notice to scrollchart.com/api/site-deactivate (again, only your home URL) so the service knows the install was removed; this does not delete any diagrams you created.
All of these are first-party Scrollchart endpoints (the service is operated by us, scrollchart.com). What is sent, who receives it, and how it is handled are documented in our privacy policy: scrollchart.com/privacy#wordpress-plugin . Use of the service is governed by our terms: scrollchart.com/terms .
