Warrant Canary

OffshoreServ Warrant Canary
Date: 25 September 2026

As of the date above, OffshoreServ has NOT received any of the following:

- National security letters.
- FISA orders or similar secret intelligence orders.
- Gag orders or any order preventing us from making this statement.
- Warrants or orders for customer data from any government or authority.
- Requests to install monitoring equipment, backdoors, or interception of
  any kind on our network or systems.

We further confirm that, as of the date above, no customer data has been
handed to any third party.

This statement is renewed every quarter. The next statement is due by
25 December 2026. If it is not renewed on time, if it disappears, or if its
PGP signature no longer verifies, treat that as a warning and do not assume
this statement still holds.

Verify this file with our public key (offshoreserv.com/pgp):
  gpg --verify canary.txt.asc canary.txt

Signing key fingerprint:
  9115 B17E CE09 44BC C461 285F F382 6B4F F2F3 8213

Statement published: 2026-09-25 (UTC)

A warrant canary is a way to communicate something we may be legally forbidden from stating directly. In some jurisdictions an authority can compel a provider to hand over data and forbid it from saying so. A canary works the other way around: we regularly publish a signed statement that we have not received such orders. If that statement can no longer be truthfully renewed, we stop renewing it. The signal is in the silence.

1. What our canary states

Our canary is a short, factual statement, dated and PGP-signed, confirming that as of its date OffshoreServ has not received the specific categories of secret government order it lists, and that no customer data has been handed to any third party. We do not reproduce the statement on this page, because the authentic, signed version is what matters. Read the current statement in canary.txt and verify it as below.

2. How to verify our canary

Verification takes a minute and proves both that the statement is really from us and that it has not been altered.

1. Download both files: the statement canary.txt and its detached signature canary.txt.asc, from https://offshoreserv.com/canary.txt and https://offshoreserv.com/canary.txt.asc
2. Import our public key from /pgp, and confirm the fingerprint matches the one published there.
3. Verify the signature with GnuPG:

   gpg --verify canary.txt.asc canary.txt

   A good signature from our key confirms the statement is authentic and unmodified.
4. Check the date. Read the date in the statement and confirm it is recent. Our canary is renewed quarterly, so it should never be older than one quarter.

3. Renewal schedule

We renew the canary every quarter. The current statement is dated 25 September 2026, and the next update is due by 25 December 2026. Each renewal is a fresh, signed statement with a new date.

4. What absence or staleness means

Treat the following as meaningful, not routine:

• The canary is not renewed on time, or its date is older than one quarter.
• The canary disappears, or the signature no longer verifies against our published key.
• The wording changes in a way that quietly drops one of the categories it used to cover.

Any of these may indicate that we can no longer truthfully make the statement, or that something has changed we are not permitted to describe. A canary cannot make promises about the future, and short delays can have ordinary causes, so do not assume the worst from a single late update. But you should take a missing, stale, or altered canary as a prompt to be cautious and to check our transparency report and any notices. Verify the signature yourself; do not rely on a screenshot or a third-party copy.