← Sandstub
DocumentationPrivacyTermsSupport

Sandstub privacy policy

Last updated: October 5, 2026

Sandstub: Countdown Timers & Urgency ("Sandstub") is an app for Wix sites made by Great Work LLC, 651 N Broad St Suite 206, Middletown, DE 19709, USA ("we"). This policy explains what Sandstub reads, what it keeps about site owners and their visitors, and for how long. Questions: hello@greatwork.company.

What Sandstub reads from your site

Through Wix's API, and only to run your timers: your plan status, your site's name, address and time zone, your Wix automatic discounts and coupons (name, code, start and end dates, whether they're active) for sale timers, your Wix Stores product names for choosing which products show a timer, and the stock count of a product a visitor is looking at when a stock line is switched on. Sandstub never reads your orders, customers, contacts, payments or site members.

What Sandstub keeps about your site

  • Your install: the Wix app instance id, site name and address, plan status, which Wix Stores catalog you use, and a random site key that names your public timer file.
  • Your timers and settings: messages, dates, design, places, store time zone and holidays. A copy of what visitors' browsers need (never timer names or results) is published as a public file so pages can show the timers.
  • Results: per day, per timer and message, how many visitors saw it, clicked its button, or added to cart. Counts only. Kept 90 days (Standard), 1 year (Pro) or 2 years (Scale).
  • This month's count of visitor checks.
  • Sessions: a random token for your dashboard, deleted after 12 hours.

What Sandstub keeps about your visitors

Nothing is stored on visitors' devices: Sandstub sets no cookies and uses no browser storage.

  • Per-visitor (evergreen) countdowns: when a visitor first sees one, our server stores a keyed hash (HMAC-SHA256 with a secret key) of the visitor's network address and browser name, plus when their countdown started and ends. The IP address itself and the browser string are never stored. The record is deleted when the timer's cool-down ends (7 to 365 days after the countdown ends, set by the site owner). This is how a visitor keeps one countdown instead of getting a new one on every visit.
  • A/B messages: which message a visitor sees comes from the same hash; nothing extra is stored.
  • Counts: views, clicks and add to cart are sent only when the visitor has allowed analytics cookies in the site's cookie banner. To count each visitor once a day, we store a hash salted with that day, deleted after 2 days.
  • Our server sees visitors' IP addresses and browser names on each request (like any website) to compute those hashes and to limit abuse. They are not written to logs for these requests.

The site owner is the controller of their visitors' data; Great Work processes it on their behalf only to show and measure their timers.

How it's used

Only to run Sandstub for your site. We don't sell, share or analyze your data or your visitors' data, don't build profiles, and don't use any of it to train anything.

Where it's stored

On Great Work's server in New York, USA (DigitalOcean). Access is limited to Great Work staff for support and maintenance. Connections use HTTPS.

Deletion

  • Settings > "Delete results and visitor countdowns now" deletes counts and every per-visitor record right away.
  • When your plan ends, timers disappear from your site at once; results and visitor records are deleted 30 days later.
  • When you remove Sandstub from your site, everything we keep about the site is deleted 30 days later (in case you reinstall), and the public timer file is emptied at once.
  • Settings > "Download what Sandstub keeps about this site" gives you a copy at any time.

Your rights

You can ask for access to, correction of or deletion of your data at hello@greatwork.company. We verify the request comes from the site owner and answer within 30 days (deletions within a week). Visitors can ask the site owner, or us; since we store only keyed hashes, we delete by site or by timer. If you're in the EU or UK, you can also complain to your data protection authority.

Processors

Wix (your site, billing and the API Sandstub uses) and DigitalOcean (hosting). No others.

Changes

We'll post changes here with a new date. Material changes are announced in the app.