Who runs DebtKeeper

DebtKeeper is built and operated by Red Ink Lab, an independent studio established in the European Union, run by its founder, that builds sites and tools for adult creators. One person designs it, writes it, runs it and answers the email. There is no company behind the company, no investors, and nobody buying the data — because nobody would be selling it.

There is no personal name on this page, and that is the studio’s policy rather than an oversight: Red Ink Lab keeps its people off the front page, the same discretion it builds for the creators it works with. It is a choice about the front page, not about accountability — there is a human at every address below, and email gets answered by the person who wrote the code.

A registered company is being set up to hold the product; when it exists, this page will name it.

On our own servers, in the European Union. The primary server is in Amsterdam; a live replica is in Amsterdam too, at a second provider, so one company having a bad week cannot take the whole thing down. Backups are daily, encrypted, kept off-site inside the EU, and restore-drilled — we have actually rebuilt the database from them, rather than assumed it would work. Everything sits under the GDPR because it is the strictest data-protection regime there is, and we would rather build under it than somewhere looser and hope nobody minds.

Both hosts were chosen because they work with adult businesses openly, so nothing here depends on a compliance department never reading the homepage. We did not take that from a marketing page: we asked their legal and compliance teams in writing about data protection, data location and processing terms, and we have the answers on file.

Under the GDPR, the operator of DebtKeeper is the data controller; the Privacy Policy says exactly what is held, why, and for how long. Reach the controller at [email protected].

Start with how little there is to lose. Signing up takes a display name — make one up, most do — an email and a password. No legal name, no address, no phone.

• It processes no payments. Not one. Money moves between a Domme and a sub on whatever platform they already use — YouPay, Throne, a bank, cash. DebtKeeper is the ledger they both agree on, and it only ever holds what one of them typed in and the other confirmed.
• No card numbers, no bank details, no payment-platform logins. The safest way to protect card data is to never accept any.
• No tracking. Two first-party cookies — your sign-in session and a “you’ve seen the 18+ notice” flag — plus a short-lived one for each connection you start to X or Discord, which expires by itself within ten minutes whether or not you finish. No analytics pixels, no ad networks, no fingerprinting.
• Your data leaves with you. One tap exports your whole account as JSON; one tap deletes it. Deletion anonymises the account and clears everything personal; the shared ledgers stay because they belong to two people, but nothing on them points at you any more.
• Age verification stores a result, not a document. The check itself is done by Didit; DebtKeeper stores “verified” or not, and never the selfie or the ID — those stay with Didit, for a limited time, and the Privacy Policy is exact about what that means.
• Private notes stay private. What you write about the other party is never shown to them and is not in their export.

If any sentence above stops being true, the Privacy Policy and the Changelog change first, and this page changes with them.

Yes, DebtKeeper is built with AI tooling, and we are not going to pretend otherwise. AI is a tool in the process, not the process — nobody types “make me DebtKeeper” and gets a working ledger. The engineering, the decisions and every figure the ledgers produce are one person’s, who understands all of it because they are the one on the hook when it breaks. It is worth being exact about what that does and does not mean.

What it means: code gets written fast, and features land often — every one of them dated on the Changelog, which goes back to the first week.

What it does not mean: nothing ships untested. Every change runs through more than four thousand automated tests before it can go live, fourteen of those suites run against a real PostgreSQL server and hammer the money paths with concurrent writers, because that is where a ledger actually dies. No current balance is ever stored — every figure is recomputed, from the agreed principal and the ledger entries, at the moment you look at it, so it cannot silently drift — and a nightly job re-derives every contract and raises an alarm if a single cent disagrees. Every change is reviewed before it deploys, deploys go to the replica first with a verified rollback, and independent security reviews have been run against it, with the findings fixed and shipped.

The stack is deliberately boring: Node, PostgreSQL, nothing exotic. Boring, documented and heavily tested is what makes a thing someone else could pick up — and it means none of it depends on any one tool being available tomorrow.

The person who wrote it also uses it, and reads every crash report the app files about itself.

It doesn’t. DebtKeeper is free; the servers, the replica, the backups and the verification checks come out of the founder’s pocket, and that is the whole reason there are no ads, no trackers and nothing sold on to anyone — it was never designed as though it had to make money out of the people using it. There are no investors, no board and no exit plan; nobody upstairs needs a number to go up.

There are no plans for a paid tier today. If one ever makes sense, it would be optional extras for people who want to chip in toward the running costs, announced on the Changelog before it lands and explained in the Discord before that. What will not change is the order things are decided in — see the next section.

DebtKeeper was built community-first from the first line, and it still is. What that means in practice, rather than as a slogan:

• The people using it decide what gets built next. Ideas go on the suggestion boards in the Discord, and every one gets a public answer — under review, planned, shipped, or not now with the reason. Saying no in public is the part most feedback boards skip, and it is the only thing that makes the yeses worth reading.
• Nothing that touches your privacy or your money changes quietly. It lands on the Changelog, dated, in plain words, and if it is a change to what is held or shown, the Privacy Policy moves in the same breath.
• The best review of DebtKeeper is one we had nothing to do with. Ask in the Discord what it is like to deal with — people who have been there a few weeks can tell you, and they have nothing to gain by saying it. That is worth more than anything written on this page.

And it is not stopping — not even close. There is a lot more coming, and it will arrive the same way: passion, honesty, and the community deciding what matters.

Because “who is behind it” is also a way of asking “how do I know a message is really from you”:

• The site: debtkeeper.app — nothing else, no other domain.
• Email: [email protected] (data and rights) and [email protected] (everything else).
• X: @debtkeeper.
• Telegram: the bot @DebtKeeperAppBot, and the Telegram guide says what it does.
• Discord: the DebtKeeper bot, and the DebtKeeper server you can only join from inside the app — there is no invite link, and anyone offering you one is not us. The Discord guide has the details.

Anything else claiming to be DebtKeeper — a different domain, a DM from a personal account, a “support” address that isn’t one of the two above — is not. If you’re unsure, email us at either address and ask.

If you find a real security or privacy issue, email [email protected]. It gets fixed fast, you get the credit if you want it, and that offer does not expire.

Ask. Email is read by the person who builds this, and it usually gets an answer within a day. The studio behind it is at redinklab.com.