<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Privacy on</title><link>https://deploy-preview-4144--ornate-narwhal-088216.netlify.app/tags/privacy/</link><description>Recent content in Privacy on</description><generator>Hugo -- gohugo.io</generator><language>en-US</language><copyright>Copyright (c) 2023 Chainguard</copyright><lastBuildDate>Thu, 16 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://deploy-preview-4144--ornate-narwhal-088216.netlify.app/tags/privacy/index.xml" rel="self" type="application/rss+xml"/><item><title>Chainguard Actions telemetry and privacy</title><link>https://deploy-preview-4144--ornate-narwhal-088216.netlify.app/chainguard/actions/telemetry/</link><pubDate>Thu, 16 Jul 2026 00:00:00 +0000</pubDate><guid>https://deploy-preview-4144--ornate-narwhal-088216.netlify.app/chainguard/actions/telemetry/</guid><description>&lt;p&gt;Most Chainguard hardened actions run a best-effort &amp;ldquo;phone-home&amp;rdquo; hook that records a usage event to &lt;code&gt;https://actions.enforce.dev/actions/v1/record&lt;/code&gt;. JavaScript actions run it as a &lt;code&gt;pre&lt;/code&gt; script, and composite actions run it as their first step. Docker actions don&amp;rsquo;t include the hook, and some JavaScript and composite actions don&amp;rsquo;t either. The hook is fire-and-forget, with a 2 second timeout that fails open, so it cannot break your build.&lt;/p&gt;
&lt;p&gt;If your runners use an egress allowlist, add &lt;code&gt;actions.enforce.dev&lt;/code&gt; so the hook doesn&amp;rsquo;t wait out its timeout on every step that uses a hardened action.&lt;/p&gt;</description></item></channel></rss>