1. What we do not store
For standard API inference requests, Enclave42 is designed not to intentionally persist the content of prompts, messages, files, or model responses in its application database after the request is processed. We retain usage metadata such as model ID, token counts, estimated cost, wallet debit, request identifiers, timestamps, and operational or security events. Customers should still avoid sending sensitive personal data unless they have the appropriate rights, controls, and legal basis.
2. Information we collect
We may collect account information, business contact details, authentication identifiers, subscription status, billing metadata, wallet balances, wallet transactions, API key metadata, model identifiers, request timestamps, token counts, estimated cost, debit records, security events, error codes, and operational telemetry.
3. Usage metadata
We retain usage metadata to provide analytics, billing, wallet debits, abuse prevention, support, security monitoring, rate-limit enforcement, debugging, and reliability improvements. Usage metadata is not intended to include the full content of customer prompts or model responses.
4. API keys and account security
We process API key metadata and authentication-related information to validate requests, enforce model permissions, apply customer controls, prevent unauthorized use, and help customers manage access. API secrets should be protected by customers and rotated if exposed.
5. Billing and payments
We use payment and billing service providers to process subscriptions, checkout sessions, wallet top-ups, invoices, customer records, and related billing events. Enclave42 does not need to store full card details directly to provide the service.
6. Service providers
We may use infrastructure, hosting, authentication, payment, monitoring, analytics, security, and support providers to operate Enclave42. These providers process information only as needed to deliver services to Enclave42 and its customers.
7. Security measures
We use technical and organizational safeguards designed to protect customer accounts, API access, billing records, runtime infrastructure, and usage metadata. No online service can be guaranteed to be completely secure, and customers remain responsible for securing their own systems and integrations.
8. Retention
We retain account, billing, wallet, usage metadata, security, and operational records for as long as needed to provide the service, comply with legal obligations, resolve disputes, enforce agreements, prevent abuse, and maintain reliable operations.
9. International processing
Information may be processed in the United Arab Emirates and other jurisdictions where Enclave42 or its service providers operate. By using the service, you understand that information may be transferred and processed across borders.
10. Your rights and choices
Subject to applicable law and operational limitations, you may request access, correction, deletion, or export of certain personal information. Some records may need to be retained for billing, security, legal, or compliance reasons.
11. Changes to this policy
We may update this Privacy Policy as our platform, security controls, services, or legal obligations evolve. Material updates may be reflected by updating the date on this page.
12. Contact
For privacy questions or requests, contact support@enclave42.com.