At a glance
Confidential infrastructure
Sealarca public routes use the protected Vault execution environment. The resources required for execution are allocated dynamically within a decentralized compute infrastructure, within the scope of the common Vault standard and applicable contractual conditions.
Content processing
Sealarca does not log or display prompt and response content in the dashboard, and Vault routes do not use a response cache for that content. Operational metadata required to run the service remains separate from content; specific conditions are communicated in the contract and, where applicable, the DPA.
Swiss FADP
Eyelo SA is established in Switzerland. Processing under its direct control is presented with minimization, security, and transparency in mind.
GDPR where applicable
Where the GDPR applies, access, rectification, deletion, restriction, or portability requests can be sent to the Sealarca support service operated by Eyelo SA. The user may also withdraw an applicable consent or lodge a complaint with the competent supervisory authority.
What this page covers
This notice describes the data categories processed to operate Sealarca and the common scope of Vault routes.
- account and user identification data;
- billing, payment, and credit data;
- technical data required for service operation and security;
- usage data: called models, tokens, costs, and consumption events;
- data voluntarily sent to support or through an API request.
Vault routes and service execution
Sealarca publishes Vault routes that use a protected execution environment. The resources required for execution are allocated dynamically within a decentralized compute infrastructure, within the scope of the common Vault standard and applicable contractual conditions.
Read the common Vault standardRead the application supplementUser requests
Data-related requests can be sent to support@sealarca.ch. Eyelo SA may request identity verification before processing a request.
Request a contract, DPA or processing information