PSB IDEAS · BUZZING BEE

Privacy policy

Effective November 17, 2026. This policy covers the Google Play edition of Buzzing Bee: Mock Location and its search service.

Who provides Buzzing Bee

Paul Steinberg LLC, trading as PSB Ideas, provides this location-simulation app. Contact support@psbideas.com or write to 418 Broadway STE N, Albany, NY 12207, United States. Our website is PSB Ideas. No Buzzing Bee account is required.

Locations and data on your device

The app reads device location to center the map. Saved locations, routes, groups, preferences, editing sessions, recent history and recorded simulated paths are stored on your device. Recent history keeps the last ten locations and ten routes. A recorded simulated path stays until replaced or deleted. We do not upload your saved route database to a publisher account or sharing feed. The Play edition has no user-to-user sharing service.

When you start simulation, the app supplies mock locations through Android. Other apps may receive those fixes under their own permissions and policies. Simulation can affect navigation, including Android Auto. Stop simulation before relying on real-location navigation; pausing continues supplying a simulated position.

Optional Google Drive backup

Subscribers can authorize Google Drive backup. With your permission, saved locations, routes, playlists and exported settings are uploaded to the private app-data area of your selected Google Drive account. Backups can contain precise selected coordinates and route geometry. Google processes this data under its privacy policy. Automatic backup, when enabled, runs approximately daily subject to Android scheduling and connectivity; the app retains the latest five backups. Use Cloud backup to restore or delete backups and disconnect automatic backup. Disconnecting does not itself delete existing backups; delete them separately. Notification-organizer history is excluded from backups.

Optional Buzzing Bee Lab notification organizer

The subscriber Lab offers an optional notification organizer, currently for Pikmin Bloom mushroom invitations. Capture is off by default and requires your explicit consent and Android notification access. Android grants access to notifications from all apps; Buzzing Bee filters for Pikmin Bloom before reading notification content. It saves the invitation sender, arrival time and a duplicate-prevention identifier only on your phone. Notification content is not sent to Firebase, advertising services, our servers, exports or cloud backups. History is limited to 500 entries; entries older than 30 days are removed when history is loaded or changed. Stop capture, revoke Android notification access, delete individual entries or delete all history using the organizer controls. These privacy controls remain available after subscription access ends. Clearing app storage or uninstalling deletes the local history. This independent feature is not affiliated with Pikmin Bloom or its publishers.

Required app updates

The production app uses Firebase Remote Config to retrieve the minimum supported app version. Google processes Firebase installation identifiers and app, device and connection information to provide this operational service, independently of optional Analytics. We do not send coordinates, routes, search text or notification content in these checks. A previously received update requirement is cached on your device and can prevent use of an outdated version until updated. Internal and preview builds do not use this enforcement service.

Maps, search and map links

Maps use OpenFreeMap and its resource hosts. Requests expose your IP address and requested map area, which may correspond to your real or selected location. Entering coordinates and reading full map links happen on your device. If you choose to open a shortened map link, the link is sent to its provider to resolve it; that provider receives connection information.

When you submit a place or address search, your query goes through our Cloudflare-hosted search service to Geoapify. Cloudflare processes your IP address, query and anonymous access credential to deliver and protect the service. Geoapify receives the query and the server connection, rather than a forwarded phone IP address. A query may contain location information or personal information you choose to enter. Avoid including unnecessary personal information.

The search service stores quota counters linked to a daily pseudonym of your network address and a random credential identifier. These records expire at the next UTC midnight and are removed by scheduled cleanup. Its database does not store raw IP addresses, search text, search results or bearer tokens. The anonymous credential is stored in private app preferences for up to 30 days and is excluded from app exports and Android backup. Cloudflare platform/security processing and Geoapify operational logs are separate from this database and follow the providers' policies. Geoapify describes successful-request log retention generally up to 24 hours. Search availability and limits are shared across users.

Advertising and choices

The free edition uses Google AdMob banner and rewarded ads. Google advertising services may process IP addresses and inferred approximate location, device or advertising identifiers, app/ad interactions and diagnostic information for advertising, measurement and fraud prevention. The app does not attach saved routes, favorites or route names to ad requests. An active ad-free subscription removes banner and rewarded ads.

