Privacy Policy

1. Who We Are

Boletus (the “App”) is developed and published by Mondrus CCS Inc (“Mondrus”, “we”, “us”, or “our”). This Privacy Policy explains how the Android and iOS versions of the App access, use, store, and transmit information.

Privacy questions and requests may be sent to [email protected].

2. Scope and Platform Differences

An account and subscription are optional on Android and iOS. Without signing in, your journal content is not uploaded to the Boletus cloud service. If you sign in with email/password, Google, or Apple, Firebase Authentication processes your account identifier and available email, display name, and profile photo; the App also registers a device identifier, model, App version, and language for the account. With Premium, the App synchronizes eligible journal data as described below. One Boletus account works on both platforms, and a Premium subscription bought on either store unlocks the same account. If you email us for support, we receive the information you choose to include.

Some information leaves your device when the App loads online maps, uses Firebase, synchronizes an account, verifies a Google Play or App Store subscription, shares a file at your direction, or participates in a system backup or, on Android, advertising. The iOS version does not contain an advertising SDK and uses Firebase Analytics without advertising-identifier support.

3. Information Stored on Your Device

3.1 Precise location, routes, and finds

When you grant location permission, Boletus uses precise or approximate device location to show your position, record a foraging outing, draw its route, and save the location of a find. Recording starts only after you start it and may continue while the screen is off or the App is not visible. Android shows an ongoing foreground-service notification; iOS may show system location indicators, notifications, and a Live Activity. The App does not start recording on its own.

Recorded GPS points, route geometry, find coordinates, timestamps, species, quantities, habitat details, and notes are stored in the App’s local database. They are not sent to Firebase Analytics or Firebase Remote Config. Eligible records and route files are also sent to our Firebase cloud service when you are signed in and have Premium.

3.2 Photos

If you attach a photo to a find, the App uses the system camera interface and stores a resized, re-encoded copy in private App storage. On supported development environments or system flows, a photo may instead be selected through the operating system’s photo interface. Boletus removes embedded image metadata, including location metadata, when it re-encodes the image. Photos are not sent to Analytics or Remote Config. A signed-in Premium account uploads them to Firebase Cloud Storage when photo upload is enabled; this setting is on by default and can be turned off or restricted to Wi-Fi.

3.3 Preferences, offline maps, and local statistics

Your language, theme, GPS profile, favourite species, notification choices, onboarding state, locally calculated statistics, and downloaded offline map regions are stored on your device. Theme, photo-attachment, and season-alert preferences can be synchronized with your Boletus account; GPS profile, photo-upload switches, the usage-statistics switch, and downloaded offline map regions remain device-specific. Season reminders are calculated locally from the bundled catalogue and your local history.

4. Information That Leaves Your Device

4.1 Online map requests

The default map provider is OpenFreeMap. A tile request identifies the portion of the map being viewed or downloaded. This can reveal an approximate area of interest, which is often near the user, but the request does not contain your saved route, find database, photos, or notes.

OpenFreeMap states that it does not store IP addresses in regular server logs, may temporarily enable IP logging for security incidents for up to 30 days, and may use Cloudflare. See the OpenFreeMap Privacy Policy. If the map provider changes, the replacement will receive the same types of request data and we will update this Policy.

4.2 Firebase Analytics

In a production build configured with Firebase, Analytics collection is enabled when the App starts unless we remotely disable it or you turn off “Anonymous usage statistics” in the App’s Profile screen; that switch stays off on that device until you turn it on again. Google Analytics automatically collects sessions, approximate geography derived from IP, app/device information, and a pseudonymous app-instance identifier. Events and these attributes can be associated with that installation, but Boletus does not set an account-level user ID.

On iOS, Boletus uses Firebase Analytics without advertising-identifier support. The iOS App does not link the AdSupport framework, access the IDFA, show third-party advertising, or use Analytics data to track a person across other companies’ apps or websites. On Android, the SDK may collect the Android Advertising ID when available and permitted, and Android Analytics data may support advertising measurement or audiences as described below.

Custom analytics events may include:

• screens viewed and actions performed;
• permission results and short technical error categories;
• GPS profile, theme, language, and whether photo attachment is enabled;
• outing duration, distance, point and find counts, GPS-quality ranges, and battery-use ranges;
• catalogue species identifiers, quantities, and whether optional find fields were used;
• offline-map download size and outcome; and
• GPX or backup success and aggregate item or size counts.

