Effective date: October 11, 2026
App version covered: Daywhisk iOS beta 1.0 (1)
Daywhisk is published by Main Street App Brewery (“we,” “us,” or “our”). This policy explains how the iOS beta handles information when you organize daily tasks and bills, import information, use optional mail features, and test the app. The initial beta is intended for adult testers in the United States.
Daywhisk processes information on your device and uses Apple services for features including iCloud synchronization. Some app records, including manually imported message bodies, can leave your device through iCloud. Optional mail features connect directly to the mail server you configure.
Information used by Daywhisk
Tasks bills and app records
Daywhisk saves information you enter or create, such as task descriptions, bill amounts and dates, notes, daily briefings, preferences, and activity history. Mail-related records can include account details, sender information, filters, cleanup plans and results, folder names, and message identifiers. Activity history may include message subjects, task or bill descriptions, and account labels.
Information you import or share
When you manually import a message, Daywhisk can save its subject, sender, received date, body text, notes, and label. The share extension can receive shared text and URL strings. It can also read text from supported shared text files; other shared files may be represented by a filename or file URL. Imported information is used to help organize and extract relevant details locally.
Optional mail connections
If you configure a mail account, Daywhisk uses the server address, account information, and password you provide to connect to your mail provider. The beta requires a TLS connection. Its statistics feature examines the inbox and retrieves sender and date headers to calculate sender, domain, and message counts. This path does not fetch live message bodies.
Other mail features can list or search folders. If you review and approve a cleanup plan, the app can create a destination folder and move the selected messages on your mail server. Those changes affect your mailbox.
Saved mail passwords use the iOS Keychain with a device-only setting that permits access while the device is unlocked. The app uses the password in memory to authenticate to your chosen mail server. Account metadata is stored separately in app records and can synchronize through iCloud.
Summaries and automated processing
The email briefing demonstration in this beta uses fictional sample email bodies. It does not retrieve live inbox message bodies for that demonstration. On supported devices, it uses Apple’s on-device SystemLanguageModel. When that model is unavailable or a generated result fails the app’s checks, the app uses a local text-extraction fallback. Manual import extraction also uses local processing.
These current summarization paths do not send text to an external AI provider or Apple Private Cloud Compute. This describes the processing step; app records and imported text can still synchronize through iCloud as explained below.
Storage and iCloud synchronization
Daywhisk stores app records in shared on-device storage used by the app and its share extension. The app’s standard data store is configured for Apple CloudKit synchronization when available. Records eligible for synchronization include imported messages and body text, tasks, bills, mail account metadata, sender and cleanup records, daily briefings, preferences, and activity history.
Synchronization depends on Apple services, device settings, connectivity, and the app’s current state. It may be delayed or incomplete. A change on one device should not be assumed to have reached every other device immediately. Apple’s handling of iCloud information is described in its privacy information.
Apple Privacy Policy
Calendar reminders and notifications
If you grant access, Daywhisk can read calendar information used in briefings, including event titles, start times, and whether an event is all day. It can also create, update, and remove calendar events for bills and reminders for tasks, including their titles and notes. The beta requests full Calendar and Reminders access through Apple’s permission controls.
Daywhisk can schedule local notifications with alerts, sounds, and badges. These may show task titles or bill payees on your device. You control permission and notification previews in iOS Settings. Turning off Daywhisk’s notification setting cancels its managed pending notifications.
Exports and other services
The app’s JSON export can include all app record types, including imported message bodies, account metadata, and activity history. It excludes Keychain passwords. You choose where to save or share an export. Daywhisk does not add encryption to the exported JSON file, so choose a destination appropriate for its contents.
The beta uses Apple services and any mail server you configure. It has no integrated advertising, advertising-tracking, third-party analytics, or third-party crash-reporting SDK. Apple’s TestFlight service handles beta testing information separately, as described below. Your mail provider’s handling of information is governed by that provider’s terms and privacy policy.
Your choices and deletion
You choose whether to configure mail features, import information, grant Calendar or Reminders access, or allow notifications. You can change Apple permissions in iOS Settings. Withdrawing permission does not necessarily erase records already created.
Removing a mail account removes its saved password on that device and app records covered by the removal operation. Other synchronized metadata may remain. Removal does not revoke the provider password or undo mailbox moves. Deleting an imported message can leave an activity-history entry containing its subject.
Delete Personal Data, after confirmation, removes eligible app records and saved device credentials. It retains deletion requests, receipts, and processed identifiers to reconcile deletion across devices. Records created after the deletion cutoff are excluded. Failures can cause partial deletion; offline or synchronizing devices may retain copies until reconciliation completes.
This operation does not remove calendar events or reminders written through Apple services, cancel scheduled notifications, delete earlier exports or provider-held emails, or erase backups and every offline copy. Manage these separately. Uninstalling Daywhisk does not confirm that all related copies have been erased.
Retention and support
App records do not have an automatic expiry period in this beta. They remain until changed or removed through the available controls, subject to the deletion limits above. Mail providers and Apple manage information in their services under their own policies.
We use support emails and tester feedback only to provide support and fix bugs. We do not use them for marketing or forward, publish, or otherwise distribute them to others. We delete copies we keep within 90 days after the related issue is resolved. This rule covers copies under our control; it does not set retention periods for information Apple or mail providers manage independently.
For privacy questions or requests about information we hold, email pythonpete62@gmail.com. Please do not include passwords or unnecessary message contents.
If you email us, we receive your email address, message, and attachments through our Gmail mailbox. Google processes that email to provide its service. Apple processes TestFlight information separately, as described below.
Google Privacy Policy
TestFlight beta testing
With TestFlight, Apple automatically collects crash and usage information and makes it available to us, including app and device details, sessions, and crashes. Your name and email may be visible depending on the invitation method. Apple says these are not shown for testers who join only through a public link.
Feedback you submit, including comments and screenshots, is shared with Apple and us. Review screenshots for personal information before sending them. Apple’s notice describes its collection, retention, and privacy controls. The support and bug-fix purposes and developer-copy retention rule above also apply to crash or usage reports we keep.
Apple TestFlight and Privacy
Changes to this policy
This policy describes the beta version identified above. An updated policy and effective date will describe changes to these practices.