Privacy Policy

1. Introduction

This Privacy Policy explains how Oleksandr Illarionov, an individual developer based in Ukraine (“BetKeep,” “we,” “us,” or “our”), collects, uses, stores, and shares information in connection with:

• the BetKeep iOS application;
• the BetKeep website at betkeep.app; and
• related support, account, synchronization, and subscription services.

BetKeep is a personal record-keeping and analytics tool for information entered by users about their own betting activity.

BetKeep is not a bookmaker, sportsbook, casino, betting exchange, gambling operator, tipster, or financial service. BetKeep does not accept, place, transmit, settle, or facilitate wagers and does not hold or transfer wagering funds.

2. Information we process

2.1 Account and authentication information

A BetKeep account is required to use the application. BetKeep supports email-and-password authentication and Sign in with Apple.

When you create or use an account, we process:

• your email address, when provided;
• your account identifier;
• your password as necessary for email-and-password authentication;
• email verification and password recovery information, where applicable;
• authentication sessions and related security information.

Authentication is provided through Supabase Auth. BetKeep does not store your password in readable form inside the application. Your credentials and authentication requests are transmitted to and processed by Supabase.

When you use Sign in with Apple, BetKeep processes the Apple user identifier, identity token, authorization code, and available profile information supplied by Apple as needed for authentication and account deletion. Whether Apple provides profile information, such as a name or email address, depends on Apple and your settings; Apple does not always provide a name or your real email address.

2.2 Profile and account settings

Depending on the information you provide or select, we may process:

• display name;
• country selection;
• time zone;
• profile avatar type;
• custom profile image;
• onboarding status;
• preferred currency;
• odds format;
• default bookmaker;
• default sport;
• default stake;
• initial reserve settings.

A custom profile image may be uploaded to private storage associated with your account.

2.3 Betting journal and financial records

BetKeep allows you to create and manage personal records concerning betting activity. Information synchronized with your account may include:

• bets and bet dates;
• sports, tournaments, events, teams, or participants;
• markets, selections, and user-entered odds;
• stakes, results, returns, cash-out amounts, and commissions;
• bankroll and reserve operations;
• bookmaker accounts and transfers;
• bookmaker commission settings;
• tipster or capper profiles;
• recommendation costs and capper-related financial operations;
• parlay and system-bet legs;
• notes and other information you choose to enter.

This information is used to provide your personal journal, calculations, statistics, backup, and synchronization features. It is not used to place bets or transfer wagering funds.

2.4 Information stored only on your device

Some information normally remains on your device and is not synchronized with Supabase. This may include:

• unfinished bet drafts;
• your local sports database;
• user-created tournaments, teams, participants, and aliases;
• locally stored sports or bookmaker images;
• custom sports;
• presentation and interface preferences;
• application language and theme;
• notification preferences;
• application-lock settings;
• your BetKeep security PIN;
• biometric authentication preferences.

The BetKeep PIN is stored using the iOS Keychain in a protected form. Face ID, Touch ID, or device-passcode authentication is performed by iOS. BetKeep does not receive or store your biometric data.

A custom profile avatar is an exception: if selected as your account avatar, it may be synchronized through Supabase Storage.

2.5 Synchronization information

BetKeep uses an offline-first synchronization system.

The application stores a local copy of your data and may synchronize eligible records with Supabase when you are signed in and a network connection is available.

Synchronization may include:

• uploading new or changed records;
• downloading records created or changed on another device;
• retaining deletion markers needed to synchronize deletions;
• detecting conflicting versions of a record;
• asking you whether to keep the local or remote version when a conflict requires your decision.

Synchronization may be delayed or unavailable because of network, account, service, or technical conditions.

2.6 Backups, exports, and imports

BetKeep allows you to export a backup file to a location you select.

A BetKeep backup may contain:

• betting and financial records;
• unfinished drafts;
• application settings;
• custom sports;
• local sports-database content;
• locally stored images;
• notification preferences;
• bookmaker and capper information.

Backup files are JSON-based files and are not encrypted or password-protected by BetKeep. You are responsible for selecting a secure storage location and controlling access to exported files.

BetKeep does not automatically upload manually exported backup files. Depending on where you save or share a file, it may be processed by Apple iCloud Drive, another cloud-storage provider, a messaging service, an email provider, or another service selected by you.

Importing a backup replaces the relevant local BetKeep data. Records that are eligible for synchronization may subsequently be transmitted to Supabase.

