Five questions
Trust page · September 30, 2026
- Is my organization’s data kept apart from other clients’ data?
Your program’s records are: they are confined to the people invited to that program, and the database enforces it for every signed-in request.
- Who checks the evidence, and who approves items?
Every Respond and Prepare item is reviewed by a named Byline reviewer before it reaches you. Note and Monitor items are set by the rules and say whether a person reviewed them. Your approver’s decision on Respond and Prepare items is separate, and Byline’s staff cannot give it.
- What does a program store?
Source details, short excerpts, claims and decisions, each under a permission profile.
- How does Byline use AI?
To extract claims, draft language and propose whether an item fits the program. Fixed rules set the call and can only lower what the model proposes.
- What does Byline not claim?
Certifications, third-party testing and service-level agreements are not in place, and are not claimed.
Kept apart
Every record of a program carries its program’s identifier, and on every request made by a signed-in user the database returns only the programs that person was invited to. Byline’s own pipeline runs under a service key and keeps programs apart in its own queries.
An automated test suite exercises cross-organization access on every change before a release is built, and a release is not deployed until it passes.
Review, approval and delivery are separate records
A Byline reviewer’s Evidence Attestation confirms that each item, its reasoning and its call are supported by the evidence cited, and that the stated uncertainties and limits are accurate. It is bound to one version of the brief and shows the reviewer’s name. It does not decide whether the call is right for your organization; that is yours. A brief that carries a Respond or Prepare item is held until a named Byline reviewer has attested it. A brief with only Note and Monitor items may go out at the attestation deadline, and says on its face that no person reviewed it.
Items whose call is Prepare or Respond, and any item whose sources disagree, require your approver’s Decision Approval. On a client program, Decision Approval belongs to your approver; Byline’s staff cannot give it.
The brief does not wait for your approver past the program’s approval deadline: an item not approved when the brief is sent goes out marked for your decision. Byline can instead set a program to leave such items out of that morning’s brief, or to email a named backup approver while the item stays in, marked.
Delivery is its own record, with the version that was sent. Briefs are prepared under a published version of your Constitution. A new version of your Constitution cannot be published without a named Byline reviewer’s signature.
Evidence attestations, corrections to a delivered brief and your team’s recorded decisions each record who acted and when, and every sealed version records when it was sealed; the database allows no edit or deletion of any of them while their brief exists, apart from clearing the link to a closed account. A Decision Approval is recorded on the item; an edit made in the product withdraws it, and the product writes each approval, rejection and edit made in it to an audit log.
No one approves their own work: the product records who last edited an item in the product, and an approval from that person is refused.
Access is by invitation, limited by role. There is no public sign-up. A viewer sees only the program they were invited to.
Deleting a program deletes its record.
Alert volume is a number anyone can state. What was read and not sent can only be proven from a record, and Byline keeps that record, with the reason recorded for every set-aside.
What a program stores
Details about its sources, short excerpts within each source’s permitted length, the claims extracted from them, and the decisions and briefs built on those claims.
Every source carries a permission profile: who owns it, how it was obtained, what use is permitted, and the excerpt limit. Nothing is read from a source without one.
Byline keeps each article’s headline and no more of its text than the excerpt limit in its source’s profile; a CSV file you upload is kept as uploaded.
Your program’s data can be exported, and deleted, on request.
How Byline uses AI
AI extracts claims, drafts language and proposes whether an item fits the program and what action the evidence supports. Priority, certainty and the call come from fixed rules; source checks and those rules can lower an item’s call or set the item aside, and nothing the model proposes can raise it. The model never sees an item’s score or call.
AI cannot send, approve or attest a brief, and cannot alter a record.
Data sent to the model provider is not used to train its models; the provider and its terms are named in Privacy.
Before a drafted item is saved, each sentence of its What changed line is compared, by the words it shares, with the source text and the claims on the story; a sentence that shares too few is dropped, and if none passes, the line is replaced by the claim the item was drafted from. A headline that neither names the subject nor shares enough words with the claim is replaced by the document’s own title where it has one. An item whose Why it matters line names nothing on the item, or describes Byline’s own matching, is not written: it is set aside with that reason, and an item already written keeps its earlier line.
A brief is sent as one sealed version, verified against its stored fingerprint before it is rendered. Each reader receives one copy of a version. A correction is a new sealed version shown beside the delivered one; it never overwrites what was sent.
Each planned Byline Daily edition covers a scope stated in advance, national or regional. An item enters only if the record’s own text falls within that scope; a federal item in a regional edition shows the sentence that ties it to the region. If nothing qualifies, the morning would be shown as quiet, with a note on what was read. Material from outside the scope is never substituted. The rule is stated on the Daily page. Nothing is delivered to a Daily subscriber yet, and billing is not open; the Daily page states what a reader can presently receive.
bylineintelligence.com loads nothing from another company, sets no cookies and uses no visitor identifiers. Its forms are received by the host and read by a person: the first-brief request on the Desk page, which asks for a full name, an organization, a work email and one issue or question, with an optional checkbox to ask about a paid continuation; the one-brief request on the Daily page; and the contact form. None starts an automated mailing. Privacy states it in full.
What Byline does not claim
Byline holds no formal certifications such as SOC 2, has not commissioned third-party penetration testing, and offers no service-level agreement. None of these is claimed anywhere on this site or in any Byline document.
Raising a concern
Send questions, concerns or security reports through the contact form: choose the topic Privacy or security and give an address for the reply. Byline would rather hear a doubt early than discover it late.
Start with one morning.
A first brief is complimentary, on one issue you follow.