Draft, for lawyer review. This page is a placeholder and will change before launch.
Privacy policy
Updated November 17, 2026.
The full privacy policy is not written yet; it will be published here and reviewed before Scorepebble launches. The people your team surveys are your customers: you control their data, and you can export or delete it at any time, per person or for the whole team. See the data-processing page.
Waitlist
- What we keep: if you join the waitlist, we keep your email address, when you joined, when we last emailed you a confirmation link and when you confirmed. Nothing else: no name, no IP address and no browser details are stored with it (to stop floods, sign-ups are counted per IP address for an hour; see Security limits). The confirmation code is stored only as a hash.
- What we send: one email to confirm the address (a fresh one at most once a day if you ask again), and once you have confirmed, one email when Scorepebble opens. Confirmation emails are sent through Postmark, our email provider, which keeps its own copy of each email it sends (your address and the email's text) for 45 days (Postmark's standard retention; we don't buy longer retention), then deletes it; that copy is not covered by the deletion times below.
- How long: an address that isn't confirmed within 7 days of its last confirmation email is deleted; an address we haven't been able to email yet is deleted after 90 days; a confirmed address is kept until you remove it or we close the waitlist, when we delete the whole list. A daily job deletes expired addresses, unless that job fails, which alerts us so we can run it again.
- Leaving: open the link in the confirmation email and press "Remove my address", or write to support@scorepebble.com.
How you found us
- How you found us: We record how a team first found us (for example, a "Powered by" link on a survey, our Notion template or an app directory) and keep daily counts of visits, badge views and team invites with no personal data. The link carries this, not a cookie.
- Which team's link: A "Powered by" link carries a random code for the team whose survey showed it. If you sign up from that link, we record which team's link it was, so we can count how many new teams each customer brings us. We don't tell that team who you are.
Security limits
- Sign-in attempts: to slow down password guessing, recent attempts to sign in, sign up, reset a password, confirm an email address or enter a two-factor code are counted per IP address, per email address or per account, with the time of each attempt. Failed sign-ins are counted per IP address, and per email address together with the IP address it was typed from (IPv6 addresses by their /64 network), so a few wrong passwords that someone else types for your email address from a different IP address or network don't stop you signing in. Each email address also has a loose cap, from any IP address: after 50 failed sign-ins in one clock hour (UTC), signing in, or confirming your password while signed in, with that address pauses until the hour ends or its password is reset (this count holds a number for the hour, not the times). In these counts, addresses are stored only as keyed hashes (HMAC-SHA-256), never in clear. A daily job soon after midnight UTC deletes these counts once they expire, so each is kept for at most 25 hours, unless that job fails, which alerts us so we can run it again. Each failed sign-in is also written to the app's own log with a keyed hash of its IP address (not the address itself); our web server's log keeps the sign-in request with its IP address (see Server logs below).
- Survey answers, the widget and the waitlist: to stop floods, answers, widget requests and waitlist sign-ups are counted per IP address (IPv6 addresses by their /64 network) for a minute, an hour or a UTC day. Addresses are stored only as keyed hashes (HMAC-SHA-256), never in clear, and the same daily job deletes each count after its minute, hour or day ends, so each is kept for at most 25 hours, unless that job fails (as above).
- Server logs: our web server logs each request, sign-in requests included, with its IP address and port, time, method, site name and page requested, the connection's protocol and encryption version, and the response code, size and time taken (no request headers, so no cookies, browser user agent, language or referring page), so a failed sign-in is in it with its IP address. The app's own log records each failed sign-in with only its time and a keyed hash of its IP address (IPv6 addresses by their /64 network), never the IP address itself or the email address. Logs are kept in a few files of limited size: the oldest file is deleted when a new one is started, so an entry is kept until its file is rotated out, which takes longer when the service is quiet.
Questions: support@scorepebble.com