Providers & subprocessors

Services used by the hosted product and when information can reach them.

Last updated
Legacy Edge Private Limited, India

Optional services appear when enabled in this hosted build. Your selected integrations or a private installation can introduce other recipients. Request the provider schedule applicable to your deployment and agreement.

1. Hosted service directory

Hosted service providers, purpose, activation and data
ProviderPurpose & activationData and notice
Amazon Web Services

Hosted infrastructure, transactional email and configured evaluation processing.

Used by the hosted service; evaluation destinations depend on the selected checks.

Account records, email delivery details and submitted workload content for configured evaluations.

Read provider information
OpenAI

Configured model-assisted evaluation.

When an enabled check uses this service; it is not used by every check or request.

Submitted text and evaluation context for that check; processing locations and retention depend on the provider account and agreement.

Read provider information
Polar

Checkout, subscriptions and payment records.

When you use billing or an assessment checkout.

Customer, order, payment and tax details; separate provider purposes may apply.

Read provider information
Google

Optional Google sign-in and Google Workspace support correspondence.

When you select Google sign-in or email the support address.

Sign-in identity/profile details, or the support message, sender and attachments you provide.

Read provider information
GitHub

Optional GitHub sign-in.

When you select GitHub sign-in.

Identity/profile details needed for sign-in; provider account processing.

Read provider information
Cal.com

Demo scheduling.

The calendar loads only when you request it; email booking is an alternative.

IP/browser details and the booking information entered.

Read provider information

2. Request the production schedule

Ask for the contracting provider entities, hosting and processing regions, support access locations, functions, applicable DPA and transfer safeguards. Infrastructure regions and external model destinations must be confirmed separately. A provider’s website is not evidence of a signed contract or a particular data residency commitment.

Contact compliance@nyraxis.io before sending data with residency or restricted-transfer requirements. This public directory does not replace any contractual subprocessor notice or objection process.

3. Customer-controlled integrations

A model, judge, Slack/webhook endpoint, identity provider or report destination you select can introduce recipients beyond the services listed above. Available integration recipes describe compatibility; they do not mean Nyraxis sends every customer’s data to each named provider. Review your selected destinations and who contracts with each provider before connecting them.

See data handling, processing terms and the privacy notice.

Company information

Legacy Edge Private Limited

CIN: U62091UP2024PTC208924

Registered office

State Highway 39, Near Shreeji Farm House
Aligarh Road, Hathras, Uttar Pradesh – 204101
India

support@nyraxis.io

Questions about this document? Contact Nyraxis.