Snipefinity Acceptable Use Policy

Effective date: 6 June 2026 Operator: Snipefinity is an independent project operated by Ahmad Alibrahim, based in Kuwait (currently unincorporated). Relationship to the Terms: This Acceptable Use Policy forms part of, and is governed by, the Snipefinity Terms of Service. Capitalised terms have the meaning given in the Terms.

1. Scope and relationship to our Terms of Service

This Policy applies to the Snipefinity web application. Our marketing website at snipefinity.com is governed by a separate privacy policy and acceptable-use posture; this Policy does not apply there.

This Policy is incorporated by reference into our Terms of Service. By accessing or using the Snipefinity web application, you agree to follow it. A violation of this Policy is a violation of the Terms of Service and may result in the consequences described in Section 12.

This Policy is written for individual users of the paper-beta application. We do not offer firm, partner, broker-dealer, asset-manager, white-label, or other business-to-business access at paper-beta. If you represent a firm or partner organisation and require business access, contact us — a separate agreement will apply, and this Policy will not be the controlling document for that relationship.

Where this Policy refers to "Snipefinity," "we," "us," or "our," it means Snipefinity (currently operated as an unincorporated project by Ahmad Alibrahim, based in Kuwait). Where it refers to "you" or "your," it means an individual who has registered for and is using the paper-beta application.

2. Purpose of this Policy

We publish this Policy for three reasons.

To protect the platform and its users. Snipefinity is a small, beta-stage technology platform. Abuse of shared resources — automated scraping, denial-of-service, account misuse — degrades the experience for every other user and forces us to spend engineering time on defence rather than improving the product.

To honour our Sharia-compliance commitment. Snipefinity is a Sharia-compliant technology platform; this is a platform-wide commitment, not a per-user toggle (see Terms of Service and Privacy Policy). This Policy describes user behaviours that are inconsistent with that commitment and prohibits them.

To define our security posture. This Policy tells you what we consider responsible use of broker connections, API surfaces, security testing, and vulnerability disclosure. Acting within this posture protects you; acting outside it puts your account, your broker funds, and other users at risk.

This Policy is plain-English imperative. Where it says "you may not," we mean we will treat the behaviour as a violation. Where it says "you should" or "please," we mean it is strongly encouraged but enforcement is discretionary.

3. Sharia compliance — no circumvention

Snipefinity classifies assets as compliant, non-compliant, or uncertain using our internal Sharia screening engine, together with industry-recognised Sharia data sources where contracted (see Privacy Policy §9, which describes how any third-party Sharia reference-data supplier would be disclosed upon contractual finalisation; none is engaged today). Our classification is informational and algorithmic — it is not a religious ruling, and we are not a religious authority.

You may not attempt to author universes, strategies, or trade intents that target assets identified as non-compliant by Snipefinity's Sharia screening engine.

This prohibition is a behavioural commitment from you. We do not represent that our platform's technical controls block every possible circumvention path today. Universe-layer enforcement (the gated-asset universe that strategies select from, and the conservative-default flag for unscreened assets) is in effect at paper-beta launch. Defence-in-depth at the order-routing layer, the strategy-DSL layer, the AI-assistant layer, and the backtest layer is still in development and will land before live-trading enablement (see our Privacy Policy). Until those layers are fully wired, the integrity of the Sharia-compliant universe depends substantially on users acting in good faith at the surfaces that are not yet technically gated. This Policy is the rule; the engineering is the safety net.

In particular, you may not:

  • Author a custom universe whose explicit purpose is to include assets that our engine has classified as non-compliant.
  • Use the strategy DSL, the AI-assistant features, the public API (when available), or any other surface to construct a trade intent referencing an asset our engine classifies as non-compliant.
  • Use third-party tools, scripts, or automation to bypass front-end controls that surface only compliant assets.
  • Attempt to coerce, prompt-inject, jailbreak, or otherwise manipulate AI-assistant features into producing strategies that target non-compliant assets.

If you disagree with a Sharia classification verdict, please contact support to raise a classification question; we will review and may revise. A user-facing dispute mechanism is in development and will be released before live-trading enablement.

A good-faith disagreement raised through the dispute channel is not a violation of this Policy. Attempting to act on that disagreement by trading the disputed asset before we have reviewed it is.

4. Account abuse

Snipefinity accounts are issued to individual humans. The contractual posture is set out in the Terms of Service §3.7 and §11:

