Privacy Policy | Fidusor

This Privacy Policy explains how Fidusor Technologies LLC ("Fidusor," "we," "us," or "our") collects, uses, discloses, retains, and protects information when you access or use Fidusor, including the website, application, support chatbot, account features, portfolio aggregation, brokerage connectivity, watchlists, market research tools, options strategy interfaces, paper-trade and planning workflows, subscription features, and related services (collectively, the "Service").

By using the Service, you acknowledge this Privacy Policy. If you do not agree with this Privacy Policy, you must not use the Service.

1. Scope Of This Privacy Policy

This Privacy Policy applies to information processed by Fidusor in connection with the Service. It does not apply to websites, applications, platforms, brokers, clearing firms, custodians, exchanges, payment processors, AI providers, data providers, or other third parties that maintain their own privacy policies or data practices.

When you connect a brokerage or financial account, use the support chatbot, sign in through a third-party identity provider, or interact with a third-party service through Fidusor, that third party may process information under its own terms and privacy policy.

2. Information We Collect

Fidusor may collect the following categories of information.

2.1 Account Information

We may collect your name, email address, password authentication data, Google sign-in identifiers where applicable, passkey credential identifiers and public keys, passkey names, authenticator transport and device metadata, passkey backup status, authentication counters and usage timestamps, account-recovery code hashes and usage status, email-verification status, security-event records, account status, requested plan tier, subscription tier, subscription status, administrative role, session metadata, and account preferences. When you electronically sign an account agreement, we also collect the typed signer name, drawn signature image, account email, document versions and cryptographic hash, acceptance timestamp and method, successful PDF-access confirmation, IP address, browser user-agent information, request identifier, and the state of each required acknowledgment. The drawn signature is retained as contract-assent evidence and is not used to create a biometric identifier or for biometric authentication.

We do not store your plaintext password. Passwords, where used, are processed through protective authentication controls.

When you create or use a passkey, the passkey private key remains under the control of your authenticator or passkey provider and is not provided to Fidusor. If your device uses Face ID, Touch ID, a fingerprint, facial recognition, a device PIN, or another local method to authorize a passkey, Fidusor does not receive or store that biometric data or local unlock secret. Fidusor receives the public-key credential information and authentication results needed to register the passkey, verify later sign-ins, manage registered passkeys, prevent replay or abuse, and maintain security records.

Recovery codes are stored in one-way protected form rather than plaintext. If you generate recovery codes, you are responsible for saving the displayed codes securely because Fidusor does not display the plaintext codes again after generation.

Electronic-signature evidence is used to establish which terms were presented and accepted, demonstrate intent to sign, maintain legal and compliance records, prevent fraud, and resolve or enforce disputes. We store the signer-specific agreement PDF in private object storage and provide it only through authenticated access. Fidusor may retain this evidence after account closure for the period reasonably necessary to satisfy legal, regulatory, audit, security, and dispute-resolution obligations.

2.2 Subscription And Billing Information

We may collect subscription plan, billing status, payment outcome, customer identifiers supplied by payment providers, card-related tokens supplied by payment providers, webhook event metadata, subscription start or end dates, requested upgrades, and related support or account records.

Fidusor does not intend to store full payment card numbers in the Service. Payment processing may be handled by third-party payment processors subject to their own privacy and security practices.

2.3 Portfolio And Brokerage Connection Information

If you connect a brokerage or financial account, Fidusor may receive account and portfolio information through secure third-party connection providers. This may include:

Brokerage account identifiers or display names.
Account type and account metadata.
Holdings, positions, quantities, symbols, asset types, option contract details, cost basis or trade-price information where available, market value, cash balances, buying power, and related account snapshots.
Position classifications, portfolio analytics, risk views, allocation views, options-book views, stress views, and data-quality indicators generated from connected-account data.
Connection status, refresh timestamps, reauthorization status, and provider response metadata.

Portfolio data aggregation is facilitated through secure, encrypted third-party connections. Fidusor does not ask for, handle, or store your primary brokerage login credentials, such as your brokerage username and password. When a brokerage connection requires authentication, you are directed through a third-party or brokerage-controlled authorization experience. Fidusor may store encrypted connection tokens, session tokens, or opaque authorization identifiers that allow the Service to refresh or display connected-account data, but those tokens are not your primary brokerage login credentials.

