Home / Privacy

Privacy policy: what data the desk holds, and how the desk uses it

A reading on what data the desk holds for the reading account, how the desk uses the data, and the data retention period. The desk is editorial; the reading is the desk's honest reading.

Editorial cover for the privacy policy

What the desk holds

The desk holds the data the reading account needs to operate: the email address you used to create the account, the password hash, the reading preferences, the bookmark list and the format tracks. The desk does not hold any payment data; the Blackjack In reading account is not a payment account, and the desk does not process any payments.

What the desk does not hold

The desk does not hold any real-money rummy account data, any deposit data, any withdrawal data, or any table history. The desk is editorial; the desk does not run any tables, does not process any payments, and does not link to any specific real-money rummy platform from the editorial pages. If you have a real-money rummy account, the data is held by the platform you chose, not by the desk.

How the desk uses the data

The desk uses the data to operate the reading account: to sign you in, to load your reading preferences, to sync your bookmarks, and to keep the format tracks current. The desk does not use the data for advertising targeting, does not share the data with any third party, and does not sell the data to any data broker.

How long the desk holds the data

The desk holds the data for the lifetime of the account, plus a 30-day retention window after a deletion request. The retention window is in place to allow a reader to reverse an accidental deletion request. After the retention window closes, the data is removed from the desk's active systems. An anonymised log of the deletion request is kept for audit purposes; the log does not contain any of the data that was on the account.

Your rights

You have the right to access the data the desk holds, the right to correct any inaccurate data, the right to request deletion of the data, and the right to object to any processing the desk does. To exercise any of these rights, use the contact form on the contact page; the desk will respond within two working days.

What the desk cannot do

The desk cannot access the data held by any real-money rummy platform. The desk is editorial; the platform you chose is responsible for the data it holds. The desk can only access the data the desk holds for the reading account.

What cookies the desk uses

The desk uses a session cookie for the reading account; the cookie is HttpOnly and SameSite=Lax, expires after 30 days of inactivity, and is signed with a server-side secret. The desk uses a preference cookie for the reading preferences; the cookie is first-party, expires after 365 days, and is not shared with any third party.

What the desk does not use: the desk does not use any third-party analytics cookie; the desk does not use any advertising cookie; the desk does not use any social media cookie. The desk does not use any tracking pixel; the desk does not use any fingerprinting technique. The desk is editorial; the data is reading data; the cookies are reading cookies.

What the desk does with the contact form data

The desk keeps the contact form data for 30 days; after that, the data is removed from the active systems. The desk does not share the contact form data with any third party. The desk does not use the contact form data for advertising targeting. The desk uses the contact form data only to respond to the reader's enquiry and to keep a record of the response.

What the desk does not do: the desk does not add the reader to a marketing list based on the contact form. The desk does not share the contact form data with any operator, any platform, any analytics provider or any data broker. The desk is editorial; the contact form is a reading resource; the data is a reading resource.

How the desk handles a data breach

If the desk suffers a data breach that affects the reading account data, the desk will notify the affected readers within 72 hours of discovering the breach. The notification will include the nature of the breach, the data affected, the steps the desk has taken to contain the breach, and the steps the reader can take to protect the reading account.

What the desk will not do: the desk will not hide a data breach. The desk will not delay a data breach notification beyond the 72-hour window. The desk will not pay a ransom to recover the data. The desk will not blame the reader for the breach. The desk is editorial; the data breach response is a reading resource; the line on responsible play does not move.

Play now