Privacy Policy
Last updated: October 8, 2026
This Privacy Policy explains what information dibbed ("dibbed", "we", "us", "our") collects when you use our website and app (the "Service") to host a drop or call dibs on one, who can see it, why we collect it, and the choices you have. It describes what the Service actually does — if a section doesn't mention a feature, that's because we don't have it.
- Information We Collect
- Who Can See What
- How We Use Your Information
- Text Messages
- How We Share Information
- Hosts and Your Information
- Data Retention and Deletion
- Your Choices and Rights
- Data Security
- Children's Privacy
- Changes to This Policy
- Contact Us
1. Information We Collect
- Your name. The name you type when you call dibs, so the host knows who claimed a spot. Your browser may remember it on your device to save you retyping it next time.
- Your mobile number. When you call dibs, we verify your number with a one-time code sent by text. Verifying it lets us enforce per-person limits fairly and text you if your spot changes.
- Sign-in information. Your phone number becomes your dibbed sign-in. If you choose to connect Google or Apple, that provider shares your name, email address, and a unique account ID with us. We never see your Google or Apple password.
- Drops you host. The title, details (for example a time, place, price, or pay rate), number of spots, per-person limit, settings, the display name you host under, and — for public drops — the city you list it in.
- Your dibs. Which drops you claimed, your spot number or waitlist position, its status (confirmed, pending, waitlisted, released, or passed), and when those changes happened.
- Bot protection. Phone verification on the web uses Google reCAPTCHA, which collects hardware and software information (such as device and browser data) and sends it to Google to check that you're a person. Its use is governed by Google's Privacy Policy and Terms of Service.
- Technical information. Like any website, our hosting provider receives standard request information such as your IP address and browser type when you load a page. Sign-in keeps a session token on your device so you stay signed in.
We do not use advertising cookies, ad tracking, or third-party analytics in the Service.
2. Who Can See What
- Anyone with a drop's link can see the drop's title, details, host display name, how many spots are claimed, and the roster — each claimer's first name and last initial (for example "Sarah M.") next to their spot or waitlist position. Hosts choose whether a drop is shared by link only or also listed publicly.
- Public drops also appear in the Service's public listings for their city, so people without the link can find them. The same roster information is shown.
- The host of a drop can see the full name and mobile number of each person who calls dibs on that drop, so they can coordinate with them (for example a pickup time or a shift).
- Your mobile number is never shown publicly — only you and the hosts of drops you claim can see it.
3. How We Use Your Information
Your information is stored using Google Firebase and is used to:
- Verify your phone number and keep you signed in
- Run drops: assign spots in the order people tap, manage the waitlist, apply per-person limits, and move the next person up when a spot is released
- Text you about your dibs — for example when a spot opens up for you, when a host confirms or passes your claim — and tell hosts when a claim needs their review
- Show drops and rosters to the people described in "Who Can See What"
- Prevent abuse and keep the Service secure
- Comply with legal obligations
We do not sell your personal information, and we don't use it for advertising.
4. Text Messages
Verification codes are sent through Firebase Authentication (a Google service) when you enter your number to call dibs. Updates about your dibs — a spot opening up, a host confirming or passing your claim — are sent by our SMS provider. We only text you about drops you've claimed or host; we don't send marketing texts. Message frequency depends on your activity, and message and data rates may apply. Reply STOP to stop dibs update texts, or contact us.
5. How We Share Information
- With hosts, as described in "Who Can See What", for drops you call dibs on.
- With service providers who run parts of the Service for us and may only use the information to provide it: Google Firebase (hosting, database, sign-in, and server functions), Google reCAPTCHA (bot protection), our SMS provider (text delivery), and Google or Apple if you choose to sign in with them.
- For legal reasons, if we're required to by law or need to protect the rights, safety, or security of our users, the public, or the Service.
- If dibbed is sold or merged, information may transfer to the new owner, who must continue to protect it under this policy.
6. Hosts and Your Information
Hosts are individuals or organizations independent of dibbed — for example a school volunteer coordinator, a shift manager, or a home baker. When you call dibs, the host receives your name and mobile number. How a host uses that information outside of dibbed (for example contacting you about a pickup) is their responsibility; please only claim drops from hosts you're comfortable sharing your number with.
7. Data Retention and Deletion
- Drops, rosters, and claims are kept while the drop exists so hosts and claimers can see their history. You can release your spot or leave a waitlist at any time; your name is then removed from the public roster.
- You can ask us to delete your account and personal information by emailing support@dibbed.app from, or mentioning, the phone number or email you use with dibbed. We'll delete it within 30 days, except where we must keep something to comply with the law or resolve a dispute.
- Information a host already received about you (your name and number) may remain in their own records outside dibbed.
8. Your Choices and Rights
- Release your spot or leave a waitlist from the drop page at any time.
- Connecting Google or Apple is optional — you can always use your phone number.
- Reply STOP to dibs update texts to stop them.
- Ask us for a copy of your information, or to correct or delete it, by emailing support@dibbed.app.
Depending on where you live (for example California or the European Economic Area), you may have additional rights over your personal information, including the right to know what we hold, to have it deleted or corrected, and not to be discriminated against for exercising those rights. Email us to exercise them; we won't ask you to create an account to do so.
9. Data Security
Information is encrypted in transit (HTTPS) and stored with Google Firebase. Access is restricted by security rules so that, for example, mobile numbers can only be read by their owner and the drop's host, and changes to drops and claims can only be made by our server code. No system is perfectly secure, but we work to protect your information and will notify you as required by law if a breach affects it.
10. Children's Privacy
The Service is not directed to children under 13, and we don't knowingly collect personal information from them. If you believe a child under 13 has given us information, contact us and we'll delete it.
11. Changes to This Policy
We may update this policy as the Service changes. We'll update the "Last updated" date above, and for significant changes we'll give notice in the Service.
12. Contact Us
Questions or requests about this policy or your information: support@dibbed.app