CloudCatch

Privacy policy

CloudCatch LLC (“CloudCatch”, “we”) builds WordPress plugins. This policy describes this website and those plugins. It is effective 30 September 2026.

This website

cloudcatch.io is a static site. We do not run accounts or comment forms on it. We use Google Analytics to count visits and see which pages are opened. Google sets a cookie in your browser and receives the page address, a client identifier, and approximate location, as described in the Google privacy policy.

Your browser requests pages from Cloudflare, which hosts the site. Cloudflare may process connection data such as IP address and the page requested, as described in the Cloudflare privacy policy.

Email you send to [email protected] is kept so we can reply.

WordPress plugins

Plugins run on the site where you install them. Content, orders, and settings stay in that site’s database. CloudCatch does not receive a copy of your visitors or customers unless a section below says a connector is used.

Zoom for WordPress

Zoom for WordPress lets a site administrator connect one Zoom user, list that user’s webinars and meetings, and register a WooCommerce customer for a webinar after checkout.

You can connect with your own Zoom app by defining the client id and secret in wp-config.php. Those credentials and the resulting tokens stay on your server. CloudCatch is not part of that connection.

If you do not define those constants, the plugin uses the connector at https://oauth.cloudcatch.io. That connector is a Cloudflare Worker with no database. When an administrator clicks the authorize button, the Worker checks that the return address is that site’s Zoom settings screen, sends the administrator to Zoom, and sends Zoom’s authorization code back to the site. The site then asks the Worker to exchange the code. The Worker adds the Zoom app’s client id and secret, receives tokens from Zoom, and returns them to the site. It does not store the authorization code, access token, or refresh token.

The plugin saves tokens in the WordPress option wp_zoom_oauth_tokens on your site. Disconnect deletes those tokens. When the connector is in use, disconnect also asks the Worker to revoke the token at Zoom. Deleting the plugin removes the tokens, the connected user id, settings, and any log files the plugin wrote.

The plugin sends registrant details from your WordPress site to Zoom, not to CloudCatch. Email, first name, and last name are always included. Street address, city, state, postal code, country, phone, and company are included only if an administrator turns those fields on. Zoom’s use of that information is described in the Zoom privacy statement.

API error logs are off unless an administrator enables them. Logs stay in uploads/wp-zoom-logs on your server and are deleted after 14 days. They do not include access tokens or registrant details.

Instagram plugins

If you use a CloudCatch plugin that connects to Instagram, the plugin requests only the access you approve. It is read-only: it does not publish, like, comment, or edit Instagram content. The Instagram user id, access token, and the posts you choose to display are stored on the WordPress site where the plugin is installed, for the period that site is configured to keep them. You can delete that data from the plugin settings or by uninstalling the plugin. CloudCatch does not collect that Instagram data onto its own servers. Meta’s policies are at the Facebook privacy policy and the Instagram privacy policy.

Changes

If this policy changes in a material way, the new version will replace this page. Continued use of a plugin after the effective date of a change means you accept the revised policy for that plugin.

Questions: [email protected].