Cookie Policy

BakkMe
Effective date: February 13, 2026 • Last updated: February 13, 2026

This Cookie Policy explains how BakkMe ("we", "us", or "our") uses cookies, device identifiers, and similar tracking technologies when you use the BakkMe mobile application, website, and related services (collectively, the "Service"). This policy should be read alongside our Privacy Policy and Terms of Service. By continuing to use our Service, you acknowledge the use of cookies and tracking technologies as described in this policy.

1. What Are Cookies

Cookies are small text files that are stored on your device (computer, smartphone, or tablet) when you visit a website or use a web-based service. They allow the service to recognize your device and remember information about your visit, such as your preferred language, login status, and other settings.

In addition to traditional browser cookies, BakkMe and its partners may use similar technologies, including:

Throughout this policy, when we refer to "cookies", we include all of the technologies described above unless otherwise stated.

2. How We Use Cookies

BakkMe uses cookies and similar technologies for the following purposes:

3. Types of Cookies We Use

3.1 Essential / Necessary Cookies

These cookies are strictly necessary for the Service to function. They cannot be disabled without breaking core functionality. They do not store personally identifiable information for marketing purposes.

Purpose Examples Duration
User authentication and session management Firebase Auth tokens, session cookies Session to 30 days
Security and fraud prevention CSRF tokens, Stripe fraud detection identifiers Session to 12 months
Load balancing and infrastructure Server routing cookies Session
Cookie consent preferences Consent state storage 12 months

Legal basis (GDPR): Legitimate interest — these cookies are essential for providing the Service you have requested.

3.2 Performance / Analytics Cookies

These cookies collect aggregated, anonymous information about how users interact with the Service. They help us understand usage patterns, diagnose technical issues, and improve the user experience.

Purpose Examples Duration
Usage analytics and reporting Google Analytics, Firebase Analytics Up to 24 months
Crash and error reporting Firebase Crashlytics Up to 90 days
Performance monitoring Firebase Performance Monitoring Up to 12 months

Legal basis (GDPR): Consent — these cookies are set only after you have given your affirmative consent, unless they are strictly necessary for a service you have explicitly requested.

3.3 Functionality Cookies

These cookies enable enhanced functionality and personalization. They may be set by us or by third-party providers whose services we have integrated into our pages or app.

Purpose Examples Duration
Language and locale preferences User preference storage 12 months
UI customization (theme, layout) Local storage entries Persistent
Chat and notification state Firebase Cloud Messaging tokens Until refreshed
Live stream and media preferences Quality, volume settings 12 months

Legal basis (GDPR): Consent or legitimate interest, depending on whether the cookie is necessary for a feature you have specifically requested.

3.4 Advertising / Targeting Cookies

These cookies are used to deliver advertisements that are relevant to you and your interests. They also help measure the effectiveness of advertising campaigns and limit the frequency of ad display.

Purpose Examples Duration
Personalized advertising Google AdMob identifiers, Facebook Audience Network Up to 24 months
Ad measurement and attribution Conversion tracking pixels, campaign IDs Up to 12 months
Frequency capping Ad display counters Session to 30 days
Interest-based audience profiling Behavioral segments Up to 24 months

Legal basis (GDPR): Consent — these cookies are only set after you have given explicit, informed consent through our cookie consent mechanism.

4. Third-Party Cookies

We work with trusted third-party services that may set their own cookies or use similar tracking technologies on your device when you use BakkMe. These third parties operate under their own privacy and cookie policies, which we encourage you to review.

4.1 Google Analytics

We use Google Analytics to understand how users interact with the Service, including page views, session duration, navigation paths, and feature usage. Google Analytics uses cookies and collects anonymized data to generate statistical reports.

4.2 Google AdMob

Google AdMob is an advertising platform that serves ads within the BakkMe mobile app. It uses device identifiers and behavioral data to deliver personalized ads. Where required by law, personalized ads are only served with your consent.

4.3 Facebook Audience Network

Facebook Audience Network delivers targeted advertising within the BakkMe app based on your interests and activity. It may use your device advertising identifier and in-app activity to serve and measure the effectiveness of ads.

