FeedbackBulb Data Policy
Here’s a closer look at our data policy, the information that we do collect, what we use it for and steps we’ve taken to comply with the cookie law and the privacy regulations such as the GDPR, CCPA and PECR.
A developer is an organization or a person offering a digital service (an app, website, software platform or component) including one of the FeedbackBulb client libraries or integrations. Developers are responsible for the data they submit to our services.
A developer can choose to implement their own mechanism for submitting data to the FeedbackBulb Services. In such cases, they continue to be responsible for the data they submit to our services.
The FeedbackBulb Client library (or feedback widget) is the component that transmits data to the FeedbackBulb Services. All FeedbackBulb Client libraries are open source and available freely for anyone to examine, download and modify.
A user is an organization or a person using a digital service created by a developer.
A feedback is one instance of data sent by a user to the FeedbackBulb Server using either a FeedbackBulb Client library or a custom implementation by a developer.
The FeedbackBulb Portal is the web app that developers use to setup, monitor and download feedback data. Developers have access to any content submitted by the user. Developers may reply to feedback using the FeedbackBulb Portal.
We do not track people across their devices and across websites and apps that they visit. All feedback reports are stored separately per application. We do not know or check if the same person has submitted feedback from multiple applications or devices. The purpose of FeedbackBulb is to facilitate the exchange of feedback between users and developers. We do not track individual visitors. We don’t use tracking cookies, and we don’t generate any persistent identifiers.
Our feedback widgets can be configured by a developer to request that the user input their email address. In such cases the email address will be stored by FeedbackBulb. Collecting the user’s email is optional and not necessary for the operation of the FeedbackBulb services. It is a developer’s responsibility to obtain consent from a user in order to ask for their email address to be stored. Email addresses are encrypted and stored securely both in transit and at rest.
When feedback is submitted to FeedbackBulb using one of the FeedbackBulb client libraries, it consists of the following:
The user-created message content of the feedback report in plain text, including any attachments.
The current URL or name and version of the FeedbackBulb client library in which the report is submitted.
A developer can include any metadata they wish with feedback reports sent using FeedbackBulb client library. They are urged to not send any data that might identify their users. They must include the types of data they send in their privacy policies. Developers are responsible for disclosing and obtaining consent from their users for the collection of additional metadata.
We strongly encourage developers to limit metadata to what's necesasry for the operation of their services.
Feedback data is retained only as long as required to provide the services of this website. Once a developer deletes a feedback, all metadata related to the deleted feedback is scheduled for immediate deletion. Our back-up systems may retain a copy of each feedback report for up to 3 months.