Privacy policy.
This page explains which categories of information may be processed when the site or API routes are used.
Information we process
We process the minimum information required to receive requests, operate the API, protect the service, and troubleshoot issues. Depending on the route, that may include path parameters, request payloads, response metadata, and technical diagnostics.
Examples include taxpayer lookup identifiers, translation request text, base currency codes, request timestamps, IP-related telemetry, and structured application logs used for security and debugging.
- Request content submitted to the API
- Metadata such as timestamps, route names, and response status
- Network and device signals used for security, debugging, and rate control
How the information is used
Information is used to execute the requested action, monitor availability, investigate incidents, and improve service quality.
- Return API responses
- Detect abuse, downtime, and malformed requests
- Investigate support requests and reproduce reported issues
- Generate aggregated internal metrics about usage and reliability
Third-party processing
Some routes depend on upstream providers, including public government services and third-party APIs. When those routes are called, relevant request data is sent to those providers to complete the request.
Those providers operate under their own terms and privacy practices. Review those dependencies before using the service in regulated or high-sensitivity workflows.
Retention and security
Operational logs and support artifacts are retained only for as long as reasonably necessary to secure the service, investigate incidents, and satisfy legal or contractual obligations.
We use administrative, technical, and organizational safeguards appropriate to the service, but no internet-facing system can guarantee absolute security.
- Access controls for operational systems
- Environment separation for development and production
- Monitoring and incident response procedures