Acceptable Use Policy

Effective from: 30 September 2026

1. Scope and Purpose

This Acceptable Use Policy sets out conduct that is not permitted on or in connection with https://deltrig.com, our products, our licensing and update services, and our support channels (the “Service”).

It forms part of, and must be read together with, our Terms of Service and Licence Agreement. It is issued by DELTRIG, a sole proprietorship owned and operated by Rahul Chouhan, of Dakra, Khalari, Ranchi, Jharkhand, India – 829210.

It applies to everyone who uses the Service — customers, visitors, guests, and anyone acting on their behalf including employees and contractors.

Why this document exists. We are one person selling software to people who build things. Almost nobody reading this will ever come close to breaching it. It exists so that when someone does, the rule was written down in advance rather than invented afterwards, and so you can see exactly where the line is instead of guessing.

2. What Is Expressly Permitted

So this document is not read more narrowly than intended, the following are all fine and need no permission from us:

• Using a product commercially — on a site or in an application that earns money, sells, advertises, or is operated for profit. We charge once for the licence and take no share of what you make with it.
• Modifying a product — editing, extending, adapting and building on its code for your own permitted installations.
• Using it for a client, within the installation count your tier allows, and transferring the licence to them as Clause 11 of the Licence Agreement describes.
• Staging, testing, local and backup copies of an installation you have licensed. They do not consume extra slots.
• Letting your team use it — employees and contractors working for you, on your permitted installations.
• Writing publicly about a product, including a critical review, a tutorial, a comparison, or a bug report. We would rather you did.
• Reporting a security flaw, under our Security Policy.

3. Licence and Distribution

You must not:

• Resell, sublicense, rent, lease or lend a product, or any part of it, whether modified or not, and whether for money or free of charge.
• Redistribute it — upload it to a public repository, file host, torrent, marketplace, forum, messaging group, paste site, or anywhere a third party could obtain it.
• Include it in something you distribute — a theme, plugin, template, framework, boilerplate, starter kit, course or bundle — where the product or a derivative of it is part of what the recipient receives.
• Provision it to your own customers as a service, such as a site builder or multi-tenant platform that installs our product into installations belonging to them, unless the product page permits it or we agree in writing.
• Share, publish or sell a licence key, or use a key you did not lawfully obtain.
• Exceed your installation count knowingly, or keep a licence activated on installations you no longer operate in order to hold slots you are not entitled to.
• Circumvent licensing — patch, crack, bypass, nullify or disable activation, verification or update mechanisms, or use software that does.
• Remove or alter a copyright notice, licence notice, attribution, author credit, or licence-verification mechanism in a product's files.
• Claim authorship of a product, or register an intellectual property right in it or a derivative of it.

This is the part we actually enforce. Redistribution is what directly damages a business like ours, and it is also the easiest thing to detect. Clause 8 sets out what happens.

4. Accounts and Identity

You must not: create an Account with false information or impersonate another person or organisation; hold more than one Account per person or organisation; create an Account to claim a promotion more than once or to evade a suspension; share your Account credentials, or use someone else's; attempt to access another user's Account, Orders, licences or downloads; or transfer or sell an Account.

You must keep your password confidential and tell us promptly if you believe your Account has been accessed without authority. We will never ask you for your password or a one-time sign-in code — anyone who does is attempting to take your Account, and that includes anyone claiming to work here.

5. Payment, Orders and Refunds

You must not: use a payment instrument you are not authorised to use; place an Order with the intention of raising a chargeback rather than paying; raise a chargeback for an Order that was delivered, or that has already been refunded, without first raising it with us; make or attempt a fraudulent, duplicate or manipulated refund claim; place Orders in a pattern designed to obtain products without ultimately paying; exploit a pricing, promotion, coupon or currency error you know or ought reasonably to know is an error; or use the Service to launder funds or test stolen payment credentials.

Buying and refunding repeatedly across products, in a pattern that is plainly evaluation-by-refund rather than genuine problems, is a breach of this Clause. Clause 6 of the Refund & Cancellation Policy explains how that weighs on a request.

If you have a payment problem, tell us. We can almost always resolve it faster than a bank dispute, and we would far rather do that.

6. Technical Conduct

You must not:

• Interfere with the Service — disrupt, overload, flood or degrade it or the infrastructure it runs on, including by denial-of-service.
• Attempt unauthorised access to any account, server, system, network or data, whether ours or another user's.
• Probe, scan or test the security of the Service, except as our Security Policy expressly permits.
• Circumvent a control — a rate limit, an access restriction, an authentication step, a human-verification challenge, a signed URL, or a licence check.
• Scrape, crawl or harvest content, product data, pricing or user information, other than as our robots directives permit. Search-engine crawling that respects those directives is welcome.
• Automate access other than through an interface we provide for that purpose, in accordance with its documentation and rate limits.
• Re-host or hotlink our files, images or download endpoints from your own site or service.
• Upload or transmit malware, or anything designed to damage, disable or gain unauthorised access to a system.
• Frame or mirror the Service, or present it as your own.
• Reverse engineer beyond what applicable law expressly permits notwithstanding a contractual restriction. Most of our products ship as readable source, so there is rarely anything to reverse engineer.