Google's User Messaging Platform manages applicable consent and opt-out messages. When available, use Ad privacy choices in the app to review your choices. Android also provides advertising-ID controls. Refusing personalized advertising does not necessarily stop all advertising-related processing. The app turns off ad personalization for its ad requests and requests general-audience ad content. These settings do not stop all advertising-related data processing. We do not sell saved route databases. Advertising partners' processing may be considered a sale, sharing or targeted advertising under some privacy laws; use the applicable privacy choices to opt out.

Optional crash reporting

Production versions offering Share crash reports use Firebase Crashlytics only for optional diagnostic reporting. Automatic report upload is off by default and requires an adult user to enable it separately from Analytics, advertising choices and news alerts. Reports can include crash stack traces, app-not-responding diagnostics on supported Android versions, app and operating-system versions, device model and runtime information, timestamps, and a Crashlytics installation identifier. The SDK may fetch service configuration and hold diagnostics locally while automatic report upload is off. We use reports to identify and fix stability problems.

We do not add saved locations, coordinates, routes, favorites, search text, email addresses or account identifiers to crash reports. The app strips exception-message text from uncaught exceptions passed through its application crash handler; stack frames and exception types are retained. If you separately enable usage reporting, supported Analytics events may appear as diagnostic breadcrumbs. Internal, preview and debug builds do not include Crashlytics. Turn Share crash reports off to stop future automatic report uploads and request deletion of queued unsent reports; this does not delete reports already received by Google. Correcting your age range also disables reporting. Google processes diagnostic data under its Firebase privacy and data-processing terms.

Report a problem

This optional menu opens a support form. You can review your description and choose whether to include the app version, phone manufacturer and model, and Android version. No logs, routes, coordinates or unique device identifiers are automatically attached. The app opens a draft in your email application; you decide whether to send it. Your email provider handles the draft and delivery under its own policies. Do not include passwords, payment information or unnecessary private locations. Copy report puts the reviewed text on your device clipboard if you choose that action.

Optional news notifications

Production versions offering News & updates can receive optional Firebase Cloud Messaging alerts about app news and releases. Alerts are off by default and separate from Analytics and advertising choices. Enabling them registers a Firebase installation identifier and messaging token with Google; Google also processes device, app and connection information to deliver messages. We do not attach your locations, routes, favorites or search text. Disable News notifications on that page to stop alerts and request token deletion; network-dependent cleanup may complete when connectivity returns. Android notification settings also control display. Internal and preview builds do not include Firebase Messaging.

The News page and version-update dialog request a public news feed from our Cloudflare service without a Buzzing Bee account or Analytics opt-in. Cloudflare receives connection information, including the IP address, to serve and protect the feed. Posts are cached on your device for offline reading. Notifications are optional and delivery is not guaranteed.

Optional usage reporting

Production versions that offer Share usage reports in Privacy & app behavior use Google Analytics for Firebase only after a user aged 18 or older opts in. This setting is off by default and is separate from advertising consent. Internal and preview builds do not include Firebase Analytics. Earlier production versions without this setting do not send these Analytics reports.

When enabled, Google processes an app-instance identifier, device and app information, session and engagement activity, approximate region derived from connection information, and Attractions opens and rewarded-ad outcomes, including numeric error codes. The SDK may also report in-app purchase activity, such as product identifiers, amounts and currency; this does not include payment card information. We do not send Analytics your name, email, selected places, coordinates, routes, favorites or search text. We disable Analytics advertising-ID collection, automatic screen reporting and advertising personalization. Reports are used to understand feature use, diagnose ad availability and improve the app. The production Firebase app is linked to AdMob so their reports can be used together.

You can withdraw consent at any time by turning off Share usage reports. This stops future Analytics collection and resets the local Analytics identifier and data; it does not itself erase reports already processed by Google. Correcting your age range also turns reporting off. Analytics retention and deletion follow the configured Google Analytics controls and Google's applicable policies. Contact support@psbideas.com for help with a data request; we do not associate Analytics identifiers with an email account and may not be able to locate a particular report from your email alone. Advertising and map/search processing described elsewhere continue under their own settings.

