Developer tools · HTML WYSIWYG editor
Drafting HTML Email and CMS Snippets Locally, With Nothing Uploaded
· Why it matters
html privacy developer-workflow
Explains why unpublished content such as reorganisation notices, pricing changes and incident updates should be drafted in a tool that never sends it anywhere, and how to confirm that.
The announcement that leaked before it was announced — opens with the risk of drafting sensitive content in online editors
An unapproved pricing notice can cause damage if it reaches the wrong service, account or log before release. ToolAcre reduces that path for editor operations: the WYSIWYG module has no fetch call, account submission or persistence API, and the surrounding toolkit states that it writes nothing to browser storage.
That is a code-path claim, not a promise that every web page is inherently private. The initial site load needs a network connection, the browser and installed extensions remain part of the environment, and copied output can be disclosed later. Use data classification and organizational policy before placing sensitive material anywhere.
Where collaborative editors may send drafts, and what this repository proves about ToolAcre
Collaborative editors commonly need a backend to synchronize or save work, and a page can send telemetry. Those are architectural possibilities, not accusations about unnamed services. A responsible comparison inspects requests, storage and published privacy terms instead of assuming that “online editor” means one universal data flow.
For this ToolAcre product, advertising is blocked in the tool record because developer inputs may contain secrets. The editor code itself only reads and writes DOM state, clipboard actions initiated by the user, and a locally generated download. No request function appears in its processing path.
What local processing means here: no tool request or browser storage after the initial load
“Runs in your browser” here means formatting, tokenization, filtering, preview construction, counting, copying and download preparation occur in the loaded page. The toolkit FAQ says it uses no localStorage, sessionStorage, IndexedDB or cookies for tool content. Reloading or closing therefore clears unsaved work.
The page still had to arrive over the network, and no service worker provides an offline application shell. Local processing also does not hide activity from the source host during initial navigation. Privacy language must describe the editor operation precisely rather than stretching it into anonymity or endpoint security.
Verifying it yourself — walks through opening the network panel while typing and formatting to confirm no requests are made
Verification begins after a clean load. Open developer tools, clear the Network panel, then type, format, switch modes, sanitize and preview a disposable sentence. Requests triggered by those actions would contradict the expected path. Inspect browser storage as a separate check before and after the exercise.
This observation is environment-specific. Extensions, enterprise proxies and browser features can create traffic unrelated to ToolAcre, while cached resources can hide the initial load. Identify initiators and request bodies rather than counting rows blindly. The source inspection supplies the design claim; the network trace tests what the current tab actually did.
Worked example: verify the data path with a non-sensitive pricing-change sample
Draft a fictional pricing-change email containing no real company, date, customer or amount. Add a heading, two paragraphs, a list and an approved public link. Switch to source, inspect the allowlisted result, copy HTML, and save a downloaded document while the Network panel remains open.
Copy and download are explicit exits from the page. The clipboard can be read by other software according to platform policy, and the saved file persists wherever the browser placed it. “Nothing uploaded” during formatting does not mean “nothing disclosed” after a user pastes or sends the result.
The trade-off: no drafts saved for you — explains that nothing stored between visits means you must copy your work out before closing
No autosave means recovery is not provided. Undo and redo are delegated to the browser command path, not stored as a durable project history. A reload, crash or closed tab can erase the current surface. Copy approved drafts to an authorized repository before leaving the page.
That limitation can be useful for temporary work because there is no ToolAcre draft account to clean up, but it shifts responsibility to the writer. Establish a save point outside the editor and follow document controls. Local ephemerality is neither version control nor an approval workflow.
What this does not cover — sending the email or publishing to a CMS, which necessarily involve a server
This article does not cover sending email, CMS authentication, collaboration, endpoint malware, clipboard managers, extension permissions or secure archival storage. Each can expose content through a different path. It also does not claim the client-side allowlist makes an untrusted draft publishable.
The sandbox protects ToolAcre’s preview from script execution and form submission, but it disappears when markup leaves the frame. A destination server accepting content must sanitize for its own context. Privacy of processing and safety of rendered publication are independent boundaries.
Takeaway: draft with fewer data paths, then publish through a separately reviewed system
Draft privately should mean fewer observed parties during the documented operation, not a sweeping confidentiality guarantee. ToolAcre’s source supports a narrow claim: editor actions need no network after load and tool content is not persisted by the toolkit. You can inspect both conditions in your environment.
Publish deliberately through a separately reviewed CMS or mail system, using only approved content. Copy work out before the tab is lost, then clear or close it according to policy. The strongest workflow combines minimal data paths, observable verification and honest acknowledgement of every later handoff.