Skip to content

Acceptable use policy

pixbix generates creative at volume, which means misuse also scales. This policy sets out what is not allowed, and what happens if it is.

Effective
15th August 2026
Entity
Thinkbix Technologies
The short version. Do not use pixbix to deceive people, infringe rights, or attack systems. Do not resell the rendering API as your own. Everything else — including building products on top of us — is fair game.

1Scope#

This policy applies to everything you do with pixbix: content you upload, templates you publish, renders you generate, and how you call the API. It forms part of the terms of service.

It applies equally to your team members and to anyone using an API key issued by your workspace. You are responsible for their use.

2Content you may not generate or publish#

You may not use the service to create, store or distribute:

  • Unlawful content — anything illegal where you are, where we operate, or where it is published.
  • Child sexual abuse material — reported to authorities immediately, with no notice and no appeal.
  • Content that infringes rights — copyrighted images, video, audio or fonts you are not licensed to use; trademarks used to imply an association you do not have.
  • Deceptive impersonation — creative designed to pass as an official communication from a person, brand, bank or government body you are not authorised to represent.
  • Fraud material — fake invoices, receipts, tickets, certificates, identity documents, or creative supporting a scam.
  • Harassment and hate — content attacking or degrading people on the basis of religion, caste, ethnicity, gender, sexuality, disability or similar.
  • Incitement to violence — including content promoting terrorism or organised violence.
  • Sexual content involving real people without consent, and sexually explicit content generally on public templates.
  • Dangerous misinformation — fabricated news, medical or electoral claims presented as fact.
  • Regulated claims you cannot substantiate — financial returns, medical outcomes, or anything requiring a licence you do not hold.

The bar for impersonation is deliberately high. A poster about a brand is normal marketing; a poster designed to be mistaken forthat brand’s own communication is not.

3Technical restrictions#

You may not:

  • Circumvent credit metering, plan limits, rate limits or watermarking
  • Share or resell API keys, or issue keys to parties outside your workspace
  • Probe, scan or stress-test our infrastructure without written permission
  • Attempt to access another workspace's templates, media or renders
  • Use the asset fetcher to reach internal, private or metadata endpoints
  • Submit edits designed to exhaust worker resources rather than produce output
  • Automate account creation to obtain additional free-plan allowances
  • Reverse engineer the service, except where that right cannot lawfully be excluded

Security research is welcome under clause 6. What is not welcome is testing our limits in production without telling us.

4Reselling#

Permitted: building a product, agency service or internal tool that uses pixbix to generate creative for your own customers. That is what the API is for, and it needs no separate agreement.

Not permitted: exposing our rendering capability as your own rendering API — a thin wrapper that resells render calls as a competing service.

If you are unsure which side of that line your product sits on, ask hello@pixbix.app before you build. We would rather agree terms than discover it later.

5Public templates#

Templates published to the shared library are reviewed before they appear, and are held to a higher standard than private work — they become part of the product other people see.

Public templates must:

  • Use only assets and fonts licensed for redistribution and server-side rendering
  • Be genuinely reusable — not a single finished design with your own branding baked in
  • Carry no third-party trademarks, contact details or watermarks
  • Be described accurately, with fields that are labelled clearly

We may unpublish a template without notice if it breaches this policy. Private templates are unaffected.

6Security research#

We welcome good-faith vulnerability research. Report findings to hello@pixbix.app with steps to reproduce.

We will not pursue action against research that:

  • Uses only your own accounts and data
  • Avoids degrading service for other users
  • Does not exfiltrate, modify or destroy data belonging to others
  • Gives us reasonable time to fix before disclosure

7Reporting a violation#

To report content or behaviour that breaches this policy, email support@pixbix.app with the template or render ID, or a link, and a description of the problem.

Copyright complaints should include the work concerned, proof of your rights, and a statement that the use is unauthorised.

We acknowledge reports within 1 business day and investigate promptly.

8Enforcement#

Our response is proportionate to what happened. In escalating order:

  1. We contact you and ask you to fix it
  2. We remove or unpublish the specific content
  3. We restrict a capability — public publishing, or API access
  4. We suspend the workspace pending resolution
  5. We terminate the account

We skip straight to termination for child sexual abuse material, coordinated fraud, or an active attack on our infrastructure or another customer.

If you believe we acted in error, reply to the enforcement notice. A person reviews every appeal, and we do reverse decisions when we get them wrong.

9Changes#

As new misuse patterns appear, this policy will change. Material changes are notified to account holders at least 14 days in advance.