Each User is permitted one (1) account on the Service. Creating multiple accounts to circumvent usage limits is prohibited and is grounds for termination of all of a User's accounts.

This Section 4 sets out the behavioural detail of that prohibition. You may not:

  • Create multiple accounts for the same person — including, in particular, alternate accounts whose purpose is to fragment activity so that aggregate usage exceeds what a single account is intended to allow.
  • Operate multiple accounts to evade beta-programme limits, rate limits, or any other usage limit.
  • Proxy for other users — operate or register an account on behalf of another person without their authorisation, or impersonate any individual or entity in your account details. The exception is the explicit fiduciary/authorised-operator path: if you are a fiduciary or otherwise authorised to operate an account on behalf of another person, contact us — at paper-beta we do not support that mode and you cannot self-serve into it.
  • Share, sell, lend, or transfer your account credentials or session to anyone else. If you need shared access for a household member, contact us — at paper-beta we do not support shared accounts, but we may at a later phase.
  • Use automation to evade our rate limits or other usage controls. This includes coordinated multi-account behaviour, IP rotation, residential-proxy rotation, or any technique whose purpose is to obtain more capacity than a single account is intended to receive.
  • Scrape or systematically extract content, asset lists, classification verdicts, backtest results, methodology pages, or any other material from the Snipefinity web application outside of our documented API surfaces.
  • Register from a jurisdiction or with a country-of-residence value that is materially incorrect. Our content tailoring and disclaimers depend on this field (see Privacy Policy §3.1); misrepresenting it undermines the protections we offer you and may make your use of the platform unlawful in your actual jurisdiction.

Where we determine in good faith that a User has created or operated more than one account to circumvent usage limits, the consequence is termination of all of the User's accounts, in addition to the other remedies set out in Section 12. We may act without prior notice where multi-accounting has caused, or is likely to cause, material loss to other users, to our infrastructure, or to Snipefinity.

5. Strategy and DSL abuse

The strategy DSL and block editor exist to let you compose trading strategies. You may not use them as a vector for any of the following:

  • Embed malicious code, payloads, or exfiltration logic in any DSL expression, strategy parameter, comment, or other user-authored field. Our DSL is not a general-purpose execution environment; do not treat it as one.
  • Denial-of-service via backtest or simulation — submitting a strategy or backtest configuration whose purpose or predictable effect is to exhaust shared compute, memory, or storage resources. This includes pathologically large universes, unbounded loops in expressions, and deliberately expensive parameter sweeps designed to monopolise the queue.
  • Resource exhaustion of any platform component or shared compute, memory, storage, or queue resource.
  • Attempts to bypass strategy validation by malformed input, encoding tricks, escape characters, or any technique designed to make a strategy or universe pass save-time validation while behaving differently at execution time.
  • Probing for vulnerabilities in the DSL parser, expression evaluator, or any related component, outside of the coordinated-disclosure process described in Section 10.

If you encounter a strategy or universe that the platform appears to validate but that behaves incorrectly, please tell us through support or the coordinated-disclosure process in Section 10 — do not weaponise it.

6. Broker connections and broker abuse

Snipefinity routes signals to your broker through our sister service, SnipeRoute (see Privacy Policy §6.3 for the narrower-scope identity record SnipeRoute holds). Your funds always live at your broker; we never hold them, and we are not your custodian, your asset manager, your financial adviser, or your broker-dealer.

All trade intents emitted via Snipefinity are self-directed. They originate from a strategy you authored or selected and from your decision to enable signal routing. Snipefinity does not recommend any specific transaction; the platform is a tool you use, not an actor that acts on your behalf.

With that architecture in mind, you may not:

  • Connect Snipefinity to a broker account you do not own or are not authorised to operate. If you are a fiduciary or otherwise authorised to operate an account on behalf of another person, contact us — paper-beta does not support that mode of access.
  • Share your broker API keys or OAuth tokens with any other person, including in screenshots, support messages, public forums, or any other channel. If you suspect a key or token has been exposed, rotate it at your broker immediately and contact support.
  • Configure broker API keys with permissions you do not need. In particular, where your broker allows it, your Snipefinity-connected key should be configured without withdrawal or transfer permissions — Snipefinity has no need for withdrawal access, and granting it expands your loss surface in the event of any compromise.
  • Use Snipefinity to violate your broker's terms of service. This includes (but is not limited to) order patterns prohibited by your broker, signal frequencies that exceed your broker's rate limits, and the use of any broker product in a jurisdiction where that product is not authorised.
  • Use Snipefinity to evade broker-side risk controls, position limits, margin rules, or pattern-day-trader designations. If your broker imposes a control, that control is between you and your broker; we will not help you bypass it.

