Security
land is built so the dangerous things can't happen, instead of relying on anyone, human or agent, to be careful. This page says what we promise, what we keep, who can reach your code, and how to reach us. It describes land as it runs today.
| Does land keep my code? | Yes. A copy of each repository you add and of the changes your agents send, until you ask us to delete it. |
|---|---|
| Does land read my GitHub? | No. Signing in reads your public GitHub profile and nothing else. land holds no GitHub access at all; your agent pushes results with its own. |
| Where does it run? | Google Cloud, in Mumbai (asia-south1). |
| Is it encrypted? | In transit over HTTPS. At rest, including backups, by Google Cloud's default encryption. |
| Can my tests reach the internet? | No. Tests run offline, cut off from the internet, from other customers and from land's own systems. |
| Can other customers see my code? | No. Every account sees only its own repositories, and each repository is checked on its own. |
| Certifications? | None yet. land is not SOC 2 audited. |
What can't happen
- main can't move without proof. When a change lands, land signs a statement naming the exact files that passed and which tests vouched for them. Your agent pushes the commit and the statement together, so GitHub takes both or neither. Anyone can check the proof offline with
land verify; runland verify --protected mainin your CI and any commit on main that didn't pass land fails it. - A change can't vouch for itself. Your tests and the code they call run without the ability to touch land's record of what passed. A change that edits the proof afterwards no longer matches it.
- Agents can't quietly weaken your tests. Every verdict, and every signed statement, lists each test that was removed, newly skipped or edited. Nothing about your tests changes without it being written down.
- Your code can't call out. Tests run with no network. Your dependencies are installed with network on only to fetch what your repository declares, and even then they can't reach land's systems, our credentials or anyone else's data.
- One customer can't reach another. Accounts are separate all the way down: repositories, test memory, landing logs, keys.
- A copy of our database can't sign anyone in. Keys and tokens are stored only as hashes.
- land can't push to your GitHub. It never has your GitHub access to begin with.
What land keeps
| What | What's in it | How long |
|---|---|---|
| Your repository | The committed files from land add (no history, never .env) and the commits land merge sends | Until you ask us to delete it |
| Test memory | File paths, function names and line ranges, which functions each test reads, content hashes, and each test's result and output | Until you ask us to delete it |
| Landing log | When each change was checked, whether it landed, how many tests ran, and how long it took | Until you ask us to delete it |
| Your account | Your GitHub user ID and login. No email address, and no GitHub token is kept | While you have an account |
| Keys and tokens | Stored only as hashes, so a copy of our database can't be used to sign in | Until revoked |
| Payments | Handled by Stripe. land never sees your card number | Stripe's terms |
land keeps a copy of your code because it merges onto it and remembers which tests each function affects. That memory is how it skips tests. The test memory itself holds names, line numbers and hashes rather than your files, though a test's output can quote your code when it fails.
Who can reach your code
| Who | What they can do |
|---|---|
| You | Everything in your account, after signing in with GitHub |
| Your agents | With the key from land login, send changes to land. main moves only when land's check passes |
A LAND_TOKEN | Only the repositories named when it was made. It can run land merge, but can't add repositories or make new tokens |
| Other land accounts | Nothing |
| Ataraxy Labs | The engineers who run land can reach the servers, and do so only to operate and fix the service |
Nothing that runs your code holds any of land's own keys.
GitHub
Signing in asks GitHub for no permissions, so land sees only your public profile. land never clones, reads or pushes your GitHub repositories. It hands your agent a commit, and your agent pushes it with the access it already has. Turn on signed commits and your agent makes the commit itself with --result tree.
Deleting your data
Copies are also kept in encrypted backups. Deleting your data deletes it from the backups too. There's no delete button yet. Email rohan@ataraxy-labs.com from the address on your GitHub profile, or name your GitHub login, and we'll delete the repository copies, test memory and landing log for your account and write back when it's done.
Reporting a problem
Found a security issue? Email rohan@ataraxy-labs.com with what you found and how to reproduce it. Please give us a chance to fix it before you share it publicly.
We hunt for these ourselves too. Every security bug we find gets a test that fails until it's fixed, and that test stays, so the same hole can't come back.