Confetti
Privacy Policy
Last updated: September 22, 2026
This policy explains how Confetti handles information when you plan, publish, share, collaborate, request support, or purchase access.
Device-first by default
Confetti is designed to keep private drafts, planning notes, selected media, saved events, social profile handles, visual preferences, and sent-card history on your device unless you choose an action that needs cloud services. We use cloud services when you publish or send a share link, sync with collaborators, search partner events, use account features, request support, or use future payment features.
Information stored on your device
- Draft event and card content.
- Planning hub notes, checklists, and saved ideas.
- Local RSVP, memory, and gift test records.
- Saved events and sent-card history.
- Selected photos and videos before sending or publishing.
- Local beta crash reports.
Information sent to cloud services
- Published events or card links so recipients can view them.
- Email card delivery details when email is used.
- Names and email addresses of guests selected by an event host, so we can send invitations and show events to guests who sign in with the same email address.
- Shared planning data when collaboration is enabled.
- Ticketmaster or partner event search queries.
- Account, authentication, support, trial eligibility, and purchase entitlement records.
- Diagnostics if hosted crash monitoring is enabled later.
Trials and purchases
Confetti stores the start and end of your free trial using the server's clock. To discourage repeated free-trial signups, the app creates a random installation token and the server stores only a one-way hash of it. That hash may be retained after account deletion as a non-identifying fraud-prevention record.
Apple or Google processes in-app purchases, and RevenueCat helps verify whether the lifetime entitlement is active. Confetti receives purchase status, product, transaction, and store-account-linked entitlement information, but does not receive your full payment-card details.
Contacts and social profiles
If you allow contact access, Confetti uses contacts on your device to help you choose guests or card recipients. We do not upload your full address book. Guests you select for an unfinished event can remain in a draft on your device. When you add a guest to a published event, we store the selected name and email with that event, send the invitation through our email provider, and show the event to that guest after sign-in with the same email. Hosts can remove guests from the planning hub. We do not sell contact lists. Social profile links are optional. Confetti saves public handles or profile URLs so guests can find your profiles. Direct platform posting requires separate platform approval and user confirmation.
Photos and videos
Photos and videos added to private drafts stay on your device. When you send or publish media, Confetti may upload it so recipients can view it. Shared media may be removed after a retention period unless you save or extend it.
Event backups and data portability
When you choose Export Event Backup, Confetti retrieves the event records available to your account and combines them with available planning data on your device. The app creates a temporary JSON file and opens the device share sheet so you can choose where to save or send it. Confetti does not automatically receive another copy merely because you export the file.
The export may contain event plans, guest names, email addresses, RSVPs, memories, and gift records. Keep it private and review the privacy terms of any storage or sharing service you select. Photos and videos are not embedded in the export. Confetti does not currently restore the file automatically inside the app.
Deletion and support
You can export event records, clear local data, or delete your account from the app profile screen. For help deleting published links or hosted records, contact support. james.marcus@vigilantegamestudio.com