Privacy & data · Dibs.software
The intended data boundary, and the surface this site does not provide.
A sign-up sheet has a narrow appetite by construction: it needs to know when a slot is open, who is entitled to claim it, and whether claiming it would break the one-winner rule. Most of what a school worries about handing to a vendor, a sheet never needs.
This page describes dibs.software and speaks for no other product. Every other product in the Stanley Studios family publishes its own policy on its own site.
Design scope, not a deployed Dibs record store
The intended scope of a claim record.
✓Times, and who may take them
The open times on a sheet, how many can take each one, and the claims against them: who claimed, for which slot, in which state (claimed, cancelled). That is the substance of the product — a sheet, and the rule about who may put a name on it.
✓The narrowest handle a claim needs
The design calls for the narrowest handle needed to evaluate a claim. Shared pure scheduling functions accept opaque references; this does not establish a Dibs identity-resolution procedure. No Dibs student-facing sheet or signed-token claim workflow is offered here.
✓A roster, only when a school turns one on
A consent-aware roster is a design boundary, not an available Dibs connection. The reviewed source does not prove a Dibs route that strips names and grades before returning a roster. This page does not provide a connection, invite a roster upload, or establish a new consent procedure.
What this product is not — said plainly
A sign-up sheet is not a roster you can browse, an ad network, or a camera.
✓No browsable list of who signed up
Dibs is designed to show open times and remaining capacity without a browsable participant list. No Dibs sheet is available here. A shared access decision is not proof of a Dibs signed-token workflow, field projection, or uniform missing-page response.
✓No advertising profile, and sheet data is not a product we sell
We do not build an advertising or behavioural profile from a claim, and we do not sell or rent sheet data. There is no ad on a sheet and no third-party analytics or advertising script on this site.
✓No photos, no face matching, no gallery
dibs.software schedules time. Every surface is a slot, a claim, or an open count — never an image. There is no face matching in a sign-up sheet because there is nothing in one to match, and no photo store because it holds no photographs.
✓No automated decision about a child
Nothing here scores, ranks, or profiles a child. Calling dibs is a person tapping a slot; the software only makes sure two people cannot tap the same one. No model is trained on who claims what.
Minors
Designed for consent-aware, access-controlled, non-public handling.
This is the existing school-related design boundary. No Dibs school sheet, roster connection, or subscription feed is offered here, and this page introduces no procedure for handling a child’s information.
The shared conference-booking route checks a recorded guardian relationship before recording a booking. The pure scheduling core requires caller-supplied access to pass. Those scoped facts do not establish a Dibs signed-token workflow, a uniform missing-page response, or a roster-stripping consent chokepoint.
The intended family wall and names-free feed remain described as designed. A product enquiry does not enable them. Source presence is not proof that a Dibs customer surface is deployed.
Money, messages, and automation — what is off
Three places a product like this usually overreaches. All three are off.
✓No live checkout, and no committed price
There is no checkout on this site and no card data reaches us here. dibs.software has no shipped product and no committed price; any fee inside a future product would be a computed, reserved line, and the payment seam exists but Stripe is not enabled.
✓Reminders are opt-in, and nothing is sent today
No reminder action is offered here. The separate conference reminder route returns a plan from supplied channel-purpose inputs; a queued-not-sent result does not prove delivery or a durable queue. This page does not provide an opt-in or withdrawal procedure.
✓No AI decides who gets a slot
Calling dibs is a person tapping a slot. No model is trained on who claims what, and no third-party service is called to decide anything. There is no AI claim on this product.
✓These pages set no cookie and run no client script
The page you are reading is a stateless server render. It sets no cookie, ships no client-side JavaScript, calls no third-party analytics or advertising endpoint, and builds no behavioral profile. Basic short-lived operational logs may record page requests.
Asking us about data
A person answers, and the answer is specific.
If you want to know what a sheet holds — or want something corrected or removed — write to [email protected] and say which sheet it concerns. Because dibs.software is pre-launch and serving no one, in most cases the honest answer is that no sheet holds your data yet.