Privacy Policy

FennEdge provides source-linked ticker research and a separate workspace for reviewing completed trading records. This Policy explains how we handle personal information when you use fennedge.ai and related FennEdge products and services (the “Services”). In this Policy, “FennEdge,” “we,” “us,” and “our” refer to the service and its operator.

By using the Services, you acknowledge the practices described here. If you do not agree, please do not use the Services.

Trader quick answers

• Are my trades public?
  No. Imported executions, broker connections, notes, searches, chats, and personal performance context are scoped to your verified account. They are kept separate from reusable public ticker intelligence.
• Does FennEdge place trades?
  No. FennEdge does not execute orders, hold brokerage assets, or ask for a brokerage password. A supported broker connection may use a separate credential or token presented as read-only.
• Do you sell personal information?
  We do not sell personal information for money. Outside the EEA, UK and Switzerland, our public website shares advertising signals with the website analytics service we use by default, which some US state laws treat as “sharing” or targeted advertising. You can opt out at any time with Cookie settings, and we honour Global Privacy Control (see section 6.1).
• Can FennEdge AI read my trades?
  Only after you allow it in the App or on the website, and only to answer your own questions. You can turn it off at any time with the AI data permission in your account settings. FennEdge staff do not have access to your saved AI conversations without your consent, except where required by law.
• Does FennEdge train AI on my data?
  No. FennEdge never uses your data to train AI models.
• Can public market data be wrong or late?
  Yes. Public filings, prices, company facts, and third-party feeds may be delayed, incomplete, corrected, or unavailable. FennEdge shows sources, timing, conflicts, and unknowns where supported.
• How do I request deletion?
  Use the privacy or account controls made available within the Services. Security records, legal holds, backups, and mandatory records may follow a different schedule.

1. Information we collect

1.1 Account and access information

When you create an account or sign in, we may receive an account identifier, name, email address, profile image, authentication status, and related security information from our sign-in provider, Sign in with Google, or another login method we make available. We may also collect invitation-code redemption and product-admission records.

1.2 Workspace and research content

We collect the searches, watchlists, notes, daily-workspace state, saved preferences, prompts, chat messages, uploaded files, and other content you choose to provide. We also process the responses, summaries, citations, and other outputs returned to you. Private workspace content is associated with your verified account so the Services can save and restore it.

1.3 Brokerage and trading information

If you connect a supported broker or trade-reporting service, we may collect the connection type, account identifiers, connection status, encrypted access credentials or tokens, token hints, sync dates, order and execution records, fees, symbols, quantities, prices, timestamps, and derived trading statistics. Supported connections are intended to be read-only. We do not need your brokerage password and do not use a broker connection to place orders.

We may normalise fills into trade episodes and derive private context such as entry windows, holding periods, realised results, trade styles, and data-quality warnings. Derived values can be incomplete or incorrect when source records are missing, duplicated, delayed, denominated in different currencies, or later corrected.

1.4 AI inputs and outputs

When you use FennEdge AI, such as Ask FennEdge, AI ticker research and Journal AI reviews, we process your question, the relevant public evidence, and the conversation it belongs to. FennEdge AI reads your own private data (imported trades and executions, positions, P&L and performance, fees, and your Journal reviews and notes) only after you allow it in the App or on the website, and only to answer your own questions. You can turn this off at any time: on the website under Account settings → AI data permission, or in the App under Account → Preferences → AI data permission. One permission covers both the website and the App, and AI stops reading your private data from the next answer. Your AI conversations are saved with your account. FennEdge staff and administrators do not have access to their contents without your consent, except where required by law; FennEdge AI may process them to answer you. Trade Log statistics are calculated from your imported records, not generated by AI. Model outputs can contain errors and should be independently reviewed.

1.5 Device, usage, and security information

We may collect browser type, device and operating-system information, language and region settings, IP address, approximate location derived from IP, request timing, feature activity, session and installation identifiers, error events, rate-limit events, and security logs. We design application logs to exclude authentication tokens, raw request bodies, questions, private notes, and model responses, but support material you deliberately submit may contain information you choose to include.