Deleting your BetKeep account does not delete backup files that you previously exported outside the application.

2.7 Subscription and purchase information

BetKeep Pro subscriptions are processed through Apple’s App Store and StoreKit.

BetKeep may offer monthly, six-month, and annual subscription plans.

Eligible users may be offered a seven-day free trial. Trial eligibility is determined by Apple and is not guaranteed to every user.

Apple processes your payment method and billing information. BetKeep does not receive your full payment-card details.

BetKeep may process StoreKit information such as:

• product identifier;
• transaction identifier;
• original transaction identifier;
• purchase and expiration dates;
• subscription status;
• renewal status;
• revocation information;
• introductory-offer or trial status;
• Sandbox or Production environment;
• an application account token used to associate the purchase with your BetKeep account.

Subscription products, prices, trial availability, eligibility, billing periods, and renewal terms are displayed by Apple before purchase.

BetKeep uses StoreKit and BetKeep server functions hosted on Supabase to verify subscription access. Server-side subscription verification is enabled. For this purpose, BetKeep may transmit and process signed AppTransaction data and signed StoreKit transaction data. BetKeep’s server may receive Apple App Store Server Notifications and reconcile subscription status with Apple, storing subscription information and the verified subscription state associated with your BetKeep account.

2.8 Notifications

BetKeep may request permission to provide local iOS notifications, including:

• application badge counts;
• reminders about pending or unsettled records.

These notifications are scheduled and delivered through iOS. BetKeep does not currently use server-based push notifications or register an APNs push token.

You can change notification permissions in iOS Settings and change BetKeep notification preferences inside the application.

Notification content may be visible on your device’s lock screen depending on your iOS notification settings.

2.9 Photos and images

BetKeep may request access to images you explicitly select for:

• your profile avatar;
• a support request;
• a custom sport, tournament, participant, or bookmaker image.

BetKeep may also request permission to save a share image to your photo library.

BetKeep does not access your entire photo library solely because you select an individual image through the iOS photo picker.

2.10 Support requests

Support from the application

When you contact support from the application, you may provide:

• your name;
• your email address;
• your message;
• an optional image attachment.

The application prepares an email in the iOS mail composer. The message is not sent until you choose to send it.

The message may be processed by your email provider, the recipient’s email provider, and other providers involved in email delivery.

Support from the website

The website support form may collect:

• name;
• email address;
• subject;
• message.

Website form submissions are handled and stored through Netlify Forms. Netlify may use Akismet to identify spam and abuse.

Support communications may be retained for up to 12 months after the support request is resolved or after the last communication, unless a longer period is required to comply with law, resolve a dispute, prevent abuse, or establish or defend legal claims.

Please do not include passwords, complete payment-card details, government identification numbers, or other unnecessary sensitive information in a support request.

2.11 Website and technical information

The BetKeep website is hosted through Netlify.

When you visit the website, Netlify or its infrastructure providers may process technical information needed to deliver, protect, and operate the website, such as:

• IP address;
• browser and device information;
• requested pages;
• request date and time;
• referring page;
• security and server-log information.

The current website does not include advertising scripts or third-party behavioral analytics.

The website may use browser localStorage to remember whether you selected the light or dark theme. The stored value contains only the selected theme preference.

BetKeep’s website code does not currently create advertising or analytics cookies.

3. How we use information

We use information to:

• create and authenticate accounts;
• verify email addresses and recover accounts;
• provide the BetKeep application and website;
• store and synchronize your records;
• calculate and display personal statistics;
• maintain account and application settings;
• provide subscription features;
• process exports and imports;
• respond to support requests;
• protect accounts, prevent abuse, and maintain security;
• diagnose technical problems;
• comply with applicable legal obligations;
• enforce applicable terms and protect legal rights.

Where applicable law requires a specific legal basis, information is processed as necessary to provide the service requested by you, comply with legal obligations, protect legitimate security and operational interests, or based on your consent where consent is required.

4. Service providers

4.1 Supabase

Supabase provides:

• account authentication;
• database hosting;
• synchronization infrastructure;
• private profile-image storage;
• server functions;
• operational and security logging.

The BetKeep Supabase project uses Ireland as its primary hosting region.

Supabase may use its own infrastructure providers and subprocessors. Some operational processing may occur outside Ireland where necessary to provide, secure, or support the service.

4.2 Apple

Apple provides:

