SyncNow skips its own control files and a few runtime items, so they stay out of an assistant's reach and out of your activity timeline.
What gets left alone
The main ones are SyncNow's own hidden folders, .sync and .syncnow. They hold the snapshot, the journal and the bridge details, and they belong to SyncNow rather than to your site, so an assistant cannot write to them.
Alongside those, certain server-owned and runtime files are treated as off limits because they are managed by your hosting, not by the work being done on the project.
The point is to keep the focus on your real content. An assistant edits the files that make up your site, while SyncNow's internal bookkeeping stays clean and protected. This also keeps your timeline meaningful, since it records genuine changes to your project rather than noise from control files. If a skipped file is targeted, the operation is refused and logged.
SyncNow