What stays on your iPhone
Children, activity labels, optional notes, imported events, detected changes, conflicts, reminder choices and travel settings are stored locally. Full calendar subscription URLs are stored in the iOS Keychain; the app shows only a redacted source address after import. Optional iCloud family sharing creates a limited, read-only copy described below.
What can leave your iPhone
When you add or refresh a calendar feed, your iPhone requests that calendar from the provider identified by the URL. App Store purchases and restores are handled by Apple through StoreKit. If you tap Check drive time, iOS uses your current location and Apple Maps to estimate a route. This is a foreground, one-time request; UpNext does not retain your route or enable background location updates. If you choose Share Schedule, UpNext creates a read-only calendar snapshot and sends it to the destination you choose. An encrypted backup goes only to the location you select in the iOS file picker. UpNext has no developer-run family-data cloud.
Drive time between events (version 2.5.7)
Version 2.5.7 includes an optional Agenda estimate between two eligible consecutive events. If you tap that estimate, Apple Maps receives the two event locations needed for the route. It does not use your device location, and it does not run automatically.
Optional iCloud family sharing
If you choose Family > Share with family, UpNext saves a read-only snapshot in your private iCloud database and uses Apple's invitation controls to share it with people you choose. The copy contains children's names and colours, upcoming event titles, dates, times, locations and status, and recent change summaries. It excludes calendar subscription links, event notes, arrival plans, reminders, backups and the full local app database. Invited people can view, not edit, the shared schedule. Sharing requires iCloud and is optional.
UpNext checks the shared schedule when the app opens; it does not track your location in the background. The developer does not operate the iCloud service or have access to the owner's private iCloud schedule records.
Apple Calendar access
Apple Calendar imports are read-only: if you grant access, UpNext reads the calendars you select to build the family view and check changes and conflicts. Separately, if you choose to copy a personal event to Apple Calendar, the title, child, dates, location, notes, link, alerts, repeat rule, and availability are written to an UpNext-managed calendar. Apple and the calendar account you select receive that event. You can keep the event only in UpNext instead.
Feedback and support email
Send Feedback prepares an editable email addressed to scott@scotthazlitt.ai. The draft includes the app version and build, iOS version, and device model. You can change or remove any text, and you decide whether to send it. If you send an email, the developer receives your email address, message, and the details you leave in the draft, and uses them to respond and troubleshoot your request. The draft does not automatically include children, events, locations, calendar links, purchases, attachments, or logs.
Children and private calendar links
Family schedules can contain sensitive information. Treat a subscription link like a password: import only calendars you are allowed to access, and do not place the full link in a screenshot or support message.
Delete your data
You can manage or stop an iCloud invitation in Family sharing. Stopping an invitation removes future access, though a recipient may retain a downloaded copy until their app refreshes or they hide that shared schedule. Use Delete all local data in Settings to remove children, calendars, imported events, changes, conflicts, settings and stored calendar URLs from your device. If you own an iCloud family share, UpNext first removes its shared records and invitation; if that fails, local deletion does not proceed. An exported schedule or backup saved outside UpNext must be deleted from its destination separately.
This website and the launch offer
The website uses Cloudflare Web Analytics for aggregate visits, referrers and performance. The analytics service does not use cookies or persistent visitor identifiers. Cloudflare may set a short-lived security cookie for abuse prevention.
If you choose to claim the launch offer, your browser keeps an in-progress anonymous challenge and, after a code is assigned, its Apple redemption URL in that tab's session storage. This lets an interrupted claim or Apple handoff resume. The browser state ends with the tab session and is sent only to the UpNext claim route and Apple redemption flow.
Cloudflare D1 stores the offer inventory, claim timestamp, random claim identifier, and assigned Apple offer code. It does not store your name, email address, family data, or Apple Account. Challenges expire after two minutes; expired challenge records are removed during later claim attempts. The claim and assigned-code offer records remain until the launch-offer records are deleted so an interrupted response can recover the same code and the limited inventory can be administered.
When the website opens Apple's redemption flow, Apple receives the redemption link and offer code. Apple handles the redemption under its own account and privacy terms; UpNext does not receive your Apple Account from that handoff.