For signed-in users, FennEdge records first-party page visits, broad visit-duration buckets, feature-use events and clicks on interface controls. Records use predefined route templates and categories, including allowlisted public page parameters (such as a stock page’s ticker, a date or a tool), subviews and the previous page; they never include arbitrary URLs or query strings. Control identifiers and short normalized labels omit numbers and monetary values. Each record also stores the IP address of the request and the approximate location derived from it (country, region and city), used for security and product analysis. These records never include entered search terms, private holdings, amounts, prices, AI conversations or trading contents. They are kept for up to 90 days, are visible only to authorized FennEdge staff, and do not prove that a task was completed, that a user was online, or that a payment was made. You can turn off behavior collection in the website's account settings or in App → Account → Privacy; the setting syncs between the website and the app. Sign-in and registration security records, including their IP address and approximate location, are kept for the same 90 days even when behavior collection is off.

Separately from the website analytics service we use (section 6.1), we keep our own first-party, aggregate visit counts for public pages, without cookies and without sending anything to third parties. When a signed-out visitor opens a public page, our server combines the connection's IP address and browser type with a random value that changes every day, uses the result only to count each visitor once that day, and keeps only daily totals by landing page and campaign source. The IP address and browser type are not stored, and the daily values are deleted after the day ends. On a public page, your browser also keeps a first-visit note in local storage (campaign tags from the link, the referring site's domain only, and the landing page) for up to 90 days; if you then create an account, we store that note with your new account to understand which pages and campaigns lead to sign-ups. Neither is collected when your browser sends Do Not Track or Global Privacy Control, or when you have chosen Reject in Cookie settings.

1.6 Public market and issuer information

FennEdge processes public or licensed information such as SEC filings, issuer facts, prices, volume, corporate actions, market-status information, and source URLs. This information is generally not personal information about you, although public filings can include information about officers, directors, reporting persons, or other individuals.

1.7 Support and communications

If you contact us, we collect your message, contact details, attachments, and the records needed to investigate and respond. Please do not send brokerage passwords, full access tokens, or unnecessary sensitive information in support messages.

2. How we collect information

We collect information:

• directly from you when you sign in, configure a workspace, connect a supported service, upload information, ask a question, or contact us;
• automatically when your browser or device communicates with the Services;
• from authentication, hosting, database, model, security, and other service providers acting for us;
• from a broker or trade-reporting service you direct us to connect; and
• from public agencies, exchanges, issuer websites, market-data services, and other evidence sources.

3. How we use personal information

We use personal information to:

• authenticate users, manage invitations, and protect account access;
• provide source-linked ticker research, private workspaces, research chat, broker sync, and retrospective trade-history analysis;
• keep public ticker research separate from user-private notes, positions, executions, and performance;
• operate, debug, secure, measure, and improve the Services;
• prevent abuse, fraud, unauthorised access, and attempts to bypass product or source limits;
• respond to support, privacy, security, and legal requests;
• send important account, security, product, Terms, or policy notices; and
• comply with law and enforce our agreements.

4. Legal bases for processing

If you are in the European Economic Area or United Kingdom, our legal bases may include:

• Contract: processing needed to provide the features you request and manage your account.
• Legitimate interests: security, support, service reliability, fraud prevention, and proportionate product analysis where those interests are not overridden by your rights.
• Legal obligation: records and disclosures required by applicable law.
• Consent: optional processing for which we specifically ask permission, such as the AI data permission described in section 1.4. You may withdraw consent for future processing.

5. Private and public data

5.1 Public ticker intelligence

Reusable issuer, filing, and market snapshots may be shared across users because they come from public or licensed sources. We label source links, timing, data basis, and known gaps where supported. Shared ticker snapshots are never built from or personalised with private trading records, positions, account size, risk tolerance, or performance. When you turn on the AI data permission (section 1.4), AI answers in your own conversations may also use your private data; this does not change what other users see.

5.2 User-private context

Your notes, chats, workspace state, broker connections, executions, and personal trading analysis are kept in an account-scoped data boundary derived from your verified sign-in session. We do not trust a browser-supplied user ID to decide access.

5.3 Model processing

To produce an answer you request, we and our processors send your question, the relevant public evidence and the conversation it belongs to through our model gateway to the model providers that generate answers. Your private trading data and notes are included only while the AI data permission described in section 1.4 is on. FennEdge never uses your data to train AI models. This is FennEdge's own commitment.

6. Cookies and local storage

We use cookies, session tokens, and similar technologies that are necessary to sign you in, maintain security, prevent abuse, and provide the Services. The web application also uses local storage and browser caches for theme, language, drafts, interface state, and short-lived task receipts. Some private workspace state is stored server-side so it can follow your verified account.

Disabling essential storage may prevent authentication or core features from working.