2.4 Watchlist, Research, Strategy Planning, And Product Data

We may collect information you create or generate in the Service, including watchlists, saved symbols, filters, notes, alerts, notifications, paper trades, strategy selections, planning inputs, option legs, selected brokerage account, support preferences, feature usage, and product-navigation events.

Brokerage trading is not currently supported. Current strategy-planning and paper-trade inputs are used for research workflows and do not submit orders. Official brokerage records, statements, and confirmations remain with your broker or clearing firm.

2.5 Support Inquiries And Chatbot Communications

If you contact support or use the support chatbot, we may collect the information you submit, including your question, conversation history, page context where applicable, account email if provided, screenshots if provided, troubleshooting details, timestamps, and support communications.

Support inquiries may be routed to a secure AI API instance for processing. This means that text you submit through the chat UI, relevant conversation history, and support knowledge-base context may be transmitted to a third-party AI provider or processed through AI infrastructure to generate a response.

You should not input passwords, brokerage credentials, API keys, security codes, private keys, full account numbers, full Social Security numbers, payment card numbers, or other highly sensitive personal or financial information into the chat UI. Fidusor support does not need that information to assist with ordinary product questions.

2.6 AI-Assisted Position Analysis

If you choose to use an AI-assisted position-analysis feature, Fidusor may send the minimum relevant context to a third-party AI provider to generate the requested analysis. That context may include symbols, position types, quantities, option contract details, cost basis or unrealized gain/loss information where available, calculated exposure or risk metrics, and the research or strategy context you selected. It does not include your brokerage login credentials, full account numbers, payment-card numbers, or security codes.

AI-assisted position analysis is optional. Do not use that feature if you do not want the relevant portfolio context processed by an AI provider. AI output is informational only and may be inaccurate, incomplete, delayed, or inappropriate for your circumstances.

2.7 Device, Usage, And Technical Information

We may collect device and usage information such as IP address, browser type, operating system, device identifiers, referring page, pages viewed, feature interactions, timestamps, error logs, request identifiers, session status, approximate location derived from IP address, and performance or diagnostic information.

This information helps us operate, secure, debug, improve, and monitor the Service.

2.7 Cookies And Similar Technologies

Fidusor may use cookies, local storage, session storage, and similar technologies to keep you signed in, remember preferences, maintain security, support product functionality, measure usage, and improve performance.

You may be able to restrict cookies through your browser settings. If you disable cookies or local storage, parts of the Service may not function correctly.

3. How We Use Information

Fidusor may use information for the following purposes:

Provide, operate, maintain, and improve the Service.
Create, authenticate, secure, and administer accounts.
Provide watchlists, research views, portfolio analytics, strategy-planning workflows, alerts, notifications, and paper-trade features.
Facilitate brokerage and portfolio aggregation through secure third-party connections.
Process support requests and chatbot interactions.
Provide plan-specific access, subscription management, billing status, waitlist management, and account administration.
Display data-quality statuses, refresh timestamps, and troubleshooting guidance.
Detect, investigate, and prevent fraud, abuse, unauthorized access, security incidents, and violations of terms.
Monitor uptime, errors, latency, performance, rate limits, and feature reliability.
Comply with legal, regulatory, tax, accounting, dispute-resolution, and contractual obligations.
Enforce agreements and protect Fidusor, users, third parties, and the Service.
Communicate with you about account status, support issues, security notices, product changes, and administrative matters.

Fidusor does not use your connected brokerage credentials because Fidusor does not receive or store primary brokerage login credentials.

4. How We Disclose Information

Fidusor may disclose information to the following categories of recipients.

4.1 Service Providers

We may disclose information to vendors and service providers that help us provide the Service, such as hosting providers, database providers, infrastructure providers, support tooling providers, analytics providers, security providers, email providers, payment processors, AI providers, and monitoring providers.

These providers are permitted to process information as necessary to provide services to Fidusor and are expected to protect information appropriately.

4.2 Brokerage, Portfolio Aggregation, And Financial Connectivity Providers

When you connect a brokerage or financial account, information may be exchanged with secure third-party connection providers, brokerages, custodians, clearing firms, and related financial infrastructure providers as needed to authorize connections, retrieve account data, and refresh portfolio information. Brokerage trading is not currently supported.

