§ A.1 — Background
Background
Spinboss Protect was established to address a persistent operational gap in rights enforcement: the difficulty of dispatching legal notices, brand-abuse complaints, and abuse escalations through a channel that is simultaneously authenticated, auditable, and recognized by counterparty intake systems. The platform consolidates dispatch, signing, routing, and reconciliation into a single coherent infrastructure tier, separate from the general-purpose mail systems used for ordinary correspondence.
Our operators work alongside content rights coordinators, brand integrity specialists, abuse desks, and trust & safety leads to maintain a defensible, evidence-grounded communication path from notice origination to counterparty acknowledgement.
§ A.2 — Philosophy
Operational philosophy
The integrity of an enforcement notice is the integrity of its delivery path. Spinboss Protect treats every outbound communication as a discrete legal artefact: signed, time-stamped, archived, and independently verifiable. Recipients are never asked to trust the sender's claims alone; they are given the cryptographic and procedural means to verify them.
This philosophy translates into specific design constraints. The platform does not send marketing material, never co-mingles enforcement traffic with general correspondence, and publishes its authentication selectors and rotation schedules so that any recipient or third-party auditor can confirm the provenance of a message.
§ A.3 — Mission
Digital trust mission
Phishing, impersonation, and counterfeit enforcement notices have eroded the trust placed in routine legal correspondence. Our mission is to restore that trust by making authenticity provable at the message level, the relay level, and the workflow level. The Verification Center is the public surface of that commitment, allowing any recipient to confirm sender authenticity independently of the channel through which the message arrived.
§ A.4 — Governance
Infrastructure governance
§ A.4.1
Change control
All material infrastructure changes — DKIM key rotations, relay topology changes, retention policy updates — pass through a documented review with paired approvals and an immutable change log.
§ A.4.2
Separation of duties
The operators who dispatch notices do not control the signing keys. The operators who hold the keys do not draft notices. Audit functions are independent of both.
§ A.4.3
Evidence handling
Evidence attached to a notice is hashed at intake, stored under chain-of-custody, and referenced by content hash in the message body so any counterparty can verify it was not altered.
§ A.4.4
Disclosure
Routine transparency reports document volume, counterparty categories, average acknowledgement windows, and significant operational events without disclosing the identities of complainants or respondents.
§ A.5 — Standards
Compliance standards
Our operating standards are aligned with the EU Digital Services Act (DSA) trusted-flagger principles, the U.S. DMCA notice-and-takedown framework, the UK Online Safety Act reporting expectations, ICANN registrar abuse coordination practice, the M3AAWG mail authentication recommendations, and the GDPR's data minimization and retention disciplines. Where regional frameworks conflict, the stricter standard is applied to the workflow.
§ A.6 — Integrity
Communication integrity principles
01Authentic by default
Every outbound message is SPF-aligned, DKIM-signed, DMARC-enforced, and TLS-encrypted in transit.
ENFORCED
02Independently verifiable
A public reference endpoint allows any recipient to confirm sender authenticity without trusting the channel of receipt.
PUBLIC
03Retained under policy
Correspondence and reconciliation logs are retained under documented retention windows aligned with legal obligation.
POLICY-BOUND
04Reviewable on request
Counter-notices and disputes are accepted, logged, and decided under a written, time-bound review lifecycle.
DUE PROCESS
§ A.7 — Timeline
Operational timeline
2021 · Q2Formation
The brand protection function is incorporated as a distinct operations group with dedicated infrastructure and governance.
2022 · Q1Authenticated relay launched
Outbound mail moved onto a dedicated authenticated relay layer with DMARC enforcement at p=reject.
2023 · Q3Verification Center opened
The public sender verification endpoint goes live, enabling independent recipient-side authenticity checks.
2024 · Q1Escalation framework formalized
Tier 1 / 2 / 3 escalation lanes are published with documented acknowledgement targets.
2025 · Q2Transparency reporting
Routine transparency disclosures begin, covering volume, counterparty categories, and operational integrity metrics.
2026 · Q1Infrastructure attestation
Continuous cryptographic attestation of relay nodes is exposed publicly at the Infrastructure Status page.