Transparency
Don't take RTL's word for it.
This page exists so you don't have to trust RTL blindly — you can see how it actually works.
Transparency topics
What's collected, and why
Privacy is described per project, not as a blanket promise. Where a project stores data locally, that's stated plainly: your data stays on your device. Where a project needs authentication infrastructure, that's stated too — account identity may be verified by RTL's infrastructure while the project's actual data stays on your own system, wherever the architecture supports it. If a project can't honestly make that claim, this page won't make it for them.
Security architecture
Admin access uses strong password hashing, multi-factor authentication, rate limiting, brute-force protection, per-device session management, and full audit logging of administrative actions. Authorization is enforced server-side — never trusted to the front end alone.
How RTL is funded
RTL is currently self-funded and independently run. There is no advertising, no data resale, and no investor pressure shaping what gets built next.
Where things run
RTL manages its own hosting, domains, and deployment pipelines rather than outsourcing infrastructure decisions. Specifics for a given project are listed on that project's own page.
What's open
Not every RTL project is open source yet. Each project page states its actual status and links to a public repository where one exists.
Responsible disclosure
Found a security issue in an RTL project? Reach out through the contact channel listed on the relevant project page before disclosing publicly. Reports are taken seriously and acknowledged directly.