Diplo Language Suite — Privacy Policy

Last updated: 2026-06-11

This policy applies to the Diplo Language Suite product and all of its components: the Chrome extension (a Google Docs side panel), the WordPress plugin, the Google account integration used by the extension, and the Diplo Language Suite backend service they connect to. The product helps editors rewrite content (DiploWRITER) and monitor whitelisted sources for updates to their content (DiploUPDATER).

Information we handle

• Account information. When you register or sign in, your email address, name, and password are sent to the backend to create and authenticate your account. Passwords are transmitted over HTTPS and stored only as salted hashes; we never store your password in the browser.
• Authentication tokens. After sign-in, a session token is stored in the Chrome extension's storage (chrome.storage.local), and sent with API requests to authenticate you. The WordPress plugin authenticates to the backend with a machine token configured by the site administrator.
• Google Docs content (Chrome extension). With your authorization (Google OAuth, drive.file scope), the extension can only access Google Docs you individually grant via the Google file picker. For each document, you explicitly grant access through a picker hosted at dls.kivos.dev/grant-access. The extension reads granted documents to link monitored questions to your content, and writes only the rewrites you explicitly accept. Text you choose to monitor or rewrite is sent to the backend for processing.
• WordPress content (plugin). On sites where an administrator installs the plugin, the questions you define, the paragraphs you link to them, your chosen sources, and the resulting suggested updates are stored in your WordPress site and synced to the backend to power source monitoring and review.
• Configuration. The backend URL you set is stored in chrome.storage.sync (extension) or your site options (plugin).
• Clipboard (Chrome extension). When you explicitly use a paste action, the extension reads the clipboard text you are pasting. Clipboard contents are not read in the background.

How we use it

Data is used solely to provide the product's features: authentication, linking monitored questions to your content, retrieving source updates, and performing AI rewrites that you request. We do not sell your data, use it for advertising, or share it with third parties except the service providers needed to deliver these features (our backend and the AI/search providers it calls).

Google user data & Limited Use

Diplo Language Suite's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google Docs content accessed via the drive.file scope is used only to provide and improve the user-facing features you request (linking monitored questions and performing rewrites); it is not used for advertising, not sold, and not transferred to others except as necessary to provide the service, to comply with applicable law, or as part of a merger or acquisition. The drive.file scope limits access strictly to files the user individually grants — the extension cannot access any Google Drive or Docs content beyond documents the user has explicitly selected.

Data retention and deletion

Account data and the content you submit are retained on the backend for as long as your account is active. You can request deletion of your account and associated data by contacting us at the address below. Signing out clears the session token from your browser; deactivating the WordPress plugin stops further syncing.

Security

All communication between the extension, the WordPress plugin, Google APIs, and the backend uses HTTPS. Machine-to-machine endpoints are protected with bearer tokens.

Contact

Questions or data-deletion requests: [email protected]