Privacy

Playing without an account

You can create and join a table as a guest. In that case we store the display name you type, a hashed random token that identifies your seat to your browser, the card you played in each round, and the timing of that vote. We do not ask for your email and we cannot tell who you are.

If you create an account

• Your profile: name, email address, whether that email is verified, and the avatar URL your sign-in provider returns.
• Sign-in method: a hash of your password if you use email and password, or the provider account id and access tokens if you sign in with Google or GitHub. We never see your Google or GitHub password.
• Sessions: a session token, plus the IP address and browser user agent of the device that signed in, so you can review and revoke your own sessions.
• Teams and workspaces: team names, membership, and invitations you send or accept.
• What you type: story titles and backlog items you add to a table.

Estimation and timing data

For each round we record the card you chose, how long after the round opened you first committed, how many times you changed your mind, and whether your estimate was an outlier relative to the group. We also record coarse technical context such as whether the browser tab was hidden and a device category, which is how the table can tell “still thinking” apart from “walked away”.

Two product commitments constrain how that data is shown: your individual timing is visible only to you. Team-level views are aggregates and require a minimum sample size before they appear. And we never rank people — Fibitup will not label anyone the fastest or the slowest estimator, and builds no such leaderboard, because that turns an estimation tool into a surveillance tool.

Cookies

All our cookies are first-party and functional. There are no advertising or cross-site tracking cookies.

• pp_guest — a random token for your guest seat, so you keep your place if you reload.
• pp_fac_… — proves you are the facilitator of a table you created.
• pp_ws — which workspace you are currently viewing.
• pp_claimed — set for about two minutes after sign-in to show one confirmation message, then discarded.
• pp_anon — a random id with no personal data in it, used to count page views without identifying you.
• Session cookies prefixed pp — keep you signed in.

Other data we keep

We record product events such as “a table was created” or “a round was revealed” against the random pp_anon id rather than your identity. To stop abuse of the sign-in and join endpoints we also keep a short-lived counter keyed to the requesting IP address.

Who else processes your data

• Railway — hosting and the PostgreSQL database where everything above is stored, in the United States.
• Google and GitHub — only if you choose to sign in with them. We request the minimum scopes: your name, email address and profile. We ask for no access to your mail, files or calendar.
• Resend — sends transactional email such as password resets. It receives your email address and the contents of that message, nothing else.

Retention and deletion

You can delete your account at any time from your account page. Doing so removes your profile, sign-in methods and sessions. Rounds your team already estimated remain in your team’s history, but the seat is detached from you and stops being attributable to your identity — otherwise one person leaving would silently rewrite the team’s past sprints. Guest data has no identity attached to begin with.

To request a copy of your data, or deletion of something this page does not cover, email privacy@fibitup.com.

Children

Fibitup is a tool for software teams and is not directed at children under 13.

Changes

If we change what we collect or who processes it, we will update this page and move the effective date above. Questions go to privacy@fibitup.com.