Your broker may impose its own restrictions on third-party-platform connections — for example, geographic restrictions on which countries can connect, asset-class restrictions, advance-notice requirements for third-party API use, or outright prohibitions on automated routing. You are responsible for complying with your broker's terms in addition to this Policy. You acknowledge that broker connectivity to Snipefinity is at your broker's discretion and may be restricted, throttled, or terminated by the broker at any time, for any reason consistent with the broker's own agreement with you.

We may, at our discretion, drop or rotate stored broker credentials for security reasons (for example, on receipt of an alert that an exchange-side key is suspected of compromise). When we do this, you will need to re-authorise the connection.

7. AI-assistant abuse

Snipefinity uses third-party LLM features (currently Anthropic; see Privacy Policy §5 for how AI-assisted-feature inputs are handled and Privacy Policy §6.1 for the Anthropic sub-processor row) to assist with strategy authoring, classification, and related analytical tasks. These features are subject to additional abuse prohibitions because the cost, safety, and integrity of AI output affects every user.

You may not:

  • Attempt prompt-injection, jailbreaking, or other manipulation of AI-assistant features intended to bypass safety filters, system prompts, content controls, or our Sharia-compliance gating.
  • Use AI-assistant features to generate strategies that target non-compliant assets, and then attempt to deploy, save, backtest, or trade those strategies. Generating such output incidentally — for example, asking an exploratory question — is not itself a violation; attempting to operationalise it is.
  • Submit prompts designed to extract our system prompts, internal configurations, methodology weights, classification thresholds, or other proprietary signals from the AI surface.
  • Use AI-assistant features to generate content that is unlawful, defamatory, harassing, sexually explicit, or that infringes the rights of any third party.
  • Use AI-assistant features to produce volume that is plainly disproportionate to legitimate individual use — for example, scripted batch invocation, bulk prompt sweeps, or use as a free inference proxy for unrelated workloads.

Where our AI sub-processor's own terms apply additional restrictions, those restrictions also apply to your use of those features through Snipefinity.

Snipefinity may use behavioural analytics tooling (tool TBD) to detect abuse patterns in AI-assistant use, in line with the consent and jurisdiction-conditional gating described in our Cookie Policy and Privacy Policy.

8. Communications, reporting, and (future) social features

At paper-beta, the Snipefinity web application does not host user-to-user messaging, public forums, comments, strategy sharing, or other social surfaces. The following rules apply now to any user-to-Snipefinity communication and will extend to user-to-user surfaces if and when they ship:

  • No harassment, threats, hate speech, or targeted abuse in any communication with our support team, security team, or any other Snipefinity channel.
  • No false or misleading dispute reports. If you flag a Sharia classification verdict (see Section 3), a security issue (Section 10), or a violation of this Policy by another user, you should believe the report to be true. Repeated bad-faith reports are themselves a violation of this Policy.
  • No solicitation, advertising, or unauthorised commercial use of our communication channels.

When user-to-user surfaces ship in a future phase, an updated version of this Policy will add explicit prohibitions covering content, conduct, intellectual property, and impersonation in those surfaces.

9. Legal and regulatory boundaries

You are responsible for your own legal and regulatory compliance. You may not use Snipefinity:

  • For any activity that is unlawful in your jurisdiction of residence or in any jurisdiction from which you access the platform. Snipefinity is a technology platform; we do not perform per-user jurisdictional gating beyond the disclosures and broker-side controls described in our Terms and Privacy Policy. Your country-of-residence declaration shapes content and disclaimers, but the underlying lawfulness of your activity is yours to confirm.
  • For money laundering, terrorism financing, sanctions evasion, or any activity prohibited by applicable sanctions regimes (including but not limited to US OFAC, UN, EU, UK HMT, and relevant GCC sanctions lists). You represent that you and any beneficial owner of your broker account are not subject to such sanctions.
  • For market manipulation, insider trading, wash trading, spoofing, layering, or any other manipulative or deceptive trading practice prohibited by the laws or rules of any relevant market, exchange, or regulator.
  • To circumvent capital controls, currency-export rules, or tax obligations in any jurisdiction.

