Felag acceptable use policy

Draft for review by an Australian lawyer; not yet in force. Version 2026-10-27.

This policy is part of the terms and the maker agreement. Most of it is also enforced in code by the review gate, the runtime and the trust module; this page says what the rules are and what happens when they are broken.

What an automation may not do

An automation, in any version, may not:

1. Act outside its footprint. Read, write or connect to anything its manifest and footprint do not declare. The gate blocks undeclared destinations; the hosted sandbox allows egress only to declared providers.
2. Collect or send out data beyond its job: no harvesting of contacts, credentials, card numbers, health records or anything in its "never" list; no exfiltration to outside endpoints, URL shorteners or raw IP addresses.
3. Hide instructions: no injected instructions ("ignore previous instructions", "do not tell the user"), hidden or zero-width text, obfuscated or encoded payloads, or dynamic code execution.
4. Carry secrets. No credential, token, key or password in prompts, settings or code. Keys reach a run from the buyer's vault by name.
5. Impersonate a person, a professional, a regulator or a brand, or produce content designed to deceive the people it contacts.
6. Make reserved decisions alone. In regulated roles, act without the professional sign-offs the schedule requires. Anywhere, take an irreversible action it was told to ask about first.
7. Break the law of the places it is sold: spam (the Spam Act requires consent, sender identification and a working unsubscribe in every marketing message), discrimination in employment or credit decisions, unlicensed legal, tax, financial, health or migration advice, or interference with a computer system.
8. Target children or process children's personal information without the buyer confirming a lawful basis in writing.
9. Copy verbatim. Ship another listing's core or watermark. Behavioural similarity is allowed and ranked (replicas at half score); verbatim copying is taken down.
10. Game the gate by extracting hidden benchmark cases, or game ranking by generating runs, reviews or seats.

What a buyer may not do

1. Use an automation for an unlawful purpose, or in a sector where its use would breach a professional or licensing law without the professional in the loop.
2. Connect accounts you have no right to connect, or process personal information without the consents and notices the Privacy Act requires.
3. Switch off a sign-off to let an automation take an action that a person must approve by law, or where the schedule says the sign-off is mandatory.
4. Share licence keys, API keys or sessions; extract, copy or redistribute an automation's core; strip its watermark; or run it outside the licence.
5. Create accounts, seats or runs to influence rankings or payouts, or buy from yourself.
6. Probe, scan, load-test or interfere with the service, other buyers or the vaults.
7. Post reviews you did not earn (a review needs a seat with at least three runs), or reviews for your own listing.

What a maker may not do

Everything above, plus: list for a regulated role without the registration or co-maker it needs; make a false declaration; use a buyer's connections or data for anything but the buyer's job; contact buyers outside Felag's support tools for marketing; or retaliate against a buyer for a review or a dispute.

Enforcement

Decisions are recorded in the audit log and can be appealed once within 7 days through support. Felag may act first and explain afterwards when a live security incident requires it.