OEURE

Left and right arrow keys move between languages.

Privacy and AI disclosure

How OEURE handles session data, and the fact that the host is software.

AI disclosure

OEURE is an AI host, not a person. Answers can be wrong. Your company is responsible for obtaining attendee consent.

Capture

New sessions keep capture off. An owner or admin has to turn it on. Turning it on or off is written to the audit log. Your company is responsible for telling attendees and getting their consent.

Retention schedule

Transcript lines are deleted 365 days after they are stored, unless the owner sets another period in Settings (1 to 3650 days). Changing the period is audited. The purge deletes transcript lines only. Accounts, session titles, agendas, knowledge, and the audit log stay.

Data the workspace can store

Account email and a password hash, company name, session titles, agenda, optional transcripts when capture is on, knowledge-base drafts, and the audit log. Audio for the live room stays in that session. Mock providers do not send this data to an outside model.

Cookies

The session cookie is named oeure_session. It is HttpOnly, SameSite=Lax, limited to this host, and marked Secure on HTTPS. A separate cookie remembers English or Chinese in this browser. OEURE does not use third-party advertising cookies.

Providers

Speech, language, and email providers are chosen in the server environment. This installation uses mock providers unless an operator configures live ones. Keys are not entered in the browser.

A participant's copy or deletion

A participant can ask for a copy of their data or for it to be deleted. An owner or admin can export a JSON file of that person's name and transcript lines, or erase those lines, the roster entry, and knowledge items tied to those lines. The file is built in this installation and is not sent to a provider. The audit log records the export or erasure without the transcript text.

Audit log integrity

Each new audit event stores a SHA-256 hash of the previous event in this workspace, and the latest hash is kept as the chain head. Editing an event or removing one from the middle breaks the chain. The latest event is pinned by the chain head, so deleting it is rejected.

Audit log

The workspace owner can download the audit log. It records capture changes, knowledge approvals and rejections, retention changes, sign-ins, sign-outs, and password changes.

HomeLog inOpen the audit log