Interwide Terminal
Interwide Privacy Policy
Last updated: 14 November 2026
Effective date: 14 November 2026
Version: 1.3
This Privacy Policy explains how BioEnergia LLP collects, uses, stores and protects personal data when you use Interwide Terminal and related services, and what rights you have.
1. Who we are
1.1. Interwide Terminal (https://interwideterminal.com) and Interwide Open are provided by BioEnergia LLP ("Interwide", "we", "us").
1.2. Interwide Terminal ("Terminal") is a B2B web platform for private transactions between organizations. It works through controlled disclosure: anonymous teaser → access request → NDA → data room.
1.3. Interwide Open ("Open") is software that runs on the user's own computer. It analyses project documents and runs calculations locally.
1.4. Privacy contact: support@interwideterminal.com.
1.5. Person responsible for organising personal data processing: BioEnergia LLP, which may be contacted at support@interwideterminal.com.
2. Scope
2.1. This Policy covers personal data processed through Terminal: accounts, organizations, KYB, listings and teasers, access requests, NDA and data-room workflows, billing records, security and audit records.
2.2. It also covers data that Terminal receives from Open. Terminal receives Open data only after an explicit, confirmed upload (Section 7).
2.3. It does not cover:
- files and project state that stay on your computer in Open;
- processing by an AI assistant host that you choose to run with Open (for example, a hosted coding assistant). That host processes data under your own agreement with it.
2.4. The Platform is for organizations and their representatives. It is not offered for personal or household use.
3. Legal framework
3.1. This is one English notice. It 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.
3.2. ISO/IEC 27701 is used only as good-practice guidance. Interwide does not claim ISO 27701 certification.
4. Roles: who decides how data is used
4.1. Platform data. For account, organization, KYB, acceptance, billing, security and audit data, BioEnergia LLP acts as owner and operator of the database in the sense of the law of the Republic of Kazakhstan and, where the GDPR or the UK GDPR applies, as controller.
4.2. Data uploaded from Open. The Open upload package is designed not to contain personal data (Section 7.4). The uploader's identity and the audit trail of the upload are Platform data (Section 4.1). If an upload nevertheless contains personal data, BioEnergia LLP processes it as owner and operator of the Platform database, only for the purposes in Section 6. The Organization remains responsible for its right to submit that data (Terms, Section 12.2).
4.3. Documents in data rooms. The Organization that uploads a document decides what it contains and is responsible for its right to disclose any personal data in it. Interwide hosts the document for the Organization. Interwide is not a participant of the data room and has no access to its contents; Interwide staff roles are denied access to data-room contents (Section 12.2).
4.4. No DPA in the pilot. Interwide does not offer a DPA during the pilot. Interwide will not onboard an organization or start an operation where law or contract requires a signed DPA. This refers to a data processing agreement with the Organization and is distinct from the providers' data processing agreements described in Sections 10.6 and 11.3.
4.5. A representative's acceptance cannot give consent on behalf of other people. The organization is responsible for informing its employees, counterparties and other people whose data appear in its materials.
5. Data we process
| # | Category | Examples | Source |
|---|---|---|---|
| 1 | Account | Business email, display name, password hash (held by the authentication provider), MFA enrollment metadata, timestamps | You |
| 2 | Legal acceptances | Document type, exact version, language, text hash, timestamp, context | You / Platform |
| 3 | Organization and roles | Membership, roles, seat assignments | You / organization / platform admin |
| 4 | KYB evidence | Company registration documents, ownership and beneficial-owner (UBO) data, representatives' names, positions, identity and authority documents, review outcomes | Organization representatives |
| 5 | Transactions | Listing and teaser fields, access requests, NDA execution metadata, access grants, data-room activity | You / organization / counterparties (limited) |
| 6 | Open uploads | Only the confirmed package (Section 7). The package is designed not to contain personal data | You, via Open |
| 7 | Open account link | Link status, scopes, expiry; hashes of link credentials | Open / Terminal |
| 8 | Billing | Invoice references, amounts, dates, payment confirmation metadata. No card numbers are stored. After the 14-day free trial, and for Membership, payment is by invoice issued on request together with a commercial proposal. | You / admin |
| 9 | Security and audit | Actor, action, object references, correlation IDs. No document contents, no secrets | Platform |
| 10 | Technical | Essential session cookies. Authentication and hosting logs may include IP address and user agent, depending on provider configuration | Your device / providers |
5.1. KYB vs uploads. Identity documents are accepted only in the KYB procedure, where the organization submits them to prove who it is and who represents it. Identity documents are prohibited in Open uploads. These are two separate flows with separate purposes and access rules.
5.2. Do not submit special-category data (for example, health data), criminal-record data, children's data, passwords or secrets, unless Interwide specifically asks for them and the law allows it.
6. Why we process data
6.1. We process personal data only to:
- create and secure accounts, including MFA;
- record legal acceptances and consents;
- manage organizations and roles;
- carry out KYB admission;
- receive and store confirmed Open uploads as private drafts;
- moderate and publish anonymous teasers at the organization's request;
- process access requests, NDAs and data-room access;
- issue invoices and keep billing records;
- keep audit and security records and prevent fraud and abuse;
- send service messages about your account and transactions;
- meet legal obligations and defend legal claims.
6.2. We do not:
- use personal data for marketing without a separate opt-in;
- build advertising profiles;
- sell personal data;
- train AI models on uploaded data;
- make solely automated decisions with legal or similarly significant effects.
7. Interwide Open
7.1. Open runs locally on your computer. By default it sends nothing to Interwide. Open has no automatic telemetry to Interwide.
7.2. Terminal receives Open data only if you confirm an upload. Before every upload Open shows an exact preview of the package and its SHA-256 hash. You must select an organization, confirm your authority and accept the current Upload Consent. If you cancel or close the dialog, nothing is sent.
7.3. What the package contains: selected numeric metrics; gaps and numeric conflicts; technical identifiers; the version, language and hash of the consent text you accepted.
7.4. What the package does not contain: original files; file names; file paths; document extracts; company names; contacts.
7.5. An upload creates a private draft of your organization. It is not a publication and not an access grant. Platform administrators cannot read unsubmitted Open drafts.
7.6. There is no reverse sync from Terminal back to Open during the pilot.
7.7. Account link. To link Open to your Terminal account you confirm a code in the browser. Open receives a credential valid for 1 hour, without renewal. Terminal stores only hashes of link credentials and codes. Pending link requests older than 24 hours are deleted. You can unlink in Open or in Terminal settings. Signing out of Terminal revokes Open links.
7.8. The upload terms are set out in the separate Upload Consent, shown in full before each upload. Interwide may enable, restrict or disable uploads from Open to Terminal at any time.
8. Consents are separate
8.1. We ask for separate, versioned confirmations. They are never combined into one checkbox:
| Code | Confirmation | When |
|---|---|---|
| A | Acceptance of the Terms and acknowledgement of this Policy; Personal Data Processing Consent, including consent to the cross-border transfer and storage described in Section 11 | Registration |
| B | Upload Consent | Before every upload from Open |
| C | Public Teaser Publication Consent | Before a teaser is published |
8.2. Each confirmation records the exact version, language, text hash and time. Any change to a consent text creates a new version. A new version requires a new confirmation. Earlier records are not overwritten.
9. Legal bases
9.1. Under Kazakhstan law, the main legal basis is the consent of the data subject (Consent A), as stated in Section 9.2. Other bases apply only where the law provides them or where the GDPR or the UK GDPR applies. Those other bases may include:
- performance of the contract (the Terms);
- legitimate interests (security, fraud prevention, accountability, defence of claims);
- legal obligation, only where a specific duty applies;
- additional consents, where required (for example, upload, teaser publication, optional cookies).
9.2. Under Kazakhstan law, the consent of the data subject is the main legal basis. Interwide relies on the Personal Data Processing Consent (Consent A) for registration and account data, and on other bases only where the law provides them.
10. Who receives data
10.1. Other organizations receive data only through the disclosure workflow: anonymous teaser, then further disclosure only after seller approval, NDA and data-room access. KYB documents are not disclosed to other organizations.
10.2. Service providers. The providers that process personal data, and their roles and locations, are listed in Section 10.6.
10.3. AI providers are not Interwide service providers for local Open analysis. If you run Open inside an AI assistant host, that host processes data under your agreement with it.
10.4. Authorities receive data only where the law, a court order or a binding regulator request requires it.
10.5. Interwide will notify Users by email at least 30 days before engaging a new service provider that will process personal data. An Organization that objects may close its account under Terms Section 16.2 before the change takes effect.
10.6. Providers on the date of this Policy. (a) Supabase: database, authentication and file storage (account, organization, KYB and upload data); EU, Ireland (eu-west-1). (b) Vercel: hosting and server functions (user requests, IP address and technical logs); EU (Dublin); static content through a global CDN. (c) Cloudflare: DNS, bot protection for forms (Turnstile) and forwarding of email sent to support@ (IP address, browser technical data and the content of support emails). (d) Google (Gmail): the mailbox that receives forwarded support emails; location under Google's terms. (e) Resend: sending of authentication emails (email address and message text), from the date it is engaged; until then Supabase sends these emails. (f) Unihost.kz: a data centre in the Republic of Kazakhstan that hosts the Kazakhstan copy of the database, including account data. The source code is hosted on GitHub and contains no personal data.
11. International transfers and storage location
11.1. 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. Account data (such as email address, telephone number, and registration and sign-in timestamps) are also copied to and stored in the Republic of Kazakhstan.
11.2. Cross-border transfer. Personal data are transferred to, and hosted in, Ireland (EU) as described in Section 11.1. By confirming Consent A, you consent to this transfer.
11.3. Transfer safeguards. Transfers to the providers in Section 10.6 rest on your consent (Consent A) and on the providers' data processing terms, including the data processing agreements of Supabase and Vercel. Support is run from the Republic of Kazakhstan and support access to personal data is from the Republic of Kazakhstan, so support access creates no further transfer. Cloudflare and Google process support emails and technical data in the locations set by their own terms.
12. Security
12.1. Interwide applies commercially reasonable technical and organizational measures designed to protect personal data, including:
- access controls in the database (row-level security) and role-based access;
- isolation between organizations;
- private storage buckets;
- TLS in transit;
- integrity hashes and minimal audit records;
- least-privilege access for staff.
12.2. Interwide staff roles are denied access to data-room contents by access controls (row-level security and roles).
12.3. Database records are hosted in Interwide's infrastructure on Supabase EU (Ireland) and, in parallel, in a database located in the Republic of Kazakhstan (Unihost.kz). This is not end-to-end encryption and not cryptographic isolation from the infrastructure operator.
12.4. The Platform supports multi-factor authentication (MFA). When mandatory MFA is switched on, it applies to every role with upload access and to all platform administrators.
12.5. Data in transit are protected by TLS. The Kazakhstan database replica is stored on an encrypted volume. At-rest encryption and backups of other systems follow the configuration of the relevant providers.
12.6. Breach notification. Interwide will notify the competent Kazakhstan authority within one working day of detecting a personal-data security breach, as the law requires. During the pilot, Interwide will also notify the affected organization within 48 hours of becoming aware of the breach, with follow-up updates.
13. Retention
| Record | Period |
|---|---|
| Unsubmitted Open draft and answers | Deleted after 90 days of inactivity |
| Organization with no remaining admin | Hidden and read-only at once; deleted after 30 days unless a new admin is appointed |
| Published teaser | Until the organization withdraws it; deleted within 30 days after withdrawal |
| Organization withdrawal of its instruction | Working data and our document copies deleted within 30 days |
| Data-room access records and deal correspondence | 1 year after the deal closes |
| Billing and payment records | 6 years |
| Audit event identifiers | 6 years |
| Acceptance and consent evidence (no document contents) | 6 years from the event |
| MFA recovery identity-check note | 30 days |
| Pending Open link requests | 24 hours |
| Account, KYB records | Life of the account and 3 years after its closure |
| Backups | Deleted data expire from backups within 7 days |
13.1. A legal hold (dispute, litigation, regulator request) pauses deletion for the affected data.
13.2. During the pilot, Interwide may carry out deletion manually under the periods above.
14. Your rights
14.1. Subject to applicable law, you may ask to:
- access your data;
- correct it;
- delete it;
- restrict processing;
- receive it in a portable form;
- object to processing based on legitimate interests;
- withdraw consent.
14.2. Withdrawal of consent does not make earlier lawful processing unlawful. Some records must be kept for audit, billing or legal reasons; we will tell you which.
14.3. Upload consent can be revoked in Terminal under Settings → Privacy → Revoke consent. Details are in the Upload Consent.
14.4. Send requests to support@interwideterminal.com. We confirm receipt within 3 working days and respond within 30 days, unless the law requires a shorter period. If you withdraw consent, we stop the processing that relied on it within 15 working days.
14.5. Complaints. You may complain to:
- the Committee on Information Security of the Ministry of Artificial Intelligence and Digital Development of the Republic of Kazakhstan, the authority that supervises personal data protection;
- where the GDPR applies, the competent EU supervisory authority;
- where the UK GDPR applies, the UK Information Commissioner's Office (ICO).
15. Cookies
15.1. Terminal currently uses essential cookies only. Non-essential trackers do not run before consent. See the Cookie Policy.
16. Children
16.1. The Platform is not for children. We do not create accounts for minors. Do not upload children's data.
17. Changes
17.1. We publish each version of this Policy with its date and version at /legal. We notify users of material changes through the Platform or by email.
17.2. A change to this Policy does not change any consent you gave. Any change to a consent text is a new version that needs your new confirmation.
18. Contact
BioEnergia LLP · support@interwideterminal.com