Your event details should be handled with purpose.

Information the platform may collect

Information you provide

• Name, email, phone number, company, role, and preferred contact method.
• Event type, date, time, location, guest count, budget, design preferences, accessibility needs, notes, and requested additions.
• Images, documents, links, or other inspiration you choose to attach, subject to stated file limits.
• Proposal decisions, communications, consent records, transaction references, and service history when those functions are enabled.

Do not submit payment-card numbers, account passwords, government identifiers, medical records, or other information that is not needed to plan the event.

Information collected automatically

Hosting, security, and application systems can process IP address, device and browser information, timestamps, requested pages, referrer or campaign parameters, error logs, rate-limit data, and cookie or consent choices. Optional analytics should load only after the applicable consent.

Payments

If hosted Stripe checkout is enabled, payment-card details are collected by Stripe. The platform is designed to retain transaction identifiers, status, amount, and related booking references rather than full card numbers. The final notice must confirm the implemented payment flow.

Why information may be used

• Respond to inquiries and build, revise, and deliver event proposals.
• Evaluate availability, site fit, guest needs, vendors, weather planning, and operational requirements.
• Administer accepted bookings, payments, communications, calendar details, support, and records.
• Protect the service from abuse, investigate failures, maintain security, and meet applicable recordkeeping obligations.
• Measure website performance and improve the planning experience when optional analytics consent permits it.

Consent to receive a response is not consent to promotional email or text messaging. Any marketing or SMS program should have a separate, specific opt-in and an effective opt-out method before use.

Service providers and disclosures

The production platform is designed to support providers for hosting, database and file storage, authentication, email delivery, payments, calendars, analytics, error monitoring, and consented messaging. Planned integrations include services from Vercel, Supabase, Stripe, Resend, and Google; Sentry or a messaging provider may also be configured.

Listing a planned provider does not mean that provider is active today. Before launch, this notice must identify the services actually enabled and link to relevant provider information where appropriate.

Information may also need to be shared with a client-approved venue, photographer, caterer, florist, rental company, transportation provider, or other event vendor to evaluate or perform the requested scope. The proposal should make the vendor role and contracting party clear.

Further disclosure may be necessary to comply with law, protect safety or rights, prevent fraud, or address a business transaction. The final policy must define these practices in legally reviewed language.

Retention and security

A final retention schedule has not been approved. The intended approach is to keep information only as long as reasonably needed for the purpose collected, active planning, service records, security, dispute handling, and applicable legal obligations, then delete or de-identify it under a documented schedule.

The platform is designed for server-side authorization, signed payment webhooks, access controls, encrypted provider connections, rate limiting, and restricted administrative access. No online system can promise absolute security, and production controls still require deployment verification.

Your choices and privacy requests

You may use the contact form to request access, correction, deletion, or another privacy review. The request process, identity verification method, response timing, exceptions, and jurisdiction-specific rights have not yet been finalized.

You can decline nonessential analytics where the consent interface is available. You can also choose not to provide optional fields, although missing information may limit the ability to evaluate a request.