Privacy Policy

What information we collect

The MVP is designed so you can use company analysis without creating an account.

We do not collect names, email addresses, financial account details, portfolio holdings, or passwords through the product UI.

• Legal acknowledgement: when you agree to the Terms, Privacy Policy, and Disclaimer, we store an anonymous consent record (timestamp, document versions, consent type, and a random identifier).
• Product analytics (included when you agree to the Terms; you may withdraw later via Privacy choices): anonymous usage events described below.
• Company analysis requests: the ticker and market you ask us to analyse are sent to our backend so scores can be generated.
• Optional Investor View: if you share how you feel about a company, we store an anonymous perception response (sentiment, business trend, valuation lean, confidence, optional short comment, and a random session/visitor id). No account is required. Individual comments are not shown publicly — only aggregated totals above sample thresholds.
• Optional AI Coach messages: if you use AI Coach, your questions and the packaged educational analysis context are sent to our backend, and may be sent to a language-model provider when that feature is configured.

Information automatically collected

When you agree to the Terms, the browser may send anonymous product-analytics events to our backend. Those events can include:

• A random visitor identifier stored in local storage (not your name).
• A random session identifier stored in session storage.
• Page path (for example /about or /coach).
• Selected market (ASX or US) and searched ticker symbols.
• Coarse device class (mobile / tablet / desktop) and browser family derived from the user agent.
• A coarse region hint derived from the browser timezone (for example Australia/). This is not IP geolocation.

IP address and device information

Application code does not store IP addresses in the product analytics or consent databases.

Web servers, hosting providers, and reverse proxies may record IP addresses in operational access logs. This policy does not claim that no IP address is ever processed at the infrastructure layer.

Pages viewed

With analytics enabled, we record page_view events with the URL path so we can see which screens are used.

Search activity and company / ticker searches

With analytics enabled, we record when a company is searched and when an analysis or comparison is viewed, including ticker symbols and (where available) a company name or sector label returned by the analysis.

Separately, analysing a company always sends the ticker to our backend — that is required for the educational analysis to run, whether or not analytics is enabled.

Usage analytics

Product analytics exist so the operator can learn which lessons, scores, and sections people open — not to identify individuals.

Events can include: session start/end, scroll depth milestones, market selection, score clicks, education content opened, metric explanations opened, section opened, comparison performed, AI Coach usage, legal/disclaimer page views, and (when such links exist) external company-website clicks.

Agreeing to the Terms includes this analytics. You can withdraw it later from Privacy choices in the footer.

Cookies

The MVP does not set third-party advertising cookies.

If Google Analytics 4 is configured, and only after you agree to product analytics, the site may also send page views and the same feature events to Google. That uses Google’s own cookies. It does not include your name, email, quiz answers, or financial account details. Visitors who decline analytics, or who block cookies, are not sent to Google Analytics.

After you acknowledge the legal documents, the browser may set a first-party cookie named mic_onboarding_seen. It only remembers whether you completed or dismissed the product tour invitation. It is not an analytics identifier and does not store your name, email, questions, or company analysis.

The browser’s local storage and session storage are used for essential product preferences (theme, selected market, logo cache) and, after acknowledgement, the consent record. Analytics identifiers are written when analytics is enabled (by default when you agree to the Terms).

Purpose of collecting data

We use the information above to:

• Provide the educational analysis you requested.
• Remember that you acknowledged the current document versions.
• Remember whether you completed or dismissed the product tour invitation (first-party onboarding cookie only).
• Improve which educational content and product areas need more time and clarity (when analytics is enabled).
• Build anonymous, aggregated Investor View perception stats (optional submissions only).
• Operate founder-level product metrics on an internal dashboard (analytics events only; admin-gated).

Third-party analytics providers

Product analytics stay on our own backend unless Google Analytics 4 is explicitly configured. When it is configured, the same consented events may also be sent to Google Analytics. They are not sent to Mixpanel, Amplitude, or an advertising network.

The frontend uses an AnalyticsService abstraction. Turning on Google Analytics still requires analytics consent and does not start before that consent.

Data storage

Consent records, analytics events, and Investor View responses are stored on the application backend (SQLite files under the server data directory in the current architecture).

Company analysis results are generated on demand and are not stored as a user history in the MVP (there is no login or saved portfolio).

Data retention

Analytics events and consent records remain in the backend database until the operator deletes them. Browser storage remains until you clear site data or withdraw analytics consent (analytics identifiers).

Security

We use standard web transport (HTTPS in production deployments) and keep API keys on the server, not in the public frontend.

User rights

You can change analytics via Privacy choices in the footer, and clear site data in your browser. Because there is no account, we cannot look up a person by name or email.

How users can contact us

Operator: Javier Navarrete

Privacy contact: luisjavito21@gmail.com

Third-party services

When you analyse a company, our backend requests financial data from Yahoo Finance using the ticker you entered.

When you use AI Coach and a model key is configured, conversation content and educational analysis context may be processed by OpenAI.

Those providers have their own terms and privacy policies. We do not control how they independently process data.

International data transfers

Yahoo Finance and OpenAI may process data outside Australia.

Changes to this privacy policy

This policy is version 1.1. Substantial changes increment the version. Users who acknowledged an older version can be asked to acknowledge the new one.