This page describes intended production handling for private trading evidence in the current TradeGospel package.
Privacy policy
Your broker evidence should only be used to explain your account.
TradeGospel processes trading history, account context and private reports to produce post-trade diagnosis and improvement tracking. It is operated by Tradegospel Technologies Pvt Ltd, 5th Phase, JP Nagar, Bengaluru, Karnataka - 560078, India.
Uploading broker files does not authorise public identity, public score, advertising use or unrelated model training.
For privacy, support, security or legal questions, contact [email protected]. Jurisdiction: Karnataka, India.
Email, authentication state, sessions, audit records and support metadata keep the account usable and secure.
Jurisdiction, currency, timezone, account type, asset classes and trading styles help TRS interpret evidence safely.
Files may contain trades, balances, fees, timestamps, account identifiers and cash movements.
Generated findings, limitations, evidence receipts and repair cycles are stored as private account history.
Support messages may include broker names, report identifiers and issue descriptions needed to investigate a problem.
Limited logs may be used for abuse prevention, reliability, security investigation and error diagnosis.
Why information is processed
TradeGospel processes information to authenticate users, classify and validate evidence, reconstruct trading activity, generate evidence-linked TRS findings, maintain private report history, operate improvement cycles, prevent abuse, investigate errors and provide support.
Evidence boundaries
Files can include trade history, account references, balances, charges, broker timestamps, contract-note data and cash movements. Evidence is account-scoped and is not published merely because it has been uploaded.
Public credibility requires a separate product flow.
Any future public trader identity, public reliability badge or public score must require separate user authorisation and separate publication controls.
Measurement and consent
This local build does not load marketing analytics, advertising tags or behavioural measurement. Optional analytics, advertising data and personalisation all default to denied and remain disabled until separate owner activation and independent privacy review.
- Only bounded public-page event names and classifications may be proposed.
- Raw trades, account or broker identifiers, credentials, upload names, report text, IP addresses and unrestricted text are prohibited.
- Campaign parameters are classified in memory only. Raw search terms and click identifiers are discarded from the page URL.
- Search Console and Bing access is designed as read-only aggregate reporting; no credentials or production property access are present in this build.
Consent denial is the active state.
No optional event transport exists, no measurement cookie or browser-storage identifier is written and no analytics activation authority is granted by this preparation.
Protected PDF passwords
A document password entered for a locked statement or contract note is intended to be used only while opening the selected document in the processing task. It should not be stored in the database, object storage, dashboard, report or audit history.
Users should never provide broker-login passwords or one-time login codes to TradeGospel support.
Service providers and transfers
Cloud, database, object-storage, monitoring, email and support services may process information on TradeGospel's behalf. Current application services and delivery limits are:
- AWS EC2 hosts the application and processing services in Docker Compose containers. Cloudflare handles the public website edge for tradegospel.com.
- PostgreSQL stores account, consent, evidence metadata, reports and privacy-case records.
- AWS S3 in ap-south-1 stores private evidence and report artifacts outside the public website.
- Cloudflare processes website requests for delivery and edge services. This is separate from the application's optional marketing and advertising features.
- Automated email delivery is currently inactive. The application uses local file-mode messages, which do not establish delivery to an inbox. SMTP and Amazon SES are supported delivery options when separately configured.
- Google OAuth is optional sign-in; Google receives the normal OAuth request and callback data needed to authenticate the user.
- ClamAV scans uploaded broker files before parsing; document processing runs in TradeGospel backend and worker containers.
- Application audit logs and container logs record operational, security and error events, with redaction governed by the configured logging controls.
- Support currently routes to Anmol Garg at [email protected]; no separate support-desk CRM is configured in this release.
- Razorpay TEST and PayPal SANDBOX preparation may process sandbox checkout metadata only; live payments and payment-instrument collection are not enabled.
- Optional analytics, advertising data and personalisation all default to denied and remain disabled until separate owner activation and independent privacy review.
Retention and deletion
The application includes account metadata export, evidence-package deletion and whole-account deletion controls. Whole-account deletion attempts to remove stored evidence and report artifacts before deleting database records, and fails closed if storage deletion cannot be completed.
- Kept while the account is active; removed from primary records during whole-account deletion after storage deletion succeeds, except required security or legal records.
- Consent and privacy-request records are kept as accountability records to prove notices, requests, withdrawals and erasure handling.
- Private evidence files are kept for the account's private reports until the user deletes the evidence package or account; primary storage deletion must succeed before database deletion.
- Generated reports and analysis history are kept with the account until the user deletes report evidence or the account, subject to backup expiry.
- Upload scan and processing logs are kept for reliability, abuse prevention and security review; release artifacts are retained for 90 days and WAF logs for 365 days where configured.
- Support and grievance records are kept until the case is closed and then retained as accountability records as needed for legal, security and dispute handling.
- Payment test and sandbox records are kept as sandbox audit records; live billing records are not created because live payments are not enabled.
- Operational logs are minimized, avoid broker secrets, and are retained according to configured platform log policies; AWS WAF logs are configured for 365 days.
- Backups and restore points are not erased instantly during primary deletion; backup-erasure evidence records the expiry boundary before an erasure certificate is treated as complete.
Your choices
- Choose which accounts and records to upload.
- Correct account context before analysis.
- Delete evidence packages where product controls allow it.
- Request whole-account deletion.
- Ask for support review when evidence reconstruction looks wrong.
The responsible legal entity is Tradegospel Technologies Pvt Ltd. Grievance and privacy requests are handled by Anmol Garg at [email protected]. TradeGospel will acknowledge privacy and grievance requests at [email protected] and target a final response within 30 days unless identity verification, user delay or law requires more time.
TradeGospel is intended for users who are 18 or older. Users under 18 are not permitted to create an account or use the platform.