Fidusor does not control the privacy practices of external brokerages, custodians, clearing firms, or financial institutions.

4.3 AI Providers

When you use the support chatbot or certain AI-assisted features, Fidusor may send relevant prompts, conversation text, support context, and system instructions to a third-party AI provider to process your request and generate a response.

For an AI-assisted position-analysis request, this may include the limited portfolio context described in Section 2.6. Fidusor sends that context only to provide the feature you requested and does not send brokerage login credentials, full account numbers, payment-card numbers, or security codes for this purpose.

Do not submit sensitive account numbers, credentials, security codes, or unrelated personal financial information into the chat UI.

4.4 Payment Processors

If subscription billing or payments are enabled, payment-related information may be processed by third-party payment processors. Fidusor may receive payment status, subscription status, customer tokens, card tokens, and transaction metadata but does not intend to store full payment card numbers.

4.5 Legal, Compliance, Safety, And Enforcement

We may disclose information if we believe disclosure is reasonably necessary to:

Comply with law, regulation, subpoena, court order, government request, or legal process.
Enforce our Terms of Service or other agreements.
Detect, prevent, or address fraud, security, technical, market-abuse, or compliance issues.
Protect the rights, property, safety, or security of Fidusor, users, third parties, or the public.
Investigate violations or suspected misuse of the Service.

4.6 Business Transfers

If Fidusor is involved in a merger, acquisition, financing, reorganization, bankruptcy, sale of assets, or similar transaction, information may be disclosed to or transferred as part of that transaction, subject to appropriate confidentiality and legal safeguards where applicable.

4.7 With Your Direction Or Consent

We may disclose information when you direct us to do so, when you connect a third-party service, when you submit information to a feature that requires disclosure, or when you otherwise consent.

5. Data Retention

Fidusor retains information for as long as reasonably necessary to provide the Service, maintain security, comply with legal and accounting obligations, resolve disputes, enforce agreements, support business operations, and improve product reliability.

Retention periods may vary depending on the type of information, account status, legal requirements, operational needs, and security considerations.

5.1 Account Records

Account records may be retained while your account is active and for a reasonable period afterward to support security, auditability, legal compliance, dispute resolution, billing, and fraud prevention.

5.2 Encrypted API Session Tokens And Connection Tokens

Fidusor may retain encrypted API session tokens, third-party connection tokens, opaque authorization identifiers, and related metadata for as long as necessary to maintain connected-account functionality, support reauthorization, provide portfolio refreshes, secure the Service, investigate errors, comply with law, or maintain audit records.

When a connection is revoked, expires, is deleted, or is no longer needed, Fidusor will take reasonable steps to disable or delete related tokens in accordance with operational, security, legal, and backup-retention requirements. Some copies may persist temporarily in backups, logs, or disaster-recovery systems until they expire or are overwritten according to standard retention cycles.

5.3 Portfolio Snapshots And Analytics

Portfolio snapshots, holdings data, data-quality indicators, and derived analytics may be retained to provide historical views, improve reliability, troubleshoot support requests, monitor data quality, and maintain auditability. Retention may continue after a brokerage connection is disconnected where needed for security, compliance, billing, dispute resolution, or legitimate business purposes, unless deletion is required by applicable law.

5.4 Communication Logs And Support Chat Logs

Support communications, chatbot conversation logs, support request details, troubleshooting notes, screenshots you provide, and related metadata may be retained to respond to support requests, improve product quality, monitor safety, debug issues, enforce rate limits, investigate abuse, and maintain an account-support history.

Fidusor may retain communication logs for a reasonable business period and may retain certain records longer where necessary for legal, security, audit, or dispute-resolution purposes.

5.5 Error Logs, Security Logs, And Technical Logs

Error logs, request logs, security logs, rate-limit logs, audit records, and diagnostic data may be retained to secure the Service, detect abuse, investigate incidents, improve reliability, and comply with legal obligations.

Authentication records, including registered passkey metadata, recovery-code status, email-verification state, session records, and security-event history, may be retained while an account is active and afterward where reasonably necessary for account recovery, fraud prevention, security investigations, auditability, legal compliance, or dispute resolution.

5.6 Deletion Requests

