Privacy Policy
PolskiThis Policy explains how personal data is handled when you visit WhaleFollow, create an account, use research features, or contact support.
Controller and scope
The controller of personal data described in this Policy is Siarhei Yahavets, Franciszka Klimczaka 16/101, 02-797 Warszawa, Poland.
Privacy questions and requests may be sent to support@whalefollow.com. You may also write to the postal address above. These contact routes are available to account holders, visitors, and people described in public filings; you do not need an account to use them.
This Policy applies to whalefollow.com, the WhaleFollow web application, account-only research features, support communications, and personal data about people identified in the public filings we analyse. The controller operates from Poland; GDPR rights described here are not limited to EU residents. Independent providers also have their own privacy notices, linked below.
Personal data we process
Depending on how you use WhaleFollow, we process the following categories:
- Account and authentication data: email address, authentication information (including a password handled by Clerk for password sign-in), first and last name if you provide them or they are received through your chosen sign-in provider, any additional profile details you choose to provide, Clerk user and session identifiers, account status, access role, creation and update dates, the time of acceptance of legal documents, and authentication or account-security events. If you choose Sign in with Google, this also includes the Google account identifier, verified email address, display name, and profile image made available through that connection, where available.
- Research preferences: watchlist tickers and related creation and update timestamps, a randomly generated local account identifier, and related account-feature records.
- Technical and security data: IP address, browser and device information, operating system, requested URL or API resource, timestamps, response status, and diagnostic or security logs generated when the Service is used.
- Server-side traffic statistics: information derived from server requests, including requested paths, referring page addresses, browser and device categories, request counts, estimated unique visitors, response times, status codes, and transferred data volumes. IP addresses are processed in access logs. Geolocation enrichment is disabled.
- Support and complaint data: your email address, message, and any information or attachments you choose to provide when contacting us.
- Interface preference: whether the navigation sidebar is collapsed, kept only in the current page memory. It is not saved as a persistent preference or sent to our server.
Where data comes from
Personal data is obtained:
- directly from you when you register, configure account features, or contact support;
- from your browser or device when it communicates with the Service;
- from Clerk when it authenticates your account and session;
- from Google, through Clerk, when you choose Sign in with Google; and
- from WhaleFollow systems when they create watchlist, diagnostic, or security records.
Public filings can contain personal data even when the person has never used WhaleFollow. That processing is described separately below, rather than treated as account data.
People identified in public filings
We obtain information from public SEC filings, including Form 4 and Form 13F, and related financial data supplied by Twelve Data. It can identify reporting insiders, officers, directors, owners, or investment managers. Categories include names, professional roles, issuer or manager relationships, filing identifiers and dates, and reported holdings and transactions, including securities, quantities, prices, values, and transaction types. Source filings may also contain business contact details and other information included by the filer.
We use this information to organize and verify filings, present reported activity, and calculate research indicators. The basis is our and our users' legitimate interest in understanding public securities disclosures under Article 6(1)(f) GDPR, subject to balancing the affected person's rights. Public availability does not remove GDPR protection. These people are not required to provide data directly to WhaleFollow or to create an account.
Relevant names, roles, and reported transactions are displayed to people accessing the research features. Hosting and infrastructure providers process the underlying records; advisers and authorities may receive them where necessary as described below. Retention depends on the reporting periods covered by the relevant research feature and whether a record is still needed to reproduce, verify, or correct an analysis that uses it. Once those purposes no longer require an identifiable record, we retain it only for a specific legal duty or claim under the criteria below. Public availability of the original filing does not by itself justify indefinite retention. Applicable erasure, restriction, and objection rights remain available.
If a filing or our presentation identifies you, you may request access, correction, restriction, erasure, or object to processing based on your particular situation using the contact details above. Identify the relevant person, filing, or page; an account email is not required. We will assess the request and explain any legal reason for retaining a record. We can correct our own records, but cannot alter the original SEC filing. The transfer, security, and rights sections of this Policy also apply to these records.
How we provide this information. Where individually informing people identified in public filings would be impossible or involve disproportionate effort, we rely on Article 14(5)(b) GDPR and make this information publicly available through this Policy. We assess this taking into account the number of people concerned, the availability and reliability of contact details, the effort required to reach them, and the potential impact on their rights. Public availability of the source filings does not, by itself, exempt us from providing notice. Where no exception applies, we provide individual notice as required. You can exercise the rights described above without creating an account.
Why we process data
We process personal data only where a legal basis applies:
- To provide the Service and perform our agreement under Article 6(1)(b) GDPR: creating and authenticating an account, keeping you signed in, delivering your watchlist, handling support needed to perform our agreement, and communicating material service or terms changes.
- For legitimate interests under Article 6(1)(f) GDPR: we use necessary technical data, such as your IP address and browser request information, to deliver the public pages and images you request. We also process data to protect accounts and systems, prevent fraud and abuse, diagnose faults, and maintain reliability. Limited account and event records help us prevent restoration of a deleted account through old credentials or repeated system events and handle repeated deletion notifications safely. Other purposes are enforcing the Terms, understanding individual support incidents, responding to general enquiries (including from people without an account), and establishing, exercising, or defending legal claims.
- To comply with law under Article 6(1)(c) GDPR: responding to binding legal requests, preserving records where required, and fulfilling data-protection or consumer-law obligations.
Our legitimate interests include making research content accessible and operating a reliable, secure service. We consider the impact on users and do not use this basis where their rights override those interests. This basis does not authorize optional tracking or device storage that requires consent.
We use account details and watchlist choices to operate, secure, and support the Service. We do not use them to train models, create marketing profiles, or supply marketing partners with data. This statement concerns your account and use of the Service; research calculations using public filings are described separately above, and provider processing is explained below.
We do not currently send marketing newsletters or use advertising trackers. Where a future optional purpose requires consent under Article 6(1)(a) GDPR, we will request it separately before processing begins. Accepting Terms or reading this Policy does not provide that consent.
Server-side analytics
We analyse server access logs using Coolify Traffic Analytics (Sentinel) on our hosted infrastructure. This helps us understand which pages and resources are requested and identify errors and performance problems. Visitor numbers are estimates based on server requests, not an exact count of people.
The legal basis is our legitimate interest in evaluating use of the Service and improving its reliability and usability under Article 6(1)(f) GDPR, balanced against your rights and freedoms. We do not combine these statistics with account profiles or watchlist contents, or use them for advertising profiles or tracking across unrelated websites.
Our server-side analytics does not use analytics cookies, browser storage, or analytics scripts. IP addresses are still processed on the server, including to estimate unique visitors. Analytics records remain on our hosted infrastructure and are not sent to an external analytics platform. Access is limited to authorized administrators and the providers described below as necessary to operate the infrastructure.
You may object to this processing on grounds relating to your particular situation by emailing support@whalefollow.com; no account is required. The retention rules and the right to object described below apply to these records.
Required and optional data
To register, you need an email address and authentication information for your chosen sign-up method, including a password if you choose password sign-up. A first name, last name, and username are not required. Without the required information, you may still view public pages, but you cannot complete registration or use account-only features. We also process necessary session and security information to operate and protect accounts. Profile names and other additional profile details, as well as watchlist choices, are optional. If you choose Sign in with Google, we may receive the profile information described above. You choose whether to contact support; the information needed to resolve an enquiry depends on the request.
Service providers and recipients
Personal data is disclosed only as reasonably necessary to:
- Clerk, Inc., which provides account registration, authentication, session management, and related security. Clerk acts as our processor for personal data it handles on our behalf. Its Data Processing Addendum also provides for an independent controller role for certain account information, including end-user account information. Clerk describes its own processing in its Privacy Policy.
- netcup GmbH, our hosting provider in Nuremberg, Germany, and infrastructure, networking, and security providers needed to operate the Service; they handle hosted records and connection or diagnostic data;
- Namecheap, Inc., which provides Private Email for our support mailbox at support@whalefollow.com. It processes sender and recipient addresses, message contents, attachments, and technical delivery data on our behalf to receive, store, and send support correspondence, under its Data Processing Addendum. You may also use our postal address for privacy requests;
- Google, which acts as an independent identity provider when you choose Sign in with Google: it receives the authentication request and makes basic identity data available to Clerk for account creation and sign-in. Google describes its own processing in its Privacy Policy;
- professional advisers where necessary for legal, security, accounting, or compliance support; and
- courts, regulators, public authorities, or other parties where disclosure is legally required.
Company logos are delivered from our own domain through a server-side cache. Our server fetches images from providers such as Twelve Data and Financial Modeling Prep without forwarding your IP address, cookies, authentication details, or browser request headers. Image providers receive our server's connection information instead of a direct request from your browser.
We do not sell personal data, share it for cross-context behavioural advertising, provide it to advertising networks, or permit third parties to use it for their own direct marketing through WhaleFollow.
International data transfers
WhaleFollow uses netcup hosting in Nuremberg, Germany, but some providers may process data outside the European Economic Area, including in the United States. A provider’s address does not by itself identify every processing location.
Clerk states in its Data Processing Addendum that eligible transfers to the United States are covered by its certification under the EU-U.S. Data Privacy Framework and, where that framework cannot be used, by the European Commission's Standard Contractual Clauses. Google describes its EU-U.S. Data Privacy Framework participation and other mechanisms in its data-transfer notice. These mechanisms apply only to covered recipients and processing; hosting in Germany does not mean that all providers process data solely in the EEA.
Namecheap states that its Private Email servers are located in the United States. For transfers of support correspondence from the EEA to Namecheap in the United States, we rely on the European Commission's Standard Contractual Clauses incorporated into Namecheap's Data Processing Addendum.
You may contact us for information about the recipients, locations, and safeguards relevant to your data, including a copy of applicable safeguards with necessary protections for confidential information. Provider terms, certifications, and processing locations may change, so this section will be updated when a material change affects WhaleFollow users.
How long we keep data
We use the following retention criteria:
- account and authentication data are kept while the account remains active and as needed to close it securely;
- watchlist data is kept while you use the feature, until you remove an item or we complete an applicable erasure request;
- diagnostic and security logs other than the Traefik access logs and Docker container logs described below are retained for the relevant operational or security check, investigation of a fault or incident, and verification of corrective measures. Once those activities are complete and the records are no longer needed for them, further retention is limited to evidence needed for a specific legal duty or claim under the separate criteria below;
- ordinary support correspondence is kept while the request is open and for six calendar months after closure, to handle follow-up questions about the same issue. We delete it during the next manual monthly review, no later than seven calendar months after closure, including associated attachments and copies in our sent mail and trash. An applicable erasure right may require earlier deletion;
- complaints, privacy requests, and records relevant to a specific dispute or binding legal duty are assessed separately. We retain only the evidence needed for the relevant duty or claim, for the period that applies to it, and delete the rest under the ordinary support rule. The possibility of an unspecified future dispute does not by itself justify keeping all correspondence indefinitely.
Server-side analytics keeps hourly statistical records for 30 days and daily statistical records for 395 days. Intermediate minute-level records are consolidated into hourly records, with a maximum configured retention of 48 hours. These periods also apply to any personal data retained within the corresponding statistical records.
Raw Traefik proxy access logs, which may contain IP addresses and other request data, are stored separately from those statistics. In our current configuration, the active log file is checked every 60 seconds. If it exceeds 20 MiB, its contents are archived and the active file is cleared. We keep the five most recent archives; when a new archive would exceed that limit, the oldest archive is deleted.
Technical Docker logs for the Traefik and Sentinel containers also rotate by size, with a configured threshold of 10 MB per file and a maximum of three log files per container, including the active file. Older files are removed as new rotations occur.
These rotation rules do not automatically delete entries based on their age. The time an entry remains depends on the volume of new log data; at low volumes, entries may remain for several months or longer. No fixed maximum retention period is configured for these raw access and container logs. The statistical retention periods above, including the 30-day period for hourly statistics, do not apply to these logs. An applicable erasure or restriction right may require earlier action.
Account deletion and remaining data
Delete your account in account settings or contact support. After processing confirmation from Clerk, we automatically remove associated watchlist records and block further access to that account. No separate email is needed. Signing out alone does not delete an account. Contact support if the process fails.
Limited account and event identifiers and timestamps are retained to prevent a deleted account being recreated with old credentials and to handle repeated deletion notifications safely. These can still be personal data. We manually review the need for them monthly and delete a record when the associated credentials can no longer restore access, repeated events can be handled safely without it, and there is no separate legal duty or need for evidence in a specific dispute.
Backup copies may contain data from before account deletion and are not erased by account closure alone. We manually review which copies are still needed for recovery monthly and delete unnecessary copies, including copies superseded by adequate replacements. Before restored data is returned to ordinary use, we manually reapply account deletions made after the backup was created. Account closure alone does not modify an older backup. Necessary evidence for a specific dispute or legal duty follows the separate criteria above. A valid erasure request may require earlier action.
You may also ask support to handle a broader erasure request. We will explain what was deleted, what remains, its legal basis, and the retention period or criterion. Account deletion does not automatically erase correspondence or every provider record; the relevant periods and rights described in this Policy apply to them.
Cookies and local storage
Clerk supplies cookies used for authentication and session security. Blocking the cookies needed for your requested sign-in session may prevent sign-in or account-only features from working.
Some authentication cookies remain in your browser between visits. The expiry of a sign-in token or the end of a signed-in session does not necessarily remove every cookie. You can sign out to end your current session and use your browser settings to remove stored cookies.
- Session token —
__sessionand suffixed variants: used on the application domain to authenticate requests. The browser cookie is set for up to one year from its latest update and may be renewed during use, subject to earlier browser removal. The token inside expires much sooner and must be refreshed for continued access; a stored cookie does not grant a year of account access. Signing out removes this session cookie. - Client and session freshness —
__clientand__client_uat:__clientidentifies the browser client on.clerk.whalefollow.com;__client_uatand its instance-specific variants provide client freshness information on.whalefollow.com, including its subdomains. These cookies are set when Clerk loads on the site, including before you sign in or open the sign-in form. In the current production configuration, Clerk requests a lifetime of 3,650 days. Browsers may impose a shorter limit: Chromium limits it to 400 days from each setting. Clerk may set these cookies again during use, including on page reload, renewing their expiry subject to browser limits. They can outlast an individual signed-in session and may be removed earlier by you or your browser. - Clerk infrastructure protection —
__cf_bmand_cfuvid: Cloudflare sets these cookies on.clerk.whalefollow.comto protect Clerk's authentication infrastructure.__cf_bmhelps detect automated traffic and expires after 30 minutes of inactivity; continued activity may renew it._cfuviddistinguishes visitors sharing an IP address for request rate limiting. It is a browser-session cookie with no persistent expiry; browser session restoration may preserve it after a restart. Both can be set when the browser contacts Clerk as the site loads, before sign-in. These are security cookies, not website analytics cookies. - Active context —
clerk_active_context: identifies the active authentication context on the application domain. It has no persistent expiry and is a browser-session cookie, removed by Clerk on sign-out. Browser session-restore features can preserve session cookies after a browser restart.
Clerk also uses temporary authentication-handshake cookies and browser storage to coordinate authentication between tabs. Necessary authentication storage is used to provide the sign-in service you request; it is not permission for optional tracking. Cookies may include an instance-specific suffix. Clerk describes these mechanisms in its cookie documentation. Clerk receives authentication data as described under Service providers and recipients.
If you choose Sign in with Google, your browser is redirected to Google, where Google may use cookies under its own terms to authenticate your Google account. WhaleFollow does not control cookies placed on Google’s domains.
The sidebar preference is stored only in page memory. It remains available during navigation within the application and resets when the page is fully reloaded or closed.
Server-side analytics does not use analytics cookies or browser storage. Objections to server-side processing can be submitted using the contact details above.
We do not use advertising trackers. This description does not cover every operation on Google's own domains. Accepting the Terms, reading this Policy, or merely visiting the site does not constitute consent to device access or storage where consent is required.
Your privacy rights
Your right to object: you may object at any time, on grounds relating to your particular situation, to processing based on Article 6(1)(f) GDPR. This also applies to people described in public filings. Following an objection, we will stop that processing unless we demonstrate compelling legitimate grounds that outweigh your interests, rights and freedoms, or the processing is necessary for establishing, exercising or defending legal claims.
Subject to the conditions in applicable law, you may request access to your personal data, rectification, erasure, restriction of processing, data portability, or object to processing based on legitimate interests. Where processing is based on consent, you may withdraw consent at any time without affecting earlier lawful processing.
Send a request to support@whalefollow.com. Use your account email where possible, but no account is required. If you cannot access it, contact us to arrange another proportionate way to verify identity. We request additional information only where reasonably needed and do not routinely require identity documents.
We respond without undue delay and within the applicable statutory time limit, normally no later than one month after receipt. If a lawful identity-verification pause is necessary, we will request the information promptly and explain the effect on timing. For complex or multiple requests, the GDPR may allow up to two further months; we will give the reason within the initial month.
Requests are normally free. If a request is manifestly unfounded or excessive, we may charge a reasonable fee or refuse to act where the GDPR permits, and must be able to justify that decision. If we do not act on a request, we will explain the reasons and your right to complain to a supervisory authority and seek a judicial remedy, without undue delay and within one month of receipt. You may also ask us to review our response.
Where Article 19 GDPR requires it, we notify recipients of rectification, erasure, or restriction of processing, unless this proves impossible or involves disproportionate effort. On request, we will identify those recipients. This does not allow us to change the original SEC filing.
You may lodge a complaint with the President of the Personal Data Protection Office in Poland (UODO), ul. Stanisława Moniuszki 1A, 00-014 Warszawa, or through the Polish supervisory authority. You may also contact the competent supervisory authority in your country of residence or work where applicable.
Depending on where you live, additional privacy rights may apply. WhaleFollow will assess verified requests under the law that applies to the requester.
U.S. residents and other jurisdictions
Depending on the applicable law and its scope, U.S. residents may also have rights to confirm processing, know or access data, receive a portable copy, correct or delete data, and opt out of sale, targeted advertising, or certain significant profiling. These additional rights apply where the relevant law covers WhaleFollow and your data. You may use the request routes above regardless of where you live.
We do not sell personal data or share it for cross-context behavioural advertising, and do not use it for targeted advertising or profiling that makes legally or similarly significant decisions about consumers. Accordingly there is no such processing to opt out of at present. The Service does not change its necessary processing in response to a browser Do Not Track signal. A Global Privacy Control signal does not disable necessary authentication or security; any applicable obligation to honour an opt-out signal remains unaffected.
If we decline a request, you may seek a review by replying to our response or writing to the same email or postal address; "Privacy appeal" is an optional subject. Explain which decision you challenge. We will give a reasoned response and observe any applicable appeal deadline and regulator-contact requirements. An authorized agent may submit a request where permitted; we may verify the authority and identity in a proportionate manner. We do not discriminate for exercising a privacy right. If another applicable law gives you additional rights or an earlier deadline, those protections remain available.
Automated processing
Automated calculations summarize reported holdings and transactions and generate security-level research indicators. They may use personal data from public filings. They are not used to decide a person's creditworthiness, employment, insurance eligibility, or investment suitability, or to make decisions about a user with legal or similarly significant effects within Article 22 GDPR. You can challenge inaccurate personal data used in this research through the rights procedure above.
Security
We use reasonable technical and organizational measures designed to protect personal data, including access controls, encrypted connections, and service monitoring. No internet service can guarantee absolute security. If you believe your account or data may be at risk, contact support promptly.
Age requirement
WhaleFollow is intended only for users who are at least 18 years old. We do not knowingly offer accounts to children. If you believe a person under 18 has created an account or provided personal data, contact us so the situation can be investigated and appropriate action taken.