Room for celebration.
Care for your information.

Utsav is a wedding planning app. Its standard mode works on your device without an account. Sample couples, guests and vendors shown in the app are fictional examples.

What you add to Utsav

You may save partner names, wedding dates and venues, guest names and phone numbers, household attendance, meal preferences, travel or accessibility notes, vendor quotes and payments, and family task assignments. Add only information you need for planning. Tell the people involved how you use and share their details.

Where your plans are kept

In standard mode, wedding plans are stored in this browser or the app’s local device storage. They are not automatically sent to a Utsav cloud service. Data is not an encrypted vault. Device access, operating-system protections and platform backup settings affect who can access it. Clearing browser storage, uninstalling the app or losing the device may remove your plans. Keep a backup when needed.

Backups and sharing

Exported JSON and CSV files contain the information you saved, including personal details. They are not encrypted. You choose where to save them and whom to share them with. Sharing a guest invitation opens your device’s share interface or copies the message; Utsav does not send emails, WhatsApp messages or SMS automatically. Shared copies are controlled by the recipient and cannot be recalled by deleting the original.

Optional family server

Family sharing is optional. The default Utsav sharing service is operated by Rajesh Ray, reachable at iamrajesh350@gmail.com, and hosted with Fly.io in Singapore. You can instead connect a separately operated server by changing its address. Only when you explicitly create or upload a shared wedding does that server receive your wedding data. The server’s operator controls its storage, access logs and backups. Family editors with an invitation can see and edit the entire wedding. Guest RSVP links show only that household’s invitation and permit changes to its attendance and meal preference. Anyone with a forwarded link can use it until it expires or is replaced. Choose a server and collaborators you trust.

One-use family invitations expire after seven days; editor access expires after 30 days. Owners can review and revoke editor connections and unused invitations. Editors can revoke their own connection when disconnecting. Connection recovery files contain private access keys and are not encrypted; anyone with an owner key can access, share or delete that server wedding. Keep them private. Replacing a device access key invalidates its old copies.

Before a shared-wedding creation or invitation-join request is sent, the app saves private pending recovery information on your device. It includes the chosen server, a random request reference and secret access key, and either the original wedding snapshot for creation or the invitation key for joining. This lets you retry if a reply is lost. It is separate from your normal wedding backup and remains until the final connection is saved or you explicitly discard it. You may export it as a private recovery file; the device record and export are not encrypted and can grant wedding access. A custom server’s optional creation key is not included. Discarding pending recovery does not delete server data, and deleting local wedding plans does not remove this separate connection recovery record.

For safe retries, the sharing service stores random operation references and hashes of the original creation request, access credential or consumed invitation with the relevant wedding/access record. These hashes check that a retry matches the original request; they are not additional readable wedding copies or usable access keys. After a wedding created through this recovery process is deleted, the service retains only its random request reference indefinitely to prevent an old pending request from recreating it. That deletion marker contains no wedding fields, guest details, payload hash or access key. The service limits the combined number of these markers and active recoverable wedding creations to 10,000. Moderation reports and hosting backups have the separate retention periods described below.

The Utsav service keeps a shared wedding until its owner deletes it or a verified deletion request is completed. Local data deletion does not delete a connected server’s records. A room owner can delete the remote wedding in the family server settings; copies on other devices and exports remain. The Utsav service uses an encrypted hosting volume and encrypted daily snapshots configured for five-day retention. Removing the active wedding does not immediately remove earlier snapshots; they expire under that retention setting. This is not end-to-end encryption: the service processes the data to provide sharing.

Sharing rules and safety reports

Before shared creation, joining, uploading or an RSVP reply, Utsav asks you to accept its sharing rules. The app stores your accepted version on the device. On the standalone guest RSVP page, acceptance stays only in memory for that invitation and is not written to browser storage. The version is sent with the shared action so the server can enforce the current rules. The server also records the accepted version and acceptance time with the relevant wedding or access record. Reporting does not require acceptance.

Reports of harmful content or people are sent to the chosen family server. A report contains the category, reason and description you enter; the wedding reference; your access role and connection reference where applicable; and received/expiry timestamps. No full wedding or guest list is automatically attached. A private credential hash is used internally to limit report abuse; it cannot be used as an access key. The Utsav operator uses reports to investigate concerns and take moderation action. Reports are not shown to other wedding members.

Reports expire after 90 days and are removed at the next service cleanup or start. They may remain after deletion of the related wedding to support abuse investigation. Hosting snapshots expire under the five-day retention setting. Use the report reference when contacting support; do not send access keys or unnecessary personal details. Independently operated servers determine their own report handling.

Permissions and reminders

Notifications are optional and requested only when you set task reminders. Task titles can appear on your device’s lock screen. You can cancel reminders in Settings or turn off notification permissions in your phone settings. Utsav does not request contacts, location, microphone or camera access. Export files may be temporarily stored in the app cache to support your device’s share sheet.

Advertising, analytics and hosting

Utsav does not include advertising, behavioural analytics or third-party tracking SDKs. The family service uses temporary in-memory IP counters to limit abuse; it does not write request bodies, access keys or RSVP paths to application logs. Fly.io may process operational network and service metadata under its own privacy policy. Fonts and artwork are bundled with the app. If you visit a hosted preview, the hosting provider processes information needed to deliver and protect the site, such as IP address and request metadata; the preview may require sign-in under its hosting access policy. Public support pages are hosted on GitHub Pages, whose provider processes network and request metadata to serve and protect those pages.

Deleting your information

Open Settings → Delete data on this device to remove the locally saved wedding, cancel scheduled reminders and remove the app’s temporary export files. A fictional sample wedding is then displayed. Backups saved or shared outside Utsav remain; delete those separately. For an optional connected server, use its remote deletion control or contact that server’s operator. The device connection and any pending connection recovery are separate from the locally saved wedding; manage them in Family sharing when no longer needed. Export or finish a pending connection before using Discard pending recovery, because the server may already have created the wedding or consumed the invitation. Delete the server wedding or retain a private recovery file before removing the only owner’s connection.

Support

Utsav’s developer contact is iamrajesh350@gmail.com. Contact this address for product support, questions about this notice, or a data deletion request. We may need to verify your authority before removing a shared wedding. Do not email passwords, access keys or private recovery files. Please avoid including your guest list or other sensitive details in a support request unless needed. Messages you send through your email app are handled by your email provider.