FinHelm Privacy Notice

This notice describes how FinHelm Corp ("FinHelm," "we," "us") handles information in connection with finhelm.ai, the FinHelm application and the FinHelm MCP connector (together, the "Service"). It is a notice. It is not incorporated into the FinHelm General Terms of Service, and it does not create contractual rights or obligations.

1. Who this notice covers

FinHelm provides the Service to businesses. This notice covers information about the people who use the Service on behalf of a business, visitors to finhelm.ai, and people who contact us. The Service is not intended for individuals under 18. If FinHelm learns that an individual under 18 has provided personal information through the Service, FinHelm will delete it.

2. Information we handle

Account information. When a business creates an account, we handle the email address, name and authentication information of each person who uses the account, and the business name.

Customer Data. The General Terms define Customer Data as information a customer enters into the Service, such as budgets, drivers, assumptions, scenarios and configuration, and information FinHelm accesses from a connected financial system under the customer's authorization. Customer Data may include personal information about the customer's own employees, vendors or customers where the connected financial system holds it.

Request information. When a browser loads finhelm.ai or the Service, FinHelm's hosting provider receives the information a browser sends in order to deliver a page, including internet protocol address, browser and device type, the address requested, and request timing.

Communications. When you contact us, we handle the information you provide.

Public assessment. The public assessment on finhelm.ai is not currently available. It produces no reading and does not ask for an email address or financial information. Where a visitor previously saved an assessment result with an email address, that saved result is part of FinHelm's lead records and is handled as described in this notice.

3. How we use information

We use information to provide, secure, support and improve the Service; to measure how finhelm.ai and the Service are used and how visitors find them, as described in Section 9; to operate accounts and billing; to respond to requests; and to comply with law. The scope of what FinHelm may do with Customer Data is set by Section 7 of the General Terms, which limits FinHelm's rights and prohibits sale, advertising, training of generally available models, and use for purposes beyond the Service. FinHelm does not sell, rent or trade personal information.

4. Connected financial systems

FinHelm reads from a connected financial system only under an authorization the customer grants through that system's own authorization process. FinHelm's access is read only. FinHelm does not write to, modify or post entries in a connected financial system.

Where a customer authorizes a planning workflow that derives inputs from a connected financial system, FinHelm may retain the normalized periodic actuals and provenance records that workflow requires. FinHelm does not copy or retain all information available in a connected financial system.

A customer may revoke FinHelm's authorization at any time through the applicable provider, or through the Service where FinHelm makes that functionality available. On revocation FinHelm stops using the revoked authorization.

FinHelm currently connects to QuickBooks Online.

5. Service providers

FinHelm uses the following providers to operate the Service. This is the canonical list; the Security page refers to it and does not keep a separate list.

FinHelm gives at least 30 days' notice before adding a new service provider that processes information FinHelm accesses from a connected financial system. To receive these notices, contact privacy@finhelm.ai.

Providers of connected financial systems, such as Intuit for QuickBooks Online, act under the customer's own relationship with them. This does not describe processing FinHelm commissions on its own behalf.

6. Where information is processed

FinHelm operates from the United States. FinHelm's server functions on Vercel are deployed in a United States region, FinHelm's account sign-in service on Amazon Web Services is in the United States, and FinHelm's PostHog project is in the United States. Vercel receives and routes requests through its global network, and FinHelm's routing middleware for signed-in application pages is deployed in Vercel regions inside and outside the United States, so part of a request may be handled outside the United States. Other service providers listed in Section 5 process information on their own infrastructure under their own terms. Self-service access to the Service is offered only to businesses organized in, or with their principal place of business in, the United States. FinHelm makes no representation about compliance with the law of any jurisdiction outside the United States.

7. Retention

FinHelm retains account information while the account is active. Within 30 days after an account is closed, FinHelm deletes the account information associated with it, except information FinHelm must keep to comply with law or a legal hold. Authentication and authorization audit logs follow the separate retention period described below. Customer Data is handled during the term as described in Section 7 of the General Terms. Content a customer authors in the Service, such as budgets and driver sets, is retained until it is deleted or the account closes. After termination, Section 7.6 of the General Terms governs: FinHelm has no obligation to retain Customer Data or to provide a copy of it, and where FinHelm retains Customer Data after termination it may use it only to secure it, to maintain it in ordinary backup cycles, to delete or de-identify it, to comply with law, to resolve disputes and to enforce the General Terms. Retention differs by record type and by the system that holds the record. FinHelm does not publish a single retention period covering every record.

FinHelm's authentication and authorization audit logs are configured with a 400-day retention period. After that period those records are scheduled for deletion. Deletion is asynchronous, and FinHelm does not guarantee the time at which it completes.

You can ask FinHelm to delete personal information by contacting privacy@finhelm.ai. Where FinHelm verifies a request to delete personal information, FinHelm completes that deletion within 30 days of verifying the request, except information FinHelm must keep to comply with law or a legal hold. Deletion under this section includes asking FinHelm's service providers to delete the information; copies in backups and in those providers' systems may take longer to be removed.

8. Security

FinHelm's security practices are described on the Security page. No method of transmission or storage is completely secure, and FinHelm does not guarantee the security of information.

9. Product analytics and session replay

FinHelm uses PostHog for product analytics and session replay to understand which parts of FinHelm are useful and improve the Service. Analytics is on by default on selected website and product pages unless you have declined it in this browser or enabled Do Not Track or Global Privacy Control. Analytics is an opt-out, and FinHelm honors both of those signals. PostHog creates visitor profiles with page visits and product actions, a browser identifier, browser and device details, the browser's user-agent string, language, timezone, IP address and approximate location. Profiles also contain initial and recent visit details, referring domains and limited acquisition categories. PostHog processes this information in our U.S. project.

