{
 "version": "https://jsonfeed.org/version/1.1",
 "title": "Geenius Newsletter blog",
 "home_page_url": "https://newsletter.geenius.io/blog/",
 "feed_url": "https://newsletter.geenius.io/blog/feed.json",
 "description": "Posts from the team building Geenius Newsletter: double opt-in, the consent log, and why a person approves every send.",
 "language": "en",
 "items": [
  {
   "id": "https://newsletter.geenius.io/blog/bringing-your-readers-with-you/",
   "url": "https://newsletter.geenius.io/blog/bringing-your-readers-with-you/",
   "title": "Bringing your readers with you, with their consent",
   "summary": "How importing an existing list into Geenius Newsletter works, what you state about consent, who is never imported, and how to take your list with you.",
   "date_published": "2026-10-24T09:00:00Z",
   "authors": [
    {
     "name": "The Geenius Newsletter team"
    }
   ],
   "tags": [
    "import",
    "consent"
   ],
   "content_text": "Most people who start a newsletter here already have readers somewhere else. This post explains how the import works and why it asks the questions it asks.\nYou state the consent\nYou upload a CSV. The import screen asks you to say, in its words, that every person agreed to get this newsletter, and where and on which day. We keep that statement together with your name and the time, so the record of who vouched for the list stays with the list.\nWho is never imported\nAddresses that unsubscribed, were erased, bounced or complained are never imported again. A person who left stays gone, even if their address is still in an old file.\nGermany and Austria\nImported readers in Germany and Austria get no real send until they confirm again by link. It is one extra click for the reader and a clean record for you.\nA careful first fortnight\nA new workspace has lower import and sending limits during its first 14 days. The limits rise on their own.\nWhat happens after the import\nAn imported reader is treated like any other: only readers who said yes get your issues. Every issue has a one-click unsubscribe, and you can erase a reader for good. Addresses that hard bounce, soft bounce three times or complain are suppressed and never get an issue again. Readers can also download their own data.\nWhy we ask\nA list is only worth what its readers agreed to. The statement you make at import, the consent log that only ever grows and the double opt-in for new signups all point the same way: you can show how and when a person agreed, and the person can leave in one click.\nYour list is yours\nA signed one-time export gives you your readers whenever you want them.\nWhere it stands\nNewsletter is in early access: invite-only, with payments in test mode. Sends run in test mode, so no mail leaves the app yet. To be let in, request access."
  },
  {
   "id": "https://newsletter.geenius.io/blog/why-a-person-approves-every-send/",
   "url": "https://newsletter.geenius.io/blog/why-a-person-approves-every-send/",
   "title": "Why a person approves every send",
   "summary": "Why every Geenius Newsletter send waits for a person, why the approval is tied to the content and the audience, and why your AI cannot give it.",
   "date_published": "2026-10-22T09:00:00Z",
   "authors": [
    {
     "name": "The Geenius Newsletter team"
    }
   ],
   "tags": [
    "approval",
    "ai"
   ],
   "content_text": "A newsletter goes to people who trusted you with their address. A wrong mail cannot be taken back. So in Geenius Newsletter, nothing goes out until a person says yes.\nThe yes is tied to what you saw\nAn approval is not a switch you flip once. It holds the exact content of the issue and the audience it goes to. If someone changes a sentence or adds a list after you approved, the send needs a new approval. What you approved is what goes out.\nYour AI prepares, you decide\nYour own AI can do a lot of the work: start a draft from your notes, fill in sections, check that an issue is ready. What it cannot do is approve, schedule a send or mail a list. Those actions do not exist on the door it uses. When your AI thinks an issue is ready, it asks, and you decide in the app.\nWhy not let it send?\nBecause the cost of a mistake falls on your readers, and on your sending reputation. An AI that misreads a note, or a page that tries to give it instructions, should never be one step from a mail to thousands of people.\nWhat an approval looks like\nThe approval card shows the subject, the content as the reader will see it, the lists it goes to and how many active readers that is. Below it are the test you sent to yourself and when. Approve, and the card records who said yes and the exact version of the issue.\nIf you then fix a typo, the card goes back to waiting. That can feel strict, and it is meant to be: the version that goes out is always a version a person read.\nPausing is part of the plan\nApproval is the first safety net. The second is that sending watches itself. A hard bounce or a complaint suppresses the address, three soft bounces count as a hard one, and when complaints pass 0.1 % of a send the send pauses. You look at what happened, then decide whether to go on.\nWhere it stands\nApproval is built and in the app. Newsletter is in early access, and sending to real inboxes is not switched on yet: sends run in test mode."
  },
  {
   "id": "https://newsletter.geenius.io/blog/double-opt-in-and-a-log-that-only-grows/",
   "url": "https://newsletter.geenius.io/blog/double-opt-in-and-a-log-that-only-grows/",
   "title": "Double opt-in, and a log that only grows",
   "summary": "Why Geenius Newsletter readers confirm before they get anything, why the consent log is never edited, and what happens to addresses that bounced or complained.",
   "date_published": "2026-10-22T09:00:00Z",
   "authors": [
    {
     "name": "The Geenius Newsletter team"
    }
   ],
   "tags": [
    "readers",
    "consent"
   ],
   "content_text": "A list is only worth something if the people on it asked to be there. Geenius Newsletter is built around that.\nConfirm first\nSomeone signs up and gets a mail with a link. Until they click it they are pending and get no issues. It costs a few signups. It saves you from typos, from addresses entered by someone else, and from complaints later.\nA log that is never edited\nEvery signup, confirmation and change is written to the reader's consent log, and the log is only ever added to. If a reader or an authority asks how a person agreed, you can show it.\nImports with a promise\nMoving from another tool? You can import a CSV, but the import screen asks you to state that everyone agreed, and where and when. Addresses that unsubscribed, bounced or complained never come back in. Imported readers in Germany and Austria confirm again before a real send.\nWhy the confirmation mail matters\nA single opt-in form takes any address typed into it. Some are typos, some belong to someone who never asked, and a few are traps that mail providers use to spot senders who do not check. Each of those turns into a bounce or a complaint later, and complaints are what get a sending domain blocked. The confirmation mail filters them out before your first issue, so the readers you count are readers who can and want to read you.\nIt also gives you a clean answer when someone asks "why am I getting this?". The consent log shows the signup page, the day, and the click on the confirmation link.\nLeaving is easy, and final\nEvery issue carries a one-click unsubscribe. A reader who leaves is suppressed, and an import cannot bring them back. You can erase a reader for good, and readers can download their own data. A signed one-time export lets you take your list with you, because it is yours.\nWhat we do not count\nNewsletter does not count opens or clicks. It counts what it needs to protect your list and your domain: what was sent, hard bounces and complaints. We think that is the honest set of numbers for mail people asked for.\nWhere it stands\nAll of this is built and in the app. Newsletter is in early access: invite-only, and sends run in test mode until real sending is switched on."
  }
 ]
}