---
title: 'Kill switch | Plainrouter'
description: 'An emergency stop control, distinct from confirmation that provider delivery has stopped.'
last_updated: 2026-09-10
---

# Kill switch

A kill switch is a control intended to stop further consequential activity. Triggering a stop and confirming the resulting provider state are different events.

## Does triggering a stop prove that ads are paused?

No. A requested or approved stop is not proof of provider execution. Check the execution result and available provider verification before claiming delivery has stopped.

## Does a kill switch reverse earlier spend?

No. Stopping future activity does not undo spend or changes that have already occurred.

## Can modeled data drive a kill switch?

No. Modeled data must not feed spend gates or kill switches. This definition does not claim that every possible emergency-stop path is implemented or verified.

## Related reading

- [Spend gate definition](/definitions/spend-gate)
- [All definitions](/definitions)
- [Signals](/product/signals)
- [Actions](/product/actions)
- [Implementation guides](/library)
- [API documentation](https://plainrouter.com/docs/api/conversions)