Subprocessors
- Last updated
- 2026-07-16
- Effective
- 2026-07-16
Osyra, Inc. plans to use the providers below to deliver the Service at launch. This register describes the intended data flow; it does not represent that a provider is currently processing production Customer Content. Questions about the register or DPA can be sent to legal@osyra.ai.
01Launch register
Planned Osyra subprocessors, their purpose, data scope, location, and activation state Subprocessor Purpose Data location Data scope Status and boundary Amazon Web Services, Inc. Compute, storage, networking, KMS, and audit-log retention us-east-1 (United States), eu-west-1 (Ireland) Service data and Customer Content required to operate Osyra Planned for launch. Planned system of record for Osyra-hosted workloads. Region selection is part of the Enterprise launch plan. Stripe, Inc. Payment processing, invoicing, and subscription billing United States (global edge) Billing contact, invoice, tax, and payment-token metadata Planned for launch. Planned billing processor. Primary account numbers remain with Stripe and are not stored by Osyra. Resend, Inc. Transactional email delivery for account verification, billing receipts, and alerts United States Recipient address and the minimum service-message content required for delivery Planned for launch. Planned for transactional service messages; not planned for marketing campaigns. Plausible Insights OÜ Privacy-friendly web analytics without cookies or cross-site tracking European Union (Estonia / Germany) Aggregate public-site page-view, referrer, and country metrics Planned for launch. Planned only for the public marketing site; not for the authenticated console or Customer Content. Functional Software, Inc. (Sentry) Application error monitoring and performance traces United States; EU data region available Scrubbed error diagnostics and performance telemetry Planned for launch. Launch configuration must scrub Customer Content and credentials before telemetry leaves Osyra. 02Register change log
- 2026-07-10 — Removed Vercel from the planned production register after the AWS-only hosting decision. Osyra is pre-release and did not deploy production Customer Content to Vercel.
03Change notification
After launch, Osyra will notify Customers of a new subprocessor at least 30 days before activation. Notice will be delivered to the primary account contact and posted here with an updated “Last updated” date.
Customers may object in writing during that window by emailing legal@osyra.ai. We will work in good faith to address objections. The executed DPA controls any termination or refund remedy.
Subscribe to changes. Prospective customers may request register change emails at legal@osyra.ai with subject “Subprocessor notifications” and the email address to add.
04Model-provider boundary
Customer-selected model providers are not part of this infrastructure and operations register. The applicable data-processing role depends on the access mode and the customer's contract for that provider:
- Bring-your-own-keys (BYO-keys).The Customer holds the contract with the model provider; Osyra forwards requests using the Customer's credentials.
- Osyra-managed access.The provider terms and data-processing role must be stated in the customer's Order Form before that route can be enabled.
Before launch, the provider catalogue will identify each supported access mode, data-retention setting, and applicable provider terms. Osyra will not infer a legal role that is not documented in the customer agreement.
05Sub-sub-processors
Provider activation is gated on review of downstream-provider terms, data location, security controls, and required contractual flow-downs. Where the applicable provider agreement permits it, supporting evidence can be requested from legal@osyra.ai.