FERG FINANCE / LEGAL
FERG Finance — Privacy Policy
Last updated: 16 November 2026
This Privacy Policy explains how MB Ferg, trading as FERG Finance ("FERG", "we", "us"), handles personal data when you use https://ferggate.com/, create an account, purchase or use the Chart Analyzer, save analyses, use supported AI-assisted conversations or contact support. We are established in Lithuania and offer services internationally. Our processing is subject to the EU General Data Protection Regulation (GDPR) where applicable, together with other applicable privacy laws.
Controller: MB Ferg, company code 308127814
Address: Laisvoji a. 5, Salakas, LT-32216, Zarasų r. sav., Lithuania
Privacy contact: info@ferggate.com
Website: https://ferggate.com/
This notice should be read with our Terms of Service and Cookie Policy. Buying a subscription or accepting the Terms does not constitute consent to optional analytics or marketing cookies.
In short: We use your account, chart and payment data to run the service. Auto analysis images may also be kept in a separate collection for up to 24 months to fix defects and to train and improve FERG's own models; you can opt out by emailing info@ferggate.com without losing access. AI visual review sends a sanitized photo to OpenAI and retains it in your owned chat, outside that separate collection. We do not sell your data. Optional analytics run only if you accept them.
1. INFORMATION WE HANDLE
Depending on the features used, the following personal data may be involved:
- Account and identity: email address, username, selected country, password hash, authentication or verification status, login-provider identifier where used, preferences, account role and records of relevant notices or agreements.
- Chart images and research: submitted screenshots and previews; information visibly included in an image; detected symbols, chart timeframes, geometry, reconstructed or inferred price series, output diagnostics, settings, calculation results, saved work and associated file or task identifiers.
- Conversations: text submitted to an available AI-assisted chat feature, the conversation context selected for processing, generated replies and related calculation or tool outputs. Do not assume text entered into a prompt is anonymous.
- Purchases and legal records: subscription and plan entitlements, usage credits and ledger events, payment-provider identifiers, amounts and currencies, renewal or cancellation events, invoices, taxes where applicable, consent or contract-version records, withdrawal notices and acknowledgements, support disputes and refunds. In the ordinary Stripe-hosted payment flow, we do not receive the full payment-card number or card security code.
- Technical and security data: IP-related request data, browser and device information, sign-in sessions, security and abuse events, file properties, processing-start and completion events, system diagnostics, error categories and related timestamps.
- Communications and optional measurements: support messages, feedback, correspondence and, only if permitted by the applicable choice and law, browser analytics identifiers and website-interaction information.
Required and optional information. An email address and authentication information are generally needed to create and secure an account; a submitted chart and relevant settings are needed for the requested reconstruction; and necessary transaction and billing information is needed to supply a paid plan and comply with applicable financial-record duties. Without the relevant information, we may be unable to provide that function or complete a purchase. Optional analytics and consent-based marketing are not conditions of purchasing the core Chart Analyzer service. We explain additional legally required information where it is collected.
Free trial without an account: when you open the Chart Analyzer without signing in while the free trial is available, we set an essential cookie with a random value and keep a keyed hash of that value, rather than the value itself, with a guest record, the number of free analyses and replies used, and records of the requests made, so that the free allowance cannot simply be reset. Charts, images, reports and chats created without an account are kept with that guest record and automatically erased about 24 hours after they are created. If you sign in or create an account in the same browser, we record a link between the guest record and that account; guest content is not moved into the account. The guest record, its counts, request records and any such link are deleted when the cookie's 180-day lifetime ends. Images submitted without an account are not added to the separate example collection described in section 4.
A chart screenshot or message may unintentionally show a name, trading-account number, email address, personal notification or another person's confidential information. Crop or redact information that is not needed for the requested analysis before submitting it; you are responsible for the information you choose to include in an image. Where we detect account numbers, names or similar details in an image, we may blur or remove them or delete the image, including before it is added to any improvement or training collection. Removing file metadata alone does not remove identifiable content visible in the image itself.
Affiliate programme: when you join, we associate your account with one public referral link and discount code and record your joining date. For qualifying purchases, we keep the buyer and affiliate account references, checkout and invoice identifiers, commission calculation, currency and refund or dispute adjustments needed to administer the programme, billing, abuse prevention and legal records. Affiliates see their own link, code and aggregated commission amounts, not customers' names, email addresses, charts or payment-card details.
For affiliate payouts, we send your verified account email, chosen payout country and internal programme reference to Stripe when you start payout setup. Stripe hosts the required identity and bank forms. We retain the connected-account reference, eligibility state, and transfer, reversal and payout amounts, currencies and statuses needed to administer and reconcile payments. FergGate does not store the bank-account or identity-document fields entered in Stripe’s hosted forms.
2. PURPOSES AND LEGAL BASES
We use data for the purposes described below and select a GDPR legal basis appropriate to the particular processing:
| Purpose | Principal basis | Examples |
|---|---|---|
| Create and secure an account; deliver requested analyses, saved work and AI features | Contract performance or steps requested before contracting (Art. 6(1)(b)) | Account identifiers, chart images, results, user-selected chat context |
| Provide the free trial without an account and keep its allowance from being reset or misused | Steps you request (Art. 6(1)(b)) and legitimate interests in preventing misuse (Art. 6(1)(f)) | Guest cookie hash, allowance counts, request records, IP-based limits, temporary charts and chats |
| Supply paid subscriptions and handle withdrawals, billing and customer requests | Contract performance and legal obligations (Arts. 6(1)(b), 6(1)(c)) | Entitlements, payment references, invoices, cancellation, complaints |
| Administer an affiliate account and attributed commission | Requested programme contract, necessary legitimate interests and legal obligations as applicable | Affiliate reference, qualifying purchase and commission/refund records; optional browser storage relies on consent |
| Comply with statutory accounting, tax and consumer record requirements | Legal obligation (Art. 6(1)(c)) | Accounting and legally required transaction records |
| Protect accounts, prevent fraud and misuse, investigate failures and defend claims | Legitimate interests, where necessary and balanced; legal duties where applicable (Arts. 6(1)(f), 6(1)(c)) | Security logs, error evidence, limited billing and incident records |
| Evaluate and improve reconstruction reliability, and train FERG's own models, using a selection of examples | Legitimate interests where a documented assessment supports necessity, proportionality and safeguards (Art. 6(1)(f)) | Selected images, geometry, diagnostics, results |
| Optional analytics or consent-based marketing | Consent where required (Art. 6(1)(a)) and applicable electronic-communications rules | Consented GA4 identifiers or marketing preference |
A legitimate interest is not an unconditional permission to collect everything technically available. Where we rely on it, we must consider necessity, data minimisation, reasonable expectations and the effect on individuals, including their right to object. The contractual legal basis does not replace consent required for non-essential browser tracking.
3. CHART-IMAGE PROCESSING
Auto analysis processes submitted chart images locally using FERG's server-side reconstruction software. Selecting Auto analysis does not send that image to an external general-purpose AI provider. AI visual review is a separate selected mode: FERG removes file metadata, normalizes the image and sends the sanitized photo and your question to OpenAI through the selected AI model. An empty question requests a brief visual overview. Visible personal or confidential information inside the image is not removed merely by stripping file metadata.
A submitted image may be analysed, rendered to your account, associated with reconstructed or estimated data and retained in saved history according to the relevant feature. The service may record processing status, file characteristics, quality warnings, a reconstruction-start event and whether a credit was consumed or restored. Such information helps supply the requested service, identify duplicate deductions and investigate technical faults. A log entry alone does not determine whether a customer has a valid statutory claim.
We restrict access to saved and diagnostic content according to the operational purpose and necessary authorisations. The security of a stored image does not turn personal information shown in that image into anonymous data.
4. QUALITY EXAMPLES AND MODEL TRAINING
When FERG's separate private example-collection function is enabled and available, a selection of submitted chart images, previews, relevant reconstruction results, diagnostic information and an account link may be retained independently of the saved analysis visible in your account. This collection is used to investigate reconstruction defects, evaluate technical changes, and train, fine-tune and evaluate FERG's own chart-reconstruction and analysis models, which we then make available to users as part of FERG services. It is not used for publication or sale of images, and we do not disclose it to third parties for their own model training.
Photos submitted for AI visual review are retained with their owned conversation and are not added to the separate reconstruction improvement or training collection described in this section.
Deleting a saved analysis from your account does not necessarily remove a copy already placed in the separate improvement collection. We assess valid erasure and objection requests across applicable locations, subject to any lawful exception such as an active claim or legal obligation. We do not describe an image as anonymous merely because its file metadata has been stripped.
Examples in this collection are kept for up to 24 months from collection and are then deleted or genuinely de-identified, unless a longer period is needed for an active defect investigation, a legal claim or a legal obligation. If an example is deleted or you object, we stop using it for further training and evaluation; a model already trained is not necessarily retrained solely because one example was removed. Automatic enrolment and opt-out: examples are included in model training by default. You can opt out at any time, free of charge and without giving a reason, by emailing info@ferggate.com from your account email. Opting out stops use of your future and existing examples for further training and does not affect your access, credits or plan. Examples collected before this notice was published are not used for model training unless we have a lawful basis for that use, such as your consent. Requests concerning a particular image are assessed across both saved history and this separate collection. You may contact us to request access, erasure or to object to this legitimate-interest processing.
5. AI-ASSISTED CONVERSATIONS
When an AI-assisted feature is used, OpenAI receives the message and relevant context needed to answer, including selected image content for AI visual review, relevant earlier messages, measured observations from attached Auto reports, calculation-tool outputs and relevant saved account memories when enabled. The current visual photo can be sent again for follow-up questions; earlier visual photos are sent when explicitly selected within that conversation. Enabling memory does not automatically send every saved photo.
When the assistant uses web search, search terms and information needed for that search are sent through OpenAI's web-search service. A query can reflect information you entered; do not assume confidential details are automatically removed before searching. Search results and source links may appear in saved replies.
For coding work, uploaded or selected saved source files, coding instructions and execution results can be sent to OpenAI. Code runs in temporary workspaces hosted by OpenAI rather than on FERG's production server. FERG requests deletion when processing finishes and configures a 20-minute idle expiry as a cleanup fallback. Provider retention can differ from workspace availability. Files exported back to the conversation remain in FERG account history until deleted under the retention rules below.
Account memory is optional and off until you enable it in Settings. It stores facts and preferences you explicitly save or ask to remember in FERG's account database and can send relevant saved facts to OpenAI in other chats. You can view, add and remove memories in Settings. Turning memory off disables it for subsequent requests but does not delete saved facts. Deleting a chat does not itself delete a separately saved memory, and deleting a memory does not erase the original chat message. FERG does not import memory from your ChatGPT account.
Please avoid including passwords, payment credentials, identity documents, sensitive personal information or confidential third-party information in messages or source files. Provider handling, safeguards, retention and international-transfer arrangements depend on the actual service and contractual settings in place. We do not promise that the external provider retains no information in every circumstance.
Conversations and their associated outputs may remain in your account history under the retention rules below. A continued conversation may use its own relevant prior context and a compacted representation of earlier conversation content. Optional account memory is separate from conversation history and does not provide unlimited recall of every chat. Records from a retired browser extension may also remain in historical account content where lawfully retained.
Normalized visual photos are stored once with their account-owned chat, and messages refer to those photos. The photo, question, reply and relevant source identifiers remain in saved chat history for reopening and follow-up questions. Deleting that conversation removes its active stored photo content under the retention rules below; applicable backup and legal-retention exceptions remain unchanged.
6. RECIPIENTS AND SERVICE PROVIDERS
Access to personal information is limited to authorised personnel and service providers where needed for the relevant purpose. Recipients may include:
- infrastructure, hosting, security, website-operation and business-email providers;
- Stripe for checkout, subscriptions, financial records, payments and disputes, including processing it undertakes under its own legal obligations;
- Google for Google sign-in when selected, and separately Google Analytics 4 only where optional analytics is lawfully enabled;
- OpenAI when you use a supported AI-assisted feature that sends relevant information to that provider; and
- professional advisers, technical incident investigators, payment-dispute participants and competent authorities where disclosure is necessary and lawful.
A provider may act as our processor for some services or as an independent controller for others. Relevant processor agreements and legal safeguards apply according to those roles. We do not sell private chart images, chats or personal data as a marketing dataset.
Trustpilot reviews. The website footer shows Trustpilot's review widget. When the footer comes into view, your browser loads it from Trustpilot A/S, which receives your IP address, browser details and the page address. The widget sets no cookies on ferggate.com. Trustpilot handles this data under its own privacy policy.
7. TRANSFERS OUTSIDE THE EEA
Some providers may process data outside the European Economic Area, including in the United States. Where the GDPR's international-transfer rules apply, we must use an appropriate mechanism, such as a relevant adequacy decision or approved standard contractual clauses and supplementary measures where required. The exact mechanism depends on the recipient, data and contractual arrangements rather than one blanket rule for all providers.
The main providers involved and the safeguards we rely on are:
| Provider | Purpose | Where data may be processed | Transfer safeguard |
|---|---|---|---|
| Stripe | Payments, subscriptions, invoices, disputes | EEA and the United States | EU standard contractual clauses and/or EU-US Data Privacy Framework, as stated in Stripe's data processing terms |
| Sign-in; optional analytics | EEA and the United States | Same, as stated in Google's data processing terms | |
| OpenAI | AI-assisted chat and selected photo review | United States and other countries where it operates | Same, as stated in OpenAI's data processing addendum |
| Hosting, security and email providers | Running the service | Depends on the provider; where outside the EEA, the same safeguards apply | Same |
You may contact info@ferggate.com to request further information about safeguards relevant to your data and a copy of the applicable protections where available, subject to lawful redactions for confidential information.
8. ANALYTICS, COOKIES AND DIRECT MARKETING
We use essential authentication, session and security storage to provide requested functions. Optional analytics, where enabled, may use Google Analytics 4 and associated browser identifiers only with a lawful affirmative choice. Rejecting optional analytics does not prevent normal access to the purchased Chart Analyzer.
Optional analytics are intended to measure page and interface usage, not the contents of private analyses. We do not intentionally send account emails, raw prompts, full payment details or chart contents as optional analytics events. The Cookie Policy explains the relevant browser storage, cookies and how to accept, reject or withdraw an analytics choice. A website page measurement may occur when viewing a workspace if optional analytics are enabled and consented to; consent does not make sensitive event content suitable to collect.
Where marketing messages require consent, we rely on the appropriate permission and provide a way to withdraw it. A customer is not required to consent to optional tracking simply to purchase the core service.
If you permit optional website analytics, FERG also maintains a five-minute count of consenting browsers using a random first-party identifier. Only a keyed identifier hash and the most recent server receipt time are stored for that count, without account identifiers, IP addresses, browser fingerprints, page addresses, charts or messages. Tabs and refreshes share the identifier; it expires after 30 minutes without a successful heartbeat and is removed or replaced when the website next runs. Withdrawing analytics clears the identifier and requests deletion of its server record. If deletion cannot arrive, the record is excluded after five minutes and remains pending bounded cleanup. This count covers consenting browsers with supported storage, not every visitor or unique person.
Optional affiliate referral storage is separate from analytics. With your permission, it remembers the latest valid affiliate link for up to 30 days. An explicitly entered affiliate discount code takes priority and works without that cookie. Without storage permission, a referral in the Plans address can still accompany the current requested checkout. Cookie preferences allow each optional purpose to be accepted or withdrawn separately; the Cookie Policy explains the storage and completed-purchase record distinction.
9. STORAGE PERIODS AND DELETION
Data is retained only as long as necessary for the applicable purpose, the contract, a lawful claim or a legal obligation. Different categories have different criteria; not all records disappear when a subscription is cancelled.
| Category | Current retention criteria and important distinctions |
|---|---|
| Account and saved workspace | Kept while the account and retained research are needed, unless deleted or another legal ground justifies limited retention. A subscription cancellation alone does not delete saved history. |
| Optional account memory | Saved facts remain until you remove them or the account's active data is erased. Disabling memory keeps the saved facts available for management. Applicable backup, legal-retention and original-conversation retention rules remain separate. |
| Free trial without an account | Charts, images, reports and chats are automatically erased about 24 hours after they are created. The guest record (a keyed hash of the cookie value), allowance counts, request records and any link to an account are deleted when the 180-day cookie lifetime ends. |
| Temporary processing jobs and technical diagnostics | Technical cleanup applies to transient processes; limited incident, security and credit-ledger evidence may remain while needed for investigation, duplicate-charge protection or lawful claims. |
| Separately retained image examples | Kept for up to 24 months, then deleted or de-identified, unless needed for an active investigation, legal claim or legal obligation. |
| Billing, invoices, taxes, contract acceptance and withdrawal records | Kept for legally required accounting, tax, consumer and contract periods, and any justified claim period. Deletion on demand may be restricted by law. |
| Affiliate accounts, attribution and commission records | Kept while needed to administer the programme and for applicable accounting, fraud-prevention and legal-claim periods. Withdrawing browser-storage consent stops future remembered attribution; it does not rewrite a completed transaction or required financial record. |
| Support correspondence and security logs | Kept for the specific support, fraud, security or legal purpose, with appropriate minimisation. A business mailbox may retain relevant records after an application queue clears. |
| Optional analytics | Browser identifiers and provider event data follow the actual consent, cookie settings, provider configurations and applicable retention rules; browser-cookie expiry is not equivalent to deletion of provider-held records. |
| Backups | Retained within justified security and recovery cycles; erasure from active systems may not instantly remove every inaccessible backup. Restores must take account of applicable erasure requirements. |
We do not claim that every personal record is automatically deleted after one fixed period, nor that removing an account-history item instantly erases a separately retained example, an invoice, a business mailbox message or every backup. Where you exercise a valid privacy right, we consider all relevant locations, applicable exceptions and required follow-up actions.
10. YOUR RIGHTS
Depending on the circumstances and applicable law, you may request access, rectification, erasure, restriction of processing and portability of eligible personal data. You may object to processing based on legitimate interests, including use of your examples for product improvement and model training, and withdraw consent for optional processing at any time without affecting lawful processing carried out before withdrawal. You also have rights concerning certain automated decisions if such decision-making becomes applicable.
Send requests to info@ferggate.com. No particular form is required. We may require only proportionate information necessary to verify your identity and protect other users. Under the GDPR, we generally respond without undue delay and within one month, with any permitted extension explained within the initial period. If we cannot fully erase specific information because a legal duty or other permitted exception applies, we will explain the relevant basis.
You may complain to Lithuania's State Data Protection Inspectorate (VDAI) at https://vdai.lrv.lt/ or another competent data-protection authority. You do not have to obtain our approval before exercising a supervisory complaint right.
11. SECURITY AND AUTOMATED RESEARCH OUTPUTS
We use technical and organisational safeguards appropriate to the risks, such as access restrictions, authentication and security controls and protection of credentials. No online service can guarantee absolute security. We investigate incidents and fulfil applicable legal notification duties where required.
Chart reconstruction, indicators and AI-generated research are technical outputs, not assessments determining a person's creditworthiness, employment eligibility or access to financial services. We do not present current chart outputs as exclusively automated legal or similarly significant decisions about an individual within the meaning of GDPR Article 22. If future features introduce such decisions, their compliance and disclosure requirements will be assessed separately.
12. CHANGES AND CONTACT
Do not upload other people's personal or sensitive information unnecessarily. Tell us if you believe such information has been improperly included.
We update this notice when actual processing, providers, purposes or legal duties change. A new paragraph alone does not authorise an incompatible purpose or substitute for legally required consent. Material changes will be communicated in accordance with applicable law.
Data controller: MB Ferg · Company code 308127814
Laisvoji a. 5, Salakas, LT-32216, Zarasų r. sav., Lithuania
Privacy contact: info@ferggate.com
Related notice: https://ferggate.com/cookie-policy
