Snipefinity Terms of Service

Effective date: 6 June 2026 Applies to: the Snipefinity private paper-beta (the Snipefinity web application). Operator: Snipefinity is an independent project operated by Ahmad Alibrahim, based in Kuwait. Snipefinity is currently unincorporated; on incorporation these Terms will be updated to name the entity (see section 21). Beta notice: This is a private, invitation-only beta. The Service runs in a simulated (paper-trading) environment. No real money is traded, and Snipefinity is provided free of charge during the beta. Not investment advice. These Terms form a binding agreement between you and the Operator. Snipefinity provides software tooling, not financial advice (see sections 2, 12, and 13).

Acceptance and scope
About Snipefinity
Eligibility and account registration
The Service — what we provide
Beta status and ability to discontinue
Sharia-compliance commitment
Broker connection and SnipeRoute
AI-assisted features
Your content and intellectual property
Acceptable use
Fees and billing
Risk disclosures
Disclaimers and warranties
Limitation of liability
Indemnification
Termination
Changes to these Terms
Governing law and dispute resolution
Jurisdictional addenda
Programmatic and agent access
Forward-clauses
Contact and Data Protection Officer

1. Acceptance and scope

1.1 Scope of these Terms

These Terms apply to the Snipefinity web application. Our marketing website at snipefinity.com is governed by separate terms.

These Terms form a binding agreement between you ("you" or "User") and Snipefinity (currently operated as an unincorporated project by Ahmad Alibrahim, based in Kuwait) ("Snipefinity", "we", "us", or "our"). Formal incorporation will be undertaken in connection with future funding or live-trading enablement; these Terms will be updated accordingly (see §17). Where these Terms reference a separate document — for example, the Privacy Policy, Cookie Policy, or Acceptable Use Policy ("AUP") — that document is incorporated by reference into these Terms and applies with the same force.

1.2 How you accept these Terms

You accept these Terms by doing any of the following:

creating an account through Clerk on the Snipefinity paper-beta application;
accessing or using the Service after these Terms are presented to you; or
expressly agreeing to these Terms through an in-product control.

If you do not agree to these Terms, you must not use the Service.

1.3 The Service the Terms cover

For the purposes of these Terms, the "Service" means the Snipefinity paper-beta application — the strategy authoring environment, the backtest engine, the paper-trading environment, the live signal-routing path (when enabled for your account), AI-assisted features, the Sharia screening engine surfaced through the application, account features, and any documentation or communications we provide in connection with the application.

The Service does not include:

our marketing website at snipefinity.com (separately governed);
any direct interaction you have with a third-party broker (governed by your agreement with that broker);
any third-party platform, market-data provider, or LLM provider acting as a sub-processor (each governed by its own terms with you or with us, as applicable).

1.4 Beta status (summary)

The Service is provided as a paper-beta. That means:

the Service is in active development; features may change, be added, or be removed without notice;
best-effort uptime only — there is no service-level agreement at the paper-beta tier;
you participate in the paper-beta on the data-use basis described in §8 and the Privacy Policy;
there is no live-money trading during paper-beta — only simulated paper trading. Live trading is gated by a separate enablement step that we will announce when it is available, governed by the version of these Terms then in force.

Additional beta-status terms — including our ability to pause, modify, or discontinue the Service at any time — are set out in §5.

2. About Snipefinity

2.1 Who we are

Snipefinity is currently operated as an unincorporated project by Ahmad Alibrahim, based in Kuwait. Formal incorporation will be undertaken in connection with future funding or live-trading enablement; these Terms will be updated accordingly (see §17). Our contact details are listed in §22. The operator is a technology company.

2.2 What we are not

Snipefinity is a pure technology platform. We are not, and we do not hold ourselves out to be:

a custodian — we never hold your funds in any form or in any flow;
an asset manager or portfolio manager — we never trade on your behalf or take discretion over your assets;
a financial advisor or investment advisor — we do not provide personalised investment advice, do not assess your suitability for any product, and do not recommend any specific security or instrument to you;
a broker-dealer, clearing firm, or introducing broker — we do not execute orders. Your broker executes;
a money services business or money transmitter — we do not touch user funds in any flow.

Nothing in the Service should be construed as a solicitation, offer, recommendation, or invitation to buy or sell any security, commodity, or other financial instrument. Strategies, signals, backtest outputs, paper-trading track records, AI-assisted suggestions, and screening verdicts are produced by our platform as an informational and operational tool for you to use at your own discretion.

2.3 Sharia-compliant trading platform

Snipefinity is a Sharia-compliant trading platform. This is a foundational, platform-wide commitment: there is no user-level toggle, no per-geography variation, and no opt-out. Trading of assets identified as non-compliant by our Sharia screening engine is not supported on the platform. Section 6 sets out the substance of this commitment in detail — including what we can confidently claim today, what is still being implemented, and the milestones by which each remaining piece will land.

2.4 Languages

These Terms are published in English. If we publish translations into other languages (for example, Arabic) the English version controls in the event of any conflict, except where applicable law requires otherwise.

3. Eligibility and account registration

3.1 Minimum age

You must be at least 18 years old to create an account or use the Service. We do not knowingly collect personal data from individuals under 18. If we learn that we have collected personal data from a person under 18 without verifiable parental or guardian consent (where required by applicable law), we will delete that data promptly. Where your broker imposes a higher minimum age for some products (for example, certain UAE broker products require age 21), you must satisfy the broker's age requirement in addition to Snipefinity's 18+ minimum (see §19.5).

3.2 Capacity and authority

By creating an account you represent and warrant that:

you have the legal capacity to enter into a binding contract in your jurisdiction of residence;
the personal information you provide is accurate and current and will be kept accurate and current;
you are using the Service for your own personal, non-commercial purposes (commercial, multi-tenant, partner, or whitelabel use requires a separate written agreement with us);
you are not maintaining, and will not create, any other account on the Service — see §3.7 and §11;
if you connect a broker account, you are the rightful holder of that account and you are authorised to grant Snipefinity (and SnipeRoute, our broker-abstraction sister service) access to it for the purposes described in §7.

3.3 Sanctions and restricted-country representation

By creating an account and on each continued use of the Service, you represent and warrant that:

you are not subject to, ordinarily resident in a country or territory subject to, or owned or controlled by any person subject to, comprehensive economic sanctions or trade embargoes administered by the United States Office of Foreign Assets Control ("OFAC"), the United Nations Security Council, the European Union, the United Kingdom (HM Treasury Office of Financial Sanctions Implementation), or other applicable sanctions authorities relevant to your or our jurisdictions (including applicable GCC sanctions lists);
you are not named on any applicable sanctions, denied-persons, blocked-persons, or specially-designated-nationals list maintained by any of the authorities listed above;
your use of the Service does not violate any applicable export-control or anti-money-laundering law; and
you will not use the Service to facilitate any activity that would breach any such law or sanction.

We may suspend, restrict, or terminate your account if we believe in good faith that this representation has ceased to be true (see §16).

