1. The list
These are the third parties that process data on our behalf, generated from what the service actually connects to rather than from a list somebody typed once. If a host is allowed to load on the page or receive a request from the console, it is here. Where a row says “only if you choose it”, nothing is sent until you do.
| Provider | Purpose | What it sees | Location |
|---|---|---|---|
| Selfmade Ninja portal (Frappe / ERPNext) | Account records, signup verification and the mail it sends — the ERP the operator works in. Run by us on our own infrastructure, listed because it is a separate system from this console. | Name, email, organisation, phone, country, plan, invoices, ticket history | India |
| Bare-metal datacenter provider — Hyderabad, India | The physical servers your workspaces run on. The provider has physical access to the hardware and no credentials to any machine on it. | Everything stored on your workspace disk, at rest on their hardware | Hyderabad, India |
| Cloudflare | Authoritative DNS for the platform zones and the DNS-01 challenge that issues TLS certificates for workspace domains. | Hostnames and DNS records for your domains; the delegation token for a zone you connect | Global (anycast) |
| Let's Encrypt (ISRG) | The certificate authority that issues TLS certificates for the console and for workspace domains. | Hostnames; issuance is logged to public Certificate Transparency logs | USA |
| Cashfree Payments | Card, UPI and net-banking payments for top-ups and plans. Card numbers never reach us: the payment form is theirs. | Payment amount, order reference, email, the payment instrument you enter on their form | India |
| Google reCAPTCHA | The human check on signup, sign-in, password reset and the enquiry form. | IP address, browser signals and the cookies Google sets for its own service | USA / global |
| Google Fonts | The typefaces the site is set in are loaded from fonts.googleapis.com until they are self-hosted. | IP address and browser user-agent, on every page load | USA / global |
| Google Sign-In and GitHub Sign-In | Optional identity providers for signing in. Used only for the accounts that choose them. | Your verified email and the provider's stable user id | USA / global |
| GitLab (git.selfmade.ninja, self-hosted) | Source of the platform software and lab templates your workspace installs, and the identity provider a trial platform starts with. | For a trial: the GitLab account you sign in with. For every workspace: nothing personal — it pulls code. | Europe (Contabo) |
| Crisp | The support chat widget on the site and the console. | Chat transcripts, the email address of a signed-in visitor, IP address, pages visited while the widget is open | EU (France) |
| YouTube (youtube-nocookie.com) | The demo recordings embedded on the product pages, in privacy-enhanced mode. Loaded only when you press play. | IP address and playback events, once a video is started | USA / global |
| Meta Platforms Ireland (Meta pixel and Conversions API) | Measuring which of our ads brought a visitor, and our ad audiences. The pixel runs only after you allow advertising cookies; what our CRM sends is set out in §9 of the privacy policy. | The page and the event with its value, the _fbp/_fbc cookies, IP address and browser; email, phone, name and country hashed (SHA-256) | EU (Ireland) / USA |
2. What is not a sub-processor
- Anything you install or connect on your own workspace. A database you run, an API you call, a backup service you configure — those are your processors, not ours.
- The identity provider your platform uses for its own users. Your workspace ships with GitLab as the default; you can point it at your own provider, and either way it is your choice and your relationship.
- Authorities we are legally required to answer. They are recipients, not processors, and the Privacy Policy covers them.
3. Changes
We email account holders at least 30 days before adding or replacing a sub-processor, and the version date at the top of this page changes when the list does. If you object on reasonable data-protection grounds, section 6 of the Data Processing Addendum says what happens next.