Security & data handling

How your content is handled.

Follow your content from the editorial brief to delivery. Review the editorial gate, data boundaries and planned controls for employee access.

Follow the content journey A practical overview for communications, HR, privacy and procurement teams.
01 / Content journey

From your brief to a private feed.

The desk prepares the running order first. Your chosen gate determines when scripting, checks and production begin.

  1. 01 Inputs

    Brief & items

    Your editorial brief, company updates and selected reporting.

  2. 02 Desk

    Prepare the rundown

    Research, select and order stories within your editorial rules.

  3. 03 Route

    Approve, or release at the deadline

    Wait for approval, or move at the deadline under your agreed rules.

  4. 04 Production

    Script, check & narrate

    Examine attribution, risky claims and language, then master the audio.

  5. 05 Output

    Deliver the edition

    Publish the finished audio by compatible feed link.

Approval, or the deadline, comes before scripting and production. Editorial checks run in either mode.
02 / Review modes

Two review modes. The same checks in both.

Approval required: a person approves each edition before production. Full auto: the edition goes ahead at the deadline, under your rules.

01 Approval required
Final gate

A person approves each edition

The desk prepares the running order and waits for the reviewer you name.

  1. The running order is prepared.
  2. Your reviewer can keep, cut or reorder stories.
  3. No approval means production does not begin.
02 Full auto
Final gate

Goes ahead at the deadline under your rules

The running order moves into production at the agreed deadline.

  1. At the deadline, your rules release the running order.
  2. Every editorial check runs during production.
  3. Fixable flags are corrected; an unfixable flag drops the story, not the edition.
03 / Audience & access

Who can listen, and how you control it.

A personal feed for each eligible employee. A company sign-in for listening inside Fivewire.

Planned access model

Individual enrollment, the Fivewire app, email revalidation and SCIM are planned. Confirm availability and configuration during your security review.

A personal feed for each employee.

Employees would visit the Fivewire website to create their own tokenized RSS URL, after corporate email verification and an audience check.

  1. Verify the work email

    Confirm control of the corporate mailbox using an email link.

  2. Check the audience

    Match the employee to the audience approved by your administrator or company directory.

  3. Create the personal URL

    Issue a unique, revocable feed token. Add that URL to a compatible podcast player.

Your administrator keeps control.

Manage the audience, approve or remove employees, and revoke an individual’s feed and app access without interrupting everyone else.

  • Approve the audience
  • Revoke individual access
  • Replace a feed token

Keep the audience current.

Periodic email confirmation

Ask employees to reconfirm their work email on a schedule you agree, such as every three months. Suspend access if they do not confirm by the deadline.

Company directory sync

Plan a SCIM connection to a directory such as Microsoft Entra ID or Okta. Provision access from assigned users or groups and revoke it when a removal is received.

Where RSS control ends

A personal RSS URL is a credential: anyone holding it may be able to use it. Revocation would block future feed and audio requests; it cannot recall files already downloaded or cached by a player.

Email verification confirms mailbox control. Audience approval determines access. SSO handles sign-in; SCIM keeps membership in sync.

04 / Data boundaries

What data we use, and what for.

Newsdesk separates producing the briefing from identifying individual listeners.

  1. 01

    Customer content

    Your items are processed to produce your edition and are not used to train any model.

    Production use only
  2. 02

    Employee access identity

    The planned access model needs corporate email, audience membership and token status to manage eligibility. Access records are separate from aggregate listening reports.

    Identity for access
  3. 03

    Listening reports

    Reports are aggregate. There is no named employee listening view.

    Aggregate reporting
05 / Practical details

Details for your review.

The provider list, demo limits and the AI anchor, for your review.

01 Providers and subprocessorsWho supports production and hosting?

The service uses a model provider, voice provider, podcast host and site host. The current full subprocessor list is available on request.

Request the subprocessor list
02 Two-week demoWhat are the evaluation boundaries?

Demo editions are watermarked with a spoken notice and periodic tone. They are for evaluation, not employee distribution, and the demo feed is revoked after two weeks unless you sign.

03 AI anchorHow is AI involvement disclosed?

The anchor is AI. Every script is prepared and checked by the Fivewire newsdesk. It airs after your approval, or at the agreed deadline in full-auto mode.

Security review

Send us your questions.

Send the desk your security, privacy or procurement questions. We can share the current subprocessor list and discuss the review mode that fits your team.

Request security details Request a demo desk For published plan scope and inclusions, compare plans and pricing.