StratPilot Community Data Notice

1. Purpose

Community Brain is an opt-in, advisory-only shared intelligence layer for StratPilot. It is designed to learn from safe, validated and approved scan and strategy metadata contributed by participating users.

Community Brain may help users compare strategies, understand scanner context, review Top 10 or Top 3 style insights, improve data quality and support future product improvement. It is not a trading authority, broker, financial adviser or order execution system.

2. Advisory-Only Use

Community Brain data is informational and advisory only. It may support analysis, comparison, strategy review, data-quality checks and product improvement.

Community Brain must not:

• place orders;
• enable live trading;
• override user settings;
• bypass user confirmation;
• bypass account, license, API, legal or payment checks;
• control exchange credentials;
• guarantee results; or
• replace the user's own review.

If a user copies, applies or uses a Community Brain suggestion, that is a user-controlled configuration action. The user remains responsible for all resulting settings, decisions, live trading activity and outcomes.

3. Opt-In and Server Control

Community Brain participation is opt-in where required. Contribution and read access depend on current Terms, Privacy/Data Notice, this Community Data Notice, consent versions, legal acceptance and account access decisions.

StratPilot's online services decide current:

• opt-in status;
• consent version;
• contribution permission;
• read access;
• qualification;
• feature availability;
• license/account status;
• support/admin review decisions; and
• access revocation.

The local app must not self-grant Community Brain contribution access, read access or qualification.

4. Data That May Be Used

When a user opts in and StratPilot allows contribution, StratPilot may process approved contribution data such as:

• strategy signatures;
• strategy metadata;
• scanner metadata;
• timeframe and mode;
• matrix counts or matrix units;
• scan/deep scan status;
• rejected or no-trade reasons;
• mock, paper and backtest metrics;
• approved safe performance metrics;
• portfolio return_pct by configured period;
• data-quality status;
• Community Brain access status;
• consent versions;
• app version;
• schema version; and
• idempotency metadata.

Portfolio performance may be submitted only as a percentage value, such as return_pct, for a configured period. Absolute balances and underlying holdings must not be submitted.

5. Data That Must Never Be Shared

Community Brain must never receive:

• raw internal access/API keys;
• license keys or license secrets;
• passwords;
• session/OAuth/reset tokens;
• database passwords;
• .env contents;
• KuCoin API keys, secrets or passphrases;
• exchange credentials of any kind;
• Telegram bot tokens;
• Telegram chat IDs;
• wallet private keys;
• seed phrases;
• absolute balances;
• start values;
• end values;
• holdings;
• wallet addresses;
• order IDs;
• trade IDs;
• raw device identifiers;
• raw logs containing secrets; or
• any other private credential or unsafe raw data.

The app and online service should use approval rules, validation, schema checks, masking and secret scans to reduce the risk of prohibited data being submitted.

6. Community Brain and Live Trading

Community Brain is separated from direct live trading control. It must not directly create exchange orders or use exchange credentials.

Community Brain may provide settings, rankings or context that a user may choose to review or apply. The user remains responsible for checking settings, risk limits, market conditions, strategy assumptions and whether live trading should be used.

7. Aggregation and Product Improvement

Allowed Community Brain data may be used for:

• shared intelligence;
• product improvement;
• anonymized or aggregated statistics;
• strategy quality checks;
• scanner and optimizer improvements;
• matrix unit analytics;
• abuse prevention;
• operational monitoring;
• data-quality analysis; and
• future aggregated marketing summaries where eligibility rules allow it.

Marketing summaries must be aggregated, must not expose individual users or secrets and must include appropriate disclaimers where performance or trading context is referenced.

8. Community Brain Metrics and Marketing Summaries

Community Brain may produce aggregate metrics such as:

• number of opt-in contributors;
• number of contributions;
• matrix units scanned;
• strategy metadata volume;
• Top 10/Top 3 candidate counts;
• aggregated portfolio return percentage by period where allowed;
• scanner/deep scan usage; and
• data-quality coverage.

If performance information is used in marketing summaries, it must be historical, aggregate, appropriately qualified and based on a sufficient sample. It must not imply guaranteed returns or financial advice.

9. Opt-Out and Changes

Users should be able to disable future Community Brain contribution where the feature is available and properly disabled. Opting out should stop future contribution from that point.

Previously processed aggregated or anonymized data may remain unless applicable rules, product policy or a separate deletion process require otherwise.

If the required consent version changes, the app may require renewed acceptance before contribution or access continues.

10. User Responsibility

Users are responsible for deciding whether to opt in, what features to use, whether to apply Community Brain suggestions and whether to use live trading.

Community Brain does not guarantee suitability, profitability, risk reduction, execution or future market performance.

11. Contact

Questions about Community Brain data may be sent to: admin@stratpilot.app

Do not send API keys, exchange credentials, Telegram tokens, license secrets, passwords, wallet keys, seed phrases, .env files or other secrets.