Cookie Policy

Effective 3 August 2026 · Last updated 3 August 2026

This document is published in English and Bengali. Where the two differ, the English version governs.

In short

We set three cookies: one to keep you signed in, one for your language, one to secure Google sign-in.
No advertising, no analytics, no cross-site tracking — which is why there is no consent banner.
Blocking the two necessary cookies will stop you signing in.

This summary is for orientation only and forms no part of the agreement. The numbered clauses below are what apply.

1. What cookies are

A cookie is a small text file that a website asks your browser to store and send back on later visits. Cookies are what allow a site to recognise you between one page and the next — without them, signing in would not survive a single click. This policy explains every cookie BekarConnect sets, and forms part of our Privacy Policy.

2. The cookies we set

We set three cookies. All three are first-party, meaning they are set by https://bekarconnect.com itself and are not readable by any other site.

Name	Purpose	Category	Expires
`bc_token`	Keeps you signed in. Holds the signed token that identifies your session to our servers.	Strictly necessary	12 hours, or 30 days if you chose “remember me”
`bc_culture`	Remembers whether you chose English or Bengali.	Functional	1 year
`bc_oauth_state`	Security check during Google sign-in. Ties the reply from Google to the request your browser made, which prevents a cross-site request forgery attack on the sign-in flow.	Strictly necessary	10 minutes

bc_token and bc_oauth_state are set HttpOnly, so JavaScript running in your browser cannot read them. All three are set SameSite=Lax, and are marked Secure when the site is served over HTTPS.

3. What we do not use

We run no advertising cookies, no analytics cookies, and no cross-site tracking of any kind. We do not use Google Analytics, advertising pixels, social media trackers, fingerprinting, or any third-party tag that follows you across other websites. We do not sell or share behavioural data, because we do not collect it.

This is why BekarConnect shows no cookie consent banner: every cookie we set is either strictly necessary to deliver a service you requested, or records a preference you chose yourself. Should we ever introduce a cookie that is not, we will ask for your consent first and update this page.

4. Third-party cookies

We embed no third-party content that sets cookies on our pages. If you choose to sign in with Google, your browser is sent to Google’s own sign-in pages, where Google sets its own cookies under its own policies. That happens on Google’s domain, not ours, and we have no control over it or access to those cookies. Links posted by other users take you to sites that may set their own cookies, which are equally outside our control.

5. Managing cookies

Every major browser lets you view, delete and block cookies, usually under Settings → Privacy. You can also browse in a private or incognito window, which discards cookies when you close it.

Be aware of the consequence: bc_token and bc_oauth_state are strictly necessary. If you block or delete them, you will not be able to sign in — you will be returned to the login page each time. Blocking bc_culture only means the site forgets your language choice between visits.

Deleting bc_token is also the most reliable way to sign yourself out of a browser you no longer control.

6. Changes to this policy

If we add, remove or change a cookie, we will update this page and its effective date. Where a change requires your consent, we will ask for it before setting the cookie.

7. Contact

Questions about cookies go to privacy@bekarconnect.com, or BekarConnect, Dhaka, Bangladesh.