Acceptable Use Policy

The rules for using the Orenyx Engine. These exist to keep the platform reliable and lawful for every customer on it, and to make clear what will get an account suspended.

Effective date: this policy applies from the date it is published on your production domain. It should be reviewed by your legal counsel and referenced from your Terms of Service before it is enforced against a paying customer.

1. Who this applies to

This policy applies to every account holder, every user invited into an account, and every system calling the API with a key issued by an account. If you give an API key to a contractor or connect a third-party tool, you remain responsible for what that key does.

2. Prohibited content and data

You may not use the platform to store, process, or transmit:

  • Content that is illegal in your jurisdiction or in the jurisdiction where the data is hosted.
  • Malware, ransomware, exploit kits, or any code intended to damage or gain unauthorized access to a system.
  • Credentials, API keys, or access tokens obtained without the owner's permission.
  • Payment card numbers, CVV codes, or full magnetic-stripe data. Card data must go to Stripe directly through the hosted checkout flow, never into a lead field, note, message body, or custom field.
  • Government-issued identification numbers, health records, or biometric data, unless you have a separate written agreement covering that category of data.
  • Content that harasses, threatens, or defames a person, or that sexualizes minors.
The card-data rule is not merely a preference. Putting card numbers into lead fields would pull your account, and this platform, into a far stricter PCI DSS assessment scope. See PCI DSS Scope for why the current architecture deliberately keeps card data out.

3. Prohibited conduct

Outreach and communications

The platform sends email and SMS on your behalf. That capability is the easiest way for one customer to damage sending reputation for everyone, so it is tightly bound:

  • No unsolicited bulk email or SMS. Every recipient must have a lawful basis for contact under the rules that apply to them, which may include CAN-SPAM, GDPR, PECR, TCPA, or CASL.
  • No purchased, scraped, harvested, or rented contact lists.
  • No falsified sender identity, forged headers, or misleading subject lines.
  • No ignoring an opt-out. Once a recipient asks to stop, further outreach to that contact must stop.
  • No sending on behalf of a third party in a way that hides who is actually contacting the recipient.

Platform integrity

  • No attempting to access another account's data, whether by manipulating identifiers, API parameters, links, or session tokens.
  • No probing, scanning, or penetration-testing production systems without prior written authorization.
  • No load-testing production. A load-testing harness is provided for non-production use; ask before pointing anything at production.
  • No reverse-engineering, decompiling, or attempting to extract source code or model prompts from the service.
  • No circumventing rate limits, quotas, plan limits, or billing, including by rotating accounts or keys to reset a limit.
  • No reselling or sublicensing access to the API without a written reseller agreement.

Automated and AI usage

Lead qualification runs through an AI model. Some additional limits follow from that:

  • Do not submit content designed to manipulate the qualification model into producing harmful output, or into disclosing its instructions.
  • Do not use the platform to generate content presented as human-written where doing so is deceptive or unlawful.
  • Do not submit another party's confidential information for AI processing without their permission.

4. Fair use of shared capacity

Each job type runs on its own isolated queue, so one account’s heavy usage should not stall another’s. Rate limits are enforced per API key rather than per account, which means one noisy integration cannot consume the whole account’s quota. Even so, sustained usage far outside your plan tier may be throttled after notice.

  • Bulk lead ingestion is capped at 1,000 leads per request. Splitting a larger import into sequential batches is expected and supported.
  • Requests that exceed a key's rate limit receive a 429 response with a retry delay, rather than being silently dropped.
  • Repeatedly hammering an endpoint through the 429 response instead of backing off is a violation of this section.

5. How this is enforced

Enforcement is graduated. The intent is to give a customer a chance to correct a problem, while reserving the ability to act immediately when there is real risk to other customers.

SeverityExampleAction
LowExceeding rate limits repeatedly; a misconfigured integration retrying in a tight loop.Email notice to the account owner, with a request to correct within a stated period.
MediumSending to a purchased list; sustained usage far beyond plan tier.Written warning, and the affected capability (for example, outreach sending) may be paused for the account.
HighAttempting to access another account's data; uploading malware; storing card data in lead fields.Immediate suspension of the account without prior notice, followed by written explanation.
LegalActivity that appears criminal, or a valid law-enforcement request.Suspension, data preservation, and cooperation with lawful requests.

Suspension is a real, implemented control rather than a policy statement alone. When an account is suspended, its API keys and access tokens stop working immediately and its bots stop processing new jobs. Requests from a suspended account receive an explicit error rather than failing ambiguously.

6. Reporting a violation

If you believe another account is abusing the platform, or you receive unwanted outreach that originated here, report it to developer@zyntriq.ai. Include headers or message identifiers where you have them, since that is what makes a report actionable.

If you discover a security vulnerability, report it to the same address and please do not test it further against production. Good-faith reports will not be pursued as violations of section 3.

7. Appeals and reinstatement

An account suspended for a Low or Medium violation may be reinstated once the underlying issue is fixed and confirmed. Write to developer@zyntriq.ai describing what changed. High and Legal severity suspensions are reviewed case by case, and may be permanent.

8. Changes to this policy

This policy may change as the platform changes. Material changes that restrict what you are currently permitted to do will be announced by email to account owners before taking effect. Continuing to use the platform after a change takes effect constitutes acceptance of it.

Was this page helpful?