7. Content, Conduct and Lawful Use

You must not use the Service, or anything bought from it, to: break any applicable law or regulation; infringe another person's intellectual property, privacy or other rights; publish or transmit content that is unlawful, defamatory, fraudulent, obscene, hateful, harassing, threatening, or that sexualises or endangers a child; send spam or unsolicited commercial messages; operate a phishing, scam or deceptive scheme; distribute malware; conduct unlawful surveillance or track individuals without consent; or facilitate any of the above.

What you build with a product is yours and is your responsibility. We do not police lawful sites built with our software and have no interest in doing so. This Clause is about using our products as an instrument of something unlawful, not about disapproving of your business.

Content you submit to us — reviews, tickets, messages, attachments — must be yours to submit and must not breach this Clause. Clause 17 of the Terms of Service governs it.

Reviews must be your genuine opinion. Do not post a fabricated review, a review of a product you did not buy where we mark reviews as verified, a review containing another person's personal data, or a review as a lever to obtain a refund or a discount. We do not remove a review merely because it is unfavourable.

8. Support Conduct

Support is one person. Please:

• Do not abuse, threaten or harass whoever answers. We will end a conversation that becomes abusive and will continue the matter in writing only.
• Do not send credentials. Never send a password, a card number, a one-time code, or a production database. We never need them, and a ticket is not a secure vault.
• Do not present custom development as a support request. Asking us to build your feature for free, repeatedly, is a breach of this Clause. If you need bespoke work, Clause 13 of the Terms of Service is the route, and we are happy to quote.
• Do not request support for an installation that is not yours, or for a licence you do not hold.
• Do not open duplicate tickets or escalate across every channel at once. It does not make a reply arrive sooner and it makes the history harder to follow.
• Do not misrepresent a fact to obtain support, a refund or an entitlement — for example, claiming a product is broken when it has been modified, or claiming an environment you are not running.

9. What We Do About a Breach

Depending on what happened and how serious it is, we may: contact you and ask you to stop; remove or edit offending content; revoke a licence key or reduce its activations; suspend or terminate an Account; refuse to supply you in future; report the matter to a payment provider, a platform, a host, or a law-enforcement or regulatory authority; and pursue any legal remedy available to us, including recovering losses and costs.

How we go about it, and we hold ourselves to this:

• Where the breach can be remedied and nothing ongoing is being harmed, we contact you first and give you a reasonable opportunity to put it right. A licence accidentally activated on too many sites is a conversation, not a termination.
• Where the breach is fraud, chargeback abuse, active redistribution, an attack on the Service, or content that endangers someone, we may act immediately and explain afterwards.
• We tell you what we did and why. You will not find an Account silently disabled with no explanation.
• A person decides. No suspension, revocation or refusal is made by an automated system alone. Automated systems flag; a human decides.
• We aim to be proportionate. The response to an honest mistake is not the response to deliberate resale.

Effect on what you bought. Termination for breach does not entitle you to a refund. Where a licence is revoked, Clause 15 of the Licence Agreement applies: your right to use the product ends and you must delete every copy.

10. Appeals

If you think a decision was wrong, email [email protected] and say so, with your Account email and what you believe happened. It will be reviewed by a person, with your explanation in front of them.

If you are still not satisfied, escalate to [email protected], where the proprietor will review it. Clause 26 of the Terms of Service sets out the dispute process beyond that.

We do make mistakes. An automated flag can be wrong, a licence can look shared when a customer has simply migrated hosts three times in a week. Tell us; we would rather correct an error than defend it.

11. Reporting a Breach

To report someone reselling or redistributing one of our products, or otherwise breaching this Policy: [email protected]. Include where you saw it and anything that helps us verify it.

For a copyright claim, use our Copyright & Takedown Policy. For a security vulnerability, use our Security Policy. For abusive content or conduct, [email protected].

We are grateful for these reports and we follow them up.

12. Changes and Contact

We may update this Policy. The current version is published on this page with its effective date, and where a change is material we will give notice through the Service. Superseded versions are retained and available on request.

Questions about whether something is permitted: [email protected]. If you are unsure whether your intended use is allowed, ask before you do it. That question takes us a minute to answer and saves everyone a dispute — and the answer is usually yes.

DELTRIG
Sole proprietorship — Proprietor: Rahul Chouhan
Dakra, Khalari, Ranchi, Jharkhand, India – 829210
Website: https://deltrig.com