We do not put precise latitude or longitude, route geometry, town names, photos, note text, user-entered outing names, file paths, GPX content, or backup content into Analytics events. Google describes its default mobile Analytics collection in its Analytics data collection documentation.

4.3 Android advertising

The Android version may display advertisements supplied by Google AdMob and participating advertising technology partners. Depending on region, consent choices, device settings, and ad availability, ads may be personalized, non-personalized, limited, or contextual. The iOS version currently contains no advertising SDK and displays no third-party ads.

For Android advertising, the Mobile Ads SDK and participating partners may process the Android Advertising ID (AD_ID), Firebase or publisher identifiers, App name/version, IP address and approximate location derived from it, device model, operating system, language, network information, ad request data, consent signals, and ad impressions, views, clicks, and conversions.

Where law requires consent, Android uses a Google-certified consent flow before requesting personalized advertising or accessing advertising storage for that purpose. Google explains this processing at How Google uses information from sites or apps that use our services.

4.4 Firebase Remote Config

Remote Config uses a Firebase installation identifier and technical request information to return and cache operational configuration. It does not receive your routes, find coordinates, photos, or notes. See Privacy and Security in Firebase.

4.5 User-directed exports

A GPX file contains the route you choose to export. A ZIP backup may contain routes, finds, notes, preferences, and photos. These files are created only when you request them and are handed to the operating system’s share or document interface. The destination you select receives the file under its own privacy terms; we do not receive a copy.

4.6 System backups

If Android backup is enabled in your device and Google account settings, Android may copy eligible App data to your Google account. On iOS, iCloud Backup or a backup to a computer may include the App’s data if you have enabled it. These transfers are performed by Google or Apple, not by a Mondrus server.

4.7 Account and cloud synchronization

Signing in creates a Boletus account through Firebase Authentication. The App stores your account profile and registered-device details so it can associate data with the correct account. When Premium is active, synchronization may run automatically in the background or when you request it. It uploads outing and find records, precise coordinates, route geometry or track files, notes, timestamps, species and habitat details, and selected shared settings. Photos are uploaded only while the separate photo-upload setting is enabled; it is enabled by default. Photos and track files are stored in Firebase Cloud Storage, with related records in Cloud Firestore. These cloud records are private to your account and are not published to other users.

When Premium ends, new cloud uploads stop, but you can still sign in and download data already stored for your account. Signing out stops synchronization on that device without deleting local or cloud data. Disabling photo upload stops future photo uploads; photos already uploaded remain in your account until you delete the relevant content or account. Cloud synchronization is separate from Android system backup and from a ZIP export you choose to make.

4.8 Subscriptions and payments

On Android, Google Play sells, bills, and manages Boletus Premium. The App sends the purchase token and product identifier to our Firebase service, which checks the purchase with Google Play and stores the subscription entitlement, plan, expiry, and renewal status against one Boletus account.

On iOS, Apple’s App Store sells, bills, and manages Boletus Premium. The App sends the transaction and renewal information that the App Store signed to our Firebase service, which verifies Apple’s signature and stores the subscription entitlement, plan, expiry, and renewal status against one Boletus account. Each purchase carries an account token derived from your Boletus account, so the subscription can be linked to the right account; Apple does not receive your Boletus account identifier.

We do not receive your full payment-card or bank-account details on either platform. Linking a subscription to one account lets us grant or remove Premium access and prevent the same purchase from being linked to multiple accounts. Google and Apple process payment and order information under their own policies. Deleting a Boletus account does not cancel billing in Google Play or the App Store.

5. Device Permissions and Capabilities

You can revoke permissions in Android or iOS system settings, but related features may stop working.

6. How and Why We Use Information

We process information to provide requested features, create and secure optional accounts, store and synchronize data you choose to keep in the cloud, verify Premium, preserve settings, display maps, maintain reliability, understand feature use, improve the product, answer support requests, comply with law, and protect our rights and users. Android advertising data may additionally be used to deliver and measure ads, perform attribution, and prevent advertising fraud. The iOS version does not use collected data for cross-app tracking or advertising.

Where the GDPR or UK GDPR applies, our legal bases are performance of our agreement for requested App functions; legitimate interests in operating, securing, measuring, funding, and improving the App where those interests are not overridden by your rights; compliance with legal obligations; and consent where required.

7. Service Providers and Disclosure

We do not sell personal information. We disclose or make data available only as described here:

