TickerForge

Appearance

Privacy Policy ​

Last updated: 05 July 2026

This Privacy Policy explains how TickerForge collects, uses, and protects data when you use the website, widgets, Telegram bot workflows, product emails, paid subscriptions, and related services.

TickerForge is operated by Anton Tkach, trading as TickerForge.

Contact: privacy@ticker-forge.com

1. What We Collect ​

We collect data needed to run TickerForge, improve product workflows, and provide requested follow-up.

Data You Provide ​

  • Email address when you request product updates, reports, or support.
  • Product intent, such as the stock, portfolio, screener, or market workflow you selected.
  • Tickers, holdings, cash amounts, or portfolio summaries that you explicitly submit to a widget or bot workflow.
  • Support messages or feedback you choose to send.

Website and Widget Data ​

We may collect:

  • anonymous user id and session id;
  • page path, source page, referrer, and UTM parameters;
  • widget usage events such as widget view, widget start, stock report viewed, portfolio report viewed, intent selected, email submitted, Telegram continuation clicked, article CTA clicks, internal link clicks, pricing CTA clicks, and scroll depth;
  • plan context and product path, such as Free, Standard payment interest, or Pro payment interest;
  • ticker or widget type when needed to understand product usage.

Telegram Connection Data ​

If you continue from the website to Telegram, we may store Telegram continuation/linking identifiers, selected intent, timestamps, and the Telegram account information made available by Telegram. We use this to connect the web request to the bot flow you opened.

Payment Metadata ​

When payments are enabled, we may store limited payment metadata from a payment processor, reseller, merchant-of-record provider, or Telegram Stars flow, such as plan tier, subscription status, customer or subscription identifiers, payment status, renewal/cancellation timestamps, and checkout event metadata needed for access control and support.

TickerForge does not store card numbers.

2. What We Do Not Send to GA4 or Meta ​

TickerForge does not send the following to Google Analytics, Meta Pixel, or advertising analytics:

  • email addresses;
  • raw Telegram IDs;
  • raw portfolio holdings;
  • raw private prompts or free-form private inputs;
  • raw continuation codes;
  • broker credentials, account numbers, or identity documents.

Analytics events use aggregate or limited product metadata such as event names, page paths, widget type, selected intent category, plan context, and UTM values.

3. Cookies, GA4, and Meta Pixel ​

TickerForge uses a cookie/analytics consent banner. Optional Google Analytics and Meta Pixel tracking should run only after consent where required.

These tools help us understand site usage, campaign performance, widget interactions, and product funnels. You can accept or reject optional analytics from the cookie banner.

4. Product Email ​

TickerForge may use Resend to send product emails, such as report-ready messages, smart alert updates, product follow-up, or support replies.

Email is used for the purpose requested by the user or for product communications related to that request. We do not sell email addresses.

5. Payments ​

When payments are enabled, a third-party payment processor, reseller, merchant-of-record provider, or platform payment flow may process payment, tax, invoicing, subscription management, and refund-related data. That provider's own policies may also apply to checkout and payment handling.

TickerForge stores only the limited payment metadata needed to provide access, support billing, and reconcile subscription status.

6. Portfolio and Widget Inputs ​

If you enter holdings, cash, or portfolio data, TickerForge uses it to generate diagnostics, snapshots, risk checks, stress tests, and related software outputs.

We do not request broker login credentials, account passwords, identity documents, or full brokerage statements in the browser widget flow.

7. How We Use Data ​

We use collected data to:

  • provide software analytics, diagnostics, monitoring, and reports;
  • send requested product emails or Telegram continuation flows;
  • operate subscriptions and paid access;
  • improve website, widget, and bot workflows;
  • detect abuse, debug errors, and maintain security;
  • measure campaign and product funnel performance, subject to consent where required;
  • respond to support requests.

8. Sharing ​

We may share data with service providers needed to operate TickerForge, including hosting providers, database providers, Telegram, Resend, payment processors, Google Analytics, Meta Pixel, and internal analytics/reporting tools.

We do not sell personal data.

9. Retention ​

We keep data only as long as needed for product operation, support, security, analytics, legal compliance, or subscription management.

Portfolio and monitoring data may be kept until deleted, replaced, expired, or no longer needed for the feature. Operational logs may be retained for debugging and security.

10. Your Rights ​

Depending on your jurisdiction, you may have rights to access, correct, delete, restrict, object to processing, export data, or withdraw consent.

To make a request, contact: privacy@ticker-forge.com

11. Security ​

We use reasonable technical and organizational safeguards, including access controls, data minimization, and operational monitoring. No system can be guaranteed 100% secure.

12. Children ​

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

13. Changes ​

We may update this Privacy Policy from time to time. The updated version will be posted on this page.

14. Contact ​

Privacy questions: privacy@ticker-forge.com

Last updated: