This notice explains how Oxelon handles information when you plan wedding floral boards, venue zones, bloom formulas, props, procurement notes, production timing, sign-off checklists, settlement figures, and design-versus-completion photo comparisons on your device.
Scope: Oxelon iOS application (local-first floral wedding workspace)Questions: [email protected]Published: This notice became effective on September 10, 2026.
What Oxelon Is Built To Hold Oxelon is a device-side workspace for florists and setup crews. You can create wedding archive boards, attach cover imagery, map Welcome / Ceremony / Table zones on a venue floor plan, keep bloom ratio formulas, calculate material gaps, track props and supplier arrivals, schedule production runway timing, complete phase sign-offs, record settlement totals, and compare design stills with completion photos.Local project boardsSandbox photosNo mandatory accountNo advertising ID tracking prompt Information That May Appear On Your Device Depending on the modules you use, Oxelon may store the following categories locally: • Wedding board text. Titles, client names, venue names, event dates, stage labels, notes, favorites, and similar project fields you enter. • Workspace records. Project briefs, zone names and types, bloom formula lines and ratios, material calculator lines, prop inventory, supplier and batch notes, arrival readiness, staff assignments, timeline slots, loss notes, checklist items, settlement amounts, and activity log summaries. • Media you choose to add. Cover photos, floor-plan images, prop or arrival stills, design and completion comparison photos, plus generated thumbnails. Images are written into Oxelon sandbox folders; models store relative paths rather than remote URLs. • Operational preferences. Lightweight values needed to run the atelier experience, such as balance counters and fulfillment markers kept on device. • Export packages you create. If you export or restore a JSON backup, that package may contain project metadata and related records you choose to share or re-import. Photos are not embedded in the JSON export and remain in the app sandbox unless you export imagery separately.Oxelon does not require registration or sign-in. There is no mandatory user account, password vault, or cloud profile system inside the app. Permissions You May Grant On iOS Access is requested only when you start a related action: • Camera. Used when you capture a cover, floor plan, arrival still, or completion photo for a wedding board. • Photo Library. Used when you import an existing still into covers, floor plans, props, arrivals, design slots, or completion slots. • Photo Library Additions. Used only if you choose to save a comparison image out to Photos. Oxelon does not request microphone access and does not present an App Tracking Transparency prompt for cross-app advertising tracking. You may refuse a permission; related capture or export features will remain unavailable until you allow them in iOS Settings. How Local Data Supports The Floral Loop • Keep each wedding archive coherent across Hub, Archives, Production, and Settings surfaces. • Refresh lists and boards after you edit zones, formulas, checklists, or settlement figures. • Show thumbnails in boards while loading larger images where needed for floor plans or Reality Mirror comparison. • Preserve activity history so studio-wide and project-level changes remain reviewable on device. Where Records Live And Whether They Leave The Device Project JSON, relative media paths, and related atelier files are stored in the application sandbox on your iPhone or iPad. Oxelon is designed as a local-first tool without a required backend account. Network activity may occur when the system loads Settings legal pages in an in-app web view, when Apple frameworks perform platform commerce or restore operations, or when you use iOS share / Files flows to move a backup you initiated. Oxelon does not operate a proprietary social feed or map tracking network as part of the floral workspace. Parties That May Touch Device Or Platform Layers • Apple. Operating-system permission prompts, Photos, Files, Share Sheet, and App Store platform services may process limited technical information under Apple policies. • You and people you choose. If you share an export file or a photo, recipients receive only what you send. • Web destinations you open. Privacy Policy and Terms links opened in the in-app web view are governed by those destinations while displayed. We do not sell wedding board contents as a marketing list. Any disclosure required by applicable law would be limited to what those laws compel. Retention, Deletion, And Studio Housekeeping Records remain on your device until you delete a wedding archive, remove a nested item, clear related media, uninstall the app, or overwrite data through a restore you perform. Deleting a project is intended to cascade nested atelier records and exclusive images associated with that board. Shared floor-plan images follow the app’s parent/child cleanup rules so removing a zone ribbon does not erase the underlying venue map. Uninstalling Oxelon generally removes sandbox data for that installation. Backups you previously saved outside the app (for example via Files or Mail) remain under your control. Practical Choices Available To You • Decline camera or library access and continue using text-only modules. • Delete boards, zones, props, arrivals, checklist rows, or comparison photos from within Oxelon. • Export metadata backups without embedding photos, or keep work entirely on device. • Email [email protected] with privacy questions about this notice. Children And Professional Use Oxelon is oriented toward professional floral wedding planning workflows. It is not directed to children under 13 (or the equivalent minimum age in your jurisdiction). Do not knowingly store information about children in wedding boards beyond what a lawful professional engagement requires. Security Posture We apply reasonable technical and organizational measures appropriate for an on-device atelier app, including sandbox storage and relative-path media handling. No method of electronic storage is perfectly risk-free. Protect your device passcode and be careful when sharing export files. Updates To This Notice If Oxelon’s data practices change in a material way, this page will be revised. The effective date above helps you see when the current wording took effect. Continued use after an update means you have read the revised notice. Governing Framework Privacy questions arising from Oxelon are handled under applicable laws of the United States and other jurisdictions where the app is offered, together with relevant regulatory requirements. Disputes may be addressed through competent dispute resolution bodies as those laws provide. For atelier privacy correspondence, write to [email protected].