Technical reference · for existing users

Yihu Follow-up Privacy: What to Share, What to Keep Private

Review follow-up text, evidence links and copies before sharing. Preview Yihu with sample material and no microphone; keep private originals within authorized access.

Preview privacy before you try

The linked preview uses preset material, needs no login or microphone, and keeps edits only in the open page. Reloading resets edits. Optional read-aloud uses the browser’s voice service; usage analytics require consent.

Keep private originals in approved tools. In the app, on-device recognition and the destination’s storage, sync and access rules are separate steps. Review the installed version before using a source-described workflow. Read the data-flow guide

US listing verified; availability depends on your storefront. No Mac or self-signing for store installation. Bring your workspace address and account; the optional speech model is about 950 MB.

Keep the original private; share only what the task needs

Use the ownership and archive checks to confirm who may read and retain each item. Keep private originals in approved tools, remove unnecessary details from shared drafts, and check the actual destination’s access and retention rules.

Sufficient evidence is not maximum collection; check retention and disclosure scope first

Teams exporting existing follow-up tasks to Radar JSON keep the source’s permissions. Yihu is not a CRM, customer collector or trade-data archive. This guide checks unnecessary text, identities and URL parameters in material being retained/shared, separating private originals from public synthetic examples. It is not an automatic redactor, compliance certification or delete-all-copies feature.

Different from ownership, claim audit and verification

Ownership checks responsibility/storage; evidence audit checks completion claims; second checks assess evidence for one anomaly claim. Here already authorized material is being prepared for retention/disclosure, so minimize content and mark private scope. It does not assign owners or adjudicate business truth.

Minimal material before retention/disclosure

Material First question Minimal/synthetic treatment Not guaranteed
Task title/next Customer names, orders or internal instructions? Use meaningless synthetic examples publicly, not copied business text Automatic sensitive-content detection/removal
evidence URL Identity/tokens in query, path or fragment? Private references remain authorized; public examples use example.invalid HTTPS candidates are redacted, trustworthy or public
Source/item identity Is an internal UUID/protected marker necessary? Use editorial sample labels, not actual markers Pseudonyms guarantee anonymity or waive permission
Original audio/text Necessary for this retention purpose? Prefer authorized minimal scope; no recordings for public demos Local storage has no backup/copies
Receipts/history Private items or original-request information? Authorized reviewers inspect only necessary source material Read access permits complete export/publication
Screenshots/logs Accounts, feeds, customer text or device identity visible? Synthetic content and non-sensitive outcomes publicly Automatic screenshot masking
Documents/clipboard/attachments Expanded copying, syncing or access? Check actual destination rules and necessary copies One deletion recalls everything
Retention/access Actual policy and authorized roles? Cite existing policy; stop if unknown One retention period, guaranteed deletion or compliance

A fully synthetic public explanation

Source: Sample project, not a real customer/order.
Scope: Field shape and visible state, without original business text.
Evidence example: https://example.invalid/evidence/sample
Archive: Confirm existing authorized rules; no new share destination created.
Unknown: Private-source retention/access remains with the original process.

The reserved-domain example supplies no real evidence and should not be placed in a live ledger as an original record. Public synthetic explanations and private authentic evidence serve different purposes. Removing all provenance does not make a public example proof of a real customer item.

From authorized material to a minimal package

Define retention purpose and authorized readers before deciding whether text, audio, identifiers or a controlled original reference is necessary. Mark unavailable evidence unreviewed rather than demanding more data. Do not provision accounts, public shares or bulk private-task exports under a complete-archive label.

Native Radar retains source text; safeEvidenceURLs selecting HTTPS does not strip queries. Text handoff does not delete original audio or other copies. After editing, still inspect note reservation/destination state. A redacted draft cannot bypass one-handoff or uncertain-stop guards.

FAQ

Does Yihu automatically archive customer correspondence and evidence?

No CRM capability is asserted. This is minimization guidance for your authorized task data, without customer collection, email or automatic record creation.

Are HTTPS evidence links automatically redacted?

Do not infer that. Parsing checks shape, not removal of parameters, identity or business paths. Review public material manually under actual permissions.

Does replacing a name with role A guarantee anonymity?

No. Text, time, paths, orders and combinations can remain identifying. No anonymization certification is supplied; use fully synthetic public examples.

Does Radar visibility permit exporting all history?

No. Check original-item, service and team scope. Reading, bulk export and publication are different operations.

Does deleting phone records delete remote copies after archiving?

No. Workbenches, clipboard, attachments, account sync and backups can retain separate copies. Check actual policies without a remote-recall guarantee.

Does minimization establish acceptance of the real business event?

Only actual authorized evidence supports a limited conclusion. A synthetic public explanation is not the original, approval, delivery or handling record.

Guides and evidence

Ownership/archive planning · Handoff evidence audit · Second-check claims · Cross-device presentation · Start · Privacy

Evidence: Radar source fields/link parsing, README sharing/history/permissions.