Where are the minutes stored?

In your own document space on your infrastructure — Feishu or Lark cloud docs — with a link back into the chat. Nothing is stored on a Hedy-operated server.

Does Hedy track action items after the meeting?

Yes. Each action becomes a tracked task with an owner and due date, and Hedy follows up before it slips.

Will Hedy repeat personal remarks from a meeting?

No. Conduct rules bar relaying gossip or personal evaluations; only decisions, actions and open questions are extracted.

Minutes filed before you refill your coffee

How Hedy runs it

Feed the recording

Drop the transcript or notes in chat; Hedy extracts what was decided, by whom, due when.

Structured output

Decisions, actions and open questions, in your template, filed to Feishu or Lark docs with a link back.

Actions become tasks

Each action item is tracked with owner and due date; Hedy follows up before it slips.

Memory, not amnesia

Decisions land in company memory — next week’s "what did we decide?" has a cited answer.

In depth

A note-taking assistant stops at a transcript. Hedy does the job that comes after the meeting. It reads the discussion and produces a structured record: what was decided, who owns each item, and when it is due. That record is written into your cloud docs, Feishu/Lark or Slack-linked storage you already run, formatted so a human can act on it without re-reading an hour of talk. One Hedy replaces the manual work a team used to split between a scribe, a project coordinator, and a follow-up chaser.

Action items do not die in a document. Hedy converts each one into a trackable task with an owner and a deadline, so the meeting output flows straight into the systems where work actually gets tracked. Nothing is invented: Hedy only records what was said. If a decision, owner, or date was not stated, it is left open rather than guessed, and the answer names exactly where each item came from.

Governance is the product, not a feature bolted on. Minutes and task creation run under the same controls as everything else: an append-only audit log, tiered approvals (L0/L1/L2), and a deny-by-default whitelist for write operations, so pushing tasks into a downstream tool is an authorized action, not an open door. Retrieval respects the asker's ACL, so a summary only surfaces what that person is cleared to see.

Two lines Hedy will not cross. It does not broadcast subjective evaluations of participants, no tone-policing, no unrequested judgments about who performed well. And it does not leave your walls: Hedy is self-hosted via ~30-minute Docker/Compose deployment, brings your own model key including local vLLM or Ollama, runs on an offline Ed25519 license, and uses no sub-processors. The meeting record is generated inside your infrastructure and stays there.

Questions

How is pushing action items into task tools kept safe?

Write operations follow a deny-by-default whitelist and tiered approvals (L0/L1/L2), so creating downstream tasks is an authorized action, not an open door. Every step is captured in an append-only audit log, and retrieval respects each asker's ACL, so a person only sees the meeting content they are cleared to access.

Does Hedy send meeting recordings or transcripts to any external service?

No. Hedy is self-hosted on your own Docker or Kubernetes infrastructure, including air-gapped deployments, and uses no sub-processors. You bring your own model key, including local vLLM or Ollama, so meeting content is processed inside your network and the minutes stay there. Licensing is offline via Ed25519, with no phone-home.

Will Hedy write subjective judgments about people into the minutes?

No. Hedy records decisions, owners, and deadlines, the factual outcomes of the meeting. It does not broadcast subjective evaluations of participants or tone-policing. Every item in the record is tied to its source under an evidence gate, so the minutes cite where each decision or action came from rather than adding opinion.

Where do the meeting minutes get archived?

Into your own cloud docs. Hedy writes structured minutes into storage you already run, with Feishu/Lark as a first-class target and Slack supported as well. Action items become trackable tasks in your systems. Nothing is copied to a Hedy-hosted cloud, because the whole platform runs on your infrastructure.