Back to AISI BET

Privacy Policy

Version
1.0
Effective
2026-08-23
Last updated
2026-08-23

SIA AISI · Registration No. 40203655530

1. Who is responsible for your data

SIA AISI, registration number 40203655530, Latvia, European Union, is the controller of personal data processed through AISI BET.

2. Account identity

Accounts are created and authenticated through our authentication provider, Clerk. Clerk processes your email address, password credentials, verification codes and session data. We store an internal mapping between your authentication identity and your AISI BET user record so your data can be linked to your account.

3. Product data we store

When you use the product, we store the following in our database:

  • profile information such as display name, avatar and country
  • app preferences, including favourite sports, competitions and teams
  • Fan and Manager profile settings, including risk level and bankroll settings you enter
  • saved strategies, strategy items and generated strategy output
  • Manager scans, opportunities, approved positions and combo positions
  • watchlists and recently analysed matches
  • calendar entries and tracked bets you create
  • AI analyses you generate
  • your legal acceptance record and optional marketing preference

Bankroll figures and stake sizes are values you enter for planning purposes. AISI BET does not hold funds and does not process any wager.

4. Technical logs

We record technical logs of calls to external sports-data providers, including endpoint, status, duration and error information, to operate and debug the service. These logs are server-side only and are not readable from the application by users.

5. Analytics and marketing

AISI BET does not currently run third-party product analytics, advertising pixels or cross-site tracking. If that changes, this policy and the Cookie Policy will be updated and, where required, your consent will be requested separately.

6. Payments

No paid subscription is active today, and we do not store card details. If payments are introduced, they will be handled by a payment processor and this policy will be updated before that processing begins.

7. Cookies

We use strictly necessary cookies for authentication and interface state. See the Cookie Policy for the full breakdown.

8. Processors we use

  • Clerk — authentication and session management
  • Supabase — database and backend infrastructure
  • Sportmonks — sports fixtures, statistics and odds data
  • OpenAI — AI analysis and explanation generation from match data you request
  • Lovable — application hosting

We do not send your account credentials to sports-data or AI providers. AI requests carry match and strategy context, not your authentication data.

9. Legal bases

  • Performance of a contract — providing the account and product features you request.
  • Legitimate interests — security, abuse prevention, and service reliability.
  • Legal obligation — retaining records of your legal acceptance.
  • Consent — optional marketing communications, which you can withdraw at any time.

10. Retention

Account and product data is retained while your account is active. Legal acceptance records are retained as evidence of consent for as long as needed to demonstrate compliance. Technical logs are retained for a limited operational period.

11. Your rights

Subject to applicable law, you may request access, correction, erasure, restriction, portability, and object to certain processing. You can withdraw marketing consent at any time from your Profile without affecting your account.

12. Account deletion

You may request deletion of your account and associated product data. Records we are required to keep, such as proof of legal acceptance, may be retained for the period required by law.

13. International transfers

Some processors listed above operate outside the European Economic Area. Where that applies, transfers rely on appropriate safeguards such as the European Commission's standard contractual clauses or an adequacy decision.

14. Security

Access to your records is restricted at the database level so that a signed-in user can only reach their own rows. Server-side credentials are never exposed to the browser.

15. Contact

A published contact address for privacy requests is being finalised and will appear here once confirmed.

16. Updates

When this policy changes materially, the version is raised and you will be asked to review the updated document.