Developer & API terms

These terms apply to developers who access Traditional Dating APIs, keys, or integration surfaces. They supplement our Terms & Conditions and Privacy Policy. Traditional-dating Legal may update them with notice where required.

1. Licence and acceptable use

We grant a limited, revocable licence to use the APIs per documentation. You must comply with Acceptable Use and must not scrape the consumer site, circumvent rate limits, or attempt to re-identify users.

2. Metered usage and billing

• API calls may be billed per request or per compute unit as shown on the pricing page and developer dashboard.
• Usage is calculated from our logs and is final except for verified billing errors within the dispute window we publish.
• Non-payment may result in suspension, denial of requests, or optional grace periods.

3. Agent restrictions

• You must obtain and maintain verifiable user consent for delegated agent actions.
• You must provide revocation mechanisms consistent with AI & agent consent.
• You must not impersonate a human without authorisation.

4. Audit and compliance

We may audit API usage for security, fraud, and compliance. Non-compliance may result in key rotation, suspension, or termination.

5. Sanctions and export controls

You represent that you are not barred from using the APIs under applicable sanctions or export control laws, and you will not facilitate use in prohibited jurisdictions or by prohibited parties.

6. Disclaimers

APIs are provided “as is” subject to any SLA we expressly offer. We may change endpoints, fields, or limits with reasonable notice when feasible.

7. Machine-readable policy

See /.well-known/traditional-dating-policy for structured billing and safety flags.