Complimentary access

If PSB Ideas provides a complimentary ad-free code, the app verifies its digital signature locally and stores it in private app storage. The code is not sent to a publisher server and is excluded from app backups and exports. It has no expiry. Remove complimentary access in Subscription or clear app storage to remove it; keep the code if you want to restore access. Redeeming or removing a code does not cancel an existing Google Play subscription.

Subscriptions and route rewards

Google Play handles payments and billing details. Buzzing Bee queries subscription purchase records, verifies purchase signatures locally and acknowledges completed purchases to provide ad-free access. It does not receive your payment card details or send purchase records to a publisher billing server. Restore purchases checks Google Play. Subscription entitlements are not included in backups.

For rewarded route starts, the app stores reward eligibility, the first successful start time and device boot information locally to manage the three-minute correction window. These values are not exported in backups. An active route continues after that window ends.

Permissions and controls

Location access and Android mock-location setup support the simulation workflow. Notifications show active sessions and a Stop action. Optional display-over-other-apps permission enables the floating joystick; it receives touches in its own window and does not inject keyboard input into other apps. Optional stability settings can increase battery use. User-enabled recovery can display a reminder to reopen the app after a restart or interrupted session.

Buzzing Bee data deletion

To request deletion of information held by Paul Steinberg LLC (PSB Ideas), email support@psbideas.com with the subject Buzzing Bee data deletion. Describe the information you want removed, such as a previous support message, and contact us from the associated email address where possible. Do not send passwords, payment details, search access tokens or unnecessary location history.

We can delete identifiable support correspondence and attachments we hold, subject to records we must retain for applicable legal obligations or resolving a dispute. We will explain any applicable exception and retention period in our response. We cannot look up your local saved routes through a server account because Buzzing Bee has no such account. Search quota records expire at the next UTC midnight; they are not a stored search history. Providers' operational, security, advertising and Google Play billing records are governed by their own retention and rights procedures linked below.

For data on your device, delete saved items and recorded paths or clear recent history in the app. Android Settings → Apps → Buzzing Bee → Storage → Clear storage removes app-local data, including local preferences and the search credential. Exported copies must be deleted separately from your chosen destination. Uninstalling or clearing app storage does not cancel a subscription: manage or cancel it through Google Play.

GPX and JSON exports can contain precise selected locations, route geometry, names and groups. They are written to a destination you choose, which may be a cloud document provider. Recent history and search access credentials are not included in backups.

Support, rights and international processing

If you contact us, we receive the email address, message and attachments you send and use them to respond. We retain support correspondence as needed to resolve the request, maintain relevant business records and meet applicable obligations. You can request access, correction or deletion of information we hold about you, or exercise other rights available under the laws where you live, by contacting support@psbideas.com. We may need proportionate information to verify a request. You may also contact the relevant privacy regulator. Service providers handle their own records and applicable requests.

We process information to provide requested app functions, manage purchases and support, protect services, honor your choices and meet applicable obligations. Service providers may process information outside your country. App-configured map and search connections use HTTPS. No security measure can guarantee absolute protection.

Age range and advertising protections

Starting with version 1.26.9, the app asks for an age range before opening its main screen. We do not ask for a birthday or identity document. The selected range stays in private app storage and is not included in route exports or app backups. It is used to configure age-treatment signals sent to Google advertising services. Ages 13–15 receive the more restrictive under-consent ad treatment; ages 16–17 receive teen ad treatment. Personalization is disabled for all age ranges. A self-declared range is not independent age verification. You can correct it in Privacy & app behavior; doing so stops any active simulation before asking again. Selecting under 13 prevents entry to the app. These settings do not grant a free subscription or bypass rewarded route access.

Audience and changes

Buzzing Bee is intended for users aged 13 and older and is not directed to children under 13. Contact us if you believe a child has supplied personal information to us. We will update this page when our practices change and show the revised effective date.

Provider information