Part 3 · Operate
Suppressions
Somebody asked not to be contacted. That survives everything.
01What it is
A permanent record that a person or a domain must not be contacted. It survives a venture reset, a workspace reset and workspace deletion.
02Why it exists
A suppression belongs to the person who asked for it, not to the account that recorded it. Deleting your workspace must not resurrect their right to be contacted.
This is the one piece of data in the product that outlives everything around it, and that is deliberate.
03How to use it
- 01Suppressions are added automatically from unsubscribes and removal requests.
- 02Add one by hand when somebody asks you directly.
- 03Expect them to persist through any reset. That is the design.
04What good looks like
- You give it
- A recipient clicks unsubscribe.
- You get
- A suppression is recorded and the pre-send gate refuses every future send to that address.
- Why
- Suppression is the first condition the gate checks.
Derived from the rules in the code
05What weak looks like, and what it costs
- You give it
- Clearing the workspace to start over, expecting a clean slate.
- You get
- Everything else clears. Suppressions stay.
- Why
- They belong to the people who asked not to be contacted.
Derived from the rules in the code