What we hold, what we have promised, and what we do not have yet.
This page is about this website and the company behind it. Both apps are still in development and will publish their own privacy policies before they ship. Where something is not true yet, it says so.
Which pages get read, if you accept analytics, and a message with its request log, if you write to us.
No third-party request until you accept one. Data stored in the EU (Google Cloud, Netherlands); pages delivered through Google's global network.
One person, one registration, one address. The registration and the address are in the imprint; the name goes there before launch.
We hold little about you, and mostly only what you choose: which pages get read, if you accept analytics; a message, if you write to us, with a 30-day log of that request; and what you report about an article, without who you are. The privacy policy names every entry: what is stored, where, and for how long.
The analytics is Google Analytics 4, and it loads only after you accept it. We say the name because you would find it anyway.
Read the privacy policy →Five things we've tied our hands on.
No ads, no data sales: structurally
The apps are meant to be paid for by the people who use them, so there is no advertising business here to feed and nothing to sell. Neither app will carry an advertising SDK.
Why it holds: the money comes from people who buy the apps, so there is no advertising business to feed.
Delete now, or with 7 days to undo
In both apps you will choose how your account is deleted: at once, or after a 7-day grace period in which you can still undo it.
Built in Readinity, which has not launched yet; planned for Cyberinity from its launch (Q4 2026). Checkable at each app's first release.
Breakage over silence
If a source or a feature stops being trustworthy, we say so in the changelog and pull it.
The record so far: the changelog was emptied and four false claims removed from this site in one day, and each removal is written down.
Preparedness for the physical world: what your household depends on, and what to do when it stops working.
Online exposure: what the internet already holds about you, and what is worth doing about it.
Readinity and Cyberinity are in development, and how they handle data is still changing. Rather than publish a summary that is out of date in a fortnight, each will publish its own privacy policy at its own address before it ships, and this page will link to them.
Everything above is easier to believe next to this list.
No independent audit. Nobody outside has reviewed the code or the infrastructure.
No open source. Every repository is private, including this website.
No bug bounty. We offer credit for a report, not money, and we say so rather than implying otherwise.
No app you can install. Neither product has shipped, and the waitlist stores nothing.
The apps are not local-first. They are being built around a server.
One person, not a team. Self-funded, no investors, nobody to answer to except the people who pay for the apps.
If the business ever changes hands, you will be told before the transfer, with export and deletion open until then. This goes into the terms before the apps take payment.
Cyberinity never puts what it finds about you behind an upgrade. This goes into its plans before launch; nothing is sold yet.
Which rules apply, and where we stand.
Not a badge, and not legal advice: the list we work from, with the status we would have to defend. Where a row says less than “met”, it says what is missing and when it is due.
This is our reading of what applies to this website and this company; each app carries its own. If you think a row is wrong, the contact form reaches a person.
AI drafts and translates; a person decides what is published. English and Dutch are read by a person before they go out. Every other language is machine-translated from that reviewed version and checked by machine. Each article says which of these applies to it, in a label at its top and again at its end.
Each article carries a label at its top saying how it was made: whether AI drafted or translated it, and whether a person reviewed it in its language. The panel “About this article”, which the label opens, repeats it and says what the text was reviewed for, and in which language.
Editorial responsibility: the owner of Novel Approaches (a sole proprietorship, KVK 93389612), as editor-in-chief. Contact: admin@novelapproaches.nl.
Every article is signed with a Content Credential: a signature saying what was published and when. For now the signing certificate is a development one, not on the C2PA trust list, and the credential is not yet offered to readers; both are planned before the public launch. A credential can be stripped by a careless re-save: it shows what was signed, not what was removed.
There are no accounts yet, so today there is nothing to delete or export. Before launch we intend deletion that takes effect at once or after a 7-day grace period you can undo, an export you can run yourself, and a notice period before any shutdown. Until export is built, we answer a portability request by hand, which is your right either way.
We target WCAG 2.2 AA: visible focus, targets of at least 24 pixels, a reduced-motion guard, a skip link, and text that carries its own direction. As a microenterprise we are exempt from the European Accessibility Act (permanently in the Netherlands, in Belgium until 28 June 2030); we follow it anyway. We check this ourselves; there has been no external audit.
Listen to this page
Phones get a menu, and inner pages reflow to one column on small screens. We don't have every device and assistive technology to test with, and nobody who relies on a screen reader or a switch device has tested the site yet. We meet the target as well as we can, and fix what we find or what you tell us about.
Pages, not PDFs: a page cannot go stale where nobody sees it.
Found something? Write to the address below. We aim to acknowledge within 3 working days and to send a status update within 10; the fix date is agreed with you rather than promised in advance. Good-faith research that does not degrade the service or touch other people’s data is welcome. We will not pursue you for it. We credit you when the issue is published, unless you would rather we did not. There is no bug bounty and no money.
Once an app ships, an actively exploited vulnerability goes to ENISA and the Dutch CSIRT within 24 hours. That is a duty under the Cyber Resilience Act, not a favour, and it applies to the apps and the servers behind them.
admin@novelapproaches.nl