Build my own private event calendar using the attached Event Days starter.

Preserve its clean design, responsive layout, timeline, agenda, interactive map, clickable event details, copy-address controls, and colored event dots on each day. This archive contains fictional demo data only.

First ask me for the city or trip, date range, timezone, and which of my email/calendar accounts to use if that information is not already clear. Inspect the available account integrations. Use only my connected sources that I authorize; if unavailable, ask me for calendar exports or event-confirmation files. Do not pretend an account connection exists.

Find my actual registrations, approvals, waitlists, invitations requiring a reply, cancellations, calendar events, and relevant travel. Deduplicate records across sources. Preserve confirmed, pending, invitation-only, cancelled, and travel statuses. An invitation is not a registration, and an application is not an approval. Keep uncertain times or locations explicit. Do not RSVP, send email, sign up for events, or modify my calendar.

Replace all fictional demo events with my own data. Set the date range and timezone from my answers. Retain source links where safe, but omit ticket-management tokens, booking references, full email bodies, unrelated personal information, and credentials. Never put access tokens or account credentials in browser code. Show an honest last-checked timestamp and source-coverage notes.

Keep my resulting calendar local or private to me. Do not replace or publish over the public template site. Public demo data and my real event data must stay separate. If you use a static page, remember its entire event dataset is visible to anyone who can open the page; do not host it publicly.

Use verified physical locations for map pins. Leave undisclosed and online venues unpinned rather than inventing coordinates. Keep map attribution and explain that the tile provider receives the visible map area and IP address. Do not invent route times.

Implement the simplest supported setup for one person. If this environment supports private hosting, publish my private copy and verify access. Otherwise deliver a local app or file I can run. Account connection and background updates are additional setup, not capabilities already included in this starter. Offer automatic refresh only if the source access and private update path can be verified; ask for the cadence before scheduling it. Report exactly what works and what remains unconnected.

The supplied tests verify the fictional starter; update their fixtures and expectations for my chosen dates and private data. Run the adapted checks, test mobile and desktop layouts, test day selection and all three views, confirm sample events have been removed from my copy, and verify that my personal data is never exposed on a public URL. Give me the finished private link or local file and brief setup instructions.