3.4 Account creation through Clerk

We use Clerk as our identity and authentication sub-processor. When you create an account you provide certain information to Clerk — at minimum an email address, and optionally a name, profile picture, or OAuth identity from a provider you choose (for example, Google, GitHub). Clerk session metadata (IP address, user agent) is collected automatically. You will also be asked to declare your country of residence (see Privacy Policy §3.1), which we use to tailor content, disclaimers, and (where applicable) jurisdictional addenda — not to block signups based on country. The full data-handling description is in the Privacy Policy.

3.5 KYC and identity verification

Your broker performs the full identity-verification ("KYC") and anti-money-laundering programme applicable to your broker account; that programme is between you and your broker. Snipefinity does not collect government-issued identification documents, national ID numbers, dates of birth, residential addresses, source-of-funds information, or biometric data.

Snipefinity does, however, operate a narrower operator-side verification gate for abuse-control and identity-confirmation purposes:

Email verification is required before you may submit backtests.
Phone verification and a light-KYC step are required before live trading is enabled for your account. The light-KYC step is narrower in scope than your broker's KYC (it is principally email confirmation, phone confirmation, and a minimal-identity attestation) and is described in more detail in the Privacy Policy §3 and in §11 of these Terms.

By creating an account and by requesting live-trading enablement, you agree to complete the applicable verification step honestly.

3.6 Account security

You are responsible for keeping your account credentials secure. You must notify us promptly if you become aware of unauthorised access to your account. You authorise us to act on instructions submitted through your authenticated session.

3.7 One account per person

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

You may not share, transfer, or sell your account. The behavioural detail of this commitment (including the prohibition on multi-account fragmentation, IP rotation, proxy-for-other-users patterns) lives in the Acceptable Use Policy §4; this §3.7 and §11 are the contractual representation.

4. The Service — what we provide

The Service consists of the following core surfaces. Each is described to identify the contractual obligation; technical detail lives in product documentation.

4.1 Strategy authoring and backtesting

The Service provides a block-editor and a domain-specific language ("DSL") for composing trading strategies on the Sharia-compliant asset universe maintained by Snipefinity. The backtest engine runs your strategies against historical market data and returns performance metrics (such as returns, drawdown, Sharpe ratio, and win rate). DSL validation rejects references to assets that our Sharia screening engine has identified as non-compliant.

You are solely responsible for the design, parameters, and economic logic of any strategy you author or select.

4.2 Paper trading

Paper trading runs your strategies forward against live market data with simulated fills — no real money is at risk, no real orders are sent to any execution venue, and no broker is involved. Paper-trading positions are an internal Snipefinity simulation. Order validation rejects non-compliant assets. Paper-trading results are not predictive of live-trading results: see §12.4.

4.3 Live signal routing (post-paper-beta phase, when enabled)

When live signal routing is enabled for your account, strategies that meet the graduation criteria (a soft gate; see product documentation) may emit signals that flow:

Snipefinity → SnipeRoute → your broker → execution venue

Snipefinity passes intent; SnipeRoute is the broker abstraction layer that handles broker-specific protocols and connectivity (see §7); your broker executes. The SnipeRoute layer also enforces Sharia compliance as a defence-in-depth check (see §6).

Live signal routing is not enabled during the paper-beta. When it is enabled, additional terms or disclosures may apply, and the then-current version of these Terms governs.

4.4 Service availability

The Service is provided on a best-effort basis. We do not guarantee that the Service will be uninterrupted, error-free, or available at any particular time. Scheduled maintenance, emergency operational interventions (including any platform-level kill-switch we operate to halt signal routing during incidents), and outages at third-party providers (including your broker, our market-data providers, our identity provider, and our hosting providers) may affect or interrupt the Service. We are not liable for the consequences of such interruptions to the extent permitted by applicable law (see §14).

4.5 Changes to features

We may add, modify, suspend, or remove features at any time. Where a change materially affects how you use the Service we will give you reasonable notice through in-product or email communication. See also §5 for our broader rights to pause or discontinue the Service during the beta phase.

5. Beta status and ability to discontinue

Snipefinity is currently a private beta. The Service may be paused, modified, or discontinued at any time without notice during this beta phase. No commitment to permanence or to specific feature availability is given.

You acknowledge that:

features may be added, changed, or removed at any time;
the Service may be made unavailable, in whole or in part, for any reason — including operator-strategic, engineering, regulatory, sub-processor-availability, or safety-related reasons;
there is no service-level agreement at the paper-beta tier; best-effort uptime only;
your participation in the paper-beta is at your own risk and on the data-use basis described in §8 and the Privacy Policy;
if we discontinue the Service or any feature you depend on, we will give such notice as is reasonably practicable through in-product or email communication, and we will honour the data-export and data-deletion rights described in the Privacy Policy; and
nothing in this section limits your statutory rights (including non-waivable consumer-protection rights — see §19).

This §5 supplements §4.4 (service availability), §4.5 (changes to features), and §16 (termination).

6. Sharia-compliance commitment

This section is foundational to the Service. It is written with deliberate care to describe what we do today, what we are building, and what we are not. Snipefinity is a technology platform; what follows is an informational and operational commitment, not a religious ruling.

6.1 Platform-wide commitment

Snipefinity is a Sharia-compliant trading platform. The constraint is uniform across the platform — all users, in all jurisdictions, trade only the compliant universe. There is no per-user toggle, no per-geography opt-in or opt-out, and no override available to users.

6.2 What our Sharia screening engine does today

We maintain a proprietary Sharia screening engine that classifies the assets surfaced by the Service. The engine combines:

sector classification of each asset (using industry data and our own normalisation);
AAOIFI-style financial ratios (such as debt, cash, receivables, and impermissible-income screens), where the underlying financial data is available;
LLM-assisted activity analysis that reads asset descriptions and corporate-activity data to identify revenue lines that would be classified as non-compliant.

Every classification is versioned (we record the methodology version under which a verdict was produced), audited (verdicts are stored alongside their reasoning so they can be reviewed and reproduced), and revisable through an operator-managed override mechanism that may only tighten verdicts, never loosen them — that is, overrides can move an asset toward "non-compliant" or "uncertain" but cannot move an asset away from "non-compliant" back to "compliant".

Our screening engine is internal today. We may combine it with industry-recognised Sharia data sources once such a provider is contracted; none is engaged as of the date of these Terms. Any provider would be named in the reference-data-supplier list of the Privacy Policy upon contractual finalisation. Per-company purification ratios used by our purification flows (see §6.7) would be sourced from the same reference-data supplier.

6.3 What is enforced today, and what is on the way

We have committed to a platform that enforces Sharia compliance at every layer — universe filtering, strategy authoring, backtesting, and order routing. Engineering reality on the date of these Terms is partially shipped today and partially on tracked engineering milestones: the universe-layer mandatory gate, the conservative-default flag on new assets, and the screening engine are operational today, and the point-in-time classification history is operational and internally verified; the strategy DSL save-time check, the backtest engine integration, the order-routing layer, and the user-facing reclassification surfaces are at varying stages of implementation. We have chosen to be honest about this rather than to claim more than we can verify.

