Cookie Policy

1. What these technologies do

Cookies are small text files placed on your device when you visit a site. They are widely used to make sites work, keep you signed in, remember preferences, and understand how a service is used. Similar technologies include browser local storage and IndexedDB, which can store data in your browser for the same purposes. Some features of the Services rely on these mechanisms because they persist across page loads in a way that is standard for modern web apps.

Whether a given identifier is stored as a classic HTTP cookie or in storage APIs, the purpose categories below describe why we use the data—not every vendor exposes the same file names in every browser.

2. How we group uses

We classify our use of cookies and similar technologies into the following categories:

• Strictly necessary — required to operate the Services, maintain security, and authenticate you.
• Preferences — remember choices you make (for example display settings) so the interface stays consistent when you return.
• Analytics — help us understand traffic, navigation, and product usage in aggregate so we can improve performance and features.
• Reliability and diagnostics — detect, report, and debug errors and performance issues to keep the Services stable.

3. Strictly necessary: sign-in and security

The Services use Firebase Authentication (Google) to manage accounts. Depending on your browser, sign-in method, and whether you choose to stay signed in, Firebase may use cookies and/or browser storage (including IndexedDB and local storage) to maintain your session, protect against abuse, and complete the OAuth flows used for providers such as Google. These mechanisms are essential for delivering the signed-in experience; without them, you cannot access account features reliably.

We may also rely on short-lived, security-related data (for example to mitigate cross-site request risks or to route you correctly after authentication) as implemented by our hosting and application framework. These uses are limited to operating and securing the Services.

4. Preferences: appearance

We store your theme preference (such as light, dark, or system default) using browser storage so that your choice applies across visits and page loads. This is not used to track you across unrelated websites; it only affects how FinityAi is displayed for you.

5. Analytics: how the product is used

Where supported in your browser and environment, we use Firebase Analytics (Google Analytics 4) to collect usage information. This includes events such as page or route views, navigation patterns, and high-level interaction signals we use to improve the product. When you are signed in, we may associate analytics with a pseudonymous user identifier (for example your Firebase user ID) and set user properties such as account creation time, last sign-in, and coarse role information—so we can understand cohorts and feature adoption, not to sell personal data.

Google Analytics commonly sets cookies whose names begin with _ga. Additional cookies or storage may be used by Google to measure engagement and to distinguish sessions. Firebase Analytics is not initialized when the app is pointed at local Firebase emulators during development, so analytics events are not sent to production measurement in that configuration.

For more on how Google uses data from sites that use its services, see Google’s documentation on Analytics and privacy, and your choices in Google’s ads and analytics settings, where available in your region.

6. Reliability: errors and session replay

When configured for an environment, we use Sentry (Functional Software, Inc.) for error monitoring, performance traces, and (where enabled) session replay. Sentry may use cookies or similar storage to correlate errors with sessions and to support diagnostics. Replay and sampling rates depend on deployment settings; not every session is recorded.

The goal is to identify crashes, broken flows, and latency issues so we can fix them—particularly important for a real-time assistant and integrations product.

7. Third-party services and links

Our Services may embed or link to third-party sites (for example documentation, status pages, or OAuth providers). Those services have their own cookie practices. This policy does not cover them; please read their policies when you leave finitybot.ai or grant permissions to another product.

8. Retention

Session and authentication data are kept only as long as needed for your login session and security. Analytics and error data are retained according to the settings in Google Analytics, Firebase, and Sentry (and may be aggregated or deleted on schedules we configure for operations and compliance). Theme preferences remain until you clear site data or change the setting in the app.

9. Your choices

Browser controls. Most browsers let you block or delete cookies and site data. If you block strictly necessary storage, parts of the Services (including sign-in) may not function.

Google Analytics. You can install browser add-ons offered by Google or others to limit analytics, where available in your jurisdiction.

Do Not Track. There is no consistent industry standard for DNT signals; we do not respond to DNT in a uniform way across all browsers.

For privacy rights that may apply to you (access, deletion, etc.), see our Privacy Policy. Questions about this Cookie Policy can be sent through our Contact page.

10. Changes

We may update this Cookie Policy when we change our technologies, vendors, or legal requirements. We will post the revised version on this page and adjust the effective date when we do. Continued use of the Services after changes means you acknowledge the updated policy.