B.I.D. / Information
Privacy Policy.
What the current website uses, why it needs it and how to contact us about your data.
Last updated: 10 November 2026Who to contact.
This notice concerns the B.I.D. project operated from Bulgaria. The contact for this website and privacy requests is betmarketintelligence@gmail.com. The project is pre-launch; registered seller and final operator details will be published before public membership sales open.
This notice describes current functionality, including sandbox testing, expressly identified administrator live checkout and the separate one-time €1 real payment test. Public membership sales remain closed. A payment-method preview does not mean every method is connected.
1. Account and membership information.
When you create a profile, Firebase Authentication, provided by Google, processes your email address, password credentials, account identifier, verification status and authentication activity. B.I.D. verifies your identity and uses an account session to recognise signed-in requests. Your raw password is not stored in the B.I.D. membership database.
When a membership purchase is linked, our membership records include the account identifier, purchase email, Stripe subscription reference, package and price reference, test/live mode, status and paid-through date. Relevant Stripe customer and invoice information may be retrieved to verify ownership, manage billing and check entitlement. We use these records to manage access and respond to queries. A one-time payment test does not create a membership entitlement.
No connection to your bookmaker account. The current service does not request bookmaker login credentials, connect to members’ personal bookmaker accounts or automatically import their personal wagers or balances. Our performance journal records B.I.D.’s published selections, rather than a feed from each member’s betting account. If you voluntarily send betting screenshots or other information to support, we may receive the information they contain; remove unnecessary personal, account and payment details first.
2. Payment services.
Stripe hosts B.I.D.’s checkout and billing portal. This includes sandbox testing, expressly identified administrator live membership checkouts and the separate one-time €1 live payment test. Information entered on Stripe’s pages is processed under Stripe’s privacy notice. The B.I.D. membership database stores payment references and membership status, not full card numbers or card security codes.
Stripe provides payment and subscription status used to verify purchases and respond to billing queries. New membership checkout sessions also identify the applicable versions of our terms and privacy notice. Stripe collects the required acceptance of the terms; displaying the privacy notice does not mean you consent to every processing activity described in it.
Card and supported wallet or local payment options are offered through Stripe subject to availability. PayPal activation remains pending. Crypto and Skrill are not connected in the current website. Selecting a preview does not itself submit payment information to those providers. We will update this notice before introducing a new provider or materially different processing.
3. Telegram and support.
If Telegram linking is enabled for an eligible membership, we use a Telegram user identifier and a temporary linking token to associate the account with channel access. Channel posts and available photo references can be stored to display private content to entitled members. Sandbox purchases do not qualify for real channel access.
Opening the public Telegram link does not automatically link your B.I.D. account or give us access to your private Telegram messages. Telegram processes information under its own policy. Email support processes the address and details you choose to send; never send passwords, login codes or full card credentials.
4. Browser storage and technical information.
The current website uses a secure, HTTP-only B.I.D. member session cookie with a maximum age of one hour. Firebase may retain authentication state in browser storage. Session storage can remember a pending checkout reference while you finish sign-in and email verification.
On the home page and public results pages, basic traffic events can record the page route, visit time, referring hostname and a broad mobile/tablet/desktop category. The application’s traffic table does not store full referring URLs, account emails or an individual visitor identifier. A session-storage flag limits repeat counting of the same page in a browser session. The client respects the browser’s Do Not Track signal.
The hosting and infrastructure providers also receive technical request information, such as IP addresses and security logs, to deliver and protect the site. Clearing browser data may sign you out or remove a pending checkout reference.
5. Purposes and service providers.
Account authentication, requested purchases and entitlement checks are used to provide the service you request and take steps connected with that service. Security, fraud prevention and proportionate troubleshooting serve our legitimate interests in protecting the website and its users, subject to applicable rights. Support information is used to answer your request; payment or dispute records may also be processed where necessary to comply with applicable legal obligations or establish, exercise or defend legal claims. Where consent is required for optional processing, it must be obtained before that processing is enabled.
Relevant providers include Google/Firebase for authentication, Cloudflare for website hosting and database storage, Stripe for test and live payment processing, and Telegram if you use its links or membership features. Email correspondence is handled through our Gmail mailbox. Each provider may process data for its own legal or security responsibilities.
Some provider processing may take place outside Bulgaria or the EEA. Applicable transfer mechanisms and provider terms must be assessed for each service; this page does not promise that all information remains in the EU. We do not sell personal account information or operate a third-party advertising programme in the website code. The current website does not automatically enrol registered users in a marketing newsletter.
6. Retention and security.
Account and membership information is kept while needed for the account, access management, support, security or applicable record-keeping obligations. Temporary Telegram linking tokens expire after ten minutes; expired tokens cannot establish a new link. Expiry of an access token does not necessarily mean every related database record is immediately deleted.
Retention depends on the data and purpose. The current application does not have an automatic blanket deletion schedule. Contact us to request account deletion or ask about a particular record; information that must be retained for a legal obligation or dispute may be kept for that purpose. Provider backups and logs may follow separate retention schedules.
Access checks and protected sessions reduce risk but cannot guarantee absolute security.
7. Your choices and rights.
Where applicable, you may request access, correction, deletion, restriction or portability of personal data, and object to processing based on legitimate interests. Where processing relies on consent, you may withdraw it without affecting earlier lawful processing. We may verify your identity and explain any legal limitations before acting.
Write to our contact email with the request and the account email concerned. Do not include identity documents unless a necessary, proportionate verification step has first been agreed. You may also complain to the Bulgarian Commission for Personal Data Protection or another competent supervisory authority. See cpdp.bg.
The service is intended for adults aged 18 or over. If you believe an underage person has provided account data, contact us.
VIP launch notice.
If you ask for the launch notice, we store your email address and the time of your request in our Cloudflare database. The site administrator can access the list to send one email when VIP opens. You can withdraw your request or ask us to remove your address by writing to the contact address above. We use this list only for the launch notice and will delete it when it is no longer needed for that purpose.
8. Updates.
The VIP launch notice section was added on 10 November 2026. The 18 October 2026 version remains available. We will update this page when the actual processing changes, including before introducing another provider, new tracking or materially different uses of personal data. Any notice or consent required for a change must be provided or obtained as applicable.