Privacy Policy
Last updated: November 2026
In short
Dinkbound is operated by Neldra Technologies LLC. You can use Dinkbound without an account, and we keep very little. We show no advertising and we do not sell personal information. If you organize, join or wait for a session, other signed-in users see your first name, the first letter of your last name and your skill level on it, and the other people in that session see what you write in its chat. If you tell us your gender, you are counted in the gender mix of the sessions you organize or join, which signed-in users see.
If you only browse
Your location, if you allow it, or the town or ZIP you type, is used to work out how far each event is from you. It is kept in a cookie in your browser (njp_loc), sent with your requests so distances can be calculated, and not stored in any account or database of ours. When you type a place, the letters you type are sent to Google, through our server, to find it; Google receives those letters and not your address.
Your filters are kept in a cookie in your browser (njp_filters), with no account: every filter is yours to change any time, and an account makes them follow you to every device. A further cookie (njp_kept) only records the day our server last renewed the others. One further cookie (njp_internal) is set only on the devices of the people who run Dinkbound, so their own visits are left out of these records. When you continue with Google on a phone, Google sends your sign-in token to our server, which passes it to your browser in a cookie (njp_gsi) that lasts one minute and is read once; our server does not keep it.
We record which pages are viewed and which actions are used (for example, that a filter was changed or an event was opened) through an analytics service, along with the address of the site that linked you here, if any. Those records carry no name, email address or location. To tell one visitor from another, a random identifier is kept in a cookie in your browser (njp_visitor) and in its local storage; it is not linked to anything that identifies you, and it is replaced with a new one when you log out. To tell automated visits from people, each visit also notes a few plain facts about the browser it came from: its screen size and time zone, whether it draws graphics in software, and whether it connects from a hosting provider's network.
For a visit that lasts more than ten seconds we also keep a recording of how the site was used: the pages opened, taps and scrolling. Anything you type, your town, every distance, anything about an account, and every session’s list of players and chat are masked out before the recording leaves your browser. Recordings are deleted after 30 days.
When something goes wrong we receive a technical error report with no personal information in it. Our hosting provider keeps a short-lived log of web requests, which includes the IP address a request came from and the approximate location it derives from that address.
If you write to us through the contact form, we keep your email address, the topic and your message in our database for 90 days after the message reaches our support inbox, or for 90 days after you sent it if it never does, and in that inbox for as long as we need it to answer you.
The Venues page shows a Google map, as does the map you can open when you choose a session’s location, and each venue's page a small map image from Google. When no location is set, the map's first view is framed around the approximate area our hosting provider derives from your connection; we do not keep that area, and it never becomes your location. With a location set, the map opens around it. Google receives the map requests your browser makes, as it does on any site that shows a Google map. Where we have one, a venue's page also shows a photo of its courts. The photos come from Google Maps listings and are kept on our own servers with their photographers' credits.
If you create an account
We keep your email address. If you choose a password, our sign-in provider stores it in a protected form that we cannot read. If you sign in with Google, Google sends our sign-in provider your email address, your name and the address of your profile picture, and the sign-in provider keeps them with your account. We use the name only to fill in the profile form for you, we add it to your player profile only if you submit that form, and we do not use the picture.
We keep your saved filters and your choice of theme with your account, so they follow you to other devices. We also keep the time you last used Dinkbound while signed in. We keep whether you have been shown the one-time tip about creating a session.
Signing in sets three more cookies: one that holds your session (your browser may store it in several parts), one that marks you as signed in (njp_user) so pages can be drawn correctly, and one that remembers a Dusk theme (njp_theme).
While you are signed in, your browser’s local storage may also hold one small note (njp_ahead) saying that a filter or theme change made on this device has not reached your account yet. It holds no personal information and is removed once the change is saved.
If you complete your player profile
We keep your first and last name, your ZIP code, your skill level if you give one, how you describe your gender if you tell us, and the time at which you confirmed that you are 18 or older. That is a time, never a date of birth. Telling us your gender is optional. If you choose “Prefer not to say”, we keep that choice, and we keep how many times we have asked you, three at most, so that we stop asking.
Your ZIP code is used to work out distances on a device where you have not shared your location; on that device the town and approximate center of your ZIP code are kept in the location cookie (njp_loc). We ask for this information so that you can organize and join sessions with other players. Nothing on your profile is shown to anyone else until you organize or join a session, and the first time you do, we ask you to agree to what is shown. Your gender is never shown beside your name; it is only counted, as described below.
If you set free hours before October 2026, they stay on your profile until you delete your account; nothing reads them now.
If you organize or join a session
A session you organize is public. Its name, type, level range, date, time, place, player limit, fee and your description are shown to everyone, signed in or not, and may appear in search engines. Please do not put personal details in them. The courts you name are shown to signed-in users only. The average skill level of the players in a session is shown to everyone as well, with no names.
On a session you organize, join or wait for, your first name and the first letter of your last name are shown to other signed-in users, as its organizer, in its list of players or in its waitlist, until the session ends. In those lists your skill level is shown beside your name, if you gave one. Visitors who are not signed in see how many players have joined, and no names. Your email address, your full last name and your ZIP code are never shown.
A session’s list of players also shows signed-in users its gender mix: how many of its players describe themselves as men, as women or as non-binary or another gender, and how many have not said. You are counted under what you told us, or under “Not shared” if you told us nothing or chose “Prefer not to say”. The mix shows numbers and never names, but it is not anonymous: on a session with few players, other people can often work out whose answer is whose. Players on a waitlist are not counted, visitors who are not signed in do not see the mix, and it is no longer shown once the session ends.
Each session has a chat that only its organizer and its players can read. A message shows your first name and the first letter of your last name, when you wrote it and, if you changed it, when you last changed it. Players who join later can read the whole chat. If you leave the session you can no longer read its chat, and what you wrote stays in it. The chat closes 24 hours after the session ends, or 24 hours after it is canceled, and nobody can read it after that.
If someone reports a chat message, we read that session’s chat to look into it, and we keep a copy of the chat as it stood for 90 days, or longer where the law requires it. If you report a chat message, we keep your email address with the report in our database for 90 days after the report reaches our support inbox, or for 90 days after you made it if it never does, and in that inbox for as long as we need it to look into the report. We also keep the time up to which you have read each chat, so that we can show you what is new, and the times of your most recent messages in each chat, so that we can limit how fast messages are sent.
If you block a player, we keep a record of the block with your account, so that we can hide their chat messages from you and keep them out of sessions you organize. The player is not told. If they were in a session you organize that has not started, we take them out of it and tell them, by email and under the bell, that they are no longer in it, without saying why. You can see who you have blocked, and unblock them, on your profile page.
We send email about sessions to the players who joined: when a session is canceled or removed, or its date, time, place or fee changes. We email you when a place opens and you are moved in from a waitlist, and when you are taken out of a session. Players on a waitlist are emailed when the session is canceled or removed, or its date, time, place or fee changes. An organizer is emailed when we remove their session. The same notices are listed under the bell while you are signed in. We do not send email about chat messages, or when a player joins, leaves or starts waiting.
We delete the list of who joined a session, its waitlist and its chat 30 days after the session’s scheduled end, and a notice under the bell 30 days after it was last changed. We keep the record that you organized a session until you delete your account; it is how the form remembers the place and level range you used last.
Who handles information for us
Supabase stores our database, runs sign-in and carries the signal that tells an open chat to look for new messages; that signal holds no message text. Cloudflare hosts the site. Resend sends the sign-in emails, the notice that a password was changed, the emails about sessions, the messages you send us through the contact form and the note that tells us a chat message was reported, so it receives your email address and, for a session email, a contact message or a report, its text; a report’s text names the session and never quotes the chat. PostHog provides analytics; it receives that random identifier, the pages you view and the address of the site that linked you here, and, when you are signed in, an internal account number and no other detail about you, and, for a visit of more than ten seconds, the masked recording described above, and those few facts about the browser. Sentry receives error reports. Google provides the Continue with Google button: when the sign-up or log-in window is shown, your browser loads that button from Google, so Google sees your IP address and can read its own cookies; on a phone the sign-in happens on Google's page in the same tab. Google also finds the places you type into the location field, receiving the letters you type and nothing else about you. Google also serves the maps on the Venues pages and in the session location picker, and the venues' ratings; the venues' photos come from Google Maps listings and are kept on our own servers. Google learns about your Dinkbound account only if you choose to sign in with it.
We do not sell personal information, share it for advertising, or use it for anything other than running Dinkbound.
How long we keep it
We keep account and profile information until you delete your account. An email address that asked for a sign-in code and never used it is deleted after 7 days. A record that your password was changed, holding only your account number and the time, is kept for 30 days.
When you delete your account, your account and your profile are removed at once. Sessions you organized that have not started are canceled, and you are taken out of the sessions you joined, so your name is no longer shown on any of them. The chat messages you wrote are deleted with your account, except in a copy kept because a message was reported, which is deleted on its own schedule. The blocks you made, and blocks made against you, are deleted with your account. Analytics records made while you were signed in carry only the internal account number and are not removed. We keep one record that an account was deleted: the date, how long the account had existed, whether its profile had been completed, and the reason if you chose to give one. That record holds no information that identifies you, so please do not put personal details in the reason.
Your choices
You can change your ZIP code, skill level, gender and theme on your profile page, and delete your account there. You can leave a session, or cancel one you organized, until it starts. You can leave a waitlist until the session starts, and block or unblock a player at any time. You can change or delete a chat message you wrote while its chat is open. You can clear the cookies and local storage in your browser at any time. To correct your name, or to ask for a copy of what we hold about you, contact us.
Children and teens
Dinkbound is not directed to children. We do not knowingly keep information from anyone under 13, and accounts are not open to them. Player profiles, organizing or joining sessions, and session chat are for adults 18 or older. If you believe a child or a teen has given us information in a way this policy does not allow, contact us and we will delete it.
Changes to this policy
When this policy changes, the date at the top of the page changes. If a change affects information we already hold about you, we will tell you before it takes effect.
Questions about this page: use the contact form or email support@dinkbound.com.