Privacy Policy
Read our GDPR notice for details about visitor data. By continuing to use our service you acknowledge the content and terms of this notice.
We do not send non-critical, non-service related or marketing communications to users who have not explicitly agreed to them.
This privacy policy has been compiled to better serve those who are concerned with how their 'Personally Identifiable Information' (PII) is being used online. PII, as described in US privacy law and information security, is information that can be used on its own or with other information to identify, contact, or locate a single person, or to identify an individual in context. Please read our privacy policy carefully to get a clear understanding of how we collect, use, protect or otherwise handle your Personally Identifiable Information in accordance with our website.
Tell visitors when you install Uptible on your site and explain how their data is used. A sign-up request can contain an email address, a name and the page address. The visitor's IP address reaches the server with the request. The widget uses the page hostname and path to match a notification. The submitted address is not stored in new capture or visit records. Web servers and providers can retain request data separately.
With notification anonymization on, new sign-ups are saved as Someone without the visitor's name. New sign-ups do not save email-derived photo identifiers. Receipts still retain keyed digests derived from the email and name. Earlier names are hidden from visitors, not deleted, and can reappear if anonymization is turned off. Names never saved cannot be recovered. Notifications do not show locations or request photos from Gravatar. The owner's leads API can return earlier stored names and locations, and older photo identifiers are retained. See the GDPR notice for details.
Your use of the service is at your discretion. This policy covers data you send through your account and data sent by sites under your control.
What personal information do we collect from the people that visit our blog, website or app?
When you register, we ask for your name and email address. When you purchase access, Lemon Squeezy collects payment and billing details on its checkout page.
When do we collect information?
We collect information when you register, purchase access or enter information on our site. The widget and API can also receive visitor events from your site.
How do we use your information?
We use account information to provide the service, manage access and purchases, respond to requests and send service-related email. Visitor events support notifications and reporting for the site owner. Reloads and tabs can share a visit ID when the browser returns the cookie. If the browser blocks or clears it, they can count separately.
Authenticated API event requests use client-supplied IDs and do not start a website session. The application stores client-supplied session IDs, so use opaque IDs without personal information.
How do we protect your information?
Account authentication and form protection control access to account features. Deployment security, operational logs and backups require separate review.
Lemon Squeezy processes payment card details. Uptible stores payment references and status information to manage access and refunds.
Do we use 'cookies'?
The account website uses session cookies to keep you signed in and protect forms. Its public pages also use website sessions. A database session can contain the IP address, user agent and previous page URL, including its query string.
The widget sets an uptible_widget_visit cookie containing a random, pseudonymous visit ID that can be linked to a sign-up. It helps deduplicate repeated events and hide a visitor's own sign-up. The cookie expires after two hours of inactivity by default. The deployment can change this period. Widget iframe, capture and track requests do not start a website session. The current embed also keeps the ID in the parent page memory for iframe replacement. Browsers may block or delete the cookie. See the GDPR notice for cookie settings and the data retained with events.
You can control cookies in your browser settings. Disabling website session cookies can prevent sign-in and form submissions.
Third-party disclosure
Lemon Squeezy processes payment and billing information when a customer purchases access. Uptible sends it a checkout reference and receives order and refund information to manage access. Stripe was our previous billing provider. Uptible no longer sends billing requests to Stripe or processes its webhooks. Historical billing identifiers and records are retained for reconciliation. Removing this integration does not erase records held by Stripe. A configured mail provider receives the recipient address and message needed to deliver account and transactional email. If Google sign-in is selected, Google receives the information needed for authentication. These services concern the customer's account; they are not used to discover profiles of visitors to the customer's website.
When a production Sentry DSN is configured, Sentry receives error diagnostics and may receive sampled timings. HTTP request details in these diagnostics omit bodies, cookies, headers and query strings. Other diagnostic text and provider retention require review.
Capture and visit data are processed in Uptible's configured database. Captures, visit records and processing receipts have no automatic expiry in the current application. Deleting a lead removes its capture but not its receipt, visit records or backups. Deleting a notification removes its captures, receipts and presence records but retains visit records. Archiving a notification and cancelling an account are soft deletions, not purges. Cached data, website sessions, logs and backups may also remain. Web server, proxy, provider and backup retention depends on deployment.
Notifications use local initials or a generic placeholder. Uptible does not use the removed FullContact, Clearbit or Picasa integrations to discover visitor profiles.
Third-party services
Payment, mail, sign-in, hosting, and error-reporting services can involve third parties. Their use depends on the feature and deployment configuration.
California Online Privacy Protection Act
CalOPPA is the first state law in the nation to require commercial websites and online services to post a privacy policy. The law's reach stretches well beyond California to require any person or company in the United States (and conceivably the world) that operates websites collecting Personally Identifiable Information from California consumers to post a conspicuous privacy policy on its website stating exactly the information being collected and those individuals or companies with whom it is being shared. - See more at: http://consumercal.org/california-online-privacy-protection-act-caloppa/#sthash.0FdRbT51.dpuf
According to CalOPPA, we agree to the following:
You can browse our public pages without an account. Those pages use website sessions as described above.
Our home page links to this privacy policy.
Our Privacy Policy link includes the word 'Privacy' and can easily be found on the page specified above.
You will be notified of any Privacy Policy changes:
• On our Privacy Policy Page
Can change your personal information:
• By emailing us
• By logging in to your account
Third-party behavioral tracking
The Facebook Pixel, Google Ads and Analytics, and FullStory integrations have been removed from the application views. Other service providers may receive request information when their features are used, as described above.
COPPA (Children Online Privacy Protection Act)
When it comes to the collection of personal information from children under the age of 13 years old, the Children's Online Privacy Protection Act (COPPA) puts parents in control. The Federal Trade Commission, United States' consumer protection agency, enforces the COPPA Rule, which spells out what operators of websites and online services must do to protect children's privacy and safety online.
We do not specifically market to children under the age of 13 years old.
Fair Information Practices
The Fair Information Practices Principles form the backbone of privacy law in the United States and the concepts they include have played a significant role in the development of data protection laws around the globe. Understanding the Fair Information Practice Principles and how they should be implemented is critical to comply with the various privacy laws that protect personal information.
In order to be in line with Fair Information Practices we will take the following responsive action, should a data breach occur:
We will notify you via email
• Within 7 business days
We also agree to the Individual Redress Principle which requires that individuals have the right to legally pursue enforceable rights against data collectors and processors who fail to adhere to the law. This principle requires not only that individuals have enforceable rights against data users, but also that individuals have recourse to courts or government agencies to investigate and/or prosecute non-compliance by data processors.