Data retention

How Mugpipe Signals handles and retains each kind of data.

Last updated: November 13, 2026. This page describes how the service is currently built. It should be read together with the privacy policy and the terms of use. It describes current practice and is not a contractual commitment.

Data used to answer a request

• Search Console and Analytics report data. Report data is fetched from Google when an AI app calls a tool and is returned to that app. We do not persist report data on our servers.
• Google access tokens. A short-lived Google access token is obtained from the stored refresh token for each request. We do not persist Google access tokens on our servers.
• Tool arguments. The dates, filters, and breakdowns an AI app sends are used to run that request. We do not persist them on our servers.

Data with a set expiry

• Public PageSpeed Insights and Chrome UX Report results for a public URL may be cached by our hosting provider for up to 12 hours. These cache entries are keyed by URL, not by account, and do not include Search Console or Analytics data.
• AI app access tokens expire after 1 hour, and AI app refresh tokens expire after 30 days. Tokens are stored as a hash, not in raw form. Expired grant records may remain in storage until they are cleaned up.
• Browser sign-in session: a cookie that expires after 14 days.
• Google connect link: a signed link that expires after 10 minutes.

Data kept while the account exists

The following records do not currently expire automatically. They are generally kept while the account exists, or until a deletion request is handled.

• Account: account id, email address, Google account id, and creation date.
• Google connection: the Google refresh token, stored encrypted, and the granted scopes. Removing Mugpipe in your Google Account permissions stops further access to Google data; the encrypted record may remain until it is deleted or replaced.
• Saved choices: the Search Console site and GA4 property you selected.
• Usage and audit records: usage counters, and records of each tool call (tool name, time, outcome, units, and the AI app's host). These records do not include tool arguments or Google report data.
• Trial and subscription records: trial and subscription status and the related identifiers from our payment provider.

Payments

Payments are processed by Polar, which acts as merchant of record. Card details are entered with Polar; Mugpipe does not receive or store full card numbers. Polar retains its own records under its own policies and legal obligations.

Logs and backups

Logging practices for each product are described on that product's privacy page. Mugpipe Signals keeps error and operational records in Cloudflare Workers Logs for up to 7 days. Those records do not include access tokens, refresh tokens, email addresses, or Google Search Console or Analytics report data. Our hosting and infrastructure providers, including Cloudflare, may also keep operational, security, and backup data under their own policies. Database recovery history may retain deleted records for a limited period, typically up to 30 days, after which it is overwritten.

Deletion requests

You can ask us to delete your account data by emailing privacy@mugpipe.com from the email address on the account. We handle verified requests within a reasonable time. Deletion is subject to our legal obligations, the rights of third parties, and technical limitations such as backups and provider-held copies. If you have an active subscription, cancel it with Polar first.

To stop Signals from accessing your Google data at any time, remove Mugpipe in your Google Account under Security, then Third-party apps and services.

Mugpipe Forecast

This section describes Mugpipe Forecast. It should be read with the Mugpipe Forecast privacy policy and the Mugpipe Forecast terms. It describes current or intended practice and is not a contractual commitment. It does not set a retention period, an availability target, or a support deadline.

• Account data. Account, sign-in, authorization, usage, and billing records for Mugpipe Forecast are deleted when a verified account-deletion request is completed, unless the law requires a longer period.
• Shared research records. Forecasts, outcomes, sources, and algorithm records in the shared research store may remain after the account is deleted. Those records are unlinked from the account. The license for contributions already in that store survives account deletion.
• Identifying data. The shared research store is designed not to store identifying information. If personal data is submitted to that store in error, Mugpipe may remove or redact it when it becomes aware of it.

Mugpipe for WordPress

This section describes Mugpipe for WordPress only. It describes current practice and is not a contractual commitment. It does not set a retention period, an availability target, or a support deadline. It is subject to applicable law. It should be read with the Mugpipe for WordPress privacy policy.

• Application password. The application password is encrypted and stored for the connected site. It is deleted when you disconnect the site, or when a verified deletion request is completed. Disconnect also attempts to revoke the application password on the WordPress site.
• Connection record. The site address, the WordPress user id, the username, and the role summary are kept until disconnect or a verified deletion request.
• Posts and pages. Post and page bodies are not stored in Mugpipe's database. A capped plain-text result may be returned to the AI application you use.
• Action log. An action log may store the tool, an action slug, and an outcome. It does not store post bodies or application passwords. It is kept until a verified deletion request.
• Logs and backups. Error and operational logs are kept for up to 7 days. They do not include application passwords or post bodies. This application does not delete a backup held by a provider. A backup, if one is kept, may retain deleted records for a limited period, typically up to 30 days, after which it is overwritten.

Changes

We may update this page at any time. The date at the top shows the latest version.