Data Transparency

Privacy Policy

“Written in plain, straightforward language for Aayojan Ace users. Last updated October 2026.”

What Information We Collect

Aayojan Ace collects only the event planning parameters you enter directly into our intake and replanning forms: event type, celebration date, guest count, city, budget amounts, style or cultural description, and non-negotiables.

We never ask for or require credit card details, bank credentials, home addresses, or government identification.

Use of Generative AI Services & Backup Provider Window

To generate realistic budgets, phased timelines, and creative event concepts, your planning input is securely processed from our server. We utilize Google's Gemini API as our primary AI engine. If Google Gemini experiences high demand, rate limits, or transient downtime, your planning request may be securely routed to Groq as an optional backup AI provider. If all AI services are unavailable, our built-in deterministic template planner generates your celebration plan entirely without external network transmission.

Demo Key Availability Window

This application was built for the PromptWars Challenge 5. The optional Groq backup AI key includes a configured expiration date (GROQ_KEY_EXPIRES_ON) corresponding to the ~2-month competition evaluation lifecycle. If the backup demo key reaches its expiration date or is rejected (401/403), the server disables the backup provider for the remainder of the session to prevent repeated network overhead. When this occurs, planning continues uninterrupted using the main Gemini AI and the built-in planner, accompanied by a calm, accessible notification.

Important Security & Privacy Guidelines:

Because planning text is evaluated by AI models, never enter sensitive personal secrets, bank credentials, private passwords, or confidential identity documents in the intake form or non-negotiables box.
All user input is wrapped strictly as untrusted passive data parameters within explicit delimiters to prevent prompt injection attacks.
No planning data is ever sold or utilized for third-party advertising.

Guest Mode vs. Firebase Cloud Storage

Guest Mode

Plan, rebalance, and print celebration plans without creating an account. In Guest Mode, your data remains solely in your browser's local storage and is never written to an external database.

Google Sign-in

If you choose to sign in with Google to save plans across devices, Firebase Authentication stores your name and email. Your plans are saved to Firestore in an isolated document tree accessible strictly by your own authenticated user identifier.

Google Sign-in & Calendar Integrations

Aayojan Ace provides two distinct pathways for saving plans and managing milestone schedules:

1. Warning-Free Default Calendar Integration (Zero OAuth Required)

Each milestone in your timeline provides a direct “Add to Google Calendar” link that launches Google Calendar's standard event template in a new browser tab. You can also click “Download all as .ics” to import the complete celebration schedule into any calendar app (Apple Calendar, Outlook, Google Calendar) with automatic 1-day advance notifications (VALARM).

These default options require no sign-in, no OAuth permissions, and zero third-party access to your calendar. Reminders follow your personal calendar notification settings.

2. Advanced OAuth Calendar Auto-Sync

For users wanting direct automated sync with popup and email reminders directly from the workspace, an optional OAuth connection is available under the Advanced section:

Unverified App Screen: Because Aayojan Ace is an independent competition project, Google may display a standard “Google hasn't verified this app” notice. Choosing Advanced → Continue connects solely the selected event creation scope.
Narrow Permission: We request strictly https://www.googleapis.com/auth/calendar.events solely to write and manage the specific milestones you select.
Session-Only In-Memory Storage: OAuth access tokens are stored strictly in browser memory for the active session. They are never written to Firestore, localStorage, cookies, or server logs, and are immediately purged on sign-out or session end.
No Reading of Personal Calendars: We never read your calendar entries, never inspect contacts, and never run background jobs.

3. Firebase Authentication & Session Lifecycle

Google Sign-in uses browser session persistence (browserSessionPersistence). When you sign out, all local cached plan data, user identifiers, and in-memory tokens are completely cleared from screen and memory.

Data Retention and Deletion

You maintain total control over your celebration plans. You can rename or permanently delete any saved plan at any time from the Saved Plans screen. Deleting a plan completely purges its records from Firestore.

About The Project Terms of Service