Your planning data should stay understandable.

Information PlanWise processes

• Planning details: selected city, date, planning window, commitments, activity intent, budget range, travel limit, selected activities, and the resulting plan.
• Google Calendar data, when you connect it: timed events from your primary calendar that overlap the selected date and planning window, including title, start and end time, and an event link when Google provides one.
• Taste preferences: preferences you save on the Taste Profile page, including likes, dislikes, personal ideas, and learned preference signals.
• Account sign-in details, when you use them: your email address, optional display name, and the minimum session information needed to send and verify a PlanWise magic link.
• Event-search details: city, date, active time window, intent, budget range, and travel limit used to search Ticketmaster.
• Place-search details: selected city and activity intent used to request restaurants, attractions, parks, wellness venues, and other places from Google Maps. If you submit a free-text Places search, that submitted phrase is also sent to Google Maps to retrieve matching places. PlanWise may keep only a broad matched category, such as Food or Culture, in this browser; it does not save the words you typed in your Taste Profile or account. PlanWise currently uses a city-centre search bias, not your precise starting location.
• Technical information: normal hosting and security logs may include request time, IP address, browser or device details, and requested route.

How and why it is used

Planning information is used to calculate free time, retrieve relevant local events, assess schedule feasibility, and show your plan. Technical information may be used to operate, secure, diagnose, and improve the service. PlanWise currently has no advertising or cross-site tracking.

Google Calendar access

Connecting Google Calendar is optional. One sign-in covers both calendar features: importing your commitments (reading events) and, on a finished plan, "Add to Google Calendar" (adding events), so you are not asked to sign in twice. The access token stays in browser memory only, is never persisted, and is revoked when you disconnect or discarded when the tab closes.

Importing reads only timed events for the selected date and planning window, and you preview and choose events before adding them to the planner. "Add to Google Calendar" creates new calendar entries only for the activities you selected in PlanWise. Neither feature edits or deletes your existing events, and nothing is read or written except when you trigger it.

PlanWise's use of information received from Google APIs is intended to comply with the Google API Services User Data Policy, including its Limited Use requirements. See Google's official API Services User Data Policy and Calendar authorization documentation.

Where information is stored

• The active plan, manual commitments, imported calendar events, and Google access token are session-local and are not saved to a PlanWise account or database.
• Taste Profile preferences and personal ideas are stored in your browser's local storage. When you sign in and account writes are enabled, PlanWise may sync the normalized profile and ideas to your account so they can follow you across devices.
• Broad categories inferred from submitted Google Maps searches are stored only in this browser. They can be cleared from Taste Profile, are not synced to your account, and do not include the search words.
• Account sign-in is optional. Supabase processes the email magic link and session cookie. When account writes are enabled, PlanWise can store normalized Taste Profile data, personal ideas, saved provider options, and plans you explicitly save. Google Calendar data and access tokens are not stored in your PlanWise account.
• Private product-validation counts, such as activities added or provider links clicked, are stored in your browser's local storage for owner testing.
• PlanWise also counts a small set of anonymous product actions on the server, such as activity added, plan completed, provider link clicked, copied summary, exported plan, or started another day. These aggregate counters store only the action name and month, not your plan, calendar content, activity titles, provider URLs, address, device identifier, or user account.
• Ticketmaster search responses may be cached on the server for 15 minutes to reduce repeated provider calls.
• Google Maps place responses use no-store requests and are kept only in the active browser planning state. PlanWise does not build a persistent Places database. If you explicitly save an option, only its normalized provider identity and limited display/fit facts are stored in your account; raw Google Maps content is not retained.

Service providers and data sharing

PlanWise uses Google for optional calendar authorization and retrieval, Ticketmaster for live event discovery, Google Maps Platform for place discovery, Supabase for optional account sign-in, Vercel for hosting, and Upstash/Vercel storage for anonymous aggregate counters and provider-usage safeguards. Search filters needed for discovery are sent to the PlanWise server and the relevant provider. Calendar titles, Google access tokens, and your complete plan are not sent to Ticketmaster or Google Maps Platform.

Third-party services process information under their own terms and privacy notices. PlanWise does not sell personal information.

Google Maps content is governed by the Google Maps/Google Earth Additional Terms and Google's Privacy Policy.

Your choices and rights

• Use PlanWise without connecting Google Calendar.
• Disconnect Google Calendar to revoke the current access token.
• Remove imported events or clear the current planning session.
• Clear PlanWise site data in your browser to remove the local Taste Preference data and private local validation records.
• Export a machine-readable copy of account data or permanently delete the account from the Account page. Browser-local data can optionally be cleared during deletion.
• Ask about access, correction, deletion, restriction, objection, or portability by emailing alin3968@gmail.com or yiyuc0124@gmail.com, where applicable.

Changes to this notice

This notice will change as PlanWise adds providers, persistence, analytics, or accounts. The updated date at the top will identify the current version. Material changes should be reviewed before the affected feature is released.