BloomingBitz Privacy Policy
BloomingBitz is developed and operated by Shibil Poulose under the EspeeLabs brand.
BloomingBitz turns walking into the gradual discovery of artwork. This policy explains how information is handled when you use the app, share a Bloom, view rewarded advertisements, or contact support.
Walking information and local storage
With your permission, BloomingBitz uses Apple’s Motion & Fitness services to count steps and recover eligible walking progress.
The app stores information on your iPhone, including:
- walking sessions, step counts, dates, artwork progress, optional labels, and received Bloom Codes (including their encoded personal messages)
- lifetime and recent credited walking totals used for the welcome greeting, together with which greeting was last shown
- a Bloom Code and personal message temporarily saved until you tap Done; historical sharing records may also remain
- the Celebration Sounds preference
Lifetime and recent totals are derived from credited walking already stored on this device. They are not a second pedometer and do not include paused time or advertisement rewards.
BloomingBitz has no user accounts or app-operated backend. The app does not upload your walking records, labels, or walking totals to a BloomingBitz server. BloomingBitz does not use HealthKit, the iPhone location permission, contacts, or your photo library.
Walking and History work offline. Advertising and consent features require a network connection.
Motion & Fitness permission
BloomingBitz requests Motion & Fitness access when you start walking progress. You can change this permission in iPhone Settings.
If access is denied, step counting and recovery may be unavailable. Saved records and History remain accessible. iOS limits how much motion history is available to the app. Where coverage is missing, BloomingBitz reports that rather than estimating steps.
Rewarded advertisements and consent
Send a Message offers optional rewarded advertisements through Google AdMob. Each new personalized Bloom Code requires a rewarded advertisement. It grants no artwork entitlement or walking credit. Personal walking does not require viewing advertisements.
Google’s advertising and consent services may process information such as device identifiers, IP address, approximate location inferred from IP address, advertisement interactions, and diagnostic information. The information processed depends on the SDK, your choices, and the advertising configuration.
The app may contact Google’s consent service at launch, before you choose to view an advertisement. Advertising services may also communicate with Google when preparing or displaying advertisements.
BloomingBitz does not supply your walking records, walking totals, or local labels, or personal message content to Google’s advertising SDK. Ad requests are configured to request non-personalized advertisements. Such advertisements can still involve data processing for delivery, frequency capping, aggregated reporting, security, and fraud prevention.
BloomingBitz does not currently present Apple’s App Tracking Transparency prompt.
Where applicable, consent choices are presented through Google’s consent tools. Privacy Options appears in Settings when required by those tools.
Read more about Google’s practices at https://policies.google.com/privacy and https://policies.google.com/technologies/partner-sites.
Sharing Bloom Codes and personal messages
When you choose Share Bloom, the app passes an invitation containing a Bloom Code to the sharing destination you select. Copy Bloom Code places the Bloom Code on your clipboard. A Bloom Code contains the encoded personal message and bundled artwork identity, with no expiry. It does not include walking records, local labels, or a rendered artwork image.
Anyone holding a valid Bloom Code may import it on their installation. The app unlocks message reading at the recipient’s first milestone, including in supported History details. This is a user-experience mechanism, not encryption: the message can be decoded outside the app. A Bloom Code does not authenticate the sender or prove walking. Recipients cannot re-share through the app, but copies already outside the app remain usable. Sharing destinations handle information according to their own policies.
Backups, retention, and deletion
Saved walking and recipient records remain on your device until you delete the BloomingBitz app. A saved pending sender transaction survives restart, but tapping Done removes local retrieval even if you never shared it. There is no new Sent history or long-term sender retrieval. Copies you already shared or saved remain usable; Done cannot delete those copies. If the app closes before your Bloom Code is saved, you will need another ad to create a new one. Finishing a Bloom closes it. Closed Blooms with at least 100 walked steps appear in History. The app does not currently offer a separate control to erase History while the app remains installed.
Deleting the app removes its local app data from the device. Device backups may retain copies of BloomingBitz records. Restoring a backup may restore those records. You can manage backups through Apple’s settings.
Backup copies and information processed by third-party services are subject to their respective settings and retention practices. BloomingBitz has no server copy from which to recover your progress.
Support enquiries
If you email support, we receive the sender’s email address and the content of the message. We use that information to respond. Support email is handled through Microsoft Outlook.
Please avoid sending sensitive information or screenshots containing information you do not want to share.
Changes to this policy
We may update this policy when the app or its information practices change. The published policy will show its effective date.
Contact
For privacy questions or support, email ourfamspace@outlook.com.
BloomingBitz is developed and operated by Shibil Poulose under the EspeeLabs brand.