How this LaunchShield server handles connected data

Data received from connected WordPress sites

After a WordPress administrator starts and approves a connection, the plugin sends the site URL and name; WordPress and PHP versions; active theme and plugin count; installed plugin and theme names, versions, and update availability; and the results of requested maintenance actions. The plugin does not send posts, comments, visitor data, or WordPress passwords.

Account and operational data

LaunchShield stores account email addresses and password hashes, project membership, site inventory, action requests, approvals, outcomes, and audit events. Session cookies are used for sign-in. The web server and HTTPS proxy may also log request metadata such as IP address, time, and requested path.

Purpose and access

The data supports software inventory, site management, approvals, and audit history. The server operator's administrators can access projects on this instance. Other users can access projects they own or to which they have been assigned. A connected WordPress site receives only supported inventory and update commands that are addressed to that site.

Storage and removal

Site-specific secrets are encrypted in the LaunchShield database. Disconnecting a site revokes its secret and cancels queued actions, but does not automatically erase inventory, action history, or audit records. The operator manages backups and retention. To ask for access to or removal of stored data, contact cadeta6@gmail.com.

Other integrations

If the operator configures other services, such as issue trackers, AI providers, or cloud platforms, LaunchShield exchanges data with them only for the connections and actions that an authorized user sets up. Jira account authorization grants read and write access to the selected Jira site and project; Google account authorization grants Gemini API access in the selected Cloud project. LaunchShield encrypts access and refresh tokens in its database and uses them to synchronize data or perform actions under its approval rules. The operator can remove a LaunchShield connection; users can also revoke access in their Atlassian or Google account. Ask the operator which integrations are enabled on this instance.

AI requests and usage records

When an authorized user submits a prompt, LaunchShield sends that prompt and any supplied system instruction to the selected AI provider. If an enabled provider is unavailable, an approved fallback provider may receive the same request. Administrators configure which providers and models each role may use. API keys are encrypted at rest and are never shown again after entry. LaunchShield records the user, provider, model, time, outcome, token counts, cache counts, estimated cost, and fallback events for budgets and audit. Personal prompt and response text is not stored in usage records. Project review jobs save their stage and final answer with the project so team members with AI and project access can inspect the result later; the job does not store the prompt packet. The operator manages review-job retention and backups. The operator's purge command removes AI usage records after 365 days; backups may retain them longer. Each provider handles submitted content under its own terms and privacy policy. Do not enter information that you are not authorized to share with the configured providers.