While analytics is on, we automatically record clicks and form change or submit actions, including repeated clicks and clicks with no visible response. We measure scrolling, time on a page and page exits, and use heatmaps to understand interaction patterns. These events can include public button or link labels, the location of an element on the page, and link destinations with queries and fragments removed. Automatic interaction events do not include the values you enter into forms.

We select all eligible sessions for session replay, recording page layout, public text, pointer movements, clicks, scrolling and viewport changes. All form values are masked in recordings. We also mask text in signed-in product pages and financial or user-content areas of the assessment. Embedded frames, canvases and designated private visualizations are blocked. Replay excludes console logs and network request or response contents. Sign-in and other excluded pages are not recorded. These recordings use the same analytics choice described below.

Usage events are drawn from a fixed allowlist, and each event carries only enumerated properties. Session replay masks text and inputs on signed-in pages. Those events do not include financial values or ledger fields.

After you successfully submit a contact form while analytics is allowed, we link your browser activity to the email address you submitted. Browser activity linked to an email address when a visitor previously saved an assessment with analytics allowed is part of that visitor's PostHog profile. Your PostHog profile may include that email, your name, company, role, company-size category, selected ERP product and tier of interest, where provided. Submitting the same email on another device can link those visits. For signed-in accounts with analytics allowed, we also use a stable account identifier, account email, plan and subscription status. We record confirmed lead saves, account visits, checkout and subscription outcomes, billing amounts and currency, and email delivery outcomes when they can be linked to an existing account or lead with analytics allowed. We do not send message bodies, financial inputs or assessment results, ledger data, payment credentials, passwords, parameters from visited URLs or sign-in tokens to PostHog.

We also use Google Analytics on selected public marketing pages, enabled by default with the same opt-out. We send selected page visits and confirmed contact-form submissions, using predefined page names and limited categories such as product tier. Google may also process browser and device information, session activity, approximate location and a random browser identifier. This integration excludes assessment, account and sign-in pages. We do not send form contents, financial inputs or results, account identifiers, raw URL query strings or referring URLs to Google Analytics. Learn how Google uses information from sites that use its services.

While analytics is enabled, we also record limited acquisition categories, such as a search engine, LinkedIn, an email campaign, or a direct visit, together with a predefined landing page. We keep these categories in session storage for the current browser tab, expiring after 30 minutes without measurement activity, and include them with confirmed lead submissions. PostHog also receives the referring origin and domain; referring paths, queries and fragments are removed. We discard advertising click identifiers and unrecognized campaign text. Declining analytics clears the locally stored acquisition categories.

PostHog also receives page-performance measurements, sanitized application error categories and server tool-call timings and outcomes. Performance events contain timings and layout-stability measurements, without page contents or form values. Error events use fixed categories and may include application JavaScript file locations and line numbers; we remove raw error messages, variables and data values. Tool diagnostics exclude prompts, tool arguments, results and model responses. These diagnostics use the same analytics choice.

We also measure delivery of selected public website requests using limited hosting logs in PostHog. These operational records contain approved public paths, response status and delivery metadata. They exclude private account and API routes, URL queries, referring URLs, request and response bodies, and runtime log messages. Client identifiers are hashed before transmission and these records do not create visitor profiles or link to account and lead identities. This operational measurement is separate from browser analytics and its opt-out.

You can turn analytics off and continue using FinHelm. While analytics is on, PostHog stores a browser, submitted-lead or account identifier in browser local storage. FinHelm uses first-party cookies lasting up to one year to pass the analytics choice and browser session context to our server and to recognize a confirmed lead when saving a choice. Google Analytics uses first-party cookies configured to expire after 180 days without refreshing that period on a visit. Use Privacy choices below at any time to select Allow analytics or Decline for both providers. A saved browser choice remains until you change it or clear browser storage; it does not expire automatically. We also save the choice against a recognized lead or signed-in account so later server events respect it. Clearing browser storage removes the local choice; a saved account decline can apply again when you sign in. Declining stops new browser events and session recording, discards replay and heatmap data waiting in the browser, and removes these integrations' stored browser identifiers. Requests already sent may finish or retry, and changing this choice does not delete events already delivered. Allowing analytics again starts a new browser identifier and recording session; a later confirmed submission or sign-in can link activity to the corresponding lead or account. We honor Do Not Track and Global Privacy Control even when analytics was previously allowed.

10. Your choices and contact

You can revoke a connected financial system authorization through the provider or through the Service where available, and unsubscribe from marketing communications at any time. You can allow or decline analytics at any time using Privacy choices, as described in Section 9. Marketing communications require a separate consent that is optional, unchecked by default and never bundled with anything else. Depending on where you live, applicable law may give you rights concerning your personal information, such as rights to access, correct, delete or port it, or to object to certain processing. This notice does not limit those rights. To make a request concerning your personal information, contact privacy@finhelm.ai. FinHelm responds to requests sent to privacy@finhelm.ai within 30 days. To ask a question about this notice, contact legal@finhelm.ai.

11. Changes to this notice

FinHelm may update this notice. Each version carries a version number and effective date. Material changes to how FinHelm handles personal information are communicated to account holders before they take effect.

12. Version and effective date

Version 1.1. Effective September 27, 2026.