Legal · Updated Oct 14, 2026
Privacy Policy
How Earnings Feed collects, uses, and safeguards your information across the public site, dashboard, and APIs.
This policy explains what personal information Earnings Feed collects, why, who receives it, how long we keep it, and the choices you have.
Who we are
Earnings Feed is operated by Lucent Enterprises Ltd., 5307 Victoria Drive, Vancouver, BC V5P 3V6, Canada ("we", "us"). We are the organization responsible for your personal information (the "controller" under EU and UK law). Our privacy contact is privacy@earningsfeed.com.
We follow British Columbia's Personal Information Protection Act and Canada's Personal Information Protection and Electronic Documents Act. If you are in the EU, the UK or California, the rules for your region in this policy also apply.
Scope & effective date
This notice covers:
- Visits to earningsfeed.com and any subdomains.
- Use of the authenticated dashboard and any APIs or alerts you enable.
- Use of the Earnings Feed browser extension.
- Connections to AI assistants through our MCP server.
- Customer support and other direct communications related to the service.
It applies to data processed on and after October 1, 2026.
Browser extension
The Earnings Feed browser extension replaces the new-tab page with public SEC filing data retrieved from earningsfeed.com.
- The extension provides a limited anonymous preview. When that preview is exhausted, a free Earnings Feed account is required to continue receiving fresh filings.
- It uses Clerk to synchronize an existing Earnings Feed website session by accessing authentication cookies only on the first-party Clerk host,
clerk.earningsfeed.com. It sends a short-lived Clerk session token toearningsfeed.comwith authenticated feed requests. The extension does not receive or store your password. - It does not read or collect browsing history, page content, bookmarks, downloads, or form entries.
- To measure distribution and improve the feed's reliability, it sends a narrow set of first-party product events to
earningsfeed.com: install or update, new-tab open, signed-in state, feed success or failure category, anonymous-limit state, theme changes, and deliberate clicks on extension controls or filing cards. Events include extension version, browser family, response duration, item count, and cache state. They use a random installation ID and do not include browsing history, visited-site URLs, filing titles, company names, search terms, page contents, passwords, email addresses, or session replay.earningsfeed.comforwards these schema-limited events to our PostHog project; no PostHog SDK, autocapture, advertising, session recording, or remotely hosted analytics code runs inside the extension. Firefox treats this technical-and-interaction collection as optional; the extension checks Firefox's built-in permission and sends no telemetry if the user declines or disables it. - It stores the selected light, dark, or system theme preference, a random installation ID, a recent cache of public filing records, and the cache timestamp in the browser's extension storage. This makes subsequent new tabs useful while fresh data loads, lets the extension identify stale cached results, and supports aggregate install and retention measurement.
- It connects to
earningsfeed.comto retrieve the filings feed and company images, and toclerk.earningsfeed.comfor account-session synchronization. Like ordinary visits to the website, those HTTPS requests may create short-lived security and operational server logs such as timestamps, IP addresses, user-agent information, requested URLs, account identifiers for authenticated requests, and errors.
Removing the extension deletes its locally stored preference, installation ID, and public-data cache according to the browser's behavior. The rest of this policy applies when the extension requests content or records schema-limited product events through earningsfeed.com, or synchronizes an account through clerk.earningsfeed.com.
Our use of information received through the extension complies with the Chrome Web Store User Data Policy, including its Limited Use requirements. We use extension data only to provide, maintain, secure, or improve the extension's disclosed SEC-filings feed and account-session features. We do not use or transfer it for personalized advertising, credit decisions, or sale to data brokers.
MCP connections to AI assistants
When you authorize an AI assistant to connect to Earnings Feed, Clerk handles account sign-in and OAuth authorization. Our MCP server checks that authorization and receives the tool inputs needed for your request, such as a company name, ticker or CIK, filing accession, transaction filters, date range or pagination cursor. The tools do not request your full chat transcript.
The server returns public SEC company information, filing metadata and document lists, and insider transaction records with source links. These public records can include individuals' names, company roles and reported transactions. The assistant receives the results you request; its provider handles your conversation, connection authorization and its copies of those results under its own policies.
We disable Sentry's automatic MCP tool-argument and result-body recording. Error and performance diagnostics remain enabled. Application logs and diagnostics can include the method and tool name, request and account identifiers, response timing, status, error details and quota information. Our database stores account-linked usage and quota records, and PostHog receives account-linked first-use, active-day and quota events. We use these records to enforce account limits, detect abuse and maintain service reliability. Disabling automatic payload recording does not delete diagnostics collected before the change.
The retention and data-rights provisions below apply to information Earnings Feed holds. For access, correction or deletion requests about your account and MCP-linked usage records, contact privacy@earningsfeed.com. Requests concerning information held by an assistant provider should also be directed to that provider.
Information we collect
We collect four broad categories of information:
Account details. Name, email address, profile image, authentication identifiers from Clerk (including last sign-in timestamp and associated metadata), billing information processed by Stripe if you subscribe to paid tiers, and API keys (stored as SHA-256 hashes with display prefixes).
Usage and device signals. Log data such as timestamps, IP region, browser/OS metadata, feature toggles used, and diagnostic events. Session recordings (captured via PostHog) include screen interactions, clicks, page navigation, mouse movements, and form inputs (password fields are masked). Error logs include error messages, stack traces, affected URLs, and (for authenticated users) user identifiers. Browser cookies and local storage for authentication, analytics, and preference management. We use this to detect abuse, measure latency, improve reliability, and diagnose technical issues.
Customer content. Watchlist configurations with custom labels, alert preferences (frequency, form types, enabled state), email preferences and opt-out choices, API key names and usage records, feedback submissions (category, message, page context, browser information), and support communications you choose to share. You control what is stored in your account.
Public market data.
SEC filings and other public records. These may reference individuals (e.g., insiders in Form 4s), but they are already public when we ingest them and are treated as market data, not private account data.
How we use information
We use the information described above to:
Deliver and maintain the product.
Provision your dashboard, run saved feeds, power search and watchlists, generate alerts, and provide customer support.Improve and research product performance.
Analyze aggregated usage patterns to benchmark reliability, tune ingestion pipelines, and guide roadmap priorities.Security, fraud prevention, and compliance.
Monitor for abuse, enforce rate limits, investigate incidents, and satisfy lawful requests where required.Communications. Send service notices, onboarding emails (welcome messages, feature highlights, upgrade information), billing updates, and (where permitted) opt-in marketing or educational content. You can manage email preferences and opt out of drip campaign emails at any time.
Measure our ads. When you arrive from one of our Google or Microsoft ads, we tell that network when you sign up, start a trial or make your first payment. See Ad measurement.
We do not use your account information to build audiences or target ads at you.
Ad measurement
We advertise on Google Ads and Microsoft Advertising in the United States and Canada. To learn which ads bring people who use Earnings Feed, we report conversions back to the network whose ad you clicked.
- What we store. When you open earningsfeed.com from an ad, the link carries a click ID (
gclid,gbraidorwbraidfrom Google,msclkidfrom Microsoft). We keep the first click ID per network in a first-party cookie for 90 days, with the time, the page you landed on and your country. We set this cookie only when our network provider places your visit in the United States or Canada. If you create an account from our sign-up form in that time, we save the click on your account and clear the cookie. - What we send. For a sign-up, a trial start or your first payment, we send the network the click ID, the event time, an event ID, and for a payment its amount and currency. We send it only to the network whose ad you clicked. Google receives it through its Data Manager API; Microsoft through its offline conversions API.
- Email. We send a hashed (SHA-256) copy of your email address only if we have turned on enhanced conversions, you have not opted out, and your ad click came from the United States or Canada. By default we send the click ID only.
- Your choice. At sign-up you can tick "Don't share my sign-up with Google or Microsoft". Then we send nothing about your account to either network. To opt out later, email privacy@earningsfeed.com.
- How the networks use it. Google and Microsoft use these reports to measure and optimize our ad campaigns, under their own terms and privacy policies. We do not send your name, your watchlists or what you read.
When we share data
We share personal data only in these situations:
Service providers. These companies process personal information for us under contract. They may use it only to provide their service to us.
Provider What they do What they receive Where Clerk Sign-in and accounts Name, email, profile image, sign-in records United States Stripe Payments and invoices Billing name, email, address, card details (we never see full card numbers) United States Cloudflare Hosting, CDN, email delivery Requests, IP addresses, email addresses for messages we send Global network, United States company PlanetScale Database Your account data, watchlists and alerts Canada (Montreal) PostHog Product analytics and session replay Product events, device data, a sample of session recordings United States Sentry Error and performance monitoring Error reports, timing, tool/method names and account/request identifiers United States Google (Workspace) Our email inbox Emails you send to our @earningsfeed.com addresses United States OpenAI AI summaries of public filings Public SEC filing text and the names of people in filings, never your account data United States Google Ads Ad conversion measurement Click ID, event time and ID, payment amount; hashed email only as described below United States Microsoft Advertising Ad conversion measurement Click ID, event time and ID, payment amount; hashed email only as described below United States Google sign-in. If you choose "Continue with Google" or Google One Tap, Google receives that you are signing in to Earnings Feed. Google One Tap loads Google's script on some of our pages. Google's own privacy policy applies to Google.
At your direction. If you connect a webhook, Zapier, the Excel add-in, or an AI assistant through our MCP server, we send filing data to the destination you choose.
Legal or safety requirements.
We may disclose relevant logs or account data if we receive a valid legal request, need to enforce our terms, or must protect the service and our users from abuse or harm.Business transfers.
If we explore or complete a merger, financing, or acquisition, data may be shared under confidentiality. This policy (or its successor) will continue to govern your information.
We do not sell your personal information.
Your choices & rights
You have controls over how your data is used:
Account and communications. Update profile fields in the product. Manage marketing email preferences via in‑message links; we may still send essential service or security notices.
API access and keys. Generate, view, and revoke API keys from your dashboard. Monitor your API usage and rate limits. API keys are stored as one-way SHA-256 hashes for security.
Data rights (region-dependent).
Depending on your jurisdiction (for example, California, EU/EEA, UK, Switzerland), you may be able to request:- Access to the personal data we hold about you.
- Correction of inaccurate or incomplete data.
- Deletion of your personal data, subject to legal and operational requirements.
- Portability of certain information in a structured, commonly used format.
- Restriction of processing in some circumstances.
- Objection to certain processing based on legitimate interests.
To exercise these rights, contact us using the email at the end of this policy. We may need to verify your identity before responding.
You can opt out of marketing at any time and may object to certain processing by contacting us with your reasons.
Security & retention
We use appropriate technical and organizational measures to protect your data, including:
- Encryption in transit (HTTPS/TLS) and at rest for core data stores.
- Least‑privilege access controls and logging of administrative actions.
- Monitoring for abuse and anomalous system behavior.
- One-way hashing (SHA-256) of API keys with prefixes for user identification without exposing full keys.
Information tied to an active account is retained for as long as the account exists, as needed to provide the service and for legitimate business purposes (for example, security and legal compliance). Backups roll off on a scheduled basis (typically within 30 days) unless law or dispute resolution requires longer retention.
Data retention by service providers
- PostHog analytics and session recordings are retained according to PostHog's data retention policy (up to 7 years for analytics data).
- Clerk authentication data is retained for the life of your account.
- Stripe billing records are retained for 7 years to meet tax and compliance requirements.
- Sentry error and performance data is retained according to the configured Sentry retention policy.
- Application database backups roll off within 30 days.
Cookies and tracking technologies
We use cookies and similar technologies (including browser local storage) for:
- Authentication (Clerk) – To keep you logged in and maintain your session.
- Analytics (PostHog) – To understand product usage, performance, and user experience through session recordings and interaction tracking.
- Ad measurement (
ef_ad_google,ef_ad_microsoft) – First-party cookies, kept 90 days, that hold the click ID of the ad you arrived from. See Ad measurement. - Preference storage (local storage) – To save your settings such as timestamp display format locally on your device.
- Session management (Next.js) – To maintain your session state across requests.
You can control cookies through your browser settings. Disabling certain cookies may affect authentication and functionality. Session recordings can be reviewed or deleted upon request by contacting privacy@earningsfeed.com.
International transfers
Our database is in Canada (Montreal). Some providers, listed in the table above, process data in the United States, so your information may be processed outside your home jurisdiction.
When we transfer personal data across borders, we use appropriate safeguards (such as Standard Contractual Clauses or equivalent mechanisms) where required by applicable law. If your jurisdiction requires additional terms—like a Data Processing Addendum—reach out and we will provide the paperwork.
Updates
We may revise this notice when product or legal requirements change.
- The updated date at the top of this page shows when changes last took effect.
- For material changes, we will provide additional notice—such as an in‑product banner or email—before they become effective where required.
If you continue to use Earnings Feed after updates take effect, that use is considered acceptance of the revised policy.
Contact
Questions, data rights requests, Data Processing Addendum requests, or regulatory inquiries:
Email: privacy@earningsfeed.com
Mail: Lucent Enterprises Ltd., Attn: Privacy, 5307 Victoria Drive, Vancouver, BC V5P 3V6, Canada
Include your organization, the email address on your account, and the jurisdiction whose laws apply so we can respond efficiently.