Skip to content
triguna
  • Product
  • Guides
  • Docs
  • Pricing
  • Changelog
Log in Get API key

Best practices

View all →
Guide Person records Guide Company records Guide Identifiers and slugs

Patterns

View all →
  • Enrich on signup 7 min read
  • Nightly backfill 8 min read
  • Agent workflows 7 min read

Reference

View all →
/v1/people/profile Person profile Identity, work history, education, skills, optional contact details. /v1/companies/details Company details Identity, headquarters, size, industries, specialities, funding. errors Conventions and errors ApiKey header, status codes, Retry-After, the 404 slug trap.
  • Product What the person and company APIs return
  • Guides Task-shaped walkthroughs and integration patterns
  • Docs Quickstart, authentication, and the full field reference
  • Pricing Usage-based pricing, per record retrieved
  • Changelog Every API change, newest first
  • Log in Existing account or a new project
  1. Home /
  2. Legal /
  3. Terms of service

Legal

Terms of service

Last updated 31 July 2026

Draft, pending legal review. This page describes our intended practice in plain language so you can evaluate the service. It is not the executed agreement. For a signable DPA or the current terms, write to security@triguna.ai.

The service

Triguna provides two authenticated HTTP endpoints that resolve an identifier you supply into a structured person or company record, assembled from independent sources at request time.

Your account and keys

  • You are responsible for activity under your API keys. Keep them server-side.
  • Keys are scoped per project and per environment and may be revoked by you at any time.
  • We may suspend a key that is causing harm to the service, and will tell you why when we do.

Acceptable use

You agree not to use the API to:

  • build a general-purpose people-search product or resell records as a database;
  • enable unlawful discrimination, harassment, or surveillance of individuals;
  • present retrieved values to third parties as verified facts about a person; or
  • circumvent rate limits, credit ceilings, or the absence of a bulk endpoint.

Billing

  • Usage is billed per successfully retrieved record.
  • Requests that resolve no record, and requests rejected for authentication, are not billed.
  • A retried request carrying the same Idempotency-Key is not billed twice.
  • Credit ceilings are yours to set. Once reached, requests return 402 rather than spending further.

What we warrant, and what we do not

We warrant that a record reports the sources that contributed to it and the time it was assembled. We do not warrant that any value in a record is correct, current, or complete. Every field is nullable and a record may be thin or absent.

If a decision in your product depends on a record being true, that judgement, and the consequences of it, remain yours. See provenance for what the record actually claims.

Availability

Availability commitments and any contractual SLA are agreed per plan. Without a signed SLA the service is provided on a reasonable-efforts basis.

Ending the agreement

You may close your account at any time; usage already incurred remains payable. We may end the agreement for material breach of the acceptable-use terms, or on notice with a pro-rata refund of prepaid credits.

Changes

We will give notice of material changes to these terms. Changes to the API itself are recorded in the changelog, including anything that alters the contents of a record.

Contact

Questions about these terms: contact page.

Privacy Terms Data processing
triguna

Structured person and company records, assembled at request time.

Product

  • Person API
  • Company API
  • Pricing
  • Changelog

Developers

  • Quickstart
  • API reference
  • Errors and retries
  • MCP server

Writing

  • Blog
  • RSS feed
  • About

Company

  • Contact
  • Privacy
  • Terms
  • Data processing
© 2026 Triguna hello@triguna.ai