Items marked LIVE today are operational. Items marked as forward-clauses are keyed to specific engineering milestones — each will be in effect by the milestone identified, and if any milestone slips, we will publish an amended version of these Terms (and the corresponding Privacy Policy section) before the gated event. The amendment process is in §17.2.

Universe-layer Sharia gate — LIVE today. A mandatory universe-layer gate ensures that only assets that pass our Sharia screening surface in the Service in any non-research environment. Strategy save validation rejects non-compliant references.
Conservative default on asset ingestion — LIVE today. Newly ingested assets receive a default screening flag that treats the asset as non-compliant until it is positively classified.
Point-in-time classification history. Backtests and reclassification handling reference each asset's Sharia classification as of the relevant historical date (point-in-time).
Order-routing layer enforcement. Snipefinity's order-routing path (operated by SnipeRoute) will block any new buy intent targeting an asset our screen has identified as non-compliant. This defence-in-depth check is being added to SnipeRoute and will be in effect before live-trading enablement.
Strategy-time enforcement. The strategy DSL will reject any strategy that resolves to a universe containing non-compliant assets, as a defence-in-depth check at strategy save and publish time. This check will be in effect before live-trading enablement.
Backtest engine alignment. The backtest engine will be wired to the live Sharia data source so that historical reclassifications affect backtest behaviour faithfully. This will be in effect before live-trading enablement.
Reclassification safe-harbour. When an asset is reclassified from compliant to non-compliant, we will apply our safe-harbour pattern (described in §6.5) and notify affected users. The user-facing notification and the new-buy block at the order-routing layer will be in effect before live-trading enablement.
Dispute mechanism with service-level commitments. A user-facing dispute mechanism in account settings (described in §6.6) — with a service commitment to acknowledge within 5 business days and resolve within 30 business days — will be in effect before live-trading enablement. Until that mechanism ships, users may raise classification questions through the support contact listed in §22.

If any of these milestones slips, we will publish an amended version of these Terms (and the corresponding Privacy Policy section) before the gated event, so that the language matches reality. The amendment process is described in §17.2.

6.4 Conservative default

When the classification of an asset is uncertain, we treat the asset as non-compliant. Newly ingested assets are treated as non-compliant until positively classified (see §6.3).

6.5 Reclassification (compliant → non-compliant)

Asset classifications can change. When an asset that you hold (or that is referenced by a strategy you authored) is reclassified to non-compliant, Snipefinity will apply a safe-harbour pattern:

Existing positions: you may continue to hold the position or exit (sell or close) it on your own initiative. We provide a per-holding banner identifying the reclassified asset and an in-product one-click force-sell control so that you can exit quickly if you choose.
Strategies referencing the asset: your strategy continues to run normally. Sell signals fire as designed. We do not freeze your strategy or otherwise remove your agency; new buy intents targeting the reclassified asset will be blocked at the order-routing layer (defence-in-depth at SnipeRoute, in effect before live-trading enablement).
User preference on_sharia_flip. You may configure how your strategies respond to a compliance flip on assets they hold. Three options:
- hold (default) — we notify you; your strategy continues to run; you exit manually via the in-product UI when you choose. This preserves the safe-harbour pattern above.
- auto_exit (opt-in) — we notify you; the system schedules a force-exit at the next bar or session open after a flip is detected. You have explicitly elected this preference; the convenience is for users who do not want to manually intervene on a flip.
- prompt (a future planned option; not yet available) — we notify you and require a confirm-or-dismiss action within a fixed window; if you do not respond, we fall back to hold.
Regardless of preference, the notification always happens. The preference changes the action we take (automatic or manual), not whether you are notified. Backtests run with parity to your live preference: our backtest engine accepts your on_sharia_flip setting through its simulation configuration so that historical results reflect how your preference would have acted at each reclassification event in the backtest window.
Grace period. A default grace period of 90 days applies to force-exit prompts under hold. After the grace period expires we may escalate the in-product notification (for example, a more prominent banner). We will never automatically liquidate or force-sell positions you hold at your broker on reclassification unless you have opted in to auto_exit.
Backtests: historical backtest records are preserved as historical artefacts; runs containing the reclassified asset will carry a watermark indicating the reclassification date so that you can interpret the results in context. Backtests reference an asset's classification as of the trade date (point-in-time history).
No automatic liquidation without opt-in. Snipefinity will not, and SnipeRoute will not, automatically liquidate or force-sell positions you hold at your broker on reclassification unless you have opted in to auto_exit.

A more detailed user-facing explanation of the reclassification flow — including the on_sharia_flip preference UX — is published in our Privacy Policy at §9.6 and in product documentation.

6.6 Disputes about a verdict

You may flag a classification you disagree with. Once the dispute mechanism described in §6.3 is in effect, you will be able to raise a verdict for review through account settings. We will acknowledge your dispute within 5 business days and resolve it within 30 business days under normal circumstances. Until the in-product mechanism ships, please contact support (see §22). We will review the verdict and may revise it. We will not act as a religious authority — final religious certainty is a matter between you and your own qualified Islamic scholar.

6.7 Purification (cross-reference)

Purification handling — capital-gain purification on reclassification exit (Flow A) and ongoing dividend purification at per-company-per-year ratios (Flow B) — is described in our Privacy Policy at §9.9 (Purification — Flow A and Flow B) and in product documentation. Snipefinity provides ledger and notification tooling; the user retains the religious-obligation responsibility for fulfilling purification. The per-company purification ratios are sourced from a third-party Sharia data reference-data supplier; that supplier will be named in the Privacy Policy upon contractual finalisation.

6.8 Fatwa-board status

As of the date of these Terms, Snipefinity has not engaged an external fatwa board. Our Sharia classification is produced by our proprietary screening engine, combined with industry-recognised Sharia data sources where contracted (no third-party Sharia data provider is engaged as of the date of these Terms; any provider will be named in the Privacy Policy upon contractual finalisation); it is informational and algorithmic, not a religious ruling, and not a fatwa.

We may engage a fatwa board in the future. If we do, we will name the board, describe its governance cadence, and update these Terms and the Privacy Policy. Until then, users seeking religious certainty should consult their own qualified Islamic scholar.

6.9 Methodology school and disclosure

The baseline methodology is AAOIFI-style financial-ratio screening combined with sector and activity classification. Users who follow other Sharia methodologies should consult their own scholars; our verdicts reflect our methodology and may differ from theirs.

We disclose our screening methodology at a categorical level in product documentation and in the Privacy Policy (for example, the activity categories we treat as non-compliant). We do not publish the full quantitative internals of our engine.

6.10 Sub-processor and reference-data-supplier framing

Our purification service is operated internally (it is not an external sub-processor). The third-party Sharia data provider that supplies per-company purification ratios and reference classification data is a reference-data supplier — not an Article-28 GDPR sub-processor for user personal data — because that supplier processes asset-reference data, not your personal data. Sub-processors processing your personal data are listed in the Privacy Policy.

