1. Who is responsible
Quantellect Technologies Inc. is responsible for the personal information described in this policy. We operate quantellect.ai and the services that expressly link to this policy.
Our Privacy Officer can be contacted at [email protected] or by mail at Quantellect Technologies Inc., Attention: Privacy Officer, 700 West Pender Street, Suite 1290, Vancouver, BC V6C 1G8, Canada. General inquiries can be sent to [email protected].
This policy explains the handling of information about visitors and users, and information about identifiable individuals appearing in research sources. Other companies and websites do not become part of this policy solely because of shared ownership, branding, or personnel.
2. Scope and current service
Quantellect currently offers research and educational features without membership fees. We do not request payment card information for the current free service. Quantellect plans to introduce paid advertising, sponsored issuer coverage, and marketing communications; section 9 describes those plans and the current status of each channel. Collection of personal information can still occur through browsing, accounts, correspondence, research tools, alerts, and service operations.
The information actually collected depends on the features you use. A description of an optional feature does not mean it is available to every user. Material changes to collection or use will be explained before they take effect where required.
3. Information you provide
We collect information you submit when you create or sign in to an account, set up a calendar reminder, or use a feature that stores your input. Correspondence you send to our mailboxes is handled in those mailboxes, outside the website's systems.
Depending on the feature, this can include your email address, authentication identifier and session, chosen display or profile fields, geography and interface preferences, selected tickers and device-local watchlists, saved screener settings, and calendar-reminder settings. Watchlist activity may also be stored with a pseudonymous owner identifier and, when available, an account identifier. A separate journal service receives an authenticated account token when a signed-in user opens the journal; that service's storage and retention are described with the journal feature and were not part of the review that produced this policy.
When you accept the Terms of Use, we keep an account-linked record of the acceptance version, fingerprints of the Terms text and of the consent wording, whether it was a first acceptance or a re-acceptance, and the server-recorded acceptance time, to administer and document our agreement.
Information marked as required on a form is needed to provide that feature. If you do not provide it, the feature may not work. Do not submit passwords for other services, brokerage credentials, government identity numbers, payment details, or another person's confidential information in a note or message to us.
4. Information collected during use
Our systems and service providers process technical information needed to deliver and secure the service, such as IP addresses, request times, device and browser information, requested pages, authentication events, error records, and suspicious activity indicators.
Cookies, browser storage, and similar technologies are described in the Cookie and Similar Technologies Policy. We do not treat silence, scrolling, or accepting the Terms as consent to optional tracking.
You may sign in by email one-time code or with Google. When Google sign-in is used, we receive the identifiers and account information presented in that authorization flow; we do not receive your Google password.
5. Information from public and commercial research sources
Our research can include information about company officers, directors, investment managers, analysts, public officials, and other individuals identified in financial or public records. Sources can include SEC filings, congressional disclosures, issuer publications, news, official records, and data suppliers.
The information can include names, professional roles, organizational associations, reported holdings and transactions, published opinions, relevant dates, and estimates or classifications generated from those records. Records can be incomplete, delayed, amended, or incorrectly matched.
Public availability does not mean personal information is outside privacy law. We use this information for financial research and public information; the purpose, source restrictions, and legal basis apply to each use. Congressional financial disclosures are not used to solicit money or to assess an individual's creditworthiness. Contact [email protected] to raise a concern about a record, an inference, or an identity match.
6. Why we use information
We use information to provide the feature requested, administer accounts and preferences, deliver requested content, respond to inquiries, detect abuse, investigate faults, correct research, maintain service security, and comply with lawful obligations.
Where permitted, we use proportionate service information to understand and improve reliability and usability. Optional marketing, optional tracking, and any separate use of private submissions for AI training require their own applicable legal basis and notice.
For processing subject to the EEA or UK GDPR, the following describes our purposes and corresponding bases. A basis applies only where its legal requirements are satisfied.
| Purpose | Basis and interest |
|---|---|
| Requested account and research features | Performance of our agreement with you, or steps you request before entering it, where the processing is necessary for that purpose. |
| Service security, abuse prevention, fault diagnosis, and ordinary support | Legitimate interests in maintaining a secure and reliable service and resolving requests, balanced against individuals' rights. Legal obligations apply where a particular law requires processing. |
| General financial research about identifiable individuals from relevant sources | Legitimate interests in accurate financial research and public information, subject to source restrictions and any applicable journalistic protections or limitations. |
| Optional newsletters, promotional messages, and tracking that requires permission | Consent. A separate legally available messaging exception is used only where its conditions are documented and explained. |
| Legal requests, required records, and handling rights requests | Compliance with applicable legal obligations. Establishing or defending legal claims can also involve legitimate interests. |
We do not use the phrase legitimate interests as permission for any purpose we might later choose. Where sensitive information or protected inferences are involved, an additional legal condition may be required.
7. AI processing and automated outputs
Quantellect does not currently provide a public AI chat or research-assistant interface.
Our internal content-management system can send an editor's article title, article type and category, current search metadata, focus keyword, and up to 1,500 characters of article text to Anthropic to suggest metadata or tags. The suggestion audit stores the provider and model, the staff user identifier, the article identifier, usage, cost, outcome, and suggestion count; it is designed not to store the prompt, the article body, or the suggestion text. Published articles marked as AI-assisted display an AI-assistance notice and indicate whether an editorial review occurred.
A separate research assistant is restricted to staff and is not exposed on the public website. When enabled, it sends a staff question and selected research evidence to OpenRouter, using a model and downstream provider selected in deployment configuration. Its database record contains the request, provider configuration, retrieved evidence, generated response, and completion metadata, and is assigned an expiry 30 days after creation.
Other automated systems use Anthropic, OpenAI, xAI, and command-line AI services to create or review editorial content, classify public social-market material, or extract information from public filings. Those paths process market, news, analyst, issuer, regulatory-filing, or staff-authored content. No path in the website or its backend sends a public account holder's watchlist, note, or account profile to an AI provider.
Research rankings about securities and public records differ from decisions about your legal rights or eligibility for a service. If we introduce a decision based solely on automated processing that has legal or similarly significant effects on you, we will provide the required explanation and safeguards, including applicable rights to challenge the decision and obtain human intervention. You can already contact us about errors or objections to an automated inference.
8. Who receives information
The recipients below are the service providers our systems send information to, with the purpose each serves. A market data supplier does not automatically receive user information.
Quantellect uses service providers for account authentication and profile storage, application databases, analytical storage, hosting and network security, error monitoring, scheduled processing, object storage, and transactional email. Our systems identify Supabase (authentication, profiles, Terms-acceptance records), Google (optional Google sign-in), PostgreSQL hosted by Neon, ClickHouse Cloud, Upstash Redis, Cloudflare, Sentry, Trigger.dev, Cloudflare R2 object storage, and Resend. Depending on the feature, these providers may receive account identifiers, email address, display or profile fields, IP address or an IP-derived value, user-agent or a hash of it, watchlist selections, reminder settings, operational request metadata, staff-authored content, or transactional message content. The AI providers named in section 7 receive the content described there. The operator of the application hosting and of the journal service is identified with those features.
Quantellect also connects signed-in users to a separately configured journal service by sending an authenticated account token to that service when you open the journal.
Information can be accessed or processed in a country other than the one where you live; see section 10.
We may disclose information where applicable law permits or requires it, including to respond to a lawful request, to establish or defend legal claims, or in connection with a business transaction. If another company processes information for Quantellect, its role and purpose must be reflected in the relevant disclosure and agreement.
We do not treat acceptance of this policy as permission to provide your information to every related business for its own marketing. If a feature intentionally makes your content public or sends it to a selected external service, its notice should explain that before you submit or authorize access.
9. Advertising, sale, sharing, and tracking
Current measured state. As of this policy's effective date, the public website does not display advertising, and no advertising, remarketing, or third-party analytics script listed below has been switched on in production. The only measurement currently active is described below under Current analytics.
Planned advertising, marketing, and tracking. Quantellect plans to introduce paid advertising, sponsored issuer coverage, and marketing communications, consistent with our Disclaimer. When introduced, this can include:
- Advertising and remarketing networks: Google Ads, Microsoft (Bing) Ads, Taboola, Outbrain, MGID, Reddit Ads, X (Twitter) Ads, and Meta (Facebook) Ads. These networks can place a cookie or similar identifier, receive information about pages you view or actions you take, and use that information to show Quantellect advertising to you on their own platforms or elsewhere.
- Web analytics: Google Analytics, Firebase, and Clicky, and a first-party analytics product we operate called Seykota.ai. This is separate from the current watchlist activity capture described below under Current analytics, which is already active.
- Visitor identification and lead generation ("visitor deanonymization"): a service such as DrivingIQ or VisitIQ that would attempt to match an otherwise anonymous website visit to a household, business, or individual so that the visit can be treated as a sales or marketing lead, using identifiers and signals that depend on the vendor and configuration eventually selected. This is a materially different practice from ordinary analytics or remarketing: it can attach an identity to a visit that never submitted any personal information to us. Before this service is introduced, we will name the actual vendor, describe the specific signals it uses and what it matches, and give effect to any required consent or opt-out.
- Push notifications: browser or device push notifications for site updates and sponsored or promotional content, subject to the permission your browser or device requests before notifications can be sent.
- Email marketing: through Beehiiv, in addition to the transactional and account emails described in section 3.
- SMS marketing: through TracklySMS, requiring your own prior opt-in and offering a working opt-out (for example, replying STOP) with every message.
None of the above is switched on today. This policy and the Cookie Policy will be updated to reflect the actual vendor, data collected, and consent or opt-out mechanism before each channel goes live where required, and the effective date will be revised accordingly. Optional marketing and optional tracking always require their own consent or opt-out separate from accepting the Terms of Use, as described in section 13.
Current analytics. The website uses Cloudflare Web Analytics, a measurement script delivered by Cloudflare at the network edge that records page views and performance metrics; on our measured visits it set no analytics cookie and no browser storage. It uses Sentry for error monitoring and masked on-error session replay, and Cloudflare for edge and network security.
The website stores watchlist activity in Quantellect's ClickHouse environment for product analysis and forensic replay. This includes a pseudonymous owner identifier, an account identifier when you are signed in, the ticker, exchange or category, and list identifiers or names. Event history is kept for two years; current membership has no code-defined expiry. This capture is disabled when your browser sends a Do Not Track signal.
Quantellect also operates a first-party advertising system that is switched off in production. It is not currently serving advertisements and is not currently recording advertising events; see Planned advertising above for what changes when it is switched on.
No system or configuration reviewed for this policy transmits personal information to another party in exchange for payment. The website does not currently implement Global Privacy Control handling or a tracking-consent banner. Where applicable law requires recognition of an opt-out preference signal, we will give effect to it for the covered processing. Any consent or opt out required for these activities is distinct from accepting the Terms.
10. International processing
Depending on provider configuration, information can be accessed or processed in a country other than the one where you live. Foreign authorities may have access under that country's laws.
For transfers subject to the EEA or UK GDPR, the relevant transfer mechanism must be legally available for the particular recipient and processing. This can involve an applicable adequacy decision or appropriate contractual safeguards and supplementary measures. Canadian incorporation alone does not establish that every transfer is covered by an adequacy decision.
Contact [email protected] for information about the safeguards relevant to your data and how to obtain a copy, subject to necessary protection of confidential information.
11. Retention and security
We keep information for the period needed for its stated purpose and applicable legal requirements. Retention depends on whether an account is active, whether a feature needs saved history, the time reasonably needed to investigate an incident or resolve a request, limitation periods, source restrictions, and obligations to preserve particular records. Public API request logs, which include IP addresses, are normally archived and removed from our analytical database after 90 days by a nightly job, with a 100-day expiry as the fallback; the archive's own retention period is set by the storage configuration.
Public research records can be retained for historical research and correction integrity where lawful. These purposes do not justify retaining unrelated private submissions indefinitely.
We respond to valid deletion requests subject to applicable exceptions; how deletion is carried out, and how long backup copies persist, depends on the affected system.
Technical controls include access controls, authentication, and error and abuse monitoring. No internet service can promise absolute security. We will notify individuals or authorities of an incident when applicable law requires it.
12. Your choices and rights
You can ask for access to your personal information and request correction. Depending on the applicable law, you may also have rights to deletion, restriction, portability, objection, withdrawal of consent, or an appeal of a denied request. These rights are subject to lawful conditions and exceptions.
For EEA and UK processing based on legitimate interests, you can object based on your circumstances. You can object to direct marketing at any time, including related profiling. Withdrawing consent does not affect the lawfulness of earlier processing.
Send requests to [email protected]. We may ask for information reasonably needed to verify identity or authority. We will handle verified requests as applicable law requires, including its time limits, and will explain any lawful extension or refusal. Exercising privacy rights will not result in unlawful discrimination.
You can complain to the Office of the Information and Privacy Commissioner for British Columbia, the Office of the Privacy Commissioner of Canada where it has jurisdiction, your competent EEA supervisory authority, or the UK Information Commissioner's Office, as applicable. You do not have to complete our internal process before exercising a statutory complaint right.
If an EEA or UK representative or a data protection officer is legally required, the relevant contact details will be published with this policy. A Canadian Privacy Officer is not automatically an EEA or UK representative.
13. Messages and consent
The customer email our systems send today is the one-time sign-in code (sent through our authentication provider when you sign in by email) and the calendar reminder you set up yourself, delivered to the address you verified for that feature; you can remove that address from the same feature at any time. No newsletter, product-update, or promotional-email sender exists in the current service. Where an account remains active, necessary security and service notices can continue as permitted by law.
Quantellect plans to introduce optional promotional email through Beehiiv and optional promotional SMS through TracklySMS. Neither is switched on today. When introduced, each will require its own separate, initially empty choice that is not combined with Terms acceptance or with each other, and every message will carry a working opt-out (an unsubscribe link for email, and a reply such as STOP for SMS, honored promptly). A consent given to another brand, another Market Jar-affiliated website, or a co-registration or sweepstakes form does not by itself mean you consented to Quantellect communications; if a specific opt-in method is used to add you to a list, the notice presented at that opt-in will describe it.
14. Children and policy changes
The account service is intended for adults who meet the eligibility requirements in the Terms of Use. We do not intentionally solicit children's personal information. If you believe a child has supplied information, contact us so that we can assess and address it.
We will update this policy and its effective date as practices change. Material changes will be brought to your attention in an appropriate way, and we will obtain new consent where required. Publication of a revised policy alone does not authorize a new use that requires consent.