4.4 Stripe (Payment Processing)

Stripe processes payments for fundraising, creator monetization, and other transactions within BakkMe. Stripe uses cookies and device fingerprinting to facilitate secure transactions, prevent fraud, and comply with financial regulations.

Stripe's cookies are classified as essential because they are necessary for the completion of payment transactions that you initiate.

4.5 Firebase

Firebase, a Google platform, provides multiple services that power BakkMe, including authentication, real-time database, cloud messaging, analytics, crashlytics, and performance monitoring. Various Firebase services set cookies or use device identifiers.

5. Mobile App Tracking Technologies

As a mobile application, BakkMe uses tracking technologies beyond traditional browser cookies. This section explains the mobile-specific technologies in use.

5.1 Device Identifiers

Mobile devices provide unique advertising identifiers that allow apps and ad networks to track activity for advertising and analytics purposes:

5.2 SDK Tracking

BakkMe integrates the following software development kits (SDKs) that collect data on your device:

5.3 Push Notification Tokens

When you enable push notifications, BakkMe receives a device token from Firebase Cloud Messaging (FCM) or Apple Push Notification Service (APNs). These tokens are used solely to deliver notifications you have opted into, such as:

Push notification tokens are not used for advertising purposes. You can disable push notifications at any time through your device settings or within the BakkMe app.

6. Your Cookie Choices

You have several options for controlling or limiting how cookies and similar technologies are used. Please note that restricting cookies may impact the functionality of the Service.

6.1 In-App Consent Management

When you first use BakkMe, we present a cookie consent banner that allows you to accept or decline non-essential cookies. You can update your preferences at any time from the app's Settings > Privacy > Cookie Preferences menu. Where required under GDPR or the ePrivacy Directive, non-essential cookies will not be activated until you have provided your explicit consent.

6.2 Browser Settings

If you access BakkMe through a web browser, you can manage cookies through your browser settings. Most browsers allow you to:

For specific instructions, refer to your browser's help documentation:

6.3 Opt-Out Links for Ad Networks

Google Ads: Manage your ad personalization settings at adssettings.google.com.

Facebook / Meta: Manage your ad preferences at facebook.com/adpreferences.

Digital Advertising Alliance (DAA): Opt out of interest-based advertising from participating companies at optout.aboutads.info.

Network Advertising Initiative (NAI): Opt out at optout.networkadvertising.org.

European Interactive Digital Advertising Alliance (EDAA): For users in the EU/EEA, manage preferences at youronlinechoices.eu.

6.4 Device Advertising Settings (IDFA / GAID)

You can control advertising tracking on your mobile device:

Disabling or resetting your advertising identifier will not reduce the number of ads you see but will make them less personalized.

7. Do Not Track Signals

Some web browsers transmit "Do Not Track" (DNT) signals to the websites and services you visit. There is currently no universally accepted standard for how online services should respond to DNT signals. As of the effective date of this policy, BakkMe does not alter its data collection or tracking practices in response to DNT browser signals.

However, we respect the Global Privacy Control (GPC) signal where required by applicable law (including the California Consumer Privacy Act). If your browser or device sends a GPC signal, we will treat it as a valid opt-out request for the sale or sharing of personal information, as applicable.

We encourage you to use the specific opt-out mechanisms described in Section 6 above to manage your privacy preferences effectively.

8. Changes to This Policy

We may update this Cookie Policy from time to time to reflect changes in the technologies we use, legal requirements, or our business practices. When we make material changes, we will:

We encourage you to review this policy periodically to stay informed about our use of cookies and tracking technologies.

9. Contact Us

If you have any questions, concerns, or requests regarding this Cookie Policy or our use of cookies and similar technologies, please contact us:

BakkMe

Privacy inquiries: privacy@bakkme.com

General support: support@bakkme.com

If you are located in the European Economic Area (EEA) or the United Kingdom, you have the right to lodge a complaint with your local data protection authority if you believe that our use of cookies does not comply with applicable data protection laws.