NoteBeeZField intelligence for better beekeeping

NoteBeeZ Account and Data Deletion

Last updated: 4 September 2026
Version: 2026-09-04

This page explains how a NoteBeeZ user can delete a cloud account, a cloud organization, and local Android data. These are separate actions. Deleting one does not necessarily delete the others. Applicable deletion controls remain available after subscription expiry, subject to authentication, role, ownership, scope, confirmation, and provider-cancellation safeguards described below.

Before deleting anything

Deletion can remove data needed for apiary operations, audits, treatment history, taxes, animal-health duties, or legal compliance. Before deletion:

  1. create and download any authorized organization export you need;
  2. save a local JSON/CSV backup if appropriate;
  3. confirm that the downloaded files open and contain the expected media;
  4. if somebody else needs the records, provide an authorized export before deletion—the current app does not support transferring organization ownership;
  5. review linked Google Calendar events; and
  6. check the Google Play subscription directly.

Exports are sensitive and are no longer protected by NoteBeeZ after you save or share them.

Delete a cloud account in the app

  1. Sign in to NoteBeeZ.
  2. Open Settings.
  3. Open the Privacy and storage section.
  4. Choose Delete cloud account.
  5. Enter DELETE and confirm.

If the account is the owner of any active organization, account deletion is blocked. The current app does not support ownership transfer, so the sole owner must first export any records that must be kept and delete every owned organization. Organization deletion also removes access for its other members.

Confirmed cloud-account deletion:

Organization records created by that account may remain in an organization controlled by somebody else. Their active author reference is removed where the database relationship permits, but the business record and organization activity history may remain until the organization is deleted. This protects shared records from being silently destroyed by a departing member.

Delete a cloud organization in the app

Only the organization owner can delete it.

  1. Sign in and select the organization.
  2. Open SettingsPrivacy and storage.
  3. Choose Delete cloud organization.
  4. Enter the organization's full displayed name and confirm.

Before making the organization inaccessible, NoteBeeZ asks Google Play to stop future renewal of the linked organization subscription. If that provider action cannot be confirmed, the deletion request fails visibly so an ongoing renewal is not silently abandoned. You should still verify cancellation in Google Play.

After confirmed organization deletion:

The delay protects against interrupted cleanup and gives the system time to complete coordinated deletion. The Service does not promise restoration during this period. Once purged, the organization and its D1 records cannot be recovered by NoteBeeZ.

Delete local Android data

Cloud-account or organization deletion does not remotely erase data that is stored locally on an Android device or in a user-created file.

In NoteBeeZ, open SettingsPrivacy and storageDelete all diary data and confirm. This deletes the local diary, private local audio/photo files, and automatic migration/restore recovery copies on that device. Alternatively, Android system settings can clear NoteBeeZ storage or uninstall the app.

Deleting local data does not delete an existing cloud organization. If the device signs in and synchronizes again before the cloud organization is deleted, authorized cloud data may download again.

Delete separately any exports, spreadsheets, PDFs, QR labels, backups, attachments, or shared copies that you saved outside NoteBeeZ. We cannot recall copies received by another authorized user or held in another service.

Request deletion without access to the app

Email notebeez@badluckstudios.com from the address associated with the account and state that you are requesting deletion of your NoteBeeZ cloud account. Do not send a password, magic link, access token, purchase token, full export, or identity-document copy unless we specifically request a proportionate verification method.

We must verify that the requester controls the account and has authority for any organization-level action. If the email account is unavailable, describe the issue and provide only the minimum information needed to propose a secure verification route. We may refuse organization deletion requested by a person who cannot demonstrate owner authority.

Public deletion page: https://notebeez.badluckstudios.com/account-deletion

Google Play subscription cancellation

Deleting NoteBeeZ, clearing storage, leaving an organization, or deleting a non-owner account does not by itself cancel a Google Play subscription.

On Android, open Google Play → profile → Payments & subscriptionsSubscriptionsNoteBeeZCancel subscription, or use Google Play subscription management. Use the same Google account that made the purchase. Cancellation normally stops the next renewal while access continues through the paid period. Refund and immediate-cancellation rights vary by law and the Play offer.

Organization deletion is designed to request cancellation before deletion proceeds, but the buyer should verify the result directly in Google Play. Uninstalling the app is never sufficient.

Google Calendar cleanup

If you want NoteBeeZ to attempt removal of linked NoteBeeZ-owned events, use the explicit Disconnect Google Calendar action before deleting the account or organization. That disconnect action attempts event removal and OAuth revocation. Account or organization deletion revokes/removes stored OAuth credentials and local links, but it does not promise provider-event deletion. If Google access was already revoked, the selected calendar was deleted, Google was unavailable, or deletion was performed without disconnecting first, external events may remain. Review and delete them directly in Google Calendar if necessary. Google independently controls its account and security records.

What may be retained

Legal retention is limited to what is necessary and does not justify retaining unrelated diary content. Further detail is in the Privacy Policy.

Timing and confirmation

An in-app account deletion response is immediate. An organization is inaccessible immediately and its production D1 purge is scheduled for 30 days after confirmation. Email requests are handled without undue delay after identity and authority verification; GDPR requests are generally answered within one month, subject to a lawful extension for complexity or volume.

If a deletion operation reports an error, do not assume it completed. Keep the displayed request identifier, retry when appropriate, and contact notebeez@badluckstudios.com with redacted details.