Privacy Policy

Triunelabs ("we", "us") operates triunelabs.ai and the related client portal. This policy explains what information we collect, why we collect it, and the choices you have. Questions any time: ethan@triunelabs.ai.

Information you give us. When you contact us or create a client account we collect what you provide: your name, email address, company details, and the content of your messages.

Account and usage information. If you use the client portal we keep records needed to provide the service: login credentials (passwords are stored only in securely hashed form), settings, and activity such as requests made and services used, together with timestamps and approximate technical context (browser type, IP address).

Cookies. We use a small number of functional cookies — see our Cookie Policy. We do not run third-party advertising trackers.

To provide and improve our services, respond to enquiries, operate client accounts, keep the service secure (for example rate limiting and abuse prevention), meet legal obligations, and send service-related messages. We do not sell personal information, and we do not send marketing email without your consent.

We run on established cloud infrastructure providers for hosting, storage, authentication, and email delivery. These providers process data on our behalf under their own security and privacy commitments, and may store data in data centers in various regions. We share information with no one else, except where the law requires it.

We keep information for as long as needed to provide the service and meet legal and accounting obligations. If you close your account, we delete or anonymize personal information within a reasonable period, except records we are required to keep.

Depending on where you live, you may have rights to access, correct, export, or delete your personal information, and to object to or restrict certain processing. To exercise any of these, email ethan@triunelabs.ai — we respond to every request.

All traffic is encrypted in transit (HTTPS). Credentials are hashed, access to production systems is restricted, and secrets are stored in managed configuration, not in code. No system is perfectly secure, but we treat your data as if it were our own.

If we make material changes to this policy we will update this page and revise the date above. Continued use of the service after changes take effect means you accept the updated policy.