6.1 Website analytics and advertising measurement

On public pages of fennedge.ai, such as the home page, pricing, tools, learning and glossary pages, and public stock pages, we use an analytics service to understand how the website is used and to measure our marketing (in this section, “the website analytics service we use”). Analytics is not used in Atlas, on profile, sign-in or gift-redemption pages, or on individual Journal pages such as trades, fees and connections. A few public addresses (for example Scanner, Research, Desk, Journal and stock pages) also open the signed-in workspace; on those addresses analytics records only the page address and title, never workspace content, searches or trading records.

The defaults depend on your region. The website analytics service we use applies them from its own approximate location of your connection. As a fallback, when you visit a public page without a saved choice, your browser also asks our server whether your region requires consent. The server derives a country from your connection for that request only and returns a yes/no answer. The result is not stored, and our application does not record the country or your IP address for this check.

• European Economic Area, United Kingdom and Switzerland: analytics storage and the advertising signals (advertising storage, advertising user data and advertising personalisation) are denied until you choose. On your first visit a Cookie settings panel asks you, with Reject and Accept offered equally. Before you choose, and after you reject, the website analytics service we use still receives limited measurement pings without cookies: for example that a page was viewed, with the page address and title, and the standard technical information that browsers send, such as IP address and browser type. These pings set no cookies and store no identifier on your device. Accept allows analytics cookies and the advertising signals; Analytics only allows analytics cookies without the advertising signals. If you chose Accept before the advertising signals were offered, that choice covers analytics only, and we ask you once more.
• Other regions: analytics cookies and the advertising signals are on by default and no prompt is shown. You can turn off the advertising signals (Analytics only) or both (Reject) at any time with Cookie settings.

Advertising signals. When the advertising signals are allowed, the website analytics service we use may set advertising cookies (such as _gcl_au), may combine visits with information about people signed in to that service's own accounts to produce cross-device and demographic reports, and may use the data for advertising measurement and ad personalisation under its own terms. Some US state privacy laws treat this as “sharing” personal information for cross-context behavioural advertising, or as targeted advertising. When the advertising signals are denied, advertising data in analytics requests is redacted.

Opting out and Global Privacy Control. You can opt out of this sharing and of targeted advertising at any time with Cookie settings: choose Analytics only or Reject. If your browser sends a Global Privacy Control signal, we treat it as a request to opt out of sale, sharing and targeted advertising: the advertising signals stay denied on that browser, even if you choose Accept, and analytics continues unless you choose Reject.

Signed-in visitors and events. When you are signed in and analytics cookies are allowed, we send the website analytics service we use a pseudonymous identifier derived from your account with a one-way hash, so that your visits from different devices can be counted together. We never send your name, email address or sign-in account identifier. We also send events with predefined names and categories, such as signing up, signing in, starting a checkout, a completed subscription purchase (plan, billing period, the amount charged and currency, with a random order reference), the type of broker you connected, and use of features such as Scanner, Desk, replays, sharing or AI chat. Events never include search terms, trade details, amounts from your trading records, AI conversations, page query strings or fragments. An event from a page that is not measured, such as a sign-in or a broker connection, waits in your browser's session storage for up to 30 minutes and is sent with your next public page view.

A choice you make (Accept, Analytics only or Reject) is saved in your browser's local storage for up to 180 days and takes precedence over the regional default. You can change or withdraw it at any time with the Cookie settings link in the footer of every page, or the Cookie settings button in this section; the change applies immediately, without reloading the page. Rejecting stops analytics and advertising cookies and removes those we can clear on this site; the limited cookieless measurement pings described above continue. Choosing Analytics only removes the advertising cookies we can clear on this site.

In short: in the EEA, UK and Switzerland, before you consent and after you reject, the website analytics service we use receives only limited cookieless measurement pings and sets no cookies, and the advertising signals stay denied unless you choose Accept. Elsewhere, analytics cookies and the advertising signals are on by default; Global Privacy Control or Cookie settings turns the advertising signals off. You can change your choice at any time with Cookie settings in the footer.

When analytics cookies are allowed, our third-party analytics service sets first-party analytics cookies (such as _ga and _ga_*) and receives the page address without query strings or fragments, the page title, the referring site's origin only (not its full address), and standard technical information that browsers send, such as IP address, browser and device type. Event-level analytics data is kept by that service for up to 14 months. We use these reports to measure and improve the website and our marketing.

7. Storage and retention

