Play Learn Practice

Privacy

Last updated November 16, 2026. To switch the anonymous usage counts off, or to manage an account, use the privacy page inside the site.

In short

Play Bridge has no adverts and no tracking cookies, and you never need an account. It keeps anonymous counts of how the site is used, your daily-deal score for that day’s ranking, the feedback you choose to send, and, only if you sign in, a copy of your progress so it can follow you between devices.

Kept in your own browser

Your settings, results (including which kinds of bidding and card-play decision went well or badly, used to suggest what to practice), practice scores, lesson progress and the deal you are in the middle of are saved on your device. Unless you sign in, this record stays on your device. Two things are sent without your name: the anonymous counts described next, and your daily-deal result. Clearing your browser’s site data removes them.

Anonymous usage counts

To learn which parts of the site are used, it records simple events: that the site was opened today, a deal was started, finished or left unfinished, a hint was asked for, a lesson was opened or completed, a practice hand was answered, the “find where to start” check was finished (with how many questions were asked and how many were right), a result or link was shared, or an error occurred in the page.

At most once a day it also records which kinds of decision your recent deals show as strong or weak, as a handful of numbers such as “responding: 60%”, and a note when a suggested area to practice appears, is used or goes away.

Each event carries the date you first visited, how many days you have visited, whether your screen is phone-sized and your country. The first event of a day also carries the website that linked you here, the part of the site you arrived on, how long the site took to start, and a short label if the link you followed had one (such as “forum”).

A finished deal carries a summary: whether you declared or defended, the result, how many hints you used, how many of your bids matched the textbook, whether it was the daily deal, whether it ended in a claim, and roughly how many deals you have played. An error carries its message, the part of the site you were on, where in the site’s code it happened, and your browser’s family (such as “safari”).

No name, account, network (IP) address or visitor identifier is stored with these events, including when you are signed in. To count return visits, your browser keeps a small note of the date of your first visit and the number of days you have visited. Events wait in a short list in your browser and are sent a few at a time. These details do not name you. On a small site they could in theory be matched to one browser; the site never tries to.

You can switch these counts off on the privacy page of the site, and none of these counts are recorded if your browser sends a “Do Not Track” or “Global Privacy Control” signal (both are browser settings). Your daily-deal result is still added to the ranking. The server adds events to running totals for each day and does not keep them one by one, except error reports, the once-a-day figures about kinds of decision and the notes about suggested practice, which are kept as separate records. Events sent before November 16, 2026 were all kept as separate records. Separate records are deleted after 60 days and the daily totals after 400 days.

Daily deal results

When you finish the daily deal, your score, contract and number of tricks are added to that day’s ranking so players can compare results. Each person is counted once. The time it arrived is kept too. If you are signed in, the entry is linked to your account. Whether or not you are, the entry is also kept for a short time with a scrambled code worked out from your network address and the date: it cannot be turned back into the address by anyone without the site’s secret key, and the site does not try; it is different every day, and it is erased within three days. Without an account, only the first result from one internet connection is kept each day. The result is sent with the bids made and cards played, so the server can check it. Entries are deleted after 90 days. Your streak is kept in your browser, or in your account if you are signed in.

Accounts (optional)

If you sign in with Google, the site stores the identifier Google gives it for you, your name, your email address, the date your account was created, a copy of your progress (lessons, results, streak and practice scores), and your daily-deal ranking entries. From then on your progress is uploaded whenever it changes, so that it can follow you between devices. Google also sends a link to your profile picture, which is not kept. The site never sees your Google password or anything else in your Google account.

Signing in sets one cookie that keeps you signed in for up to 90 days, and a second that lasts ten minutes while the sign-in is completed. They are used for nothing else. The server keeps a record of each sign-in (when it started and when it expires), removed once it has expired.

On your account page you can see everything stored about you, sign out on every device, and delete your account. Deleting removes your account, your stored progress, your daily-deal ranking entries, your sign-in records and any feedback sent with your email address, and offers to clear your progress from the device you are using. Copies in the hosting provider’s automatic backups disappear within 30 days. To also withdraw the site’s access at Google, visit myaccount.google.com/permissions.

Feedback you send

A feedback message is stored with the page you were on, your screen type and your country. An email address is stored only if you type one in, and is used only to reply to you, and to find your messages if you ask to see or delete them. If you check “Include technical details”, your browser’s family (such as “safari”), your screen size and the last error the page hit are stored too; the form shows them before you send. Messages are deleted after two years, or sooner if you ask.

Where it is kept, and who can see it

The site and its database are hosted by Cloudflare, which may process data in the United States and other countries. Nothing is sold, and nothing is shared with anyone else. Only the person who runs the site looks at feedback messages and the usage counts.

Like every website’s host, Cloudflare sees your network (IP) address in order to deliver pages, and the site uses it briefly to limit abuse. Cloudflare keeps technical logs of requests to the site’s server for a few days. The site does not copy your address into its own database.

Your choices and rights

You can ask to see, correct, receive a copy of, or delete anything held about you, and you can object to the usage counts by switching them off. Signed-in players can do most of this themselves from the account page; your name and email address are refreshed from Google each time you sign in. For anything else, send a message through the feedback page and include an email address so that you can be answered. You also have the right to complain to your local data-protection authority.

The usage counts and the daily ranking are kept because they are needed to run and improve the site; the counts contain nothing that names you, and a ranking entry is linked to you only through your account, if you have one. Account data is kept because you asked for an account, for as long as you keep it.

Children

The site is not aimed at children and does not knowingly collect personal information from them. If you believe a child has sent personal information, say so through the feedback page and it will be removed. Accounts need a Google account, which has its own age requirements.

Changes to this page

If this page changes in a way that matters, the date at the top of the page changes.

Credits

The computer players analyze card play with DDS, the double-dummy solver by Bo Haglund and Soren Hein, used under the Apache License 2.0 (a copy is at /licenses/dds.txt). Its source is at github.com/dds-bridge/dds; this site uses release 2.9.0 compiled to WebAssembly.