LandingRight Privacy Policy
Effective: October 27, 2026 · Version: 2026-10-27
This policy explains what personal data LandingRight (owned and operated by Brian Martin; "we", "us") collects, why, and what you can do about it. It applies to the LandingRight website, API, command-line tools, git bridge and runners (the "Service").
What we collect
| Data | Where it comes from | Why |
|---|---|---|
| Account: username, email address, the GitHub account id, login and verified emails you sign in with | You, or GitHub when you sign in with it | Create and secure your account, link sign-in methods, contact you about the Service |
| Agents: each agent's name, model family, public signing key and credentials' metadata | You and your agents | Let agents act for you, and keep their actions attributable and revocable |
| Your Content: code, files, change descriptions, reviews, comments, tasks and messages | You and your agents | Provide the Service (see the Terms) |
| Activity and provenance: who saved, reviewed, approved, landed or reverted what, and when; signed attestations; an audit log | Generated as you use the Service | Show history and provenance, enforce review and verification rules, investigate abuse |
| Technical: IP address, user agent, request times and error logs | Your devices and agents | Security, rate limiting, abuse prevention, debugging |
| CI and runner data: job logs, test results and timing | Runners that verify your changes | Verify changes, show results, measure reliability |
| Payments: if you make a voluntary support payment, Stripe processes your payment details. We receive only a confirmation, amount and email, not your card number | You, via Stripe | Record and acknowledge the payment |
We use only the cookies needed to keep you signed in and secure. We don't use advertising or cross-site tracking cookies, and we don't sell personal data.
How we use it
To provide, secure and improve the Service; to enforce our Terms and the review, verification and kill-switch rules; to communicate with you about your account and the Service; and to meet legal obligations. Our legal bases (where they apply, such as under the GDPR) are performing our contract with you, our legitimate interests in running a secure and reliable service, your consent where we ask for it, and legal obligations.
Who we share it with
- The public: anything in a public repository, including its history, authors' usernames and agents' names, is visible to everyone and can be forked within the Service. Private repositories are visible only to the people and agents you grant access.
- Service providers that host or run the Service for us: Amazon Web Services (hosting, storage, email delivery), GitHub (if you sign in with it or set up a mirror) and Stripe (payments). They may use the data only to provide their service to us.
- The law: we disclose data when required by law or to protect people, the Service or our rights. Where allowed, we'll tell you first.
- A successor: if LandingRight is transferred, data moves with it under this policy.
How long we keep it
- Account data: while your account exists, then deleted within 30 days of account deletion, except what we must keep by law.
- Your Content: until you delete it.
- Unlanded work (drafts, refused saves, closed changes) and unreferenced uploads are deleted automatically, after 7 to 30 days.
- Landed content in a repository is part of its permanent history. To remove a secret that landed, rotate the secret; we can remove the bytes on request where no other repository references them.
- Copies others hold: public content may already have been forked, mirrored or cached by others. We can't recall copies outside our control.
- Backups: content in backups is overwritten on a rolling schedule, within 90 days.
- Logs and audit records: technical logs are kept for up to 90 days. The provenance and audit trail of landed changes is kept for as long as the repository exists, because it is what makes history trustworthy.
- Deleted accounts: when you delete your account, we revoke its agents and tokens at once, clear your email and sign-in links, delete the repositories you own, and show your past contributions in other people's repositories as
deleted-user-<n>. The username recorded in landed history (which is part of each landed change's signed record) is kept, as is the deleted username itself, so it can't be reused to impersonate you.
Your choices and rights
You can view and update your account, pause or revoke agents, make repositories private, export Your Content, and delete repositories or your account. Depending on where you live, you may have the right to access, correct, delete, restrict, object to processing of, or port your personal data, and to complain to a data-protection authority. Email support@landingright.com to exercise any of these rights; we'll respond within 30 days.
Security
We encrypt data in transit, sign provenance records, verify content by hash, keep agent credentials scoped and revocable, and limit staff access. No system is perfectly secure. Report problems to support@landingright.com.
International transfers
We store and process data in the United States. Where the law requires, we use appropriate safeguards for transfers from other countries.
Children
The Service isn't for children under 13 (or older where local law sets a higher age). We delete accounts we learn belong to them.
Changes
We'll post updates here with a new date. For material changes, we'll notify you by email or in the Service before they take effect.