iCloud sync

Pinwork stores your task data locally on each device and uses Apple’s iCloud system to sync that data between your devices when iCloud is available.

There is no Pinwork account for task sync, and Pinwork does not run a separate task-sync server.

What syncs

Pinwork syncs the main task database through Apple’s CloudKit-backed Core Data sync.

This includes:

tasks
projects
tags
checklist items
task status
When and Deadline values
estimates
recurrence rules
project and tag relationships
archive state
task ordering and app metadata

Production device builds use your private iCloud database. The CloudKit container belongs to the app, but the records are stored in your private iCloud scope.

How sync happens

Pinwork saves changes locally first.

When iCloud is available, Core Data exports local changes to CloudKit. Changes from other devices are imported by Apple’s sync system on its own schedule.

Pinwork listens for remote change notifications. When new data arrives, the app refreshes local views and asks open task, project, and tag screens to reload from the store.

This means a device can be fully usable before every change from another device has arrived.

What Check Sync Status does

Open Settings and use Check Sync Status when you want Pinwork to re-check the local sync state.

It can:

save pending local changes
refresh local data that has already been imported
update the visible sync status
show recent sync activity or an error message

It cannot force an instant iCloud download.

Sync status messages

The Sync section in Settings can show:

status
iCloud account status
last Cloud activity
last checked time
last error
Check Sync Status

Status labels can include Ready, Checking, Recent activity, or Needs attention.

If iCloud is signed out, unavailable, not authenticated, out of quota, rate limited, or temporarily busy, sync can pause until iCloud is available again.

Preferences and extension data

Most task data syncs through the main iCloud-backed store.

Some preferences sync separately through iCloud Key-Value Storage, including:

GTD mode
completion behavior
auto rollover
Calendar Peek
linked calendar event visibility
upcoming time range
onboarding completion and version
starter project version and ID

Widgets, Shortcuts, the Share Extension, Focus Filters, and Live Activity controls use small shared payloads in the App Group container so they can work outside the main app.

That shared data is not a second full task database. It is a lightweight snapshot or action queue used by extensions.

Offline use

Pinwork works offline.

While offline, the current device keeps using its local store. You can continue creating, editing, completing, and organizing tasks.

Pending changes export when the device reconnects and iCloud sync resumes.

Conflict behavior

Pinwork does not show a field-by-field conflict resolver.

If the same task is changed on two devices before sync finishes, Core Data and CloudKit merge the incoming records into the local store. Open screens then reload from the store.

If the result is not what you expected, edit the task again on the device that shows the current data. Where available, use Undo or Archive restore to recover the previous state.

Apple Watch sync

Apple Watch keeps its own local Watch store and receives task data and access state through the companion iPhone.

Watch sync can lag behind iPhone sync. If the iPhone has not received the latest iCloud data yet, the Watch cannot show it either.

For Watch-specific issues, see Apple Watch and Apple Watch is not updating.

Sync and privacy: the broader data and privacy guide.
Sync is not updating: steps for delayed sync.
Offline behavior: what works without network access.

Was this page helpful?