You are responsible for the tax treatment of your trading activity, including any Zakat treatment of trading gains under the rules applicable to you. Snipefinity does not provide tax advice and does not file tax forms on your behalf. The accuracy of any tax-related export, summary, or report we may offer is your responsibility to verify before relying on it.

10. Security testing and coordinated disclosure

We welcome security research that helps us harden the platform — but only when conducted within the boundaries described here.

You may not conduct penetration testing, vulnerability scanning, fuzzing, or any other intrusive security testing of the Snipefinity web application, SnipeRoute, our APIs, or any infrastructure we operate, without our prior written consent. This includes any technique whose purpose or predictable effect is to identify exploitable weaknesses, exfiltrate data, escalate privileges, or move laterally between systems.

If you discover a vulnerability in the normal course of using the platform, please report it to legal@snipefinity.com. Coordinated-disclosure expectations:

  • Do not access, modify, or download data belonging to any other user.
  • Do not retain a copy of any data you incidentally accessed; tell us what you saw and delete your copy.
  • Give us a reasonable window to investigate and fix before any public disclosure. We will work with you on timing.
  • Acting in good faith under this section will not be treated as a violation of this Policy, even if your investigation touched parts of the platform you would not normally touch in regular use.

Bug-bounty programme. A formal bug-bounty programme is under consideration and will be published if and when it launches. Until then, the coordinated-disclosure expectations above apply, and we may, at our discretion, offer recognition or compensation for high-quality reports.

11. Programmatic and agent access

Programmatic and agent access to the Service (an application programming interface, a command-line tool, or access by an automated or AI agent acting on your behalf) is not available during the private beta. If and when such access is offered, the acceptable-use rules for it will be published at that time.

12. Consequences of violation

If we determine that you have violated this Policy, our response will depend on the nature and severity of the violation, your history on the platform, and any harm to other users or the platform. Possible responses include:

  • Warning — a notice to your account, with the violation logged.
  • Feature suspension — temporary removal of access to specific features (for example, AI-assistant, custom universes, or broker connectivity) while we investigate.
  • Account suspension — temporary loss of access to the platform.
  • Account termination — permanent loss of access, with data retention and deletion handled per our Privacy Policy.
  • Recovery of damages, indemnity claims, or other legal remedy — where the violation has caused us, our partners, or other users material harm.
  • Reporting to relevant authorities — where the conduct may involve unlawful activity, fraud, market manipulation, sanctions evasion, or threats to other persons.

We will, where reasonable and consistent with our security obligations, give you notice of the action we are taking and an opportunity to respond — but we may act without notice where delay would aggravate harm (for example, an active security incident, ongoing data exfiltration, or threats to other users).

Termination of your account does not relieve you of any obligation you owe us under our Terms of Service or this Policy, and does not entitle you to a refund of any fee unless our Terms expressly say so (at paper-beta, the platform is offered without a fee).

13. Reporting violations by others

If you believe another user has violated this Policy, please report it to support@snipefinity.com. Include:

  • A description of what happened and, if applicable, when.
  • Any evidence you can share without violating our Policy yourself (for example, do not include another user's API keys or personal data you obtained outside of normal use).
  • Your account identifier, so we can contact you for clarification.

We treat reports confidentially to the extent permitted by law and our security obligations. We may need to share aspects of a report with affected users, broker partners, or authorities where appropriate.

False or bad-faith reports may themselves be a violation of this Policy (see Section 8).

14. Changes to this Policy

We will revise this Policy as the platform changes, in particular when new features (for example, live trading) ship.

Amendment process (per the canonical process described in our Terms of Service §17, applied to privacy-specific changes in Privacy Policy §16):

  • If an engineering milestone tied to a forward-clause in this Policy or our Privacy Policy slips, we will publish an amendment narrowing the claim before the gated event rather than letting the claim silently lapse.
  • We will give notice of material changes through an in-product banner and an email to the address on file, before the change takes effect.
  • Non-material changes (typos, clarifications, formatting) may be made without notice.

Continued use of the platform after a change takes effect means you accept the revised Policy. If you do not accept it, you should stop using the platform and may request account deletion under our Privacy Policy.

15. Forward-clauses — what changes when new features ship

This Policy will be updated when new features ship (for example, live-trading enablement). Until then, the prohibitions above apply in their current form. Any new feature that introduces new conduct rules will be accompanied by an updated version of this Policy before, or at the time of, launch.

16. Contact

Operator: Snipefinity (currently operated as an unincorporated project by Ahmad Alibrahim, based in Kuwait). Registered address: Kuwait.