What you
may and may not.

This policy sits alongside the Terms of Service. It spells out the narrow set of behaviours we do not allow, why, and what enforcement looks like. We aim to enforce sparingly and predictably. Reading this document once is enough.

What you may do

• Connect your own exchange API keys, trade your own funds, keep all PnL.
• Use the automated trigger system, webhooks, and TradingView integration for any lawful trading strategy.
• Run the platform through your own scripts and tooling at the documented rate limits.
• Share screenshots, charts, and trade cards publicly — we provide deliberate share affordances for this.
• Run the platform concurrently with your own custom bots against the same account, provided you understand the collision risks.

What you may not do

1. Market manipulation. Spoofing, layering, wash trading, marking the close, cross-market manipulation, or any activity prohibited by your exchange, jurisdiction, or applicable securities/commodities regulation.
2. Credential abuse. Connecting API keys that do not belong to you. Connecting a key with withdrawal permission. Sharing your account credentials or API keys with third parties.
3. Service abuse. Exceeding published rate limits; circumventing rate limits with multiple accounts; scraping private user data; running denial-of-service patterns against our API or our exchange connectors.
4. Reverse engineering in bad faith. Decompiling or deobfuscating the service with the intent to clone it, replicate non-public algorithms, or extract commercial IP. Security research is welcomed under the security policy.
5. Malicious tooling. Injecting malware, phishing pages, or credential-harvesting UI via any user-supplied content (notes, shared trade cards, referral links). Using the platform as a C2 relay or a money-laundering conduit.
6. Identity fraud. Creating accounts using false personal information, synthetic identities, or compromised IDs. Bypassing sanctions or jurisdictional restrictions — see risk disclosure for the list of restricted regions.
7. Resale and sublicensing. Reselling platform access, running signal-copying businesses that redistribute our output as your own product, or embedding our service into a downstream paid offering without written agreement.
8. Abusive behaviour. Harassing our team or other users via any channel. Spamming referral links in places they are not welcome. Attempting to extract support resources under false premises (e.g. "my friend lost their password").
9. Illegal activity. Any activity that violates the law of your jurisdiction, the law of the jurisdiction where the exchange operates, or applicable international sanctions.

Reporting abuse

If you see behaviour you believe violates this policy, email [email protected] with enough detail to investigate (screenshots, usernames, timestamps). We acknowledge reports within two business days and will not share your identity with the reported party.

Enforcement

Violations are handled on a sliding scale:

• Warning. First-time, low-severity, likely accidental. We contact you, you correct the behaviour, we move on.
• Temporary restriction. Repeat or moderate-severity. We restrict specific features (automation, webhooks, public sharing) for a defined period.
• Account suspension. Serious violations, or refusal to correct behaviour after restriction. Funds on connected exchanges remain yours — we do not hold your money.
• Permanent ban. Fraud, manipulation, criminal use. Reserved for cases with clear evidence. Appealable to [email protected].
• Referral to authorities. When required by law, by court order, or when we believe in good faith that life or property is at immediate risk.

Appeals

Every enforcement decision is appealable. Email [email protected] within 30 days of the action. Appeals are reviewed by someone other than the person who made the original decision. Our response time target is five business days.

Changes

We revise this document when behaviour patterns on the platform require it. Material changes are announced by email and in-app banner at least 14 days before taking effect.

// trust & safety · [email protected] · appeals · [email protected]