Terms of use.

Everything here is descriptive. Pages, diagrams and service lists explain how BRONAXIS works; none of it is a quote, an offer or a contract, and prices are not published here because scope decides them.

The projects on this site are prototypes and demonstrations built to show architecture and approach. They are labelled as such. No client names, revenue figures or performance metrics are claimed anywhere on this site, and nothing here should be read as a case study of a paying engagement.

No testimonials or client reviews appear on this site. If any are published later they will be attributed and verifiable — not written in-house and not edited into looking real.

Security testing is performed only on systems where the client has explicit authorization.

Before any assessment begins, the following must exist in writing:

• Authorization from the party that owns or legally controls the target system.
• A defined scope: the hosts, domains, applications and accounts in and out of bounds.
• An agreed testing window and a named contact reachable during it.
• Agreed limits on intrusive techniques, and no testing that degrades a live service.

Third-party systems, shared platforms and vendor infrastructure are out of scope unless that vendor has given its own documented permission. Requests to test a system the requester does not control, or to work without written authorization, are declined.

Deliverables are defensive: reproducible findings, impact, and the remediation steps needed to close them. BRONAXIS does not supply exploitation tooling, weaponised proof-of-concept code, or techniques for evading a third party's monitoring.

Systems are built to an agreed specification, tested, and documented. Timelines and estimates are honest estimates, not fixed dates, and they move when scope moves.

What is not promised: a specific revenue, ranking or conversion outcome. Automation removes manual work reliably; it does not guarantee a business result, and any provider claiming otherwise is guessing.

A security assessment reports what was found within the agreed scope and window. No assessment can prove a system has no remaining vulnerabilities.

Most systems depend on services BRONAXIS does not own — automation platforms, model providers, hosting, CRMs, email infrastructure. Their terms, availability, rate limits and pricing are theirs. Subscription costs are the client's and are quoted separately from build cost.

On final payment, the client owns the deliverables built for them: source code, workflows, configuration and documentation. BRONAXIS keeps the right to reuse its own generic libraries, patterns and internal tooling — never client data, credentials or business-specific logic.

Client systems, data and documents are treated as confidential and are not discussed, published or used as examples without written permission. Access is requested at the lowest level that does the job and handed back when the work ends.

This website is provided as is, without warranty, and BRONAXIS is not liable for decisions made on the basis of information published here. Liability for paid work, and the law and venue that govern it, are set out in the signed engagement agreement for that project.

Anything unclear here is worth asking about before work starts. Write to paulbivanjit@gmail.com.