Privacy & Support

You can use local plans or a fictional Sample Day without connecting a calendar. If you grant Full Calendar Access, Day Board uses Apple’s EventKit framework to show calendars available on your iPhone. You choose which calendars to import.

Day Board imports the previous 30 days and next 90 days. Information used can include:

• Event titles, locations, notes, start and end times, all-day status, time zones, and event or meeting links.
• Calendar and source names and identifiers, including identifiers for recurring event occurrences.
• Attendee information used locally for display initials and event categorization. Up to five attendee initials are retained with an event. Day Board does not request Contacts access.
• Your line names, colors, assignments, selected calendars, preferences, and sorting rules. A learned rule can include a normalized event title.

You choose where new events are saved. In Add Event, choose “Day Board only” to keep a plan in the app, or choose a connected, writable calendar to create an event there. Saving to a calendar uses Apple’s EventKit framework and your calendar provider may sync the event to your other devices. Day Board only writes a new calendar event when you choose a calendar destination and save.

Existing imported events are read-only in Day Board. Changing their line assignment changes Day Board’s organization, not the source event. To change or delete the source event, use your calendar app.

Your schedule, local plans, line settings, remembered calendar names, assignments, and sorting rules are stored on your device. An on-device shared store lets the app provide a schedule snapshot to its widgets.

The widget snapshot includes titles, locations, timing, line identity, and sample or sync status. The shared store also includes selected-calendar identifiers, remembered sorting rules, and line assignments so widgets can refresh the same calendars. A sorting rule can include a normalized event title. It does not include the app’s event notes or attendee list.

Day Board has no account service, calendar-upload service, advertising SDK, tracking SDK, or third-party analytics SDK. Day Board does not send your calendar content to a Day Board server. System backups, Apple services, external links, and information you choose to share are separate.

Calendar changes refresh when you open Day Board or a calendar-change notification arrives while the app is running. When iOS gives a widget a refresh opportunity and Calendar access is available, the widget also reads your selected calendars on-device. Widgets never request permission or write calendar events. iOS controls refresh timing, so this is not continuous syncing and an earlier view may remain visible until the next refresh.

Disconnecting calendars

Deselecting a calendar removes its imported events from the active schedule and requests a widget update. If you revoke Calendar access in iPhone Settings, imported events are removed when Day Board next checks permission. Local plans remain. The widget also checks permission when generating its next snapshot or timeline.

If a selected calendar is temporarily unavailable, Day Board may keep its previously imported events with a warning. Explicitly deselecting that calendar removes its active cached events.

What can remain

Disconnecting does not erase every remembered item. Calendar and source names, selected-source identifiers after permission revocation, line assignments, and learned sorting rules may remain on your device. You can remove learned rules or reset learned sorting in Settings; manual line assignments remain.

Local plans remain until you delete them. Sample events remain until you end Sample Day or a successful import replaces the sample schedule; ending Sample Day does not remove your local plans. Local plans and sorting preferences have no automatic age-based deletion.

Recovery copies & backups

If a saved file cannot be read, Day Board preserves a recovery copy. A backup is also retained when older local all-day plans are upgraded to stable calendar dates. These copies may contain earlier calendar or local-plan details, and calendar deselection or permission changes do not automatically erase them. Recovery-file export is optional and warns about private content. Day Board has no separate in-app control to delete these copies.

For a full local reset, delete Day Board rather than offloading it. Apple controls system storage, backups, restores, and previously rendered widget views. Backups, exported files, and feedback you already sent are separate copies; manage them through the relevant service or location.

Day Board does not automatically send its own diagnostic summary. In Settings → About, Privacy & Help, you can review and choose to share it.

The summary includes the app version and build, operating-system version, permission and sync state, calendar and event counts, last complete-sync time, and recovery-copy availability. It excludes event titles, notes, locations, meeting links, calendar names, and account identifiers.

If you contact support or send feedback, the developer receives what you provide, such as your email address, message, technical details, screenshots, or recordings. Support email is handled by the developer’s email provider and used to investigate and respond to your issue.

Review attachments before sending. Screenshots and recovery files can expose calendar content even though the diagnostic summary is redacted. Only send a recovery copy if you intend to share its contents.

Support retention

Support correspondence and any separately retained diagnostic or beta-feedback copies are deleted within 12 months after the issue is resolved, unless a longer period is legally required. You can request earlier deletion through the support inbox, and requests are honored where possible. Apple-controlled records follow Apple’s policy.

TestFlight is Apple’s beta-distribution service. Apple automatically collects crash logs and usage information and shares them with the developer; testers cannot opt out. This may include your name and email address, depending on how you were invited. Feedback you submit is also shared.

This is separate from Day Board’s on-device calendar handling. Apple says it retains beta feedback for one year and may retain crash and usage data until bugs are resolved. Those are Apple’s practices, not a promise about the developer’s retained copies.

Calendar accounts, iCloud and device backups, and other Apple services depend on your device and account settings. Day Board does not control those providers’ data handling.

Opening a Maps location or joining a meeting sends the selected destination to the relevant app or website. Sharing diagnostics, exporting a recovery file, or sending support email transfers that information to the destination you choose. Those services handle it under their own policies.

This policy is updated when Day Board’s data handling changes. Its effective date appears at the top of this page.

For privacy questions or requests about information sent to the developer, use the support email below. Do not include private event details unless they are necessary.

Day Board is provided by Joe Cirillo. You can contact the developer at hello@rillo.tv.