Cookie Policy
BalanceFlow Cookie Policy
Effective date: 1 September 2026
This Cookie Policy explains the cookies used on our public website, balanceflow.cloud, and our application, app.balanceflow.cloud. Read it together with our Privacy Policy and Terms of Service.
Who we are
BalanceFlow is operated by Raman Miura, Mieczysława Karłowicza 14 30-047 Kraków, NIP: 6772465624 (“BalanceFlow”, “we”, “us”). Contact us at [email protected] about this policy or your cookie choices.
Necessary cookies
Necessary cookies support the public site's basic operation and remember your cookie choice. The application uses cookies for authentication and security. They are used without optional analytics consent. The following cookies are used on the public website and application:
| Cookie | Where | Purpose | Lifetime |
|---|---|---|---|
balanceflow_cookie_consent |
balanceflow.cloud |
Remembers analytics when you select Accept analytics, or necessary when you select Reject optional cookies |
180 days |
balanceflow-session |
Host-only cookies on both balanceflow.cloud and app.balanceflow.cloud, separately |
Maintains a session for site or app operation | 120 minutes, renewed on each web response |
XSRF-TOKEN |
Host-only cookies on both balanceflow.cloud and app.balanceflow.cloud, separately |
Helps protect requests against forgery | 120 minutes, renewed on each web response |
The balanceflow-session and XSRF-TOKEN cookies persist when the browser closes. Each response through Laravel’s web middleware renews their expiration to approximately two hours from that response. The underlying database session expires after 120 minutes of inactivity. balanceflow-session is HttpOnly; XSRF-TOKEN is readable by JavaScript to support request protection. These cookies are independent on each host and are not shared across subdomains.
The balanceflow_cookie_consent cookie has path / and SameSite=Lax. It uses Secure on HTTPS. It is readable by JavaScript (HttpOnly is not set) so the public site can apply your choice. It has no explicit Domain attribute, so it belongs only to balanceflow.cloud and is not sent to app.balanceflow.cloud. Your choice is stored in your browser, not in a Laravel session or a database acceptance record. If you clear cookies or use a different browser, you may need to choose again.
Optional analytics cookies
If you choose Accept analytics, we use Google Analytics on the public website to understand visits and page views. The application uses no analytics or frontend debugging tools. If you choose Reject optional cookies, or have not made a choice, we do not load Google Analytics on the public website. Cloudflare Web Analytics is disabled. Production checks confirmed that Google Analytics does not load before consent or after rejection.
| Cookie | Provider and location | Purpose | Typical lifetime |
|---|---|---|---|
_ga |
Google Analytics on the public website | Distinguishes visitors | Up to two years by Google's default settings |
_ga_LHSF8NECBY |
Google Analytics on the public website | Maintains session state | Up to two years by Google's default settings |
The analytics cookies are host-only on balanceflow.cloud. They are not sent to app.balanceflow.cloud, where Google Analytics is not installed. Actual expiration can be shorter than Google's default because browsers limit cookie lifetimes. Cookie expiry is separate from the retention period for information held in Google Analytics, which is described in our Privacy Policy.
Changing your choice
You can use the Cookie settings link in the public site's footer at any time to accept or reject optional analytics. Changing your choice to Reject optional cookies stops future Google Analytics collection from this site and removes existing Google Analytics cookies. The page reloads without those cookies or Google Analytics initialization. Your browser settings also let you inspect or delete cookies and block them. Blocking necessary cookies may prevent sign-in or other functions from working.
Updates
We may update this policy when the cookies or services we use change. We will update its effective date when we publish a new version. For more information about personal data, providers and your rights, see our Privacy Policy.