Skip to content

Documents

Privacy

Effective from

In short

  • We keep the account, sessions, subscription and payments, journal, alerts and their settings; there is no advertising or analytics on the site.
  • Periods: a session lasts 30 days from last use, read notifications 180 days, the trial-day fingerprint 90 days, financial records at least 3 years.
  • The data goes to Resend (email), the payment provider — Heleket or OxaPay (payment), Telegram and push services (alerts), Polymarket (the journal address), ntfy.sh (requests to the founder), hosting in Bulgaria and cloud storage for encrypted database backups (Backblaze B2, EU).
  • We hold no keys to wallets or bookmaker accounts; access, correction and deletion of data go through support.

1. What this document covers

This document describes what data BetSpace receives from you and about you, why we need it, who gets it and how long we keep it. It covers the betspace.club site: the scanner, terminal, journal, alerts, subscription and referral program. The founder of the service is responsible for the data; questions and requests for access, correction and deletion go to support@betspace.club.

We keep what the service needs to work. There is no advertising or analytics on the site. Data leaves us only for the services in section 4.

2. What data we keep

Some of the data you enter yourself, some appears while you use the service.

  • Account. Email address, password hash (Argon2id; we do not have the password itself), profile name (by default the part of the email before the “@”), interface language, time zone, role, status and referral code. If you came through an invitation or a referral link, we remember the invitation code and who invited you. If 2FA is on, the TOTP secret and backup codes are stored.
  • Sessions. For each session: IP address, browser string, start and end time. The list is visible to you in settings, where you can also end any other session.
  • Invitation request. Email address, Telegram and “a few words about yourself” (the last two fields are optional), form language.
  • Subscription and payments. Plan, status, dates, pauses and the history of subscription events; payments — amount, status, invoice number at the payment provider, refunds; the provider's payment notifications in full, as they arrived. We have no bank card details: payment happens on the provider's side.
  • Referrals, balance, payouts. Referral credits, the balance and its entries; payout requests — amount, network (TRC20 or TON), the wallet address you gave, the transfer hash and the rejection reason, if there was one.
  • Journal. The public address of the Polymarket wallet you entered; the trades and redemptions of that address from Polymarket's public API (only for markets in our catalog); your arb and bet sessions — legs (bookmaker, odds, stake, currency) and notes.
  • Alerts and notifications. Alert rules (name, filter, channels, interval); the Telegram link — chat identifier and username; web push subscriptions — the address of the browser's push service, subscription keys and browser string; account notifications and their delivery log; notification settings and quiet hours.
  • Scanner. Saved filter presets and reports on arbs: reason, comment and a snapshot of the arb.
  • Feedback. Messages from the “Idea or bug report” form: kind, text and the account page you came to the form from.
  • Trial day. To keep the trial from being taken twice, we store a fingerprint of the device and network — hashes, not the IP address or browser itself — and the decision on the request.
  • Action log. Significant events: changes of password, email and 2FA, ended sessions, invitations, operations on subscriptions, payments and payouts, staff actions on your account. An IP address may be attached to a record.
  • Technical logs. The web server's request log — IP address, page address, browser; cookies, stream tokens and invitation codes do not get into it. Passwords and tokens are cut out of service logs.

What we do not have: passwords in plain text, card details, keys and seed phrases of wallets, logins and passwords of your bookmaker accounts.

3. How long we keep it

DataPeriod
Account, scanner presets and reports, feedback messages, settings, alerts, journalwhile the account exists; not deleted automatically
Sessionvalid for 30 days from last use; the record of an expired session (IP address, browser) is not deleted automatically — we delete it on request
Account notificationsread ones are deleted 180 days after reading, together with their delivery log; unread ones stay
Trial-day fingerprint90 days; requests waiting for manual review — until the decision
Invitation requestsno automatic period; we delete them on request
Payments, refunds, the payment provider's notifications, referral credits, balance, payout requestsat least 3 years; not deleted together with the account
Action log3 years
Web server request loglimited by size, not by time: new files push out old ones

With an active subscription you delete journal sessions yourself on the journal page, without one — through support; you can remove the wallet address there at any time. By removing the wallet address you stop the import of trades, but the trades already loaded stay — they can be deleted through support.

4. Who receives the data

  • Resend sends our emails: confirmation codes, emails about changes of password, email and 2FA, payment and subscription notifications. It receives your email address and the text of the email.
  • The payment provider — Heleket or OxaPay, whichever you chose on the payment page — accepts the subscription payment. From us it gets the amount, the currency and the payment number in our system, without your email or name. What the payment page itself collects is for the provider to decide. The other provider receives no data about the payment.
  • Telegram delivers alerts to the chat you linked. Telegram sees the text of the messages and the chat identifier.
  • Browser push services — Google, Mozilla, Apple and Microsoft: push notifications go through your browser's service.
  • Polymarket — the wallet address you entered in the journal goes to Polymarket's public API: the trades are read by it.
  • ntfy.sh — through it the founder gets a message about a new invitation request (with the email and Telegram), about a trial request waiting for review (with the email) and about a payout request (with the amount and the email).
  • Hosting — the service runs on a rented server in Bulgaria (EU); the database and the logs are there.
  • Backblaze B2 — cloud object storage in the EU. On our instructions it keeps encrypted backup copies of the database, that is, the data kept in the database (section 2), but only in encrypted form: the copies are encrypted on our side before upload.

5. Cookies and data in the browser

  • Session. The sign-in cookie; lasts 30 days from last use. If you tick “Trust this device for 30 days” when entering the 2FA code, one more cookie appears for 30 days: the code will not be asked when you sign in from this device.
  • Language. The NEXT_LOCALE cookie remembers the interface language you chose; it is a session cookie and goes away when the browser closes.
  • Referral link. Following a /r/… link sets the of_ref cookie for 30 days (HttpOnly, SameSite=Lax); it is needed to link you to the person who invited you at sign-up. After sign-up the cookie is removed.
  • Browser storage (localStorage). The theme, the last scanner filter, hidden rows, sound and a mark that you have opened an arb card. This data stays in your browser and is not sent to us.

There are no advertising or analytics cookies or trackers.

6. Your rights

You can ask for a copy of your data, its correction or deletion — write to support@betspace.club from the account's email address. We do not promise response times.

A lot is available without contacting us: end sessions, turn off email notifications by type, delete alert rules, unlink Telegram and push. Removing the wallet address and (with an active subscription) deleting journal sessions is possible on the journal page in the account.

We delete an account by hand, on a request to support. If the account had payments, credits or payouts, what stays is the email address, the subscription with its event history, the financial records — payments, refunds, referral credits, the balance and payout requests, for at least 3 years (section 3) — and the trial-day fingerprint until its period ends. The action log stays in any case, for its own period from section 3. The rest of the account data is deleted: the password and 2FA, sessions, settings, notifications, alert rules, Telegram and push links, scanner presets and reports, the journal and the wallet address.

7. Protection and changes

How accounts and infrastructure are protected is described on the Security page. The rules of use are in the Terms of use document.

We may change this document. A new edition is published on this page with its effective date, and the list of editions stays at the end of the document.

Past editions

  • The payment provider may be Heleket or OxaPay, whichever you chose when paying (sections 2–4).
  • First edition.