プライバシーポリシー

This Privacy Policy explains how fcontext handles information in the current market research workspace, including account access, browser-stored workspace data, product settings, market research inputs, AI analysis flows, support surfaces, and machine-readable resources.

This policy is scoped to the product currently available in this repository and deployment. If hosted sync, paid subscriptions, production analytics, enterprise support, marketplace integrations, or external authorization flows are added later, this policy may be updated.

Personal Information means information that identifies or can reasonably be linked to an individual, such as email address, display name, account identifiers, device or browser details, request metadata, and support messages.

Workspace Data means tickers, watchlist items, portfolio holdings, search history, model settings, pattern settings, prediction logs, alert preferences, copied page context, prompts, and other product inputs or outputs.

Local Storage means browser storage, cookies, cache, and similar technologies used to keep settings, sessions, history, and workspace data on your device.

Providers means third-party services that may support authentication, market data, news, sentiment, AI analysis, search, company logos, hosting, logging, or notification features.

fcontext handles information needed to provide the current research workspace and account experience.

• Account information, such as email address, display name, session identifiers, magic link events, and Google sign-in identifiers when enabled.
• Workspace inputs, such as searched tickers, selected symbols, watchlist items, portfolio holdings, model settings, pattern settings, alert preferences, and copied page context.
• Research outputs, such as cached predictions, technical-analysis results, market snapshots, news summaries, sentiment results, and AI-generated analysis shown in the product.
• Technical information, such as device/browser details, request metadata, logs, error messages, cookies, and local development configuration needed to run and secure the service.

Information may be collected when you sign in, request a magic link, use Google sign-in if configured, search for a symbol, save a watchlist or portfolio entry, change settings, create alerts, copy page context, run AI analysis, request market data, open support pages, or interact with browser notification controls.

Some information is generated automatically through logs, cookies, session handling, request metadata, error reporting, caching, and browser or device behavior needed to operate the product.

Some information is received from Providers when the workspace fetches quotes, fundamentals, news, social sentiment, calendar events, logos, search results, AI responses, or authentication status.

Several current product features store information in your browser, including watchlists, portfolio holdings, prediction cache, search history, fundamentals cache, and model or pattern preferences. This data remains on the device unless you export it, copy it, clear it, or a future sync feature is added.

Authentication uses cookies and session data through Better Auth. Local development magic links may be printed to the server console or stored temporarily to support developer login flows.

If you use a shared device, private browsing mode, browser extensions, or aggressive cache-clearing settings, your workspace data may be exposed to others on the device or may be deleted unexpectedly.

We use information to operate the workspace, authenticate users, remember settings, display market research views, generate analysis, troubleshoot errors, protect the service, and improve product quality.

We do not use fcontext to provide personalized investment advice. Payment details are handled by Creem; fcontext stores account, subscription, and metered usage records needed to operate plan access.

We may use aggregated or de-identified technical and product information to understand reliability, feature usage, performance, data-provider gaps, and product quality.

• Authenticate users and maintain sessions.
• Load and personalize workspace views, settings, watchlists, portfolios, and alerts.
• Fetch and display Market Data, news, calendar events, and related research context.
• Generate AI Output and prepare agent-ready context when you use those features.
• Debug errors, prevent abuse, protect API routes, and maintain service reliability.
• Communicate about support, account, security, or product changes where applicable.

The workspace may send requests to third-party providers for authentication, market data, company fundamentals, news, social sentiment, economic calendar data, company logos, and AI analysis. Examples in the current product include Better Auth, Google sign-in when configured, AITA Quote or related market-data wrappers, Nasdaq options data, Tradestie/Reddit sentiment feeds, ApeWisdom, logo providers, and configured AI providers.

Those providers may process information according to their own terms and privacy policies. You should review their policies before enabling or relying on those integrations.

Provider availability and identity may vary by deployment and environment variables. Local development environments may log more information to the console than a production deployment.

AI analysis features may send ticker data, market context, news snippets, indicator values, and user prompts to configured AI services. The Connect AI and Agent Skills areas are currently setup and catalog surfaces unless a separate authorization flow is enabled.

If you copy page context into an external AI assistant, you decide what to share and the external assistant's privacy practices apply.

Do not submit secrets, private credentials, regulated personal data, material nonpublic information, or confidential trading plans to AI features or copied page context unless you have independently confirmed that the environment and provider are appropriate.

fcontext may use cookies and similar technologies to maintain sessions, remember interface preferences, support security, and keep the workspace usable. Browser localStorage may be used for product preferences and local workspace data.

You can control cookies and local storage through your browser settings, but disabling them may break authentication, saved settings, watchlists, portfolio views, prediction cache, and other workspace features.

We do not sell personal information. We may share information with service providers that help operate authentication, hosting, analytics, market data, AI analysis, support, or security. We may also disclose information when required by law, to protect rights and safety, or in connection with a business transfer.

When you choose to copy, export, paste, or send workspace context to another tool, you control that disclosure and the receiving tool's policies apply.

Browser-stored workspace data remains until you clear browser storage, use in-product clear controls where available, or remove it manually. Account and server logs are retained only as long as needed for operation, security, troubleshooting, legal compliance, or development workflows.

Because some data is stored locally in your browser, fcontext may not be able to access, export, or delete that data for you. You can usually remove it by clearing site data in your browser or by using product controls where available.

You can choose not to sign in, avoid optional integrations, clear browser storage, delete local watchlist or portfolio entries where controls exist, disable browser notifications, sign out, avoid copying page context, and avoid submitting sensitive information.

You may contact support for account-related questions. Depending on deployment and data location, some requests may require identity verification or may be limited by local-only storage.

We use reasonable technical and organizational safeguards, including session cookies, environment-based secrets, server-side API keys, and access controls. No system is perfectly secure, especially when running local development builds or connecting external providers.

You are responsible for protecting your device, email account, provider keys, local environment variables, browser profile, and any copied or exported workspace context.

Depending on your deployment, fcontext and its Providers may process information in different regions. If you use the workspace from outside the hosting region, you understand that information may be processed where the service or Providers operate.

fcontext is intended for users who are old enough to make market research and account decisions under applicable law. It is not directed to children, and users should not submit children's personal information to the workspace.

We may update this Privacy Policy as the product scope changes, including if hosted sync, paid subscriptions, production support flows, or external AI authorization are added.

The updated version will be posted on this page with a revised last-updated date.

For privacy questions, contact support@fcontext.local or use the Help & Support page in the workspace.