First thing first - we never have and never will sell any user information we collect to any third party company, period. The only exception is a scenario where we are bought out by a third party company that necessitates transfer of data to the new operator.
Moving on to the fine details: Webpushr processes two broad categories of personal information when you use our software platform:
- Your personal information as a developer customer of Webpushr - information that we refer to as Account Data, and
- The personal information of your end users’ who use or interact with the push notifications you have built using Webpushr - this contains both your Customer Usage Data (e.g. interactions w/ push optin prompts, interaction with push messages, page visits, custom event information) and your Customer Content (e.g., location, device information, browser information, IP address.).
Webpushr uses & processes these categories of personal information differently because the direct relationship we have with you, our developer customer, is different than the indirect relationship we have with your end users.
Now, we will go through each of the above and explain how we use and process this information:
Your, our customer, information
We use your information primarily for authentication. What this means is that once you sign up with us, we use your e-mail address and password to enable you to subsequently sign into our platform to use our services. We sometimes also use your information to proactively reach out to you in case of technical issues. Our account teams and account representatives might also use your information to contact you about new features or pricing information.
Your end user information
We primarily collect and use your end user information within the well-defined realm of standard web push notification enablement so that you can update your customers via web push notifications. That is what our platform is about and the guiding principle for our data collection policies. We use your end user information so you can use various features we offer as part of our software platform. These features include but are not limited to dashboards, user segmentation, custom events, conversion tracking, automatic push notifications, manual push notifications etc. We, sometimes, do internally use your end user information at an aggregated meta level to improve our products or services.
Below is a detailed breakdown of 1- all user data that is stored by Webpushr on your behalf on its servers, and 2- Data that is stored by Webpushr in your visitors' web browsers (Cookies, etc.):
User Data that is stored on our Servers
We only store user data on our servers for visitors that have actively subscribed to receive push notifications. We do not store any data or information related to your site visitors that are not subscribed to push notifications. Following data points are stored by us on your behalf for all subscribers (users that have actively opted to receive push notifications):
date |
This is the date when the subscribers opts to receive push notifications from your site. |
endpoint |
The endpoint takes the form of a custom Endpoint (The endpoint is the push services URL.) and associated encrypted keys (web-only auth & web-only p256) pointing to a push server. This is collectively called PushSubscription object. |
timezone |
Subscriber's local timezone. |
device_type |
Mobile or Desktop. |
operating_system |
Mac OS, Windows, Android, etc. |
browser |
Chrome, Firefox, Opera, Edge, etc. |
ip_address |
Subscriber's IP Address. You can configure storage setting in Webpushr Dashboard. |
city |
Geographic Location: City |
state |
Geographic Location: State |
country |
Geographic Location: Country |
session_date |
Date corresponding to the last session |
Data that is stored in the Browser (Cookies, Local Storage, etc.)
Webpushr JavaScript snippet use HTTP Cookies & local browser based Storage environment to "remember" what a user has done on previous pages / interactions with the website. These data points are primarily used to control the opt-in prompt behavior on the site, based on user specifications.
_webpushrPageViews |
We only store this cookie if you set the prompt to show after x page visits. It is not set if prompt type is set to Native |
_webpushrSubscriberID |
We set this for non-https sites only, to check if the user is subscribed or not |
_webpushrPromptAction |
This cookie is stored if the user declines to receive push notifications and dismiss the custom prompt. This helps us remember that decision. |
_webpushrEndPoint |
This cookie stores a unique URL associated with the user's push subscription. It is only stored if the user accepts to receive push notifications. |
_webpushrLastVisit |
This cookie stores timestamp associated with the user's last visit on the site. It is only stored if the user accepts to receive push notifications. This helps us successfully manage and send push notifications. |
_webpushrbellnotification |
This cookie is only stored when a user takes an action on the subscription bell feature (this bell is only shown to users who have opted in to receive push notifications). The value of this cookie tells our SDK if the user has turned notifications ON or OFF using the subscription bell. Our SDK then uses the value to show the correct status of the subscriber on the subscription bell. |
_webpushrSessionLog |
This cookie is used to enable/show the entire opt-in funnel (unique user sessions, prompt impressions, user actions on custom and native prompt, etc.) at the site level in Webpushr Dasboard. |
Frequently asked questions
Can Webpushr determine the end-user identity with the location and all other data that is stored?
All data stored by Webpushr on your behalf is listed on this page. Webpushr is not able to determine end-user identity with the current data it stores. The only exception is if Custom Attributes feature is used by you to enhance customer data with personally identifiable information such as full name, address, etc.
Will I lose any Webpushr functionality if I turn IP address storage off?
You can configure whether or not Webpushr stores subscriber IP address here. You will not lose any functionality if you decide to turn this off.
What happens if a subscriber unsubscribes from receiving push notifications. What happens to such user's data? Does the website owner have to delete all the subscriber data manually/API?
You, as the website owner, do not have to perform any manual action to delete subscriber data when a user unsubscribes from receiving push notifications. Webpushr automatically deletes all subscriber data from it's servers when a user unsubscribes
How long do you store subscriber data?
We store subscriber data indefinitely unless two conditions are met: 1- You, the site owner, deletes the site from our platform. 2- The subscriber unsubscribes from receiving push notifications.
How can I be GDRP compliant while using Webpushr?
In order to comply with GDPR or other regulations, please plan to appropriately disclose all information, that is listed on this page that Webpushr will store on your behalf, to your site visitors. Most of our EU based customers append existing disclosures with information listed on this page. You must also turn IP storage setting to OFF to be GDRP compliant.
Hopefully, with the above disclosures, we have been able to demonstrate our committment to data privacy. Your trust is the most important thing to us and, it is also the guiding principle for all our design and execution activities.