• Sign in with Apple;
• the App Store;
• StoreKit purchases and subscriptions;
• subscription management and refund-request systems;
• iOS notifications;
• photo-selection and photo-library services;
• Keychain and biometric authentication;
• optional App Store and TestFlight crash or diagnostic reports.

Apple processes information under its own privacy policies and agreements.

4.3 Netlify

Netlify provides:

• website hosting;
• request processing;
• security and infrastructure services;
• website support forms.

Netlify Forms may use Akismet to filter spam submissions.

4.4 Email providers

Support and authentication emails may be processed by email-delivery providers, your email provider, and the provider used to receive BetKeep support messages.

We do not currently integrate advertising networks or third-party behavioral-tracking SDKs into the BetKeep application.

5. International processing

BetKeep may be available through multiple App Store territories.

Our service providers may process information in countries other than the country where you live.

Primary account and synchronized data stored through the BetKeep Supabase project is hosted in Ireland. Supabase, Netlify, Apple, email providers, and their subprocessors may perform additional operational processing in other countries.

Where required by applicable law, appropriate contractual or other safeguards will be used for international transfers.

6. Retention

We retain information according to the following general criteria:

• Account and synchronized data are retained while your account remains active and as needed to provide synchronization and account functionality.
• Synchronization deletion markers may remain until they are removed through account deletion or database maintenance.
• Local application data remains on your device until you remove it, reset local BetKeep data, delete the application, or delete your account.
• Exported backup files remain wherever you saved or shared them until you delete them.
• Support communications may be retained for up to 12 months after the request is resolved or after the last communication.
• Technical logs and provider backups may remain for the periods applied by the relevant service provider and service plan.
• Information may be retained longer where required by law or reasonably necessary to resolve disputes, prevent fraud or abuse, enforce agreements, or establish or defend legal claims.

Deletion from an active system may not immediately remove information from disaster-recovery backups or security logs. Such information is not intended to be restored except when needed for disaster recovery, security, or legal compliance.

7. Your choices and rights

Depending on applicable law, you may have rights to:

• access personal information;
• correct inaccurate information;
• request deletion;
• receive a portable copy of information;
• restrict or object to certain processing;
• withdraw consent where processing is based on consent;
• complain to an applicable data-protection authority.

Within BetKeep, you can:

• review and update profile information;
• export a backup;
• clear betting data;
• reset local device data;
• disable notifications;
• remove a profile image;
• initiate deletion of your account.

Clearing local device data does not delete the remote account or synchronized server data. If you sign in again, synchronized information may be restored.

Account deletion is separate from subscription cancellation. Deleting your BetKeep account does not automatically cancel an Apple subscription.

To exercise a privacy right or ask a privacy question, email support@betkeep.app or use the BetKeep support form. We may need to verify your identity before completing a request.

8. Account deletion

You can initiate account deletion inside BetKeep.

For an email-and-password account, deletion requires recent reauthentication with your password. For an account using Sign in with Apple, deletion requires a new Sign in with Apple authorization. During Apple-account deletion, BetKeep’s server carries out the Apple authorization-token revocation process.

When deletion succeeds, BetKeep is designed to delete:

• your Supabase authentication account;
• synchronized profile and account settings;
• synchronized journal and financial records;
• associated subscription-entitlement records stored by BetKeep, if any;
• custom profile avatars stored in BetKeep’s Supabase Storage;
• local BetKeep account data on the device where deletion is performed.

Account deletion does not automatically delete:

• backup files exported outside the application;
• copies you shared with another service or person;
• support emails or website support requests;
• information that must be retained under applicable law;
• an Apple subscription.

Apple billing may continue until you cancel the subscription through Apple.

9. Security

We use technical and organizational safeguards intended to protect information, including authenticated access, private account ownership rules, device storage, iOS Keychain protection, and private profile-image storage.

No storage or transmission system can be guaranteed to be completely secure.

Exported BetKeep backup files are not encrypted or password-protected by BetKeep. You should store them only in a location you trust.

10. Children and eligibility

BetKeep is not directed to children or people under 18 years of age.

You may use BetKeep only if you are at least 18 years old, or any higher minimum age required by applicable law in your location, and are legally permitted to access betting-related services and information.

BetKeep does not make gambling lawful where it is prohibited.

11. Changes to this Privacy Policy

We may update this Privacy Policy when BetKeep, its service providers, or applicable requirements change.

The effective date at the top of the policy will be updated when a revised version is published.

Where required, we will provide additional notice or request renewed acceptance.

12. Contact

The controller responsible for this Privacy Policy is: