Your Financial Data

How we keep your financial data yours.

Our Approach

As with the data we collect from your plugin users, we limit the transactional information we can see in order to protect your data privacy.

Your transactions should remain your own, and for that reason, we've implemented End to End (E2E) encryption on the amount field of each transaction.

Definitions

We = PluginPulse

You = Bubble plugin developer using PluginPulse for analytics

User = Bubble application developer using the plugin developed by You

End user = The user of the Bubble application

How we encrypt your transaction data

It was important that while implementing encryption on the transaction amount that we ensured:

1. We would be unable to store, decrypt or otherwise read the value of the amount field directly from the database.

2. You can access PluginPulse and your data across devices without the need for you to manage the encryption key

To achieve this, our system uses a layered encryption model to keep your data secure. When you first sign up, a unique master key is generated in your browser. This key is used to encrypt all your data locally, ensuring that your information is protected before it even leaves your device. To make sure you can access your data on any device, we encrypt (or “wrap”) this master key using a secondary key derived from your password and a unique salt. The wrapped master key and salt are then safely stored in our database.

When you log in from any device, your password is used to recreate the secondary key, which unlocks the master key, allowing you to decrypt your data. This method not only maintains high security but also provides a seamless experience across devices.

To see what we see in our database, while logged in, take a look at the endpoint that fetches and returns your transactions in encrypted form.