Who this is for
Skyeline's DPA is intended for business customers, including enterprise accounts, that use the service to process personal data on behalf of their organization and need vendor data-processing terms. In those cases, the customer typically acts as the controller or business, and Skyeline acts as the processor or service provider.
Individual self-serve beta users generally rely on Skyeline's Terms of Service and Privacy Policy rather than a separate DPA.
Status of this page
This page is a public overview of how Skyeline approaches data-processing terms during the beta. It is not a binding standalone data processing agreement, does not automatically apply to every account, and is not a substitute for a signed enterprise contract.
If a business customer needs a DPA for procurement, privacy review, or compliance, Skyeline can share a signed version for eligible accounts on request.
When a DPA is relevant
A DPA is typically relevant when a company uses Skyeline to process personal data relating to its employees, customers, end users, or other third parties through prompts, logs, application content, observability data, or connected providers.
If you are only signing up as an individual to evaluate the beta for your own use, a separate DPA is usually not required.
What an enterprise DPA would cover
A signed enterprise DPA would typically cover the processing roles, subject matter and duration of processing, categories of personal data, customer instructions, confidentiality obligations, security commitments, subprocessors, international transfers, and deletion or return of customer data at the end of the relationship.
How to request one
To request an enterprise DPA, email hello@skyeline.dev with your company name, expected use case, and any procurement or compliance requirements you need us to review.
Skyeline may still decline or defer DPA requests that are not a fit for the current beta, but we can review them with you case by case.