1. Planning information
BunchMath processes flower names, wholesaler bunch sizes, on-hand stem counts, arrangement names and recipes, batch quantities, and an optional breakage buffer. It uses these values to total needs, subtract stock, round shortages to complete bunches, and estimate stems remaining.
The app does not require an account, client records, contacts, photos, location, notifications, or health and payment information.
2. Storage and transfer
- Flowers, recipes, stock counts, and the current batch are stored in local app storage on your device.
- ORBIS does not operate a backend that receives this planning data and does not send it to an external AI service.
- Deleting entries in the app or removing the app's data from the device removes the corresponding local records, subject to device backups you control.
3. Advertising and consent
BunchMath uses Google Mobile Ads and Google's User Messaging Platform. Depending on your region and choices, Google and its advertising partners may process device, network, consent, advertising, and ad-interaction information under their own policies to request and measure ads.
Where required, BunchMath asks for consent before requesting ads and offers privacy choices again from the app. Permission for personalized tracking may be requested only when applicable. Declining consent or tracking does not block planning features.
4. Support and retention
- You can choose not to send a support email.
- If you contact us, we use the email address and message only to handle the request and related follow-up, then retain it only as reasonably necessary for that purpose or legal obligations.
- Do not send client identities, supplier contracts, payment information, advertising identifiers, or private event details in a support request.
5. Operator and contact
- Service and operator: BunchMath by ORBIS
- Privacy and support: orbisflux@gmail.com
- Company website: orbisunus.com
6. Policy changes
If data practices materially change, this page and the in-app notice will be updated before the change applies where required. Revision and effective date: August 15, 2026.