Privacy, plainly.

Saved on your device

Where You Wanna Be, shown as Wanna Be on your Home Screen, is made by Zesty Fernandez (ZestyTS). The app has no accounts, ads, analytics SDKs, or developer-operated server.

Activities, prompts and next-time notes, favorites, sets and their optional saved filters, Today plans, repeating routine templates and their weekday/time choices, per-day edits and done/skipped status, reminder choices, preferences (including the opening screen), history, and the current timer are saved locally and may be included in device backups. They are not sent to the developer automatically. On iPhone and iPad, Apple processes payment information for the optional Lifetime Upgrade. Wanna Be uses a StoreKit-verified transaction and on-device entitlement to enable and restore saved activity sets, expanded app-pause selections, premium themes, and alternate app icons. If entitlement is lost, saved sets and premium-theme choices stay stored but inactive. The developer receives no payment card data; activity history is not uploaded for purchase checks. Search and the weekly completion recap use only local saved data. iOS manages the selected Home Screen icon; icon changes do not upload activity data.

The Android private test build has no purchase flow or Google Play Billing integration. Its theme, icon, and set choices are saved on the device without a payment entitlement. The Android build disables automatic app-data backup; wheel exports and task files are choices you make separately.

Optional calendars and Today plans

Today works without calendar permission. If you choose Show my calendar, iOS asks for Full Access so Wanna Be can read existing events. The app uses event titles, calendar names, start/end times, all-day/free status, and identifiers or plan links to display the selected day and show advisory time overlaps. To cover long tasks that cross midnight, the read is bounded to that day plus up to 24 elapsed hours afterward; only selected-day events appear in the agenda. These event details stay in memory; they are not added to the app’s saved plan automatically, included in wheel backups, or sent to the developer. Only your calendar-reading preference is saved. Disconnecting, losing permission, or leaving the visible calendar scene clears the displayed event data. You can also revoke access in iOS Settings.

Add to Calendar is a separate action. Before opening Apple’s editor, the app explains that the plan title, first step, time block, and a link back to its item will be copied to the calendar you choose. You review, choose a calendar, and save or cancel there. The link contains a local item identifier, not its title or first step. Your calendar provider may sync the event to its service and other devices; people with access to a shared calendar may see it. Reading existing calendars is not required for this reviewed add flow.

On Android, connecting calendars requests Read Calendar permission. Wanna Be reads events for the selected day from visible calendars you choose, up to 200 entries. Titles, calendar names, times, all-day/free status, and a local task identifier parsed from an event description are used for the agenda. Event details stay in memory; only the connection preference and selected calendar identifiers are saved locally. Disconnecting clears the selection. Add to Calendar opens your calendar app’s event editor with the title, notes, and time block for review; Wanna Be does not request calendar-write permission or write an event directly.

Calendar and Today hold separate copies. Changes, completion, moves, or deletion in one do not update the other. Remove a copied Calendar event separately if you no longer want it. Wanna Be has no two-way calendar sync and does not automatically create calendar events or send invitations.

Optional app pause and reminders

With your permission, Apple’s Screen Time picker lets you select apps, categories, and websites to pause. Selection tokens and break settings stay on your device and are used by Wanna Be’s own Screen Time extensions. Free selection allows one individual app; Lifetime Upgrade adds multiple apps, categories, and web domains. Saved selections remain manageable and removable after entitlement loss, while new selections must meet the free limit. The app does not read your messages, social feeds, or browsing history, or send your selections or activity history to the developer.

You can turn off App pause in Wanna Be and revoke its Screen Time access in iOS Settings.

On Android, app pause uses an optional accessibility service. It observes the foreground app’s package identifier to decide whether to show a local focus screen for an app you selected. It does not read screen contents, accessibility nodes, typed input, messages, or screenshots. Selected package identifiers and break settings stay on the device. The service can be disabled in Android accessibility Settings; it does not provide the same system enforcement as Apple’s Screen Time shield.

