Interwide Terminal
Interwide Cookie Policy
Last updated: 14 November 2026
Effective date: 14 November 2026
Version: 1.0
This Cookie Policy explains how BioEnergia LLP uses cookies and similar technologies on Interwide Terminal. It should be read with the Interwide Privacy Policy. If there is any conflict about personal data, the Privacy Policy prevails.
1. Who we are
1.1. Interwide Terminal at https://interwideterminal.com ("Terminal", the "Platform") is provided by BioEnergia LLP ("Interwide", "we", "us").
1.2. Privacy contact: support@interwideterminal.com. Person responsible for organising personal data processing: BioEnergia LLP, which may be contacted at support@interwideterminal.com.
1.3. This Policy applies the law of the Republic of Kazakhstan on personal data to all Users. The EU GDPR and the UK GDPR apply only to Users located in the EU or the UK to whom the Platform is deliberately offered. Interwide's main market is the Republic of Kazakhstan and the CIS, and it does not currently target Users in the EU or the UK.
2. What this Policy covers
2.1. A cookie is a small text file that a website stores on your device. Similar technologies include other storage on your device, such as session storage in your browser, and security checks that run in your browser.
2.2. This Policy covers cookies and similar technologies set or used when you visit Terminal, including the public pages, sign-in, sign-up and password recovery, and the signed-in Platform.
2.3. It does not cover cookies that other websites set, including a site you open from a link on the Platform.
3. Essential use only
3.1. Terminal currently uses essential cookies and similar technologies only. They are needed to operate the Platform securely: to sign you in, keep your session, remember which Organization you have selected, complete sign-in and recovery checks, and, when you are signed in, remember which tabs you have open in the Platform shell.
3.2. Interwide does not use analytics, advertising, social or profiling cookies or trackers, and does not sell personal data or build advertising profiles (Privacy Policy, Section 6.2).
3.3. Non-essential trackers do not run before consent (Privacy Policy, Section 15.1). If Interwide later introduces optional cookies, they will not run before a separate consent, this Policy will be updated, and you will be able to withdraw that consent as easily as you gave it.
3.4. Because only essential cookies and similar technologies are used, Interwide does not display a cookie-consent banner.
4. Cookies and similar technologies we use
| Name or type | Category | Purpose | Duration | Provider |
|---|---|---|---|---|
Supabase authentication session cookies, named in the form sb- followed by the project reference and -auth-token. If the value is large, the cookie may be split into numbered parts of the same name. | Strictly necessary | Keep you signed in and allow the Platform to authenticate your session on the server. The session cookie is HttpOnly, so page script cannot read it. It is set only after you sign in or complete an authentication flow. | Up to 400 days, or until you sign out, whichever is sooner. The authentication session is also subject to the authentication provider's token validity and is refreshed while you use the Platform. | Supabase Auth, used by Interwide (EU, Ireland) |
| Short-lived Supabase login-check cookies (PKCE code-verifier cookies), using the same project-prefixed name with a code-verifier suffix | Strictly necessary | Complete the sign-in, sign-up or password-recovery check in a secure way, then be cleared. | Only for the authentication flow; cleared when the flow finishes or is abandoned, and when you sign out. | Supabase Auth, used by Interwide (EU, Ireland) |
meridian-active-organization | Strictly necessary | Remember which of your Organizations you last selected, so the Platform can open in that context. This is a preference only. Access is always re-checked on the server from your memberships; the cookie is never authority. | Up to 1 year. HttpOnly, SameSite=Lax, Secure on the production site, path /. Signing out does not itself delete this cookie. It remains until it expires, is replaced when you select another Organization, or you delete it in your browser settings. | Interwide |
iw2.tabs.v1 (browser session storage, not a cookie) | Strictly necessary | Remember, on your device only, the tabs you have open in the signed-in Platform shell (the path and a generic title derived from the route). It holds no account identity and is not authority for access. | Until the browser tab or window is closed. It is not sent to Interwide's servers as a cookie. | Interwide, stored on your device |
4.1. All first-party cookies listed above are set for the Terminal site, with path / and SameSite=Lax. On the production site they are marked Secure. Authentication session cookies and meridian-active-organization are HttpOnly.
4.2. These cookies are not set when you only visit the public pages of the site, including the home page and the anonymous catalogue. Authentication cookies are set when you sign in or complete an authentication flow. The organization-preference cookie is set when you join, create or select an Organization. The tab storage is written only after you are signed in and use the Platform shell.
5. Cloudflare Turnstile
5.1. On the sign-in, sign-up and password-recovery request pages, Interwide uses Cloudflare Turnstile as bot protection for those forms (Privacy Policy, Section 10.6). A verification token is written into the form and checked by Interwide's servers. That token is not a cookie set by Interwide on interwideterminal.com.
5.2. The check is provided by Cloudflare and is loaded from Cloudflare's servers (challenges.cloudflare.com). Cloudflare may process technical data, such as IP address and browser data, under Cloudflare's terms, and may use cookies or similar technologies on Cloudflare's own domain to operate the check. Interwide does not use Turnstile for advertising or analytics.
5.3. Turnstile is not loaded on the public home page, the anonymous catalogue, or the page on which you set a new password after opening a recovery link.
6. Providers, logs and storage
6.1. Providers that process personal data, and their roles and locations, are listed in Section 10.6 of the Privacy Policy. They include Supabase (authentication and database), Vercel (hosting and server functions; static content through a global CDN), Cloudflare (DNS, Turnstile and forwarding of email sent to support@), and Unihost.kz (the Kazakhstan copy of the database).
6.2. Authentication and hosting logs may include IP address and user agent, depending on provider configuration (Privacy Policy, Section 5). Those logs are not cookies.
6.3. Personal data processed through Terminal are stored in a database located in the Republic of Kazakhstan (Unihost.kz) and, in parallel, in Supabase EU (Ireland, eu-west-1). Website server functions run in Vercel EU (Dublin, Ireland). Static content is delivered through Vercel's global CDN. Cross-border transfer to Ireland is described in Section 11 of the Privacy Policy and is covered by the Personal Data Processing Consent given at registration.
7. Legal bases
7.1. Under Kazakhstan law, the consent of the data subject is the main legal basis, as explained in Section 9 of the Privacy Policy. Essential cookies and similar technologies are used to operate the account, keep the service secure and perform the contract (the Terms).
7.2. Optional cookies are not used. If they are introduced, they will run only with a separate consent (Privacy Policy, Section 9.1).
8. How to control cookies
8.1. You can delete or block cookies in your browser settings. Blocking strictly necessary cookies will prevent sign-in and will stop the signed-in Platform from working correctly.
8.2. You can sign out at any time. Signing out clears the authentication session cookies. It does not itself delete meridian-active-organization.
8.3. You can clear site data, including session storage, in your browser. That will forget the tabs open in the Platform shell on that device.
8.4. There is no cookie preference centre, because optional cookies are not used.
9. Changes
9.1. Interwide may change this Policy by publishing a new version at /legal with its date and version. We notify users of material changes through the Platform or by email, as described in Section 17 of the Privacy Policy.
9.2. A change to this Policy does not change any consent you gave. If Interwide introduces optional cookies, that will require a separate consent.
10. Contact
BioEnergia LLP · support@interwideterminal.com