How we research, label and correct what we publish
StackWeaver publishes guides on African fintech regulation and compliance evidence. People use them to make real decisions, so we hold them to rules we can show you.
Last updated 2026-10-04
Who is responsible
Our guides are written by our founder, Oluwafemi Ofobutu, with research support from the StackWeaver team, and he is responsible for what we publish. Each page shows who wrote it and when it was published and last updated. When a named specialist, such as a lawyer or a certified auditor, has reviewed a page, we show their name and the review date. We only do that when the review actually happened.
Where our information comes from
We start from primary sources and link to them:
- →Central Bank of Nigeria (CBN) circulars, frameworks and baseline standards
- →Nigeria Data Protection Commission (NDPC): the NDPA 2023 and the GAID 2025
- →Nigerian Financial Intelligence Unit (NFIU) guidance
- →AICPA (SOC 2), the PCI Security Standards Council (PCI DSS) and ISO (ISO/IEC 27001)
- →Named news reporting and law-firm analysis, used only to add context, and labelled as such
Regulatory dates and thresholds change. Every guide carries a published date and an updated date, and we revise guides when the underlying rules change.
Facts, views and examples are labelled
A fact we can point to: a regulator circular, a framework document, a court or enforcement record, or named reporting. The source is linked next to it.
Our opinion or recommendation. It is labelled so you can weigh it as a view from a company that sells compliance evidence software and services.
An example, scenario or sample built to explain an idea. It is not a real client, a real result or real data. NovaPay is one such fictional sample.
What we will not claim
- ×We do not claim that StackWeaver, or anyone using it, is certified, approved or endorsed by a regulator or standards body.
- ×We do not claim that a company is "compliant" or "passed" an audit because of us: only regulators and independent auditors decide that.
- ×We do not claim statistics, timelines or savings we cannot source.
- ×We do not claim client names, logos, quotes or results without written permission.
- ×We do not claim credentials for people we do not name.
How we use AI
We use AI tools to help research and draft. They do not decide what we publish. Every factual statement must trace to a linked source or be labelled as our view or an illustration, and a person at StackWeaver is accountable for each page.
Our interest
StackWeaver sells compliance evidence software and engineering services. Where our product is relevant to a guide, we say so plainly. We do not accept payment to mention other products.
Corrections
If you find an error, email info@stackweaver.cloud with the page address. We check it against the source, correct confirmed errors, update the page date and note material corrections on the page.
Not legal advice
Our guides explain regulations and how to prepare evidence. They are not legal advice. For decisions about your own obligations, speak to a qualified lawyer or the relevant regulator.
Common questions
Who writes StackWeaver guides?
Our founder, Oluwafemi Ofobutu, writes them with research support from the StackWeaver team, and he is responsible for what we publish. When a named specialist reviews a guide, the page shows their name and the review date.
Do you use AI to write content?
Yes, as a research and drafting aid. AI does not decide what we claim: every factual statement must trace to a linked source or be labelled as our view or as an illustration, and a person at StackWeaver is accountable for each page we publish.
Is StackWeaver content legal advice?
No. Our guides explain regulations and how to prepare evidence. For decisions about your own obligations, speak to a qualified lawyer or your regulator.
How do I report an error?
Email info@stackweaver.cloud with the page address and what is wrong. We correct confirmed errors and update the page date; material corrections are noted on the page.