What we do, and what we have not done yet.

Where we are: still in development

Nothing in the catalogue is open for download yet. The applications are still in development, and until one is genuinely finished we would rather say so than put a download button on a page.

We are not going to ship early to look busy. Something you can download is something you will run on a machine that matters to you. That is a higher bar than a demonstration, and we would rather be late than clear it badly.

When an application is ready, its page carries the download, the size of the file, and a reference code you can check it against.

What is already true

• Nothing is tracked. We do not watch what you click, how long you use anything, or what your files contain.
• Fault reports only, and only if you turn them on. The one thing worth collecting is what broke, so we can fix it. It stays off until you say yes, it shows you what it would send, and the software works exactly the same if you decline.
• It runs on your own machine. The work happens there, not on our servers. An internet connection is something you use, not something the software needs before it will start.
• It opens without asking permission. Your licence is checked on your own machine, using a key built into the application. It does not contact us to let you in, so it still opens if your internet is down, or if ours is.
• Encrypted on disk wherever an application keeps sensitive records.
• One failure stops a release. Anything that does not pass every check does not go out, and there is no override.

How the applications defend themselves

The question most software never answers: once it is running on your machine, what stops somebody else getting at it? These are the specific measures, per application, not a general promise.

• There is very little to attack. Because the software runs on your own machine, there is no account of yours sitting on our servers holding your data, so there is nothing of yours for anyone to break into. A company cannot leak what it never collected.
• Nothing is listening to the internet. Where an application needs a network it stays on yours. Beyond Phone Sync uses no middleman server of any kind and never opens a way in from outside. Beyond Video Calls keeps the part that does the translating off the internet entirely, by design.
• Devices prove themselves to each other. Phone Sync makes the phone and the computer confirm a code you set, over an encrypted connection, and keeps the list of paired devices locked in Windows' own protected storage. Another device on your network cannot join by asking nicely.
• Sensitive records are encrypted on disk. Beyond Books keeps your ledger in an encrypted file, not a plain one sitting in a documents folder, so a stolen laptop does not hand over your finances.
• Financial history is tamper evident. Every entry is chained to the one before it. Altering a past record breaks the chain and shows, which is what makes the books hold up when somebody asks.
• AI is kept in a box. Beyond Video Calls does its listening and speaking in separate, walled off processes, rather than handing over the machine.
• An application reaches only what you named. Beyond Publisher posts to the exact pages and accounts you authorised, and refuses anything outside that list before a request leaves, so letting us run one page never means handing over an account.
• No password is hidden inside our software. An application carries only the half of a key that is safe to publish. There is no password, token or private key buried in there for somebody to dig out, because there is none in there.

How this website is secured

The same standard applies to the site you are reading. Every item here is asserted by our test suite, so the claim fails the build before it can become untrue.

• The page can only run code that came from us. Nothing else is allowed to run here at all, and no part of another site can be embedded in this one.
• Nothing is loaded from anyone else. No analytics, no font service, no advertising network. The one outside address a public page may reach is B-Bot, our own assistant, and it only receives what you choose to type or say to it.
• Always encrypted. Browsers refuse to talk to this site over an unencrypted connection, before the first request is even made.
• No other site can wrap this one. It cannot be framed, embedded, or reached into from somewhere else.
• Your camera and location are refused at the door. Along with payment and connected devices. This site is not permitted to ask. The microphone is the one exception, on public pages only, so you can talk to B-Bot: your browser asks you first, and nothing embedded from elsewhere may use it.
• The public site holds nothing of yours. The client area is invite only, and nothing secret is kept in readable form there: not your password, not your sign-in, not your invitation code. Only a scrambled one way version of each.

How we keep updates honest

An update channel is a way for new code to reach your machine, so it is worth protecting properly. The list of what is in an update is signed with a key we keep offline, away from the machines that build the software, and your application checks that signature before it downloads a single byte. The keys are kept separate from each other, so losing one would not put the others at risk.

Check our homework

None of this is our own standard invented in private. These are the public references the measures above are built against, so you can read the source rather than take our word:

• The OWASP Secure Headers Project, the public checklist this site is measured against.
• The HSTS preload list, the public list of sites that browsers refuse to load unencrypted. This one is on it.
• Content Security Policy reference, if you want to read what a page is and is not allowed to load.
• Run an independent TLS audit of this site, from a service we do not control.

Reporting a vulnerability

Send findings to office@beyondllcfl.com. We acknowledge receipt, keep you updated while we work, and credit you when it is fixed unless you ask us not to. We will not threaten you for reporting in good faith.

Machine-readable policy: /.well-known/security.txt