Privacy policy

 
 

At Lickstats, we value our users’ and our users’ users’ privacy above our own interests.

We feel a strong responsibility to safeguard privacy at all costs even if it means discarding potential revenue streams.

We are proud supporters of the EU’s General Data Protection Regulation (GDPR).

We believe GDPR’s unprecedented legally-enforceable level of privacy and transparency requirements was long overdue.

As a company, we use third party analytics and customer support software to market and operate our business.

As an analytics service provider, we gather and store data that allows us to offer the services our users love.

Unless stated otherwise bellow, data is not (and will never be) shared with third parties without consent.

Before jumping into specifics, let’s define a few terms that will be referred to bellow.

Platform: lickstats.com, app.lickstats.com or any other Lickstats-owned website or software (such as our Chrome extension)

Users: people who have signed up to Lickstats, are logged-in and are using our platform

Our users’ users: people who are exposed to the services of Lickstats following the actions of our users (generally speaking, people who click on Lickstats campaign links)

Leads: non-users (or logged out users) who visit our platform

 

Bellow, you will uncover what data we gather, store and/OR share with third parties.


Users

We use third party analytics and customer support software to better understand how our users interact with our platform.

We use Google Tag Manager to manage the implementation of third party analytics and customer support software.

We use Google Analytics to gather anonymous data such as (but not limited to) the approximate geolocation of our users and how they interact with our platform. We anonymise IPs before they are sent to Google Analytics and have not enabled Display Features to limit how much data is shared with Google Analytics.

We use Intercom to offer convenient chat-based customer support. In order to offer this service to our users, we share limited personal data and very limited usage data with Intercom.

We use Inspectlet to record sessions from time to time to conduct quality assurance testing of our user interface and user experience design. We anonymise IPs before they are sent to Inspectlet and censor all input fields on all pages.

We use Sentry to track bugs. To this extent, we share IPs, user agents and Lickstats user IDs with Sentry.

We use YouTube to embed videos on our platform.

We use Stripe to process credit card payments. To this extent, we share email, credit card and payment history data with Stripe.

We use Squarespace to host lickstats.com. Although we do not currently use the analytics tools provided by this third party, anonymous data is gathered.

We use MailChimp and SendGrid to communicate with our users by email. To this extent, we share emails with these third parties.

We use a very limited implementation of Facebook, Twitter and YouTube sharing features to provide our users with ways to help us through word of mouth.

We use DigitalOcean to host the servers that run Lickstats.

We store the IPs of all requests made to our servers to monitor our infrastructure and mitigate abuse.

We store Lickstats user IDs, bearers (it’s like a password but safer) and, on rare occasions such as signups and password resets, emails using cookies. These cookies are solely used to allow our users to log in and remained logged in to our platform.

For more information on how the above third parties handle privacy, please have a look at their respective privacy policies.

Our users’ users

We offer analytics services to our users.

We store the IPs and user agents of people who click on Lickstats campaign links. The IPs are solely used to geolocate clicks, monitor our infrastructure and mitigate abuse. Please note that they are not accessible by our users.

We store a cookie per click to track unique vs total clicks.

Leads

We use third party analytics and customer support software to better understand how our leads interact with our platform.

We use Google Tag Manager to manage the implementation of third party analytics and customer support software.

We use Google Analytics to gather anonymous data such as (but not limited to) the approximate geolocation of our leads and how they interact with our platform. We anonymise IPs before they are sent to Google Analytics and have not enabled Display Features to limit how much data is shared with Google Analytics.

We use Intercom to offer convenient chat-based customer support. Our leads remain anonymous unless they provide personal data such as an email to be contacted later.

We use Inspectlet to record sessions from time to time to conduct quality assurance testing of our user interface and user experience design. We anonymise IPs before they are sent to Inspectlet and censor all input fields on all pages.

We use YouTube to embed videos on our platform.

We use Squarespace to host lickstats.com. Although we do not currently use the analytics tools provided by this third party, anonymous data is gathered.

We use MailChimp to communicate with leads who have subscribed to our newsletter. To this extent, we share emails with MailChimp.

For more information on how the above third parties handle privacy, please have a look at their respective privacy policies.


Notes

Safegarding privacy at all costs

A while back, we prototyped a new enterprise feature that allowed our users to personally identify people on Google Analytics. Even though this feature showed great potential, we decided to drop it as it did not comply with our privacy standards. That’s how serious we are about privacy.

Very limited implementation of Facebook, Twitter and YouTube sharing features

Facebook, Twitter and YouTube earn a living by gathering as much data about people as possible. By default, implementing sharing features gives these third parties access to a lot more than you would expect. Therefore, we only enable these features when necessary (when a user wishes to use them) and do so using scope isolation to prevent third parties from accessing our users' data.