diff --git a/CITATION.cff b/CITATION.cff
index 8cd938e..42a235b 100644
--- a/CITATION.cff
+++ b/CITATION.cff
@@ -5,6 +5,10 @@ type: software
 authors:
   - family-names: "Yaylali"
     given-names: "Kemal"
+contact:
+  - family-names: "Yaylali"
+    given-names: "Kemal"
+    email: "support@yaylali.uk"
 version: "2.0.0"
 date-released: "2026-09-30"
 license: MIT
diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
index 0ff76d8..ba8acdb 100644
--- a/CODE_OF_CONDUCT.md
+++ b/CODE_OF_CONDUCT.md
@@ -25,6 +25,6 @@ anyone representing the project elsewhere.
 
 ## Enforcement
 
-Report problems privately to the maintainer through the contact details on https://gitea.yaylali.uk/kemal. Reports
-are handled confidentially. The maintainer may edit or remove contributions and may block people who do not follow
-this code, starting with a private warning where that is reasonable.
+Report problems privately to **support@yaylali.uk**. Reports are handled confidentially. The maintainer may edit
+or remove contributions and may block people who do not follow this code, starting with a private warning where
+that is reasonable.
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 94d5955..e658519 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -62,3 +62,5 @@ and 3.13. If your change touches file formats, calling, QC or outputs, also run
 Use the issue templates. For a wrong or unexpected result, attach the `run_manifest.json` of the run and the exact
 command; it records every version, option and input checksum. Please do not attach vendor files or any genetic data
 of real people. For security issues see `SECURITY.md`.
+
+Questions and feedback that do not fit an issue are welcome at **support@yaylali.uk**.
diff --git a/README.md b/README.md
index 02aa4f1..175b7bb 100644
--- a/README.md
+++ b/README.md
@@ -40,6 +40,7 @@ It runs on anything from a Raspberry Pi to a cloud server.
 * [Development](#development)
 * [Repository layout](#repository-layout)
 * [Documentation](#documentation)
+* [Feedback and support](#feedback-and-support)
 * [Citing](#citing)
 * [Licence, data and trademarks](#licence-data-and-trademarks)
 
@@ -356,6 +357,12 @@ packaging/         conda recipes (plus Dockerfile at the root)
 * [`CONTRIBUTING.md`](CONTRIBUTING.md), [`SECURITY.md`](SECURITY.md), [`CODE_OF_CONDUCT.md`](CODE_OF_CONDUCT.md)
 * [`branding/README.md`](branding/README.md) and [`blog/`](blog/)
 
+## Feedback and support
+
+Bug reports and feature requests go to the [issue tracker](https://gitea.yaylali.uk/kemal/SimurgArray/issues), using
+the templates. Questions, feedback and anything that should not be public, such as security reports, go to
+**support@yaylali.uk**.
+
 ## Citing
 
 If SimurgArray helps your research, please cite it using [`CITATION.cff`](CITATION.cff) (version 2.0.0, 2026).
diff --git a/SECURITY.md b/SECURITY.md
index 5ce148d..3539265 100644
--- a/SECURITY.md
+++ b/SECURITY.md
@@ -6,8 +6,7 @@ Security fixes go into the latest release. Older releases are not patched; upgra
 
 ## Reporting a vulnerability
 
-Please do not open a public issue for a security problem. Contact the maintainer privately through the contact
-details on the maintainer's profile page, https://gitea.yaylali.uk/kemal, and include:
+Please do not open a public issue for a security problem. Write privately to **support@yaylali.uk** and include:
 
 * the SimurgArray version (`simurg --version`),
 * what an attacker could do and under which conditions,
diff --git a/blog/05_using_simurgarray_and_the_bird_behind_the_name.md b/blog/05_using_simurgarray_and_the_bird_behind_the_name.md
index 3981e09..a73925b 100644
--- a/blog/05_using_simurgarray_and_the_bird_behind_the_name.md
+++ b/blog/05_using_simurgarray_and_the_bird_behind_the_name.md
@@ -153,6 +153,6 @@ A tool for researchers does not need a marketing department, but it does need to
 
 ## Thank you
 
-If you have read all five posts, you now know more about SimurgArray than most of the machines it has run on. The code goes public on the calendar from the previous post. Until then, if you work with arrays and want to try it, or want to tell me which of my choices are wrong, I would be glad to hear from you.
+If you have read all five posts, you now know more about SimurgArray than most of the machines it has run on. The code goes public on the calendar from the previous post. Until then, if you work with arrays and want to try it, or want to tell me which of my choices are wrong, I would be glad to hear from you at support@yaylali.uk.
 
 The birds made it to the mountain. Now the interesting part starts.
diff --git a/pyproject.toml b/pyproject.toml
index 4cdd9bb..c696edd 100644
--- a/pyproject.toml
+++ b/pyproject.toml
@@ -10,6 +10,7 @@ license = "MIT"
 license-files = ["LICENSE", "THIRD_PARTY_NOTICES.md"]
 requires-python = ">=3.12"
 authors = [{ name = "Kemal Yaylali" }]
+maintainers = [{ name = "Kemal Yaylali", email = "support@yaylali.uk" }]
 keywords = ["genotyping", "microarray", "infinium", "idat", "gtc", "vcf", "bioinformatics"]
 classifiers = [
     "Development Status :: 5 - Production/Stable",