Data Tracking Guide

Our Approach

At PluginPulse, we care deeply about privacy, transparency, and security—just like you do. When you use a plugin that includes PluginPulse analytics, we collect some basic data about your app to help the developer understand how their plugin is being used, and ultimately, build better plugins. That’s a responsibility we take seriously. Here's how we collect, store, and protect that data.

Key Terms

• PluginPulse = Us
• Plugin Developer = The developer of the plugin that includes PluginPulse
• You = Bubble application developer using a plugin that includes PluginPulse
• End User = The users of your application

How your application's data is tracked

When a plugin you’ve installed includes PluginPulse, it adds a small script to your app. This script runs in the background and does the following:

• Reads the app’s ID and the plugin version from the browser.
• Immediately hashes and truncates the app ID to 12 characters before it leaves the browser. This means:
  • We can’t see or recover your original app ID.
  • The plugin developer also doesn’t know which specific Bubble app is using their plugin.

To go even further, we hash the hashed ID again on our server using a secret salt. This extra step ensures that even if someone tried to reverse-engineer the data (which would already take centuries), they’d still hit a dead end.

Additionally, all of this is only done in the testing version of your Bubble application (/version-test/), so your end users are never tracked by PluginPulse.

In Short:

• We never store your original app ID.
• What we store can't be linked back to you or your application.
• You stay anonymous and your privacy is respected.
• Your end users are never tracked by PluginPulse.

This setup is fully compliant with GDPR—and it's designed to work without requiring any permissions or manual configuration.