Bind exported subscriber lists in the TOS
A creator who exports a subscriber list holds addresses outside our
database. The joint-controller arrangement already states the obligation
that follows; the TOS, where a creator agrees to it, said nothing. Add a
Subscriber Lists clause under Creator Terms, cross-reference it from the
arrangement page, and list that page on /policy.
Co-Authored-By
Claude Opus 5 (1M context) <noreply@anthropic.com>
<li><a href="/docs/acceptable-use">Acceptable Use</a>: specific behaviour that gets accounts suspended</li>
87
87
<li><a href="/docs/copyright">Copyright & DMCA</a>: how takedowns and counter-notifications work</li>
88
88
<li><a href="/docs/appeals">Appeals</a>: how to challenge a moderation decision</li>
89
+
<li><a href="/docs/mailing-list-data-processing">Mailing List Data Processing</a>: who answers a subscriber's request about a project mailing list</li>
An erasure request against a project mailing list is fulfilled by Makenotwork, and it removes the address from the creator's list at the same time. The creator does not hold a separate copy to be chased down: the subscriber list a creator sees is a view of our database, and an erased address is gone from both at once.
49
49
50
-
A creator can export their subscriber list, which puts a copy of the addresses on their own machine. That copy is outside our database, so it is worth being exact about it. Under this arrangement a creator must not keep mailing an address after it is erased, and must delete the exported copy when we tell them an erasure covers it. A subscriber does not have to chase that: write to privacy@makenot.work and we pass it on and follow it up.
50
+
A creator can export their subscriber list, which puts a copy of the addresses on their own machine. That copy is outside our database, so it is worth being exact about it. Under this arrangement a creator must not keep mailing an address after it is erased, and must delete the exported copy when we tell them an erasure covers it. A subscriber does not have to chase that: write to privacy@makenot.work and we pass it on and follow it up. The same two obligations are written into the [Terms of Service](./terms-of-service.md), under Creator Terms, which is where a creator agrees to them.
51
51
52
52
Suppression records are the exception, and they are the same exception the Privacy Policy already makes. If an address bounced or filed a complaint, we keep a one-way record that we must not mail it again. Erasing that record would mean mailing the address again the next time somebody adds it.
53
53
@@ -78,7 +78,7 @@
78
78
## What This Does Not Cover
79
79
80
80
- **Account mail.** Receipts, security notices and password resets are ours alone. No creator is involved and no creator can stop them. See [Email you cannot turn off](../guide/email-you-cannot-turn-off.md).
81
-
- **Lists a creator runs somewhere else.** If a creator exports their subscribers and mails them from another service, that service and that creator are the parties involved, and we are not one of them.
81
+
- **Lists a creator runs somewhere else.** If a creator exports their subscribers and mails them from another service, that service and that creator are the parties involved, and we are not one of them. The erasure obligations above still follow the addresses, because they came from here.
Makenotwork is operated by Make Creative, LLC ("we", "us", "our"). By using our service, you agree to these terms.
6
6
@@ -42,6 +42,18 @@
42
42
### Content Moderation
43
43
We remove content that violates these terms. We try to give notice before removal when possible. See [Content Moderation](./moderation.md) for details.
44
44
45
+
### Subscriber Lists
46
+
47
+
If you run a project mailing list, you and Makenotwork are joint controllers of the subscriber data on it. The arrangement is set out in [Mailing List Data Processing](./mailing-list-data-processing.md), and running a list means you agree to it.
48
+
49
+
Exporting your subscriber list puts a copy of those addresses on your own machine, outside our database. While you hold such a copy:
50
+
51
+
- You must not mail an address after it has been erased.
52
+
- You must delete the exported copy of an address once we tell you an erasure covers it.
53
+
- You are responsible for keeping the copy secure for as long as you hold it.
54
+
55
+
A list you mail from another service is yours to answer for, and we are not a controller of it. That does not release the obligations above, which follow any address you took from us.
56
+
45
57
## Fan Terms
46
58
47
59
### Purchases
@@ -66,6 +78,8 @@
66
78
- We don't sell your data
67
79
- You can export or delete your data
68
80
81
+
If you run a project mailing list, [Mailing List Data Processing](./mailing-list-data-processing.md) sets out who answers a subscriber's request and what you agree to as a joint controller.
82
+
69
83
## Termination
70
84
71
85
### By You
@@ -109,5 +123,6 @@
109
123
110
124
- [Privacy Policy](./privacy-policy.md): Data collection and handling
111
125
- [Acceptable Use Policy](./acceptable-use.md): Content rules
126
+
- [Mailing List Data Processing](./mailing-list-data-processing.md): Joint controllership for project mailing lists
112
127
- [What We Guarantee](../about/guarantees.md): Platform commitments
113
128
- [How We Work](../about/how-we-work.md): Business model and pricing