Privacy Policy
Tied in Bloom is designed so the developer does not receive your wedding plans. This policy explains what the app processes on your device and in Apple's iCloud, what happens when you share or export information, and what limited information the developer may receive if you contact support.
1. Summary
- No developer accounts, advertising, tracking, or third-party analytics.
- The developer does not operate a server that receives your wedding data.
- Wedding data is stored on your device and, when iCloud is available, in your private iCloud database through Apple's CloudKit.
- You control partner invitations, contact selections, notifications, exports, and deletion.
For Apple's App Privacy disclosure, the developer selects Data Not Collected. Apple may process information through the App Store, iCloud, and device services under Apple's own policies. Apple-collected data is not data collected by this developer for the App Privacy label.
2. Information processed by the app
Depending on what you choose to enter or import, the app may process:
- your and your partner's names, wedding date, guest estimate, and preferences;
- checklist items, notes, deadlines, and completion status;
- budget amount, currency, expenses, vendor names, payment status, and notes;
- guest names, groups, RSVP status, plus-one status, notes, and postal addresses;
- seating tables, seat assignments, and wedding-day schedule; and
- app settings, such as appearance and reminder time.
This information is used only to provide the planner features you request. The developer does not receive it.
3. On-device storage, widgets, and iCloud
The app stores wedding data locally using Apple's Core Data framework. A small snapshot needed for the home-screen widgets is stored in an Apple App Group on your device so the widgets can display the countdown, RSVP totals, and upcoming tasks.
When you are signed in to iCloud and iCloud is available, Apple CloudKit syncs the app's records through your private iCloud database. Apple, not the developer, operates iCloud and processes that data under the agreements and privacy terms associated with your Apple Account. The developer does not have an administrative dashboard or server access to read your private CloudKit records.
4. Partner sharing
If you invite another person, Apple's CloudKit sharing feature makes the selected wedding and its connected plans available to that participant. The participant can view and edit the shared plans. The wedding owner chooses whom to invite and can manage or stop sharing through the app's Settings screen and Apple's sharing interface. Once sharing stops, the participant loses access to the shared CloudKit records, although copies they previously exported, copied, or recorded are outside the app's control.
Do not share plans with anyone you do not trust. You are responsible for having permission to add and share other people's personal information.
5. Contacts and file imports
When you choose From Contacts, Apple's out-of-process contact picker lets you select specific contacts. The app receives only the selected contact's name and, when available, the first postal address. It does not request broad access to or scan your address book, and it does not receive selected contacts' phone numbers, email addresses, birthdays, or other fields.
When you choose a CSV or text file, the app reads the file you selected to create guest records. The import is performed on device. The source file is not uploaded to the developer.
6. Notifications
If you enable reminders and grant notification permission, the app schedules local notifications on your device for incomplete checklist items with due dates. The developer does not send remote marketing notifications and does not receive your reminder content.
7. Exports and the share sheet
The app can create guest-list, budget, day-plan, and seating-chart files on your device. Text and CSV exports are written to the app's temporary directory, which iOS manages. When you open the Apple share sheet, you choose the destination. The receiving app, service, person, or organization handles the export under its own terms and privacy practices. The developer does not receive a copy.
Review exports before sending them because they may contain personal or financial information about you, guests, or vendors.
8. Information received outside the app
If you email support or send TestFlight/App Store feedback, the developer may receive information you voluntarily provide, such as your email address, message, attachments, screenshots, and diagnostic details supplied by Apple. This information is used to answer the request, troubleshoot, prevent abuse, and comply with law. Do not include wedding plans or other sensitive personal information unless necessary for support.
Support email is currently handled by Google. Apple may also provide the developer with aggregate App Store performance information and user-authorized crash or diagnostic reports. The app does not add its own analytics or tracking SDK.
9. Disclosure, sale, and advertising
The developer does not sell wedding data, share it for cross-context behavioral advertising, use it to profile you, or display advertising. The developer may disclose support correspondence only when reasonably necessary to provide support, protect rights and safety, prevent fraud or abuse, comply with law or legal process, or complete a business transfer subject to appropriate privacy protections.
10. Retention and deletion
Wedding data remains on your device and in iCloud until you delete it, subject to Apple's iCloud retention, backup, and synchronization behavior.
For a wedding you own, use Settings → Start fresh → Erase everything to delete that wedding and its connected records from the app and request that deletion sync to iCloud. If the wedding was shared, the invited participant loses access. An invited participant cannot permanently delete the owner's shared wedding from inside the app.
Deleting the app removes its local app container but may not delete records already stored in iCloud. Those records may return after reinstallation. Use Start fresh before uninstalling when you want the owned wedding removed from iCloud. Apple controls iCloud propagation, backups, and any residual retention required for security or legal reasons.
Temporary exports may remain until iOS clears the app's temporary storage or the app is deleted. Copies you saved or shared must be deleted from their destinations separately. Support correspondence is retained only as long as reasonably necessary for support, security, recordkeeping, or legal obligations, then deleted or de-identified.
11. Your choices and requests
You can:
- avoid entering optional information;
- decline Contacts and notification features;
- turn reminders off in Settings or iOS Settings;
- stop partner sharing through Settings;
- delete an owned wedding with Start fresh; and
- ask the developer to access, correct, or delete support correspondence by emailing support@tiedinbloom.com.
The developer cannot access, correct, export, or delete wedding data stored only on your device or in your private iCloud database. Those controls are available to you in the app and through Apple.
Depending on where you live, privacy law may provide additional rights. The developer will honor applicable rights for information the developer actually possesses and does not discriminate for exercising privacy rights.
12. Security and data loss
The app relies on iOS security and Apple's CloudKit protections. No method of storage or transmission is perfectly secure. Keep your device and Apple Account secure, use a device passcode and two-factor authentication, share only with trusted people, and maintain exports or other backups of information you cannot afford to lose.
13. Children
The app is a general-audience planning tool and is not directed to children under 13. The developer does not knowingly collect personal information from children through the app. Adults should avoid entering a child's personal information unless they have the authority and a valid reason to do so.
14. International processing
Apple and Google may process information in countries other than your own under their respective terms and privacy policies. The developer's handling of support correspondence may also occur in the United States.
15. Changes
This policy may change when the app's features or legal requirements change. The effective date above will be updated. Material changes will be communicated through the app, the App Store listing, or the public policy page when reasonably appropriate.
16. Contact
Sergio Romano
Email: support@tiedinbloom.com