Bulletins

Updates

Every bulletin carries a reference, a category, a date and the same four sections: summary, background, details, remediation. Nothing is published here that is not also traceable to a document in the register. Sub-processor changes are notified 30 days before they take effect under NTC-GL-001, not after.

No incident bulletins yet.

Pensieve has published no incident bulletins. That is a statement about a short operating history, not about resilience. Read the commitments on the status page and judge those instead.

See every bulletin Status and incident commitments Vulnerability disclosure policy

The categories

What gets published here, and under which label

Compliance: A change to what Pensieve holds, claims, publishes or has stopped claiming. Certification positions live here.
Vulnerability: A defect in the platform or in a dependency, its severity, and the state of the fix.
Incident: Something went wrong in production. What was affected, what was not, and what changed so it does not recur.
Sub-processor: An addition, replacement, removal or relocation in the sub-processor register. Notified 30 days in advance under NTC-GL-001.
General: Everything else this Trust Center publishes, including changes to the register itself.

Subscribe to bulletins

Every bulletin is published here first and mailed from the same day: the site sends a set number of bulletin messages a day, sub-processor changes first and then each bulletin in the order it was published, a turn for every mail domain at a time, so a long list takes more than one. Sub-processor changes are notified 30 days before they take effect, which is the whole point of subscribing. We email a confirmation link first, and nothing is sent until it is followed.

Your address is stored in Pensieve’s own Postgres, is used for nothing but these bulletins, and is never passed to a third party beyond the mail provider listed on the sub-processor register. You can have it erased at any time from Your data.

How a bulletin is structured

Summary: what happened and whether you need to act.
Background: why the matter arises at all.
Details: the specifics, including what was not affected.
Remediation: what Pensieve did, and what, if anything, you must do.

A section with nothing true to say in it is omitted rather than padded. The format is fixed so a bulletin can be read in thirty seconds by someone who reads a hundred of them.

Machine readable

/updates.rss (the full feed)
/api/public/updates (JSON, the same source)

The marketing site consumes these endpoints. It keeps no copy of its own, which is why a correction published here is a correction everywhere.