Overview
DigiBouquet is an iOS app for creating and sharing private digital flower bouquets. The app is intentionally designed to avoid accounts, public submissions, social feeds, and server-side bouquet galleries. A sender can choose flowers, greenery, a card style, a mood, and a message, then save the bouquet locally or share a compact link. In the current model, the bouquet content is encoded into the shared URL rather than uploaded to a DigiBouquet database. This policy describes that model in plain language so users can understand what happens before they create or open a bouquet.
This policy applies to the DigiBouquet iOS app and the DigiBouquet informational website at https://digibouquet-ios.pages.dev. The website is hosted on Cloudflare Pages. The app and site may evolve, and this policy should be updated if the product later adds accounts, analytics, cloud sync, payments, support forms, custom domains, Universal Links, or other services that collect additional information.
Information you create
When you create a bouquet, you may enter a recipient name, sender name, and card message. You may also choose flower counts, greenery, color mode, card style, theme, and arrangement seed. This content is personal because it can describe a relationship, emotion, occasion, or recipient. DigiBouquet is designed so this bouquet payload can be encoded in a share URL. That means anyone who receives or obtains the link may be able to open the bouquet content in the app or compatible viewer. Treat bouquet links as private messages, not as secret or access-controlled documents.
If you save a bouquet in the app, it is stored locally on your device using app storage. Local storage means it may be included in device backups depending on your device settings, operating system behavior, and backup provider. DigiBouquet does not need an account to keep those local saves. If you delete the app, clear device data, restore a device, or change backup settings, local bouquets may be lost or carried forward according to iOS behavior.
Information we do not intentionally collect in v1
The current app is designed not to create user accounts, not to require a login, not to sell personal information, not to run a public bouquet feed, not to upload bouquet contents to a DigiBouquet server, and not to process payments. The app also does not need your camera, microphone, location, contacts, or photo library to create a bouquet in the current design. If a future version asks for additional permissions, the request should be explained at the point of use and reflected in an updated privacy policy.
DigiBouquet does not intentionally collect sensitive categories of personal information through the app. However, a user may choose to write sensitive content inside a card message. Because shared bouquet links can contain the message payload, do not write information in a bouquet that you would not be comfortable sending through the chosen messaging channel. The app cannot control what a recipient does with a link after receiving it.
Website and hosting data
The public website is hosted by Cloudflare Pages. When someone visits the website, standard web infrastructure may process technical information such as IP address, browser type, user agent, requested URL, timestamps, referrer information, and basic security signals. This information is used by hosting providers to deliver pages, protect the service, diagnose issues, and operate the network. DigiBouquet's static website does not require a login, does not include a contact form, and does not need cookies for core page viewing.
Static assets such as generated hero images, flower images, stylesheets, and HTML pages may be cached by Cloudflare and by the visitor's browser. Caching improves load time and reduces repeated downloads. It does not mean the website knows who created a bouquet in the iOS app. Website visits and app-created bouquet payloads are separate parts of the product unless a future version introduces a connected backend.
Sharing and third-party services
When you share a bouquet, you choose the sharing channel. That channel may be Messages, Mail, a social app, a workplace chat, or another third-party service available on your device. Those services are not operated by DigiBouquet. Their privacy practices, retention rules, link preview behavior, and account systems are governed by their own policies. If a service generates link previews, syncs messages across devices, scans links for safety, or stores message history, that may involve the bouquet URL you shared.
If you open a bouquet link, the link itself may contain the bouquet content. If you forward the link, post it publicly, paste it into a shared document, or allow another app to preview it, you may be revealing the bouquet content to others. DigiBouquet's private-by-default design reduces the need for a public feed, but privacy still depends on how links are handled after sharing.
Children, retention, rights, and changes
DigiBouquet is not designed for children under 13 and should not be used to knowingly collect personal information from children. Because the current app does not maintain user accounts or a server database of bouquet content, DigiBouquet may not be able to identify or delete a specific bouquet after it has been shared as a URL. You can delete locally saved bouquets from your device where the app provides that control, and you can manage message history through the third-party service where you sent the link.
Depending on where you live, you may have privacy rights related to access, deletion, correction, portability, objection, restriction, or opt-out of certain uses of personal information. Because the current product is intentionally minimal, many requests may be limited by the fact that DigiBouquet does not have an account record to search. If you have a privacy question, contact the developer through the distribution channel where you received the app. This policy may change as DigiBouquet changes. Material changes should be reflected by updating this page and the effective date.