Cookie Policy

COOKIE POLICY This Cookie Policy explains how GOT2DEV, INC. ("GOT2DEV," "we," "us," or "our") uses cookies, local storage, and similar browser technologies in connection with Got2Dev Business Manager (the "Service") and related web properties. It should be read together with the published Privacy Policy. 1. WHAT THESE TECHNOLOGIES ARE Cookies are small data files stored by a browser. Similar technologies may include local storage, session storage, or comparable browser mechanisms. They can support authentication, security, preferences, service operation, and—where enabled—analytics or other optional functionality. 2. STRICTLY NECESSARY TECHNOLOGIES Got2Dev Business Manager may use technologies required for sign-in, session continuity, account switching, authorization, security, anti-forgery protection, load or request integrity, and other functionality necessary to provide the Service. Blocking these technologies may prevent core features from functioning. 3. PREFERENCE TECHNOLOGIES Where enabled, preference storage may remember settings such as interface choices, display preferences, or other user-selected options. We distinguish optional preference technologies from strictly necessary technologies when the Service can reasonably operate without them. Use of optional technologies is subject to any legally required disclosure, consent, and preference controls. 4. ANALYTICS AND OPTIONAL TECHNOLOGIES At the time of this version's configuration snapshot, analytics, advertising, and non-essential browser technologies were disabled, as recorded in Section 11. If we later introduce or enable analytics, measurement, advertising, or other non-essential browser technologies, we will disclose their purposes and applicable providers and implement any consent or choice mechanisms required by applicable law before their use. We do not classify optional technologies as strictly necessary solely for convenience. A future configuration change does not silently rewrite this published policy. 5. THIRD-PARTY TECHNOLOGIES Connected or embedded third-party services may set or read their own browser technologies when their functionality is used. For example, visits to separately hosted payment or other provider pages may be governed by those providers' own terms and privacy notices. The presence of an integration does not mean every third-party technology is active for every user. Our own responsibilities under applicable law are not excluded by the use of a third party. 6. COOKIE CHOICES Users can use browser settings to block or delete cookies and related storage. Where applicable law requires additional consent or preference controls for optional technologies, we will provide the required controls before enabling the relevant processing. Disabling strictly necessary technologies may prevent sign-in or other protected functionality. Browser controls may need to be configured separately for each browser or device. 7. GLOBAL PRIVACY OR BROWSER SIGNALS Where applicable law requires us to honor a recognized browser-based opt-out preference signal, such as Global Privacy Control, for processing covered by that law, we will honor that signal as required. This provision does not imply that analytics, advertising, or other non-essential browser technologies were enabled when this version's configuration snapshot was created. Necessary authentication and security technologies are not automatically disabled by an opt-out signal directed at optional processing. 8. SECURITY AND AUTHENTICATION Authentication and security cookies should be protected using appropriate browser security attributes and should contain only the information necessary for their operational purpose. Sensitive payment credentials are not stored in Got2Dev Business Manager cookies. 9. CHANGES TO THIS POLICY Published revisions identify their version and effective date. This policy may be updated when technologies, providers, product functionality, or legal requirements change. Material changes will be communicated where required by law. A published version is preserved as the version in effect for its stated time and is not dynamically changed by later configuration updates. 10. CONTACT Questions about browser technologies used by Got2Dev Business Manager may be sent to support@got2dev.com or legal@got2dev.com, or raised by telephone at (786) 975-3187. Mail may be addressed to GOT2DEV, INC., 8520 SW 133 AVE. RD., APT. 122, Miami, FL 33183. Additional information is available at https://www.got2dev.com. 11. CONFIGURED BROWSER-TECHNOLOGY SNAPSHOT This version was generated from the Service configuration then in effect. The snapshot is preserved in this legal version and is not dynamically rewritten if configuration later changes. This configuration snapshot does not itself constitute an independent audit of every browser response or third-party page. Optional-technology posture at draft generation: analytics=off; advertising=off; non-essential browser technologies=off. Configured browser-technology inventory at draft generation: - BusinessManager.Auth | Category: Strictly necessary authentication | Purpose: Maintains the signed-in Got2Dev Business Manager application session and authorization context. | Retention: Up to 8 hours with sliding expiration, subject to sign-out and security-stamp revalidation. | Scope: First-party secure HttpOnly cookie - BusinessManager.ActiveMembership | Category: Strictly necessary account context | Purpose: Remembers the selected business/workforce membership so one login can safely switch between authorized accounts. | Retention: Session-only in some flows or up to 30 days when the selected context must persist. | Scope: First-party secure HttpOnly cookie - BusinessManager.PortalBusiness | Category: Strictly necessary portal context | Purpose: Keeps the authenticated customer portal scoped to the selected business and its branding/context. | Retention: Up to 30 days while the portal business context remains selected. | Scope: First-party secure HttpOnly cookie - __Host-BusinessManager.Antiforgery | Category: Strictly necessary security | Purpose: Pairs with anti-forgery form/request tokens to protect state-changing requests from cross-site request forgery. | Retention: Security/request lifecycle as managed by ASP.NET Core and the browser. | Scope: First-party security cookie - ASP.NET Core Identity temporary security cookies | Category: Strictly necessary account security | Purpose: Supports temporary identity flows such as multi-factor authentication and other protected sign-in transitions. | Retention: Short-lived for the applicable identity/security flow. | Scope: First-party security cookies