Trust
Sub-processors
In short. Three providers process data to run Seylo for every customer, and two more serve Seylo’s model, which Nightshift and the in-page assistants use by default unless your organisation uses its own key. Others process data only if your organisation turns on a feature that needs them. We will update this page before adding a sub-processor.
1. Used for every organisation
| Provider | What it does | Data | Location |
|---|---|---|---|
| Microsoft Azure | Hosts the Service: application servers and database | All data Seylo stores | United States |
| Azure Communication Services (Microsoft) | Sends transactional email | Recipient email addresses and message content | United States |
| Cloudflare | DNS, network protection and delivery for portal.seylo.in and seylo.in | Traffic in transit, including IP addresses | Global network |
Seylo’s model
Seylo’s model is the default for Nightshift and for the Ask AI and Build with AI assistants, unless your organisation saved its own key before it made a choice or an administrator chose Your own key under Nightshift → Settings. It is GLM-5.3, served through Microsoft Azure AI Foundry in a Data Zone Standard deployment in the United States: requests are processed within the US Data Zone, never through a Global deployment.
| Provider | What it does | Data | Location |
|---|---|---|---|
| Microsoft Azure AI Foundry | Serves Seylo’s model (GLM-5.3) to Seylo’s service | Redacted evidence for the investigation being run; for an assistant, the question asked with metric and field names, never your data | United States (US Data Zone) |
| Fireworks AI | Hosts the model (FW-GLM-5.3) for Microsoft within Azure AI Foundry | The same requests, as Microsoft’s sub-processor | United States |
2. Only if you turn a feature on
| Provider | When | Data |
|---|---|---|
| GitHub | You connect a GitHub repository or the Seylo GitHub App | Repository content you choose to sync; your GitHub login |
| Your chosen model provider | An administrator enables AI features with your organisation’s own API key | Redacted evidence for the question asked. This is your provider, under your agreement with it — not a Seylo sub-processor. |
Destinations you configure for alerts — Slack, Microsoft Teams, Google Chat, PagerDuty, Opsgenie / Jira Service Management, or your own webhooks — receive the alert content you route to them. They are services you choose, under your agreements with them.
3. This website
seylo.in is hosted on Cloudflare Pages and loads its typeface from Google Fonts, which receives visitors’ IP addresses. It runs no analytics.
4. Payments
Payments are made through Razorpay: at checkout in the product, or through the payment link in an emailed invoice. The payment page names Seylo Labs Private Limited as the business you are paying.
| Provider | What it does | Data | Location |
|---|---|---|---|
| Razorpay Software Private Limited | Processes payments for invoices and coding agent seats | The payer’s name, email address and phone number, the amount and invoice reference, and the payment details entered on Razorpay’s page. Card and bank details go to Razorpay only; Seylo never receives them. | India |
5. Changes
We update this page before a new sub-processor starts processing customer data. If you have signed our Data Processing Addendum, we will also notify you as it describes.