Privacy and data boundary

Your work should stay clear before it leaves Dauntless.

The Dauntless Syndicate stores the material needed to keep your work coherent between sessions. Connected providers should receive data only through specific reviewed actions, not as a side effect of signing in.

Stored in Dauntless

What the workspace can store

  • Dauntless

    approved account access and workspace identity

  • Dauntless

    your starting context, constraints, chosen path, and current goal

  • Dauntless

    confidence notes, source notes, assumptions, and reviewer signals

  • Dauntless

    working papers, trackers, outlines, exports, receipts, and activity history

  • Dauntless

    connected-tool receipts after a reviewed action succeeds

Google sign-in

Used to open the private workspace when the account is approved. Sign-in alone does not create Docs, Sheets, Slides, email drafts, or calendar items.

Optional connected actions

A connected action can create a reviewed Google file only after the permission path is healthy and the specific request is approved.

Exports

Downloads stay local to the workspace flow. Exporting does not publish the work or send it to another person.

Data control

What you can inspect today

You can review saved documents, structured lists, slide outlines, files, exports, receipts, and activity records inside Dauntless.

You can export materials from Assets without moving them into Google.

Deletion and retention automation are not claimed as mature product features yet.

Provider-side records, if created later with approval, must be managed through that provider and Dauntless receipts.