We retain information only while it is reasonably needed for the disclosed purpose, security, disputes, or law. In general:

• Account and admission records are kept while the account is active and for a limited period after closure where needed for recovery, security, disputes, or legal obligations.
• Workspace, chat, notes, and private trading records are kept while associated with your active account or until you delete them through an available control, subject to backups and legal exceptions.
• Encrypted broker credentials are kept only while the related connection remains active or while needed to complete a user-requested disconnection and security process.
• Public ticker snapshots may be retained and reused because they are not private account content, but source and freshness limits still apply.
• Support records are kept until the matter is closed and no longer reasonably needed for follow-up, security, disputes, or law.
• Error, audit, and security logs are kept for the period needed to investigate reliability, fraud, abuse, or security events and are then deleted or de-identified.

Encrypted backups may retain information until the published schedule completes. Information subject to a legal hold, fraud-prevention need, or mandatory recordkeeping may be kept longer.

8. How we share information

We do not sell personal information for money. We do not share it for cross-context behavioural advertising, except for the advertising signals on our public website described in section 6.1, which you can turn off with Cookie settings or Global Privacy Control. We may disclose information to:

• Service providers for authentication, hosting, databases, model inference (routed through our model gateway; see section 5.3), email, security, support, and website analytics, restricted to providing services to us, except that the website analytics service we use may also use the advertising signals described in section 6.1 under its own terms where they are allowed.
• Connected services such as a broker or trade-reporting provider when you direct us to establish or operate a connection.
• Data-source providers when a request is needed to retrieve or refresh public or licensed evidence.
• Authorities or affected parties where required by law or reasonably necessary to protect rights, safety, property, users, or the Services.
• Transaction counterparties in a merger, financing, reorganisation, bankruptcy, acquisition, or sale of assets, subject to appropriate protections.
• Others at your direction when you choose to export, copy, connect, or share information.

We may use and disclose aggregated or de-identified information that cannot reasonably identify you.

9. Security

We use reasonable technical and organisational safeguards, including encrypted network transport, access controls, verified session boundaries, server-side secret handling, encrypted storage for supported broker credentials, user-scoped database access, rate limits, and security logging. No internet transmission, service, or storage system is completely secure, and we cannot guarantee absolute security.

If you believe your account or a connected credential has been compromised, revoke the credential with its issuer where possible and contact us promptly.

10. Your rights

Depending on where you live, you may have rights to access, correct, delete, restrict, or receive a portable copy of personal information; object to certain processing; withdraw consent; appeal a privacy decision; or complain to a regulator. Applicable exceptions may allow or require us to keep certain records.

Submit a request through the privacy, account, or support controls made available within the Services. We may verify your identity and authority before acting. We will respond within the period required by applicable law.

California residents may also request the categories, sources, purposes, and recipients of covered personal information. We do not sell California residents' personal information for money. The advertising signals on our public website described in section 6.1 may be “sharing” for cross-context behavioural advertising under California law. You can opt out with Cookie settings (Analytics only or Reject), and we honour Global Privacy Control as a valid opt-out request. Residents of other US states with similar laws, such as Colorado, Connecticut, Virginia, Texas and Oregon, can opt out of targeted advertising in the same ways. We do not unlawfully discriminate against a person for exercising privacy rights.

11. International data transfers

We and our service providers may process information in countries other than the country where you live. Where applicable law requires a transfer mechanism, we use recognised safeguards such as adequacy decisions, Standard Contractual Clauses, or another legally recognised transfer mechanism.

12. Children's privacy

FennEdge is intended for adults who can legally manage their own trading and account decisions. You must be at least 18 years old and legally capable of entering these Terms. We do not knowingly collect personal information from children. If you believe a child has provided information, contact us so we can investigate and delete it where required.

13. Changes to this Policy

We may update this Policy as the Services, providers, or law change. We post the revised Policy on this page with a new effective date. When a change materially affects how we use personal information, we will also notify you by email or another reasonable method, such as a message where you sign in, unless a change must take effect sooner for legal, security, or urgent operational reasons. We do not show a recurring banner on the website for policy updates. Where the law requires your consent to a change, we will ask for it.

14. How to contact us

For questions, complaints, or privacy requests, email legal@fennedge.com.

For privacy and data-protection purposes, the operator of FennEdge is the controller responsible for personal information processed to provide the Services.

If you are in the EEA or UK and are not satisfied with our response, you may complain to your local data-protection supervisory authority.