• Google LLC and Google Cloud: Firebase Authentication, Cloud Firestore, Cloud Storage, Cloud Functions, Analytics, Installations, Remote Config, Google Sign-In, Android advertising and Google Play billing services, and optional Android backup. See Google’s Privacy Policy and Firebase privacy information.
• Apple Inc.: App Store billing and subscription management, Sign in with Apple, and optional iCloud Backup. See Apple’s Privacy Policy.
• Android advertising technology partners: only when involved in selecting, delivering, measuring, or securing an Android ad.
• OpenFreeMap / Hyperknot Software Kft. and delivery providers: online map content and fonts.
• Your chosen export destination: only when you direct the system to share or save a GPX or ZIP file.
• Authorities or transaction parties: when reasonably necessary to comply with law, protect rights and safety, investigate abuse, or complete a corporate transaction, subject to appropriate safeguards.

The App does not currently use Firebase Crashlytics or Firebase Performance Monitoring. Google Play handles Android subscription payments and the App Store handles iOS subscription payments; our Firebase service verifies entitlements.

8. Retention and Deletion

• Local App data: remains until you delete records or offline regions, clear App storage, or uninstall. Android system backups and iOS device backups may remain separately under Google or Apple account settings.
• Boletus account and cloud journal: retained while your account exists, including previously uploaded data after Premium expires. When you delete your account, we delete its active cloud records, files, registered devices, authentication account, and linked entitlement data. Provider backups and records required for security, fraud prevention, dispute resolution, or law may persist for their applicable retention periods.
• Google Play and App Store payment records: controlled by Google or Apple and may remain after Boletus account deletion under their retention rules. We do not control their deletion.
• Analytics: user-level event data is retained for no longer than 14 months under our Analytics retention settings, unless a shorter period applies. Aggregated reports may remain longer.
• Android advertising data: retention depends on the advertising provider, purpose, consent status, and applicable law.
• Firebase installation identifiers: Google retains them according to Firebase retention and deletion procedures.
• Support correspondence: is retained only as reasonably necessary to answer requests, maintain support records, resolve disputes, and meet legal obligations.

Delete your Boletus account: In the App on Android or iOS, open Profile, scroll to “Delete cloud account”, and confirm. This deletes account data from our active cloud service but leaves the journal on that device. If you signed in with Apple, the iOS App also asks Apple to revoke the App’s access to your Apple Account before deleting. If you cannot access the App, request account or data deletion on this page; we may need to verify that you own the account before deleting it. Signing out or uninstalling does not delete cloud data. Account deletion does not cancel your subscription: cancel separately through Google Play subscriptions or App Store subscriptions. To stop future App collection, uninstall the App. Android users may also reset or delete the Advertising ID in device privacy settings. For other requests concerning data controlled by us, email [email protected]. Analytics is pseudonymous and associated with an installation rather than a Boletus account; if we cannot reliably identify the relevant record, we will explain that limitation.

9. Your Privacy Rights

Depending on where you live, you may have rights to request access, correction, deletion, restriction, portability, or objection; withdraw consent where processing is based on consent; and complain to a data-protection authority. We will not discriminate against you for exercising a privacy right.

California residents may request information about categories of personal information collected, sources, purposes, and recipients, and may request access, correction, or deletion as provided by law. We do not sell personal information for money. Android advertising disclosures for personalized or cross-context behavioural advertising may be considered “sharing” under some US state laws; applicable Android consent and privacy controls are provided where required. The iOS version does not perform cross-context behavioural advertising.

10. International Processing

Google, OpenFreeMap, their delivery providers, and Mondrus may process information in countries other than yours. Where required, transfers are protected through contractual safeguards, adequacy decisions, or other legally recognized mechanisms.

11. Security

Data sent to Firebase, Android advertising providers, and the map provider is transmitted using encrypted network connections. Firebase Cloud Firestore, Cloud Storage, and Authentication encrypt stored data. Cloud journal access requires authentication and is scoped to the account. Local data is protected by the Android or iOS application sandbox and device security. Exported files are protected by the destination you choose. No storage or transmission method is completely secure.

12. Children

Boletus is intended for adults and is not directed to anyone under 18. Android advertising requests are not intended to be treated as child-directed. We do not knowingly collect personal information from children. If you believe a child has provided information to us, contact [email protected].

13. Changes to This Policy

We may update this Privacy Policy as the App, providers, or law changes. We will post the revised version at this URL and update the “Last updated” date. Where required, we will provide additional notice in the App.

14. Contact Us

• Privacy contact: [email protected]
• Developer and publisher: Mondrus CCS Inc
• Application: Boletus for Android and iOS