Contact
Write to the title, not the imprint.
The writing lives where the byline lives, so a note about an article reaches the person who can act on it fastest by going straight to that publication’s own address. The imprint’s inbox is for the network as a whole — and for anything its legal pages are answerable for.
The imprint
One address, read by the people who run Cognate Press. There is no ticketing system behind it and no autoresponder in front of it.
What belongs here
- The network as a whole — the imprint, this site, the way it is put together.
- Rights, syndication and permission to reuse anything published at cognate.press.
- Press, interviews, and speaking.
- The Cognate letter: subscription problems, or anything about the list itself.
- Data protection: any request under the GDPR concerning cognate.press.
The publications
Each title answers on its own domain, under the same local part. A correction, a disputed benchmark, a version detail that has changed since publication — send it here and it reaches the byline directly.
seven publications, seven addresses — each one contact@ the domain its writing is published on.
Where to send what
When it is genuinely unclear, the imprint’s address is the safe one — a message sent to the wrong inbox is forwarded, not dropped.
A correction to an article
→ The publication that ran it
Permission to translate or republish a piece
→ The publication that ran it
A question for the author of an issue
→ The publication they write
Data processing on a publication’s own domain
→ That publication
Press, rights, or the imprint as a whole
→ The imprint
A GDPR request about cognate.press
→ The imprint
What to expect
There is no contact form here, and that is deliberate. These are static sites with nothing running behind them; a form would need a third party to receive it, and that third party would then be processing your message on our behalf. Email needs neither, and it leaves the record in your own sent folder rather than only in ours.
Most messages are answered within a few working days. A request under the GDPR is answered within one month, as Art. 12(3) requires; if a request is complex enough to need longer, you are told so inside that first month. What happens to the message itself is described in the Privacy Policy.
Corrections are welcome and are the fastest way to make a piece better. If a claim is wrong, a benchmark does not reproduce on your machine, or a version detail has moved since publication, say what you observed — the article is corrected in place, with the date and the evidence that changed it.