6.11 Snipefinity is not a religious authority

Snipefinity is a technology platform. Nothing in §6 is a fatwa, a religious ruling, or a substitute for consultation with a qualified scholar.

7. Broker connection and SnipeRoute

7.1 Your broker is your counterparty

To take real-market action on a strategy, you must connect a broker account that you hold in your own name. The broker is your counterparty. Snipefinity does not hold your funds, does not execute trades, and does not provide a brokerage service. Your broker's terms govern your relationship with that broker; you should read those terms carefully.

7.2 SnipeRoute

Broker connectivity is delivered by SnipeRoute, Snipefinity's broker-abstraction sister service. SnipeRoute is operated as a separate service (see §22) and acts as a sub-processor for Snipefinity for the purpose of broker connectivity.

SnipeRoute (Snipefinity's broker-abstraction sister service) receives broker-connection metadata, signal payloads, and a limited identity record (your email address from Clerk plus session metadata required to manage your broker connections). SnipeRoute does not store user-set passwords; authentication is delegated to Clerk. See Privacy Policy §6.3 for the corresponding privacy disclosure.

7.3 Encryption and credential handling

Broker access tokens and refresh tokens are stored encrypted at rest by SnipeRoute using authenticated symmetric encryption (currently AES-256-GCM with a separate key-management layer). The plaintext tokens are held in memory only during the moments needed to call your broker. The full description of credential handling is in the Privacy Policy.

7.4 Broker authorisation, self-directed intent, and your obligations

When you connect a broker, you authorise Snipefinity (via SnipeRoute) to act as your agent in transmitting signals to that broker on your behalf, within the scope of authorisation you granted. You acknowledge that:

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;
Snipefinity does not assess your suitability for any transaction;
your broker's risk management, margin policy, order-routing policy, execution priority, fee schedule, and venue selection are matters between you and your broker;
you must comply with your broker's terms; if your broker's terms restrict third-party platform connections (for example, requiring advance notice from the connecting platform, or limiting third-party use of the broker's API), you remain responsible for that compliance, and we may add or restrict broker connections to remain compatible with broker-side terms;
Snipefinity makes no representation about "best execution"; execution and order routing are determined by your broker, and Snipefinity's role ends at signal transmission.

7.5 Broker availability and disconnection

A broker may restrict, throttle, or terminate connectivity to Snipefinity at any time at the broker's discretion. If a broker cuts off connectivity, your account on the Service is not affected, but signal routing to that broker will stop until connectivity is restored.

7.6 Non-US residents and US brokers

Some brokers we support are restricted to particular geographic markets (for example, certain US brokers serve US residents only). If your country of residence is incompatible with a broker's geographic restrictions, you must not connect that broker. You are responsible for compliance with your broker's terms regarding geographic eligibility.

8. AI-assisted features

8.1 What AI features do

We offer AI-assisted features — for example, natural-language strategy authoring, AI-assisted classification, and analytical tools — built on top of large-language-model ("LLM") infrastructure. Our primary LLM provider is Anthropic (the maker of Claude); some inferences are handled by a self-hosted fallback model operated by Snipefinity. AI inputs and outputs may include text you type, content you author, descriptive metadata about assets, and other context required to perform the requested task.

8.2 What transits Anthropic

On most AI calls, your input text is sent to Anthropic for inference; on some, a self-hosted fallback model operated by Snipefinity handles the inference instead. Where Anthropic processes inputs, it does so per its commercial terms — as Anthropic's commercial terms stand today (which may change), Anthropic does not by default use API inputs to train its models, and applies a short-term trust-and-safety retention window under its then-current data-retention policy for abuse prevention. This is independent of any retention choice you or we have made on the Snipefinity side.

8.3 What Snipefinity retains

Snipefinity retains your raw AI-feature inputs and outputs for up to 12 months to develop and improve our platform, with a scheduled deletion job enforcing this retention limit. During Snipefinity's beta program, this processing forms part of your beta participation. After the beta program ends, processing continues on the legal basis of our legitimate interest in improving the platform. You may opt out at any time via account settings, and you may request deletion of your retained inputs and outputs through our data-subject-rights mechanism described in the Privacy Policy at §5 (AI features) and §11 (Your rights).

We continuously evaluate stricter data-retention configurations with our LLM sub-processor. When activated, the sub-processor list and the corresponding Privacy Policy section will be updated.

8.4 AI outputs are not advice

AI outputs may contain errors, omissions, or "hallucinations". You must verify any AI-generated strategy logic before deployment — including in paper trading, and especially before any live signal routing is enabled for that strategy. AI features do not understand your personal financial situation, risk tolerance, or investment objectives; nothing produced by an AI feature is personalised investment advice.

8.5 Additional or replacement LLM providers

We use Anthropic (Claude models) as the sub-processor for content generation, classification, and analytical tasks. We may add additional LLM sub-processors as our product evolves; we will update the sub-processor list and notify users via in-product communication or email before enabling new processors.

8.6 AI risk-management framing

Our AI development and deployment practices are designed to align with widely-recognised AI risk-management and transparency good practice, including the applicable transparency obligations of the EU AI Act as they enter into force (see §19.2).

9. Your content and intellectual property

9.1 What "User Content" means

"User Content" means any content you create, author, upload, or submit to the Service — including strategy DSL expressions, parameters and configurations, names and descriptions, tags, notes and comments, backtest configurations, and the text you supply to AI-assisted features.

9.2 You own your strategies

You retain all intellectual-property rights in your User Content, including in any strategies you author. We do not publicly share, publish, or sell your strategies; any future feature that would share or publish your strategies will require your separate, explicit consent.

9.3 Limited licence to operate the Service

To operate the Service for you, you grant Snipefinity a non-exclusive, worldwide, royalty-free, fully sublicensable licence — limited to the scope of operating the Service for you — to host, store, process, transmit, execute, backtest, paper-trade, route signals from, display to you, and make backups of your User Content. This licence exists only to make the Service work; it does not extend to other users, does not grant Snipefinity rights to train AI models on your User Content, and does not allow Snipefinity to share your User Content publicly.

This licence terminates when you delete the relevant User Content or close your account, subject to (a) reasonable time required for deletion to propagate through backups and logs, and (b) retention required by applicable law (for example, audit-log retention required by financial-regulatory or anti-fraud obligations once live trading is enabled).

9.4 Our intellectual property

The Service, the platform infrastructure, the Sharia screening engine, the DSL, the backtest engine, the platform code, the user interface, our trademarks, and all related documentation are owned by Snipefinity (or its licensors) and protected by copyright, trademark, trade-secret, and other intellectual-property laws. You receive a limited, non-transferable, non-sublicensable, revocable licence to use the Service for the duration of your account and within these Terms. You may not copy, modify, reverse-engineer, scrape, or create derivative works of the Service except to the extent permitted by applicable law that cannot be lawfully restricted.

9.5 Feedback

If you send us feedback, ideas, or suggestions about the Service, you grant us a perpetual, irrevocable, royalty-free licence to use that feedback to improve the Service. You waive any moral rights in that feedback to the extent permitted by applicable law.

10. Acceptable use

The full Acceptable Use Policy ("AUP") is published separately and is incorporated by reference into these Terms. This section summarises the categories of conduct that are prohibited. In the event of a conflict, the AUP controls.

10.1 Sharia-compliance circumvention

You may not attempt to author universes, strategies, or trade intents that target assets identified as non-compliant by Snipefinity's Sharia screening engine. If you disagree with a verdict, the dispute path in §6.6 is the route — not technical evasion.

10.2 General prohibitions

You may not:

use the Service to violate any applicable law or regulation, or any third party's rights;
use the Service for any purpose that is fraudulent, defamatory, harassing, hateful, or harmful;
attempt to gain unauthorised access to the Service, other users' accounts, or any non-public component of our infrastructure;
introduce viruses, malware, or any code intended to disrupt, damage, or gain unauthorised access to any system;
bypass, disable, or interfere with any security, rate-limit, kill-switch, or screening feature of the Service;
scrape, crawl, or extract data from the Service except through interfaces we have explicitly authorised for that purpose;
benchmark, copy, or reverse-engineer the Service or any feature of it for competitive purposes;
resell, sublicense, or commercially redistribute the Service without our prior written consent;
use the Service to operate a business that hosts other end users on Snipefinity's infrastructure without our prior written consent (commercial multi-tenant use requires a separate written agreement);
use the Service to engage in market manipulation, spoofing, wash trading, layering, or any conduct that is prohibited by your broker's terms or by applicable market-conduct rules.

10.3 Suspension and enforcement

If we reasonably believe you have breached the AUP or this §10 — or that your conduct presents a material risk to the Service, to other users, to your broker, or to Snipefinity — we may suspend, restrict, or terminate your access in accordance with §16.

11. Fees and billing

Positioning principle. Snipefinity sells tooling and infrastructure: strategy authoring, backtesting, paper trading, signal routing, AI assistance, Sharia screening, and the supporting reporting. We do not sell investment returns, and we do not promise that any strategy will produce a particular outcome. You choose your strategy; the outcome is yours. This is consistent with section 2 (we are a technology platform, not an asset manager or financial adviser) and section 12 (risk disclosures).

The beta is free. During the private beta the Service is provided free of charge. Snipefinity charges you no fee during the beta.

Future paid plans. Snipefinity may introduce paid plans after the beta. If and when it does, the applicable prices and terms will be presented to you in-product before they apply, and these Terms will be amended in accordance with section 17 to add billing-specific terms. No Snipefinity fee is charged until that happens, and you may decline by not taking up a paid plan.

We do not hold your money. Snipefinity does not hold, custody, or have access to your funds. Your broker holds your funds and handles any KYC and anti-money-laundering requirements applicable to your account. We never verify, audit, or attest to your account balance. See section 2 (we are not a custodian, asset manager, or money services business) and section 7 (your broker is your counterparty).

Broker-side fees are between you and your broker. Your broker may charge fees, such as commissions, spreads, financing, withdrawal, market-data, regulatory, or custodial fees, for activity initiated via signals you authorise. Those fees are governed by your agreement with your broker. Snipefinity does not receive, collect, process, or share in them, and we have no visibility into them.

One account per user. Each user may hold one (1) account on the Service. Creating multiple accounts to circumvent any limits is prohibited and is grounds for termination. This is also reflected in section 3 and in the Acceptable Use Policy.

Live trading is not part of the beta. Live trading is not enabled during the private beta; all activity is simulated (paper) only. If and when live trading is offered, it will require additional verification, including identity confirmation, and a separate enablement step on your account. The data collected for that verification is described in the Privacy Policy.

12. Risk disclosures

The Service is informational and operational; the risk is yours. The following disclosures are not exhaustive. Read them carefully.

12.1 Trading risk

Trading and investing involve substantial risk and can result in losses, including total loss of the capital you have committed at your broker. Past results — including any results displayed in backtests, paper-trading track records, leaderboards, demonstration content, or marketing materials — are not indicative of, and do not guarantee, future returns. Volatile markets can produce outcomes that no historical record predicted.

12.2 Sharia screening risk

Our Sharia classification process is algorithmic and informational, combining our internal Sharia screening engine with industry-recognised Sharia data sources where contracted (no third-party Sharia data provider is engaged as of the date of these Terms; any provider will be named in the Privacy Policy upon contractual finalisation). It is not a fatwa and not a religious ruling. When classification is uncertain, the asset is treated as non-compliant. Asset classifications can change; when an asset is reclassified, our safe-harbour pattern applies (see §6.5). Users seeking religious certainty should consult their own qualified Islamic scholar. Methodology school: AAOIFI-style is our baseline; users following different schools should consult their own scholars.

12.3 AI-assisted feature risk

LLM outputs may be incomplete, incorrect, or fabricated. You must independently verify any strategy logic, code, parameter, or recommendation produced or assisted by an AI feature before relying on it. AI features do not understand your personal financial situation, risk tolerance, time horizon, or constraints.

12.4 Backtest and paper-trading risk

Backtest and paper-trading results have inherent limitations. Common biases include:

Look-ahead bias — strategies may inadvertently use information that would not have been available at the time of a historical decision.
Survivorship bias — historical data may exclude assets that ceased trading, biasing results upward.
Regime change — past market conditions may not recur; backtests over one regime may not predict the next.
Data quality — historical market data may be incomplete, contain errors, or differ from the data that was actually published in real time.
Simulated fills — paper-trading uses simulated fills against live market data. Live execution differs in ways that may materially affect strategy performance, including slippage between observed price and fill price; partial fills; order rejection by the broker; latency between signal emission and broker receipt; broker-side risk-management overrides; venue outages; and execution-priority differences. Paper-trading track records are not predictive of live track records.

We mitigate these biases where we can within the Service, but we cannot eliminate them. For US-targeted product surfaces in any future version, additional FINRA Rule 2214-style disclosures (criteria + methodology + limitations + key assumptions; variability over time; universe + selection methodology; hypothetical-results warning) will be added to these Terms before such surfaces are launched.

12.5 Service-availability risk

The Service is provided on a best-effort basis. There is no SLA at paper-beta. Scheduled maintenance, emergency operations (including any kill-switch we operate to halt signal routing during incidents), and outages at our hosting provider, identity provider, market-data providers, LLM provider, or other sub-processors may interrupt your use of the Service. The Service may also be paused, modified, or discontinued at any time during the beta phase (see §5).

12.6 Broker-execution risk

Execution and order routing are determined by your broker. Snipefinity does not promise "best execution", "guaranteed fill", or any specific execution quality. Slippage, partial fills, order rejection, latency, broker risk-management overrides, broker outages, and venue outages are between you and your broker. Snipefinity's role ends at signal transmission.

12.7 Margin and leverage risk

Margin and leverage features at your broker can amplify both gains and losses, and may cause losses exceeding your deposited capital. For users following Sharia-compliant strategies, margin (which typically involves interest, or riba) is generally disabled by default; you are responsible for verifying that any leverage product you elect at your broker is compatible with your Sharia preferences and with the Sharia-compliance commitment described in §6.

12.8 Algorithmic-trading risk

Strategies you author or select that are executed via Snipefinity are algorithmic in nature. They may produce unexpected results in market conditions that differ from the backtest distribution; they may emit a high volume of orders in a short interval; and they may exhibit failure modes that human traders would not. You are responsible for monitoring the strategies you have enabled.

13. Disclaimers and warranties

13.1 As-is and as-available

To the maximum extent permitted by applicable law, the Service is provided "as is" and "as available", without warranties of any kind, whether express, implied, statutory, or otherwise. We disclaim all warranties of merchantability, fitness for a particular purpose, non-infringement, accuracy, completeness, reliability, availability, security, and freedom from harmful components.

13.2 No advice — financial, legal, tax, or accounting

Nothing in the Service is investment advice, financial advice, legal advice, tax advice, or accounting advice. We do not assess your suitability for any transaction. Nothing in the Service is a solicitation, offer, or recommendation to buy, sell, hold, or otherwise transact in any security, commodity, or other instrument. Tax consequences (including Zakat treatment for users with Zakat obligations, and capital-gains / income-tax treatment of activity at your broker) are your responsibility; consult your own tax adviser or qualified scholar as applicable.

13.3 No regulated status

Snipefinity is not a broker-dealer, custodian, asset manager, investment advisor, money services business, or money transmitter, and is not registered as such in any jurisdiction. References in the Service to specific assets are operational and informational; they are not invitations or inducements to invest.

13.4 Third-party content and services

The Service may include or reference content, data, or services provided by third parties (such as market-data providers, brokers, and LLM providers). We do not warrant the accuracy, completeness, timeliness, or availability of any third-party content or service. Your relationship with any third party is between you and that third party.

13.5 Jurisdictional limitation

Snipefinity does not intend to offer or solicit anyone to use the Service in jurisdictions where doing so would be contrary to applicable laws or regulations. If you access the Service from such a jurisdiction, you do so on your own initiative and you are responsible for compliance with local laws.

14. Limitation of liability

14.1 Excluded damages

To the maximum extent permitted by applicable law, Snipefinity (and the operator personally, and our affiliates, contractors, agents, licensors, and service providers, including SnipeRoute) will not be liable for any indirect, incidental, special, consequential, exemplary, or punitive damages, or for any loss of profits, revenue, goodwill, data, business opportunity, anticipated savings, or use, arising out of or in connection with your use of (or inability to use) the Service — whether based on contract, tort (including negligence), strict liability, statute, or otherwise — even if we have been advised of the possibility of such damages.

14.2 Aggregate cap — paper-beta with no fees collected

The Service is currently provided free of charge during the paper-beta. No fees have been or are currently collected from you. The contractual measure that would ordinarily ground an aggregate-liability cap (fees paid in the trailing 12 months) therefore resolves to zero or a symbolic amount during this beta phase.

To the maximum extent permitted by applicable law, Snipefinity's total aggregate liability arising out of or in connection with the Service is capped at the greater of (a) the total fees you have paid us in the 12 months before the event giving rise to the claim, and (b) US$100.

The §14.1 (excluded damages), §14.3 (specific allocations of risk), and §14.4 (carve-outs that cannot be excluded) clauses apply regardless.

14.3 Specific allocations of risk

Without limiting §14.1 and §14.2:

We are not liable for losses caused by broker execution, broker outage, broker risk-management overrides, or any other broker-side action or inaction.
We are not liable for losses caused by third-party data providers, LLM providers, hosting providers, or identity providers.
We are not liable for losses caused by your own conduct, your strategy choices, your AI prompts, your override of system warnings, or your decisions to enable or disable features (for example, AI-feature opt-outs).
We are not liable for the unauthorised actions of any person who accesses your account using your credentials.

14.4 Things we do not exclude

Nothing in these Terms excludes or limits liability that cannot be excluded or limited under applicable law — for example, fraud, fraudulent misrepresentation, death or personal injury caused by negligence, and (in some jurisdictions) gross negligence and wilful misconduct.

14.5 Allocation of risk

You acknowledge that the limitations in this §14 are an essential element of the bargain between you and Snipefinity, that the Service would not be offered to you on these economic terms — including free of charge during the paper-beta — without these limitations, and that the limitations apply even if a remedy fails its essential purpose.

15. Indemnification

To the maximum extent permitted by applicable law, you will indemnify, defend, and hold harmless Snipefinity (and the operator personally, and our affiliates, contractors, agents, licensors, and service providers, including SnipeRoute) from and against any and all claims, demands, suits, proceedings, losses, damages, liabilities, costs, and expenses (including reasonable legal fees) arising out of or relating to:

your use of, or inability to use, the Service;
any User Content you author, upload, or submit;
your violation of these Terms, the AUP, or any law or regulation applicable to your use of the Service;
any breach by you of the sanctions and restricted-country representation in §3.3;
any act or omission of any person who accesses your account or uses your credentials;
any dispute between you and your broker, including any claim by your broker that arises from a signal you authorised Snipefinity (via SnipeRoute) to transmit; or
your infringement of any third party's intellectual property, privacy, or other right.

We may, at our option, assume the exclusive defence and control of any matter otherwise subject to indemnification by you, in which case you agree to cooperate with our defence at your reasonable expense.

16. Termination

16.1 Your right to close your account

You may close your account at any time through account settings or by contacting us at the support address in §22. Closure is effective when we confirm it.

16.2 Our right to suspend or terminate

We may suspend, restrict, or terminate your access to the Service, with or without notice and with or without cause, including (without limitation) where:

we believe in good faith that you have breached these Terms or the AUP;
your conduct presents a material risk to the Service, to other users, to your broker, or to us;
we believe in good faith that the sanctions and restricted-country representation in §3.3 has ceased to be true with respect to you;
we are required to do so by law, regulation, or order of a competent authority;
a sub-processor or service provider critical to the Service has ceased to be available;
you have remained inactive for a prolonged period and we reasonably believe the account is dormant;
we cease to offer the Service or the relevant feature (see §5).

Where the suspension or termination is at our convenience (rather than for cause), we will give reasonable notice, by in-product or email communication.

16.3 Effect of termination

On termination:

your right to access the Service ends;
Sections that by their nature should survive termination — including §§6.5–6.8 (reclassification, disputes, and Sharia framing for residual obligations only), 9 (IP), 12 (risk disclosures, with respect to historical activity), 13 (disclaimers), 14 (limitation of liability), 15 (indemnification), 17 (changes), 18 (governing law), and 22 (contact) — survive;
we will retain User Content and personal data only for the periods described in the Privacy Policy or required by applicable law; data-subject rights described in the Privacy Policy continue to be available to you;
broker connections you authorised will be revoked at the SnipeRoute layer; you should also separately revoke Snipefinity's access at your broker through the broker's interface.

17. Changes to these Terms

This §17 is the canonical description of the amendment process for the Snipefinity legal pack. The Privacy Policy (§16) and the AUP (§14) reference this section rather than duplicating it.

17.1 Routine changes

We may revise these Terms from time to time. We will publish the revised Terms at the URL where you found these Terms (or in-product), update the effective date at the top of these Terms, and where the changes are material we will notify you in advance through in-product communication or by email to the address on file with Clerk. Continued use of the Service after the effective date of revised Terms constitutes acceptance.

17.2 Amendments tied to Sharia milestones

Section 6 contains forward-clauses tied to specific engineering milestones. If a milestone slips, we will publish an amended version of §6 (and any corresponding Privacy Policy section) before the gated event. The intent is to keep the language matched to actual platform behaviour — never to publish a forward-clause that has quietly lapsed.

The amendment process is:

We review these Terms before any material change to the Service takes effect, and update them as needed.
A revised draft of §6 is prepared to narrow the forward-clause to match actual platform behaviour.
The revised draft is reviewed by counsel (a focused review, not a full re-review).
The amended Terms are published before the gated event.
You are notified through an in-product banner and (where we have your email on file) by email.

17.3 Material changes that disadvantage you

For material changes that are materially adverse to you, we will give you at least 30 days' advance notice (or such longer period as applicable law requires), during which you may close your account if you do not agree. Where shorter notice is required by law or regulation (for example, to comply with a regulatory directive), we will give the longest notice reasonably practicable.

17.4 Updated Terms on incorporation

Snipefinity is currently unincorporated. These Terms will be amended upon incorporation of the operating entity (see §1.1 and §2.1). The amended Terms will identify the incorporated entity, its registered office, the governing law, and the venue for disputes (see §18). By continuing to use the Service after the effective date of the post-incorporation Terms, you accept the amended Terms.

18. Governing law and dispute resolution

18.1 Governing law and venue

Snipefinity is currently unincorporated. These Terms are governed by the laws of Kuwait, and you and the Operator submit to the non-exclusive jurisdiction of the courts of Kuwait, except where non-waivable consumer-protection or data-protection law in your country of residence applies. On incorporation of the operating entity, the amended Terms (see §17.4) will confirm the governing law and the venue or arbitration forum for dispute resolution.

Until the operating entity is incorporated and the governing-law clause is fixed, the parties intend that these Terms be interpreted consistently with the unincorporated-project framing in §1.1 and §2.1 and with the operator's residence in Kuwait, subject in each case to any non-waivable consumer-protection or data-protection rights you have under the law of your jurisdiction of residence.

18.2 Class-action waiver

To the maximum extent permitted by applicable law, you and Snipefinity each waive any right to participate in a class action, a class arbitration, or any other representative proceeding, with respect to any claim arising out of or relating to these Terms or the Service. Disputes will be resolved on an individual basis. This waiver does not apply where it cannot lawfully be enforced (for example, under non-waivable consumer-protection laws in the European Union, the United Kingdom, or other jurisdictions where representative-proceeding rights are non-waivable).

18.3 Informal resolution

Before commencing any formal dispute, you agree to contact us at the address in §22 and attempt in good faith to resolve the matter informally for a period of at least 30 days.

18.4 Time limit

To the maximum extent permitted by applicable law, any claim arising out of or relating to these Terms or the Service must be commenced within one (1) year after the cause of action accrues, or be permanently barred. This time-limit does not apply where a longer period is mandated by applicable consumer-protection law (for example, certain EU member-state and UK statutory limitation periods).

18.5 Severability

If any provision of these Terms is held invalid or unenforceable, the remaining provisions will continue in full force and effect.

18.6 Entire agreement

These Terms — together with the Privacy Policy, the Cookie Policy, the AUP, and any other document expressly incorporated by reference — constitute the entire agreement between you and Snipefinity regarding the Service, and supersede any prior or contemporaneous understandings.

18.7 No waiver

Our failure or delay to enforce any provision of these Terms is not a waiver of that or any other provision.

18.8 Assignment

You may not assign your rights or obligations under these Terms without our prior written consent. We may assign these Terms to an affiliate or in connection with a corporate transaction (including incorporation of the operating entity, a merger, acquisition, financing, restructuring, or sale of assets), provided that the assignee assumes our obligations to you.

19. Jurisdictional addenda

The following addenda apply in addition to the body of these Terms when you reside in the listed jurisdiction. Where there is a conflict between an addendum and the body, the addendum controls for that user.

19.1 Gulf Cooperation Council (GCC) — Saudi Arabia, UAE, Qatar, Kuwait, Bahrain, Oman

Data protection. Snipefinity is designed to align with the principles of applicable GCC data-protection regimes, including the Saudi PDPL (and its Implementing Regulations and Cross-Border Transfer Regulation), the UAE Federal PDPL, the DIFC Data Protection Law 2020 (where applicable to the operating entity post-incorporation), the ADGM Data Protection Regulations 2021 (where applicable to the operating entity post-incorporation), the Bahrain PDPL 2018, the Kuwait CITRA Data Privacy Protection Regulation, the Qatar PDPPL, and the Oman PDPL. Detail — including cross-border transfer mechanisms, lawful bases, and data-subject rights — is in the Privacy Policy.
Sharia. Section 6 applies uniformly. Snipefinity is not a religious authority; nothing in §6 is a fatwa.
Marketing-claims framing. When we describe the Service in marketing or in product as "Sharia-compliant", we are describing the platform-level constraint that non-compliant assets are not supported; we are not asserting certification by a fatwa board (none is engaged as of the date of these Terms). Users seeking certification-grade assurance should consult their own qualified Islamic scholar.
Cross-border transfer disclosure. Personal data primarily resides on self-hosted infrastructure operated by the Operator in Kuwait. Sub-processors in the US receive subsets of your data via the EU-US Data Privacy Framework (where the sub-processor is certified) or Standard Contractual Clauses, supplemented for Saudi-resident users by Saudi-form SCCs and written risk assessments per the SDAIA Cross-Border Transfer Guideline. See the Privacy Policy for detail.
Saudi-specific complaint route. Saudi-resident users may file complaints about our handling of their personal data with SDAIA (the Saudi Data & AI Authority). Our internal contact for data-subject requests is in §22.

19.2 European Union and European Economic Area (EU/EEA)

Lawful bases. Our processing of your personal data relies on the lawful bases described in the Privacy Policy (typically: performance of these Terms; legitimate interests; consent for specific opt-in features). You have the rights granted by the GDPR — access, rectification, erasure, restriction, portability, objection, and the right not to be subject to solely automated decision-making with legal or similarly significant effects (in our paper-beta the Service does not perform such decision-making about you).
Withdrawing consent. Where consent is the basis of processing (for example, certain optional features), you may withdraw it at any time without affecting the lawfulness of processing carried out before the withdrawal.
Cross-border transfers. Personal data primarily resides on self-hosted infrastructure operated by the Operator in Kuwait, which is not currently the subject of an EU adequacy decision; the paper-beta does not target EU/EEA residents. Transfers to sub-processors (in the US and to Cloudflare's edge network) rely on the EU-US Data Privacy Framework (where the sub-processor is DPF-certified) or on Standard Contractual Clauses, and appropriate Article 46 safeguards for the Kuwait store will be in place before any EU/EEA availability. See the Privacy Policy.
Statutory rights — Consumer Rights. Nothing in these Terms limits any statutory right you have as a consumer that cannot be waived under applicable EU or member-state law (including non-waivable rights of redress against representative-proceeding waivers, see §18.2).
EU AI Act transparency (Article 50). Our AI-assisted features are designed to meet the applicable Article 50 transparency obligations when they apply (from 2 August 2026): you are informed when you interact with an AI feature, and AI-generated content surfaced to you (where applicable) is labelled.
MyData / DSAR. Data-subject requests are handled per the Privacy Policy.

19.3 United Kingdom

UK GDPR + DPA 2018. We aim to handle UK-resident personal data in line with the UK GDPR and the Data Protection Act 2018, and will appoint a UK Article 27 representative before any UK expansion. You have the rights granted by the UK GDPR — access, rectification, erasure, restriction, portability, objection, and complaint to the Information Commissioner's Office (ICO).
UK Representative (forward). If our processing of UK-resident personal data becomes regular, we will appoint a UK Representative under Article 27 UK GDPR and publish the contact details in the Privacy Policy.
PECR (cookies). Our cookie practice is described in the Cookie Policy. The Service today sets only strictly-necessary cookies (session, routing); if we activate first-party behavioural analytics tooling for UK users in the future, we will assess and disclose the basis (consent or a narrow exemption) before activation, in line with current ICO guidance.
Financial-promotion perimeter (FSMA s.21 / FPO). Snipefinity does not offer regulated investment activities in the UK, is not authorised by the Financial Conduct Authority, and does not direct invitations or inducements to engage in investment activity at UK residents. If you reside in the UK, the Service is made available to you on the basis that you have sought it out (rather than been targeted), and Snipefinity makes no UK-specific financial promotion. We intend to operate and present the Service in a manner consistent with the framing in Article 12 of the Financial Promotion Order ("communications directed only at persons outside the United Kingdom"); a more specific FPO-based posture, including any procedural systems to prevent UK-resident engagement, will be confirmed in connection with the operator's incorporation and operational geo-controls.
Consumer Rights Act 2015. Nothing in these Terms limits any non-waivable consumer right you have under the Consumer Rights Act 2015 or other UK statutory protection.

19.4 United States

Not investment advice; not a broker-dealer; not an investment adviser. Snipefinity is not registered with the U.S. Securities and Exchange Commission or with any state securities regulator as an investment adviser or broker-dealer. All trade intents emitted via Snipefinity are self-directed (see §7.4); Snipefinity does not make personalised recommendations and does not act as a fiduciary. Nothing in the Service is investment advice or a recommendation; the Service is informational only. To the extent the foregoing implicates the SEC investment-adviser perimeter, the self-directed framing is intended to fall outside the perimeter; this is a structural framing, not a regulatory determination.
CCPA / CPRA and state patchwork. Your privacy rights — including the right to know, the right to delete, the right to correct, the right to opt out of "sale" or "sharing" (note: we do not sell or share personal data for cross-context behavioural advertising), and the right to limit use and disclosure of sensitive personal information — are described in the Privacy Policy. We detect and respect the Global Privacy Control (GPC) as described in the Privacy Policy.
Eligibility for US brokers. Some brokers we support (for example, certain US broker-dealers) may serve U.S. residents only. If your country of residence is non-US, you must not connect a US-only broker. Conversely, you are responsible for confirming your broker's eligibility rules in your state of residence.
State law. Disputes brought by a U.S. resident under U.S. consumer-protection or state privacy law are addressed in the Privacy Policy and in the Privacy Policy's state-specific notices.
No tax advice. Tax consequences of trading in your broker account are between you, your broker, and your tax adviser (see also §13.2).

19.5 UAE-specific items

Broker-product age. Some broker products and account types in the UAE have a higher minimum age (typically 21). You must satisfy your broker's age requirement in addition to Snipefinity's 18+ minimum (see §3.1).
Marketing-claims framing. UAE / DFSA / FSRA / SCA marketing standards may apply to descriptions of the Service as "Sharia-compliant"; the framing in §19.1 ("Marketing-claims framing") applies.

19.6 Other jurisdictions

If you reside in a jurisdiction not specifically addressed by these addenda, applicable local consumer-protection and data-protection laws may still grant you rights that cannot be waived. Nothing in these Terms limits those rights.

20. Programmatic and agent access

Programmatic and agent access to the Service (for example, 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, it will be governed by additional terms published at that time, and any action taken under your credentials by any agent or automated system you authorise will be treated as your own action under these Terms.

21. Forward-clauses

The following are changes we have signalled but that are not in effect during the private beta. They are listed so that you have a single map of what may change.

Incorporation of the operating entity. Snipefinity is currently unincorporated (see sections 1, 2, and 22). On incorporation, these Terms will be amended to identify the entity, its registered office, the governing law, and the venue. The amendment will be published before, or at the time of, incorporation.
Live-trading enablement. Live trading is not available during the beta. A separate future enablement step, with additional verification, will activate live signal routing for eligible accounts. Before then, these Terms will be amended to match actual platform behaviour where needed (see section 17).
Paid plans. Snipefinity may introduce paid plans after the beta (see section 11). Prices and terms will be presented before they apply.

22. Contact and Data Protection Officer

Operator: Snipefinity, currently operated as an unincorporated project by Ahmad Alibrahim, based in Kuwait. Formal incorporation will be undertaken in connection with future funding or live-trading enablement; these Terms will be updated accordingly (see §17.4).
General contact and support: support@snipefinity.com.
Legal / contracts contact: legal@snipefinity.com.
Data-subject requests (privacy): privacy@snipefinity.com. Detail in the Privacy Policy.
Data Protection Officer (DPO) contact: the operator currently serves as the DPO contact pending headcount sufficient to designate a separate DPO. DPO designation will be revisited upon incorporation.
SnipeRoute (sister service) — contact for SnipeRoute-side data: privacy@sniperoute.io.
Saudi-resident users' complaint route to regulator: SDAIA — Saudi Data & AI Authority (National Data Governance Platform).
EU/EEA-resident users' complaint route to regulator: the data-protection authority in your member state of residence.
UK-resident users' complaint route to regulator: Information Commissioner's Office (ICO).
California-resident users' complaint route: the California Privacy Protection Agency (CPPA).
EU Digital Services Act (DSA) point of contact (where applicable, on launch): an Article 11 DSA point of contact will be designated if and when the Service is offered to EU users, with the Article-19 micro-enterprise carve-out preserved where applicable.