GDPR Compliance Notice
This notice describes what Uptible receives and stores when a site uses the widget or an API client submits events.
Widget iframe, capture and track requests do not start an Uptible website session. For an account with live access, the application sets an uptible_widget_visit cookie on the Uptible origin. It holds a random, pseudonymous visit ID that can be linked to a capture and visit records. The ID helps deduplicate repeated events and hide a visitor's own sign-up. By default, it expires after two hours of inactivity. The deployment can change this period. Successful widget loads and collector requests that rely on the cookie renew its expiry. The current embed also keeps the ID in the parent page memory and reuses it when it replaces the iframe.
On HTTPS, the cookie is Secure, HttpOnly, SameSite=None and Partitioned where the browser supports partitioning. On HTTP, it is HttpOnly and uses the browser default same-site policy. Browsers may block or delete the cookie. Reloads and tabs can share a visit ID when the browser returns it. If the browser blocks or clears it, a reload can start a new visit.
When a page matches an active notification, the widget sends a visit even if there are no captures to show. With the current embed, replacing the iframe repeats the request without adding another visit record. If the browser blocks the cookie, an older cached embed can create a new visit on each replacement until the updated script loads.
The widget sends the host page address without its fragment. The application uses the hostname and path to match a notification. The address can include a query string. A sign-up request can also include the full page address, including its query and fragment. The collector ignores that field. The widget does not store these submitted addresses, the visitor's IP address or user agent in new capture or visit records.
A sign-up request sends an email address and may send a name. The visitor's IP address reaches the server with the request. While anonymization is on, new sign-ups are saved as Someone without the visitor's name. Sign-up notifications show Someone with a generic placeholder instead of a photo while anonymization is on. Processing receipts retain keyed digests derived from the email and name whether anonymization is on or off. With anonymization off, the application can save a shortened name. New sign-ups do not save email-derived photo identifiers.
Earlier sign-ups are hidden from visitors, not deleted. The account owner's leads API can still return their stored names and locations. Notifications never show a location. Turning anonymization off may show earlier stored names, but cannot recover names that were never saved. New sign-ups are saved without a location, and the capture path does not look one up.
Notifications use local initials or a generic placeholder. They do not request photos from Gravatar. Older stored photo identifiers are retained.
Authenticated API event requests use client-supplied session and event IDs and do not start a website session. The application stores client-supplied session IDs, so clients should use opaque IDs without personal information.
Uptible's own public and account pages use website sessions. Account sessions can contain the IP address, user agent and previous page URL. The URL can include a query string. Sessions on public pages can contain the same details. Session retention depends on deployment and cleanup. If an earlier widget version created session records, this change does not delete them.
Captures, visit records and processing receipts have no automatic expiry in the current application. Deleting a lead removes its capture but not its receipt or visit records. 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.
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.
Web servers, proxies and providers may retain request data in their own logs. Logs, backups and provider retention depend on deployment and require separate review. Deleting application records does not by itself remove those copies.
Contact: gdpr@uptible.com
Last updated: Wed, 18 Nov 2026 18:40:21 +0000.