Cookie Policy

We use cookies and similar technologies to authenticate users, keep the Service secure, remember your preferences, and understand how the Service is used so we can improve it. We do not use cookies for advertising personalization.

Cookies are small text files that a website stores on your device when you visit it. Cookies can be “session” cookies (deleted when you close your browser) or “persistent” cookies (which remain until they expire or you delete them). We also use similar technologies such as local storage and pixel tags, which we refer to collectively as “cookies” in this Policy.

We use the following categories of cookies:

• Strictly necessary — required to operate the Service (for example, authentication and security).
• Functional — remember your preferences and improve usability.
• Analytics — help us understand usage and improve the Service.
• Third-party — set by providers we integrate with, such as Stripe and Google.

Authentication cookies (and equivalent local-storage tokens) keep you signed in as you navigate the Service and confirm that requests are made by you. Without these, you would have to sign in again on every page.

Security cookies help detect abuse, prevent CSRF and session hijacking, rate-limit malicious activity, and protect user Accounts.

Analytics cookies collect information about how visitors use the Service, such as pages visited, features used, and errors encountered. This information is aggregated and used to improve performance and reliability.

Functional cookies remember choices you make, such as language, theme, and recently viewed projects, so you don’t have to set them every visit.

Some cookies are set by our service providers when their components are loaded in the Service. These providers use cookies in accordance with their own privacy and cookie policies.

When you use Google Sign-In or otherwise interact with Google services embedded in the Service, Google may set cookies to authenticate you, secure the session, and prevent abuse. Google’s use of cookies is described in the Google cookie policy.

Stripe sets cookies to enable secure payment processing, detect fraud, and comply with financial regulations. Stripe’s use of cookies is described in the Stripe cookie policy.

Because strictly necessary cookies are required for authentication and security, disabling them will prevent you from signing in or using the Service. You can, however, control functional and analytics cookies through your browser settings.

Most browsers let you view, manage, and delete cookies through their settings. See your browser’s documentation for instructions:

• Google Chrome
• Apple Safari
• Mozilla Firefox
• Microsoft Edge

Where the ePrivacy Directive, the GDPR, the UK GDPR, or a similar law applies, we rely on the following legal bases for our use of cookies and similar technologies:

• Strictly necessary cookies are placed on the basis of our legitimate interest in operating a secure and functional Service and do not require consent.
• Functional and analytics cookies that are not strictly necessary are placed only after you provide consent, where consent is required by your jurisdiction. You may withdraw consent at any time by adjusting your cookie preferences or your browser settings.
• Third-party cookies set by our providers are subject to the legal basis and consent framework maintained by the applicable provider, in addition to any consent collected through the Service.

Cookie lifetimes vary by purpose. The following table sets out representative retention periods for the categories described above; actual expirations may be shorter in specific browsers or when a cookie is refreshed:

• Authentication — session and rolling refresh cookies expire between 7 and 30 days after last use, and immediately when you sign out.
• Security — up to 12 months to detect abuse and enforce rate limits.
• Preferences — up to 12 months, or until you change the corresponding preference.
• Analytics — up to 14 months in aggregated form, after which analytics identifiers are rotated or deleted.
• Third-party provider cookies — governed by the retention schedule of the applicable provider (see Section 17).

Forgeo does not use cookies, pixels, or similar technologies for behavioral advertising, cross-context behavioral advertising, audience-building for advertising networks, or the sale or sharing of personal information for advertising purposes. If we introduce advertising cookies in the future, we will update this Policy and, where required, obtain your consent before doing so.

The Service recognizes the Global Privacy Control (GPC) signal as a valid request to opt out of the sale or sharing of personal information, to the extent applicable under laws such as the California Consumer Privacy Act. When we detect a GPC signal from your browser, we treat it as an opt-out for the browser and device from which the signal was received.

The following third parties may set cookies or similar technologies when their components load in the Service. Each provider is responsible for its own cookies, and you should consult the provider’s own policies for full details:

• Google LLC — Google Sign-In, YouTube embedded components, and reCAPTCHA. Cookies are used for authentication, session security, abuse prevention, and, where applicable, embedded video functionality.
• Meta Platforms, Inc. — Instagram Graph API authorization flows. Meta may set cookies for authentication and session security during the OAuth handshake.
• Stripe, Inc. — payment processing, checkout, and fraud prevention cookies loaded during subscription purchases and billing management.
• Product analytics and error monitoring providers — set first-party or third-party cookies to distinguish browsers, measure product usage, and diagnose errors.

We may update this Cookie Policy from time to time to reflect changes in the cookies we use or in applicable law. The “Effective date” above indicates when this version was last updated.

Questions about our use of cookies can be sent to forgeo.support@gmail.com.