01
No brokerage control
SignalShield does not place trades, manage brokerage accounts, or make buy/sell decisions for users.
Security and product boundaries
Clear boundaries around trader discipline data.
SignalShield helps traders organize alert pressure, execution records, cooldowns, locks, and behavior review. It is not a broker, signal seller, trading bot, or financial advice product.
Product safeguards
Know what belongs inside SignalShield—and what does not.
These boundaries describe how SignalShield positions trader discipline workflows, account access, review data, and support.
02
Authenticated app workflows
Customer workflows such as alerts, journal records, cooldowns, locks, and system state belong behind authenticated app access.
03
Discipline data, not signal advice
TradingView alerts and journal records are used for accountability and review. SignalShield does not sell entries, exits, or market predictions.
04
Support without sensitive credentials
Support requests should include the page, action, expected result, and timestamp. Do not send brokerage passwords, API keys, or sensitive financial credentials.
Responsibility split
Account safety also depends on what the user keeps private.
Useful support context
Share enough information to reproduce the problem.
- ✓The SignalShield page involved
- ✓The action you took
- ✓What you expected to happen
- ✓What happened instead
- ✓The approximate timestamp
Keep out of support messages
Do not send sensitive brokerage credentials.
- ×Brokerage passwords
- ×API keys
- ×Sensitive financial credentials
Policy references
Use the policy page that matches the question.
Security boundaries, privacy practices, service terms, and support requests answer different questions. Keep them separate so the relevant policy is easier to find.
Privacy
Data practices
Review the published Privacy Policy for information handling and user choices.
Read privacy policy →
Terms
Service boundaries
Review account responsibility, acceptable use, billing, and trading-risk boundaries.
Read terms →
Support
Account or workflow help
Send the relevant page, action, expected result, actual result, and approximate timestamp.
Contact support →
Need help with account or alert behavior?
Send enough context to investigate without sending sensitive credentials.
Include the page, action, expected result, actual result, and approximate timestamp. Keep brokerage passwords, API keys, and sensitive financial credentials out of support messages.