You may request deletion of certain personal information by contacting Fidusor. We may decline or limit deletion where retention is necessary for legal compliance, security, fraud prevention, dispute resolution, accounting, tax, contractual obligations, product integrity, or other legitimate purposes permitted by law.

6. Security

Fidusor uses reasonable administrative, technical, and organizational safeguards designed to protect information. These may include encryption, access controls, credential protections, passkey authentication, one-way protection of passwords and recovery codes, logging, monitoring, secure configuration, and separation of duties where appropriate.

Portfolio aggregation is facilitated through secure, encrypted third-party connections. Fidusor does not handle or store primary brokerage login credentials. Connection tokens or session tokens used to support integrations are intended to be stored in encrypted or otherwise protected form.

No security measure is perfect. We cannot guarantee that information will never be accessed, disclosed, altered, or destroyed. You are responsible for protecting your account credentials, maintaining device security, and promptly notifying Fidusor of suspected unauthorized access.

7. Your Choices And Controls

Depending on the features available to you, you may be able to:

Update account information.
Add, rename, or remove registered passkeys through available account-security controls.
Generate replacement recovery codes, which invalidates previously generated recovery codes.
Sign out of active sessions.
Change product preferences.
Disconnect or reauthorize brokerage connections.
Delete or modify watchlist items, alerts, and notes.
Request support regarding account access, privacy, or data concerns.
Opt out of certain non-essential communications where available.

You may also use your brokerage or the third-party connection portal to revoke account-access permissions, subject to the controls provided by those services.

8. Privacy Rights

Depending on where you live, you may have rights to request access, correction, deletion, portability, restriction, objection, or information about the categories of personal information collected, disclosed, or shared. You may also have the right to appeal certain privacy decisions.

To exercise privacy rights, contact Fidusor at [email protected]. We may need to verify your identity before responding. We will not discriminate against you for exercising rights provided by applicable law, though certain requests may affect your ability to use parts of the Service.

9. California Privacy Notice

If you are a California resident, this section provides additional information. In the preceding 12 months, Fidusor may have collected the categories of personal information described in this Privacy Policy, including identifiers, commercial information, internet or electronic network activity information, financial-account-related information processed through connected-account features, approximate geolocation derived from IP address, professional or employment-related information if you provide it, inferences derived from product usage, and sensitive personal information such as account login information for Fidusor or financial-account information received through secure aggregation.

Fidusor uses these categories for the purposes described in this Privacy Policy, including providing the Service, account administration, security, support, analytics, billing, compliance, and product improvement.

Fidusor may disclose these categories to service providers, brokerage or portfolio aggregation providers, AI providers, payment processors, infrastructure providers, security providers, professional advisers, legal authorities, and business-transfer recipients as described above.

Fidusor does not intend to sell personal information for money. Fidusor does not intend to use or disclose sensitive personal information for purposes that require a right to limit under California law, except as permitted by law, such as providing the Service, securing accounts, preventing fraud, or maintaining integrations you request.

California residents may request to know, access, correct, delete, or receive information about certain disclosures, subject to legal exceptions. Contact [email protected] to submit a request.

10. Children's Privacy

The Service is not directed to children under 13, and Fidusor does not knowingly collect personal information from children under 13. If you believe a child has provided personal information to Fidusor, contact [email protected].

11. International Users

Fidusor is operated from the United States. If you access the Service from outside the United States, you understand that information may be processed in the United States and other jurisdictions where Fidusor or its service providers operate. Those jurisdictions may have data protection laws different from those in your location.

12. Do Not Track

Some browsers transmit "Do Not Track" signals. Because there is no uniform industry standard for responding to those signals, Fidusor may not respond to them in a consistent manner. We will honor legally required opt-out mechanisms where applicable.

13. Third-Party Links And Services

The Service may link to or integrate with third-party websites, brokerages, connection portals, payment processors, AI providers, data providers, support tools, and other services. Fidusor is not responsible for the privacy, security, accuracy, or practices of third parties. You should review their terms and privacy policies.

14. Changes To This Privacy Policy

Fidusor may update this Privacy Policy from time to time. If changes are material, Fidusor may provide notice through the Service, by email, or by updating the effective date. Your continued use of the Service after an updated Privacy Policy becomes effective means you acknowledge the updated policy.

15. Contact

Questions, privacy requests, or security concerns may be sent to Fidusor Technologies LLC at [email protected].