Privacy Policy

Last updated: 08 February 2026

This Privacy Policy explains how TickerForge ("we", "us", "our") collects, uses, and protects data when you use:

The TickerForge website (ticker-forge.com),
The TickerForge Telegram Bot, and
Any services or pages that link to this Policy.

By using TickerForge, you agree to the practices described here.

1) Who We Are

Data Controller: TickerForge
Contact: privacy@ticker-forge.com

TickerForge provides portfolio analytics, diagnostics, and educational investing tools, primarily through Telegram.

2) What Data We Collect

We collect only what is necessary to operate and improve the service.

2.1 Data you provide voluntarily

Depending on what you use, you may provide:

Email address (e.g., support requests)
Telegram display name / username (if available from Telegram)
Feedback you submit (messages, bug reports, feature requests)

2.2 Data collected automatically

When you use the Telegram bot or website, we may store:

Telegram user ID (required to operate the bot)
Basic usage events (e.g., which feature/menu was used)
Technical metadata for reliability and security (e.g., timestamps, error logs)
Website analytics/cookies (if enabled on the site; see Cookie Policy if applicable)

2.3 Mock trading & portfolio service data

To run portfolio features (watchlists, mock trades, analytics), we may store:

Mock balances and their settings
Mock trades and related performance data
Computed analytics and reports generated by the service

2.4 Data we do not collect

TickerForge does not collect or store:

Your private Telegram chats (beyond direct interactions with the bot)
Credit card numbers (payments are handled by processors)
Identity documents (passport, ID, etc.)
Broker login/passwords or brokerage account credentials

3) Import Privacy (Broker Portfolio Import)

This section applies to the Import Broker Portfolio feature (e.g., /importbalance_request).

3.1 What we collect for import

When you import a portfolio, we store the portfolio data you submit, including:

Tickers
Quantities / position sizes
Side: LONG / SHORT
Cash amount you enter (if asked by the import flow)
Timestamps (import time and snapshot time)
Computed metrics / snapshots, such as portfolio score, risk flags, concentration metrics, stress preview, and other diagnostics derived from the imported portfolio

3.2 What we do not collect for import

We do not collect or store:

Broker login or password
Brokerage account number
Full brokerage statements
Personal identity data (passport, national ID, address) as part of the import process

3.3 Why we store imported data

We store imported portfolio data to:

Generate your reports and diagnostics (snapshot, health score, sector allocation, stress tests)
Show history over time (snapshots)
Help you track improvements and changes in portfolio structure

3.4 Retention for imported data

Imported portfolio data is retained:

Until you delete the balance (recommended default), or
Snapshots are retained according to the current system configuration and may be updated in the future.

If you re-import into the same balance (e.g., Imported), the newest import may replace previous imported holdings depending on how the feature is configured.

3.5 Your control over imported data

You can control your imported data via in-bot actions:

Delete an imported balance (removes associated snapshots and analytics stored for that balance)
Archive a balance (if supported)

Export:

If export is not implemented, do not promise it.
Recommended wording: “Export is not currently available.”
If export is implemented later, this policy will be updated.

3.6 Aggregation / analytics

To improve diagnostics and write educational content, we may compute anonymized aggregate statistics from user interactions (e.g., common portfolio structure issues, concentration patterns, repeated input mistakes).

Important safeguards:

We do not publish user IDs.
We do not publish your individual portfolio or holdings.
Aggregates should be designed to avoid exposing specific tickers tied to a single user.

TickerForge may integrate with social platforms (e.g., Instagram, Pinterest) for the limited purpose of publishing content via API.

We do not:

Read or store private messages from users on those platforms
Collect followers, comments, or audience profile data for targeting
Build advertising profiles based on social platform users

5) Payments

TickerForge may use third-party payment processors (e.g., Stripe, Telegram Stars).

We do not store card details. Payment data is handled by the processor.

We may store limited payment metadata such as:

Plan tier (Free/Standard/Pro)
Subscription status and expiration date
Payment status (success/failure)

6) Why We Use Data

We use collected data to:

Provide the service (reports, analytics, bot operations)
Maintain reliability and security (fraud prevention, error investigation)
Improve features and diagnostics (aggregate analytics, performance tuning)
Respond to support requests

We do not sell personal data.

If applicable, we rely on:

Contract (to deliver the service you request)
Legitimate interests (service reliability, security, product improvement)
Consent (where required for optional features or website analytics)
Legal obligation (where required by law)

8) Data Retention (General)

We keep data only as long as needed to provide the service and operate it safely.

Typical examples:

Telegram bot identifiers: while your account uses the bot
Operational logs: limited time for security and debugging
Portfolio data (mock/import): until deleted by you, unless retention rules are configured

We may share data with service providers necessary to run TickerForge, such as:

Hosting providers (infrastructure)
Telegram (platform)
Payment processors (Stripe, Telegram Stars)

We do not share personal data with advertisers.

10) International Transfers

Your data may be processed in countries outside your own. Where required, we use appropriate safeguards.

11) Your Rights

Depending on your jurisdiction, you may have rights to:

Access your data
Correct inaccurate data
Request deletion
Restrict or object to processing
Data portability (where applicable)
Withdraw consent (where processing is based on consent)

To exercise rights: privacy@ticker-forge.com
We typically respond within 30 days.

12) Children’s Privacy

TickerForge is not intended for users under 16.
We do not knowingly collect data from children under 16.

13) Security

We use reasonable technical and organizational safeguards, such as:

Access controls
Data minimization
Logging and monitoring for abuse prevention

No system is 100% secure, but we aim to protect data using standard best practices.

14) Changes to This Policy

We may update this policy. The “Last updated” date will change when we do.

15) Contact

Email: privacy@ticker-forge.com

Privacy Policy ​

1) Who We Are ​

2) What Data We Collect ​

2.1 Data you provide voluntarily ​

2.2 Data collected automatically ​

2.3 Mock trading & portfolio service data ​

2.4 Data we do not collect ​

3) Import Privacy (Broker Portfolio Import) ​

3.1 What we collect for import ​

3.2 What we do not collect for import ​

3.3 Why we store imported data ​

3.4 Retention for imported data ​

3.5 Your control over imported data ​

3.6 Aggregation / analytics ​

4) Social Media Integrations (Instagram & Pinterest) ​

5) Payments ​

6) Why We Use Data ​

7) Legal Basis for Processing (GDPR) ​

8) Data Retention (General) ​

9) Sharing Data with Third Parties ​

10) International Transfers ​

11) Your Rights ​

12) Children’s Privacy ​

13) Security ​

14) Changes to This Policy ​

15) Contact ​