AisleSide

Privacy Policy

Last updated:

This policy explains how AisleSide handles information when you use its wedding setup and teardown features. Event records and imported attachments are processed and stored on your device. The app does not require an account or automatically send your event content to the developer.

1. Information you enter and import

You choose what to record. This can include event and host names, dates, venue addresses, access times, contact details typed into fields, zone instructions, reference images, venue PDFs, inventory, quantities, task assignments, notes, completion records, on-site changes, approval names, and handoff details. A venue address is manually entered information; the app does not obtain your device location.

AisleSide uses this information to display and update your books, relate tasks and items to zones, preserve changes, calculate progress, and generate the exports you request. Names entered for completion or approval are record labels and are not identity verification or electronic signatures.

2. Local storage and preferences

Event records, photos, original imported venue PDFs, change histories, and export metadata are saved in the app's local storage. Unfinished form entries, including selected attachments where applicable, may also be saved locally so that you can resume editing. Your progress-record name and initialization preferences are stored in device preferences.

Imported photos may be resized and compressed. Imported files are copied into the app's records, rather than remaining dependent on the original file's location. PDF exports and event archives are also saved locally when generated. Older data files may be retained locally during migration or recovery.

AisleSide does not operate its own cloud backup or synchronization service. Apple device backups and any storage provider you select may handle app data or exported files according to your device settings and that provider's terms.

3. Camera, Photos, Files, and voice input

These attachment and voice input features are optional. You can create and use text-based event records without them. The app does not request location, contacts, notification, Bluetooth, or Health data access.

4. Exporting and sharing

Generating a PDF or archive does not automatically upload it. The iOS share sheet lets you choose whether to save or send a generated file through another app or service. Your selected destination handles that file under its own policies.

Exports may contain names, venue details, photos, assignments, notes, approval records, and other content within the selected scope. A complete event archive includes event records and embedded attachments, including retained change history and export metadata. Previously generated PDF files are separate from the archive. Check the contents and recipients before sharing. AisleSide cannot recall files already sent or delete copies held by recipients.

5. Third-party software and diagnostics

The app uses Apple's system frameworks and SnapKit, a library for arranging the interface. It contains no advertising, tracking, analytics, or remote crash-reporting SDK. It does not sell event information or use it for advertising.

The app may write a local system diagnostic message if initial content cannot be saved. It does not implement a developer-operated log-upload service. Apple may handle device diagnostics according to your Apple settings and policies.

6. Retention and deletion

Saved books remain available until you delete them. Archiving an event changes its status; it does not delete its content. Use the event book menu and Delete event to remove an event from the active local database. Item and attachment removal controls remove their selected content from current records; retained change history may still contain earlier details or photos.

Deleting an event does not automatically erase generated exports, migration or recovery copies, unfinished form storage, or files saved outside the app. The app does not provide a single control to erase all of these categories. Deleting the app through iOS removes its local app data; offloading it can retain data. Exported files, external copies, and device backups must be managed separately in Files, the relevant service, or your Apple settings. Photos added with Save to Photos remain in your system photo library after you remove the attachment, delete the event, or delete the app; delete those copies separately in Photos.

There is no server account to delete. The developer cannot retrieve, edit, or erase books held only on your device.

7. Email support and external pages

If you email support, we receive your email address, message, and any attachments you choose to send. We use that correspondence to respond to your request and investigate the issue. Do not send a complete event archive or other people's personal details unless needed for your request. Email is handled through the email providers involved and may be retained as part of the support correspondence.

Links opened in your external browser are handled outside AisleSide. Browser and website data practices are governed by their respective providers. This policy concerns the app and support correspondence; it does not promise that a hosting provider or external website collects no access information.

8. Changes to this policy

This page may be updated when the app's information handling changes. The Last updated date identifies the current policy.