If enabled, timer, plan, and routine reminders are local notifications. Repeating task reminders use a rolling seven-day window, with up to 50 upcoming plan alerts; opening the app refreshes that window. Their visible text does not include your activity title, plan title, or first step. Plan reminders carry a local item identifier and, when needed, its day so tapping can return to the plan. Turn a task reminder off in its day/routine editor, turn timer reminders off in Wanna Be Settings, or manage notification permission in iOS Settings. On Android, notification permission is optional and reminders can be delayed by battery saving or device settings. A reminder never starts or completes an activity or unlocks apps. On iOS, the free What’s next? widget contains no personal data. Saved wheel reads set names, identifiers, and a display-only availability flag from a shared container on this device. Its snapshot contains no activity details, filters, history, or Screen Time tokens. Nothing is sent to the developer; opening a set rechecks upgrade access in the app.

Sharing is your choice

Share task prepares one task’s title, first step, checklist, smaller start, time estimate, and any suggested day/time and time zone you choose to include. When you share a bigger task, its included groups and subtasks are sent together. Completion status, history, Screen Time selections, read calendar events, and unrelated tasks are excluded. You choose whether, how, and to whom to send the task file or link. The recipient reviews and edits a separate copy before adding it to their plan or calendar. Sharing does not enable reminders, send a calendar invitation, or create an account or shared inbox. Later changes and completion do not sync between people.

A .wannabetask file contains the same task details as a task link. Anyone with the file or link can read them; neither is protected by a password. The task page reads and creates task files and decodes and creates links entirely in your browser, without uploading task details, saving them in browser storage, or requesting calendar access. Opening a file or link shows a review; nothing is added to a plan or calendar automatically. Task-file opening is available in compatible iOS and Android builds. You can open an attachment with Wanna Be, or save it and use the app’s Import task action. Existing links remain available for older task-sharing builds. A task link contains its details in the URL fragment (after #). The fragment is not sent to GitHub Pages as part of the page request, but the browser, messaging service, and recipients can retain the full link. The page uses a no-referrer policy for links to other sites. Calendar-file downloads happen locally; your chosen calendar provider may sync the saved copy. The website sends no reminders.

Wheel exports contain activities, sets, and any filters saved with sets, including written prompts, next-time notes, and favorites. They exclude Today plans, routine templates and per-day changes, plan/routine reminders, read Calendar events and calendar preferences, history, timers, app-pause selections, ordinary current wheel filters, appearance, and other preferences.

Share feedback prepares your note, app version/build, and iOS or Android version. You choose the recipient and service. Nothing is sent automatically. Files and messages you share are then handled by the recipient and service you choose.

Keeping and deleting information

You can edit or delete activities and one-off plan items, change or skip a routine task for a day, remove routine templates, and clear activity history in Settings. Removing a routine stops its unchanged repetitions; already saved per-day changes and done/skipped occurrences remain in the plan. Deleting an activity retains the most recent undo copy and does not erase its past history. Removing a plan item does not remove a Calendar copy or its previously recorded activity history. Clearing history and importing a wheel do not erase your Today plans, routines, or per-day changes. The app may preserve recovery copies when saved data cannot be read.

To remove local app data, turn off App pause and delete Wanna Be rather than offloading it. Delete exported files and device backups separately. Deleting the app does not delete Apple’s lifetime-upgrade purchase record. Apple manages those records under its own privacy practices.

On Android, app data can also be removed with Clear storage in the app’s device Settings. Disable app pause first and delete exported files separately.

Support and beta testing

If you email the developer, your message and contact details are used to respond and improve the app. Support correspondence may remain in the developer’s email service. You can request deletion by contacting ZestyTS@gmail.com.

During TestFlight testing, Apple also provides testing information, crash reports, and submitted feedback to the developer. That information is used to improve the app and is handled through Apple’s service. See Apple’s TestFlight privacy information.

This support website

These pages use GitHub Pages hosting. We do not add analytics, advertising, cookies, or tracking scripts. GitHub logs visitors’ IP addresses for security when serving Pages sites. Read GitHub’s Pages hosting information and privacy statement for its practices.

Following an external link or sending an email uses the service you choose and its privacy practices.

Questions or requests

Contact Zesty Fernandez at ZestyTS@gmail.com with privacy questions or requests about information you have sent.

Changes to these practices will be reflected on this page, with an updated date.