Security
Sub-processors
Effective October 12, 2026
Airgetlam Labs LLC uses a small number of other companies to run its service. This page names every one of them, what it does, and what it can see.
We will tell customers before we add or replace a sub-processor, so that a customer who objects has time to raise it with us. If a provider fails or becomes unsafe, we stop sending it your data right away and tell you. Its replacement gets your data only after you've had the chance to object.
For the product
These are the companies that handle customer data for the product. The list is short by design: the code Ryo reads goes to one place, Google Cloud, and does not pass through anybody else on the way.
| Company | What it does | What it can see | Where |
|---|---|---|---|
| Google Cloud | Runs the service, stores each customer's code and model, and runs the nightly training | A customer's code and their own model, inside that customer's own storage, under that customer's own encryption key | United States (us-central1) |
| Stripe | Takes payment and runs each subscription | A customer's billing contact, payment details and subscription — never their code | United States |
| Resend | Sends the product's notices by email | Your account's contact addresses and the notices we send — never your code | United States |
| Google Workspace | Hosts our company mailbox, where replies to the product's emails arrive | What you email us, and our replies | Google's data centres, inside or outside the United States |
Your own code host — GitHub, for example — is not on this list. It is your provider, not ours: we read the repositories you connect us to through an app you install and can remove.
Ryo runs on our own infrastructure. Your code reaches another company's AI service only as answers to the AI tools your team connects, under your company's own terms with their makers.
For this website
The website is a separate system. It holds no customer code, no model and no product data — it exists to explain the service and to take enquiries. These three handle what you send us through a form on it, or by email.
| Company | What it does | What it can see | Where |
|---|---|---|---|
| Vercel | Hosts and serves the website, runs the function behind each form, and counts visits | The site's request logs, visit counts, and an enquiry in transit — the site itself stores nothing | United States |
| Resend | Sends each enquiry to us as one email, and the sender one confirmation | The contents of those two emails, and its own record of having sent them | United States |
| Google Workspace | Hosts our company mailbox | Every enquiry from our forms, what you email us, and our replies | Google's data centres, inside or outside the United States |
Each of these three publishes a data processing agreement and a list of its own suppliers, and we will provide the terms we are engaged under on request.
Development tools
Tools we use to build the service, like our code host, our package registries and our scanners, are not sub-processors, because customer data never reaches them. We keep an internal record of every one, and we will walk a customer's security team through it under the mutual agreement described on the security page.
Questions
Email privacy@airgetlamlabs.com and we will answer. If you object to a sub-processor we have given notice of, tell us and we will work through it with you.