Data Handling and Security
Protect API credentials and sensitive identity response data.
Identity data and API credentials are sensitive. Design your integration to minimize exposure.
API keys
- Keep keys on trusted servers.
- Use a secret manager in production.
- Never include keys in client-side JavaScript, mobile applications, screenshots, or support messages.
- Use separate test and live keys.
- Revoke and replace exposed credentials.
Identity responses
Idyntic returns personal identity information. Your application is responsible for lawful collection, access control, retention, and deletion of that data.
Only request a verification when you have the appropriate legal basis and user consent for your use case.
Operational logging
Idyntic operational logs exclude full identity payloads. Your application should follow the same principle and log only the minimum information required for support and auditing.
Idempotency storage
Completed live responses retained for replay are encrypted and expire after 24 hours.
Logging guidance
Do not write full identity payloads, API keys, or authorization headers to application logs. Prefer:
- Idyntic
reference X-Request-Id- Endpoint and status code
- Your own customer or transaction identifier
Support
When reporting an API issue, provide the endpoint, timestamp, HTTP status, Idyntic reference when available, and X-Request-Id. Do not send identity payloads or API secrets unless a secure support process explicitly requires them.
Updated about 2 hours ago