TTWOS
Privacy & permissions

How your data moves

TWOS connects services you choose. Sending to another provider is a separate disclosure of the selected content to that provider.

Updated November 17, 2026 · Publisher: Jing Huang.
This policy describes the public direct-download TWOS 1.0.11 / 101.59 and its bundled Nyra. A Mac App Store edition is not yet available; its final disclosures will be checked against its actual submitted build.

1. Provider websites and AI sharing

ChatGPT, Claude and DeepSeek load their official websites in embedded browser views. Their pages can receive your connection information, account/session information, content you enter and files you upload, and use their own cookies and website storage. Their retention, training choices and deletion controls follow their policies and your account settings.

When you click a TWOS handoff, the selected reply or instructions and explicitly selected attachments are bound to the chosen destination. Automatic replies can continue transferring complete replies between the selected participants while enabled. This may send the same content to more than one provider. A website subscription is not an API authorization.

2. Local Codex and selected files

The direct-download app can connect to your installed Codex App Server. Task content is handled through that connection and the service behind it. Approved local work may read or change files and run commands within the configured execution scope. TWOS retains actual permission requests; a model’s text is not your approval.

Selecting an attachment creates a local selection/snapshot for the handoff. Selection alone does not upload it. Sending, including an authorized automatic exchange with those files, can upload selected content to the bound provider. Removing a selection prevents its inclusion in a future handoff; it does not erase a copy already sent or a previously stored receipt.

3. What remains on the Mac

TWOS stores settings, task/directory authorizations, drafts, handoff content and receipts, automatic-exchange state and selected-file snapshots in its local profile and environments. Provider website sessions are kept in WebKit’s website data store. Local diagnostic logs may contain paths and operational details; inspect and redact them before sharing.

The publisher does not operate a TWOS conversation relay server in this release. That does not mean no data leaves your Mac: provider websites, the Codex service, GitHub downloads and any support material you submit have their own processing.

4. Stop sharing and remove data

  1. Stop future automatic sharing: turn off “Automatically send replies” or use “Stop auto-send” on either side. Already submitted messages may still finish; stopping cannot retract them.
  2. Remove pending attachments: choose ⋯ More → Remove selection and verify the selection is empty before another send. This does not delete the original file or a provider’s uploaded copy.
  3. Sign out of a provider: use that website’s account menu inside the affected TWOS pane. Manage chat deletion, account deletion and data-use choices through that provider’s own settings or privacy-request channel. Deleting a local app does not delete provider data.
  4. Remove TWOS local records: stop active work, quit TWOS normally and back up anything you want to keep. In Finder use Go → Go to Folder to inspect ~/Library/Application Support/Tianma Work OS Preferences (workbench settings, handoff records and snapshots) and ~/Library/Application Support/Tianma Work OS Environments (local project environments). Delete only the TWOS records you deliberately choose to remove. These actions can remove drafts, history and directory authorizations. User-selected business folders are separate and are not removed by uninstalling TWOS.
  5. Local desktop logs: review ~/Library/Logs/Tianma Work OS Desktop if present, and remove only the logs you intend to delete after quitting the app. Custom or engineering profiles can use different locations.

Removing the preferences folder is not a complete WebKit-cookie erasure control. This release does not expose an in-app “erase every website session” function. Sign out of the provider and follow its account controls; do not delete unrelated Safari data. We do not claim that uninstalling alone clears all local website data.

There is no universal retention deadline for local files: they remain until you remove them or the relevant product operation replaces them. Remote services apply their own retention rules, including any required legal retention.

5. Nyra and audio

Nyra receives bounded read-only activity states, opaque correlation identifiers and up to two fresh active conversation titles (at most 90 characters each). Titles are kept in memory rather than playback or visibility logs. Only current activity appears by default; confirmed idle or ended work closes the bubble, and a brief observation gap is unconfirmed. Use Show current tasks to explicitly show or hide labels; disconnect the read-only companion connection to stop receiving status and titles. Clicking the character uses a separate authenticated host-only channel to restore the verified running TWOS window. This path contains no task, turn, draft or command and grants no execution rights; it works without task-edit permission. The status channel excludes conversation bodies, code, file contents, credentials and account details. It cannot execute tasks or approve requests.

The 13 Chinese Tian recordings and 13 matching tiny-voca F2 American English WAVs play locally. The generating model is not bundled or run by the app. Installed macOS speech voices remain a local fallback. The pet’s ordinary action audio does not record a microphone or send task text to a voice-generation service. Imported audio remains a user-selected local file. Provider website voice features are separate and follow the provider’s permissions and policy.

Task controls: TWOS 1.0.11 / Nyra 1.0.8

The status connection stays read-only. A separate authenticated control channel accepts task-specific user-initiated focus, draft inspection/editing, submission, pending-queue editing and exact-task stopping. TWOS remains the sole controller and verifies the host, component, task, turn, scope and request identity. The official application’s active chats do not gain control permission through this feature.

The control channel also returns up to two bound task summaries with provider, side, a title of at most 90 characters, state/freshness, available actions and opaque IDs. On-demand control summaries can retain ended or stale tasks for result inspection or draft recovery; the default activity bubble does not keep these terminal rows visible; they exclude raw workspace paths and full conversations.

The selected draft or supplement, up to 64,000 UTF-8 bytes, passes locally between Nyra and TWOS and then through the existing authorized provider pipeline only when sent. TWOS retains its existing local drafts, queues and receipts. Nyra also keeps one bounded owner-only recovery record before a control edit or send; a matching confirmed result clears it. Unconfirmed or recovered input is copy-only until explicitly reconciled. Status and diagnostic records do not include instruction bodies, code, attachments, credentials or account details.

Standalone task controls require a separate explicit grant; a previous visibility-only connection is not silently upgraded. To stop using controls, disconnect the companion through its connection controls. Hiding the task bubble only changes its visibility and does not cancel a task. Stopping affects future dispatch and the exact active task, not already-created files or messages.

6. Support and this website

Our support page links to public GitHub Issues. Your GitHub identity and what you submit are visible there. Do not send sensitive data; request a private contact method without publishing the private details. You can edit your own issue/comment and use GitHub’s support or privacy controls for deletion requests; copies, notifications and legal retention may remain.

These public pages contain no analytics script, forms, remote fonts or site-set cookies. GitHub Pages hosts them and may process request logs and security information under the GitHub privacy statement. Linked destinations have their own policies.

7. Scope and changes

The current app is macOS-only. It does not automatically buy credits, subscribe you to a service or change your provider billing path. macOS permissions and provider prompts still apply.

This page is not an App Store privacy-label certification and does not assert “Data Not Collected.” We will update it when a shipped data flow changes. Contact the publisher through the support page for questions, sharing concerns or non-sensitive privacy requests.