Usage acceptable

Minfis exists to help you explore what could be built on a site. Use it for that, on sites and material you have the right to use, from your own account, at human speed. Everything below is that sentence in detail.

2.1. Do not use Minfis to do anything unlawful where you are, where we are, or where the result will be used.

2.2. Do not submit, generate or distribute through Minfis:

• content that is unlawful, or that promotes or facilitates unlawful acts;
• content that infringes someone's copyright, trade mark, design right, database right, trade secret or moral rights;
• content that defames, harasses or threatens a person, or that targets a private individual;
• sexual content involving minors, in any form or framing — we report this;
• content designed to deceive: fabricated approvals, forged documents, false records, or material presented as the work or endorsement of a person or organisation that did not produce it;
• personal data about other people that you have no right to process, and special-category data — health, biometric, political or religious information — which has no place in a design brief.

2.3. Do not use Minfis to plan or support violence, weapons development, or damage to infrastructure.

2.4. Do not use Minfis in a way that would mislead a public authority, an investor or a buyer about what the output is. Section 11 of the Terms explains what the output is not: an AI-generated concept presented as approved design documentation is a misuse of this service.

3.1. Do not describe, upload or otherwise submit a site you have no right to work on, if doing so would breach someone's rights or a duty of confidence you owe.

3.2. Do not submit someone else's drawings, models, renderings, photographs or written concepts as input, unless you own them or have permission to use them that way.

3.3. Do not submit material under a confidentiality obligation you would breach by sending it to a third-party AI provider. Your brief and the images made from it are sent to external model providers; the Privacy Policy names them.

3.4. You are responsible for having the rights you assert. We do not check them, and we cannot.

4.1. Do not circumvent, or attempt to circumvent, the limits that meter the service. That includes:

• creating multiple accounts to collect the free project more than once per person or organisation;
• using different network addresses, disposable e-mail addresses or automation to reset the daily limit on starting projects;
• interfering with how a project is charged, or trying to obtain a paid stage without it being charged;
• using a payment method you are not authorised to use, or reversing a legitimate charge instead of asking us for a refund.

4.2. Do not attempt to restore an entitlement your plan does not include — export of the 3D file, an unwatermarked booklet, priority in the queue — by any route other than buying the plan that includes it.

4.3. Repeated chargebacks against valid charges are treated as a breach of this policy and of the Terms.

5.1. Your account is for you. Do not share your sign-in details, and do not let another person use your account. Minfis permits one active session per account, and colleagues each need their own account.

5.2. Do not resell, sublicense, rent out or operate the service on behalf of others as if it were your own — running a bureau service on one Minfis account, or offering "Minfis projects" as a product of yours, is not permitted. Team accounts exist for organisations; talk to us if you need something different.

5.3. You may of course sell your own work to your own clients, including the output of a project you paid for. Section 12 of the Terms sets out your rights in the output. The restriction here is on reselling access to the service, not on using what it made for you.

6.1. Minfis does not publish an API. Until it does, use the service through its interface, as a person.

6.2. Do not scrape, crawl, script or otherwise drive the service automatically; do not run headless browsers against it; do not generate load that a human user would not.

6.3. Do not run bulk operations designed to enumerate results, harvest output, or measure our providers through us.

6.4. If we publish an API, use of it will be governed by its own published terms, and automated use within those terms is fine.

7.1. Do not attempt to access another account, another customer's projects, or any part of our systems you are not authorised to reach.

7.2. Do not probe, scan or test the security of the service without our written permission, and do not interfere with its operation — no denial-of-service, no flooding, no attempts to corrupt data.

7.3. Do not reverse engineer, decompile or disassemble the service, and do not attempt to extract our prompts, our pipeline or our models' instructions — including by instructing a model to reveal them.

7.4. Do not use the service, or its output, to build or train a competing model or a competing generative service. Our providers impose this restriction on us, and it passes to you.

7.5. Do not introduce malware, and do not use Minfis to distribute it.

7.6. If you find a security problem, tell us at [email protected] before telling anyone else. We will not pursue anyone who reports a genuine vulnerability responsibly and does not exploit it.

8.1. Do not attempt to make the models produce content this policy prohibits — by rephrasing, encoding, role-play, splitting a prohibited request across several briefs or edits, or any other technique.

8.2. Do not use edit instructions to steer output towards prohibited content that a brief would have been refused for.

8.3. Attempts of this kind are logged and are a breach whether or not they succeed.

8.4. Our model providers publish their own acceptable-use policies. Those rules reach you through us; where they are stricter than this policy, they govern.

9.1. Depending on what happened, how serious it is and whether it has happened before, we may:

• refuse a specific request or stage;
• warn you and ask you to stop;
• apply a stricter daily limit to your account;
• withdraw an entitlement;
• suspend the account, or a team member's seat;
• close the account;
• for a team account, act on one member's seat rather than the whole organisation, where that is the fairer response;
• report the matter to the authorities, where the law requires it or where there is a risk to a person.

9.2. We aim to warn before we suspend, and to suspend before we close. Where the breach is serious — unlawful content, a security attack, content involving minors — we act immediately and explain afterwards.

9.3. If we close an account for a breach, unused balance is not refunded. See section 15 of the Terms.

9.4. Preserving evidence: if we suspend an account over a suspected breach, we keep the material involved for as long as we need it to make and defend the decision.

10.1. A person reviews every appeal. No account is closed permanently by an automated rule alone, and no appeal is answered by a machine.

10.2. To appeal, write to [email protected] from the address on the account. Say what happened, what you were doing, and why you think the decision was wrong.

10.3. We reply to an appeal within one business day, and we give you the decision within thirty days of receiving it. Those are the same two commitments we make everywhere: one business day for an e-mail, thirty days for a formal answer.

10.4. If we were wrong, we restore the account and anything we withdrew from it. If we were right, we say what rule was broken and what, if anything, you can do about it.

10.5. Appealing does not extend a subscription period or pause a renewal. If you need the subscription stopped while an appeal runs, say so.

11.1. If you believe someone is misusing Minfis, or that output from Minfis infringes your rights or misrepresents your work, write to [email protected] with enough detail for us to find it: the account, the project, the file, and what is wrong.

11.2. We investigate reports we receive and act under section 9. We do not promise an outcome, and we do not disclose what we did about another person's account.

12.1. We may update this policy as the service changes and as new kinds of misuse appear. The revision and date at the top always say which version you are reading.

12.2. Material changes are notified the same way as changes to the Terms: you are asked to accept the new revision before continuing to use the service.

ANOMONUS - FZCO, DSO-IFZA, IFZA Properties, Dubai Silicon Oasis, Dubai, United Arab Emirates
[email protected]