Workspace text
Text pasted into work.plainsift.com is processed in that browser document and held in memory only. PlainSift does not transmit or store the input, output, prefix, suffix, filter term, pipeline, or content-derived counts. Workspace text is not placed in URLs, cookies, browser storage, telemetry, parent-window messages, error reports, advertising, or analytics.
The workspace sends its parent only a versioned ready message and a numeric document-height message. It loads no third-party code and its content security policy blocks network connections. Resetting, navigating away, or closing the document clears its in-memory state.
Public-page technical requests
Loading plainsift.com creates ordinary requests to the static hosting provider. The provider may process technical request data such as an IP address, requested path, timestamp, user agent, security signals, and caching information to deliver and protect the site. Pasted workspace text is not part of those requests.
Public-page analytics
Public pages on plainsift.com load a traffic analytics script fromanalytics.zelvon.com. It receives the public page URL and title, referrer, screen dimensions, and browser language. As with an ordinary network request, the analytics host may also process the IP address and user agent needed to receive the request. PlainSift uses this information to understand visits and navigation on its public pages.
The analytics script is never loaded on work.plainsift.com. The public page cannot read the cross-origin workspace document, and the workspace never sends input, output, options, or content-derived counts to the parent, so pasted text is not included in analytics.
Advertising and consent
Advertising is disabled in the default build. If the owner enables validated Google AdSense configuration, ads appear only on public tool pages and never inside the workspace. Google and approved partners may then process identifiers, cookies, IP addresses, consent choices, and related advertising data under the active certified consent platform and Google’s policies.
For regions where Google requires it, the owner must configure Google Privacy & Messaging or another Google-certified consent management platform before ads are enabled. Consent and advertising settings depend on the final account, host, operating entity, and applicable law and must be reviewed at launch.
Messages sent to privacy@plainsift.com are processed by the sender’s and recipient’s email providers for the purpose of handling privacy, security, legal, or factual correction matters. Do not include private workspace text unless you deliberately choose to send it by email.