Aller au contenu

Business Terms

Version 2026-11-04

L'arabe est la seule version faisant foi pour les conditions et politiques ; l'anglais est une traduction fournie à titre de référence. En cas de divergence de formulation ou de sens, la version arabe prévaut dans toute la mesure permise par la loi, sans réduire les droits impératifs ni exclure la responsabilité en cas de traduction trompeuse.

1. Scope and parties

Arabic is the authoritative version of these terms; English is a reference translation. Arabic prevails in a conflict to the extent permitted by law, without reducing mandatory rights or excluding responsibility for a misleading translation.

These provisions apply to professional and business use, including sole professionals and organisations, regardless of Plan name. Account labels do not create or remove consumer status; purpose and applicable law govern.

For an organisation's account, the customer is the organisation represented by an authorised person; employees are not automatically personal guarantors. A sole professional contracting in their own name remains the contracting party.

Section 5 applies wherever we process data on a customer's behalf even if other Business Terms do not apply. Mandatory rights and valid specific contracts prevail as set out in the Terms of Service.

2. The organisation and the Workspace owner

2.1 The organisation is answerable to us for the Workspace: its use, its members, the content uploaded to it, and billing.

2.2 The Workspace owner controls members, roles, teams, templates, knowledge, brand voice, billing and Workspace settings, and can transfer ownership to another member. The owner alone holds certain powers (such as deleting the Workspace) that are not given to others.

2.3 The organisation keeps at least one active owner. A Workspace is not left without an owner.

2.4 The organisation ensures that those it invites are authorised to use the Service for its business, and have been told of the terms of use and of what administrators can see.

3. Administrators, members and Seats

3.1 Each active member, and each pending invitation, occupies one Seat. Seats are set by the Plan and by what is bought beyond it, and no new member is accepted when the Seats are full.

3.2 Disabling a member frees their Seat even though their record stays. Removing them ends their access for good.

3.3 The organisation may give administrators specific management powers (such as members, teams and templates) without the owner's powers, and is responsible for judging what it grants.

3.4 Plan limits (such as the number of included Seats and the maximum) may change with notice before renewal, without affecting what has been paid for.

4. Workspace content

4.1 Content uploaded to the Workspace (templates, knowledge, brand voice and documents) is controlled by the organisation, and its ownership stays with it and whoever owns it, under the Terms of Service.

4.2 A member's personal content (such as their own request history) stays theirs. Administrator access to text, excerpts and statistics is subject to permissions and approved disclosures under sections 7.3 and 7.5 of the Privacy Policy.

4.3 When a member leaves the organisation, the documents and templates they created for the Workspace stay under the organisation's control.

4.4 The organisation judges who may see knowledge (the whole Workspace, teams or particular members), and is responsible for what it allows.

5. Data processing terms

5.1 Parties and roles: the customer is controller or authorised processor; Bayan is processor or subprocessor according to facts. A processor customer needs appropriate controller authorisation. The agreement does not override statutory roles.

5.2 Subject/duration: processing Content and necessary data throughout the relationship and lawful return/deletion period. Purpose: providing requested features, including enabled background jobs. Operations may include hosting, import, organisation, retrieval, generation, export and deletion.

5.3 Categories: Content, correspondence, documents and necessary metadata; individuals may include customers, staff and correspondents. Sensitive data, minors' data and high-risk uses are not automatically within general scope.

5.4 Instructions: we follow documented lawful instructions in the agreement, settings and authorised requests. If law requires other processing, we inform the customer beforehand unless prohibited. We flag apparently unlawful instructions and suspend them pending lawful resolution.

5.5 Confidentiality/security: authorised personnel are bound to confidentiality and need-based access. Bayan is required to take technical and organisational measures appropriate to the data and processing risks under applicable law, and any additional measures agreed in writing.

5.6 Subprocessors: authorisation requires a known, current list, advance change notice and reasoned data-protection objections. We require appropriate protections and remain responsible for performance where contract or law requires. If a justified objection cannot be resolved, the customer may terminate the affected services and obtain a refund of the unused term.

5.7 International transfers: accepting this agreement is not a standalone transfer safeguard. Each route requires applicable safeguards, assessments and documents.

5.8 Rights/incidents: we appropriately assist with rights requests, assessments and statutory consultations. We notify customers of data incidents without undue delay, with available information and updates, not awaiting complete investigation. We coordinate external notices without preventing duties imposed directly on us.

5.9 Return/deletion: on lawful request, return or delete data at service end within statutory deadlines and any agreed schedule that does not reduce those rights, including suppliers/backups under statutory requirements. Legally required retention is restricted.

5.10 Evidence: we provide appropriate information and facilitate proportionate audits with notice and safeguards for others' data and security. Documentary review is preferred where sufficient, without preventing legally required audits or those justified by incidents or breach indicators. Agreed reasonable fees must not obstruct mandatory rights.

5.11 Customers are responsible for their lawful bases, notices, instructions and permissions; our independent obligations remain. These terms do not grant a licence to train general models on customer Content; processing purposes and provider terms are described in the Privacy Policy and AI Usage Disclosure.

5.12 Processing-specific details are completed in a written agreement where required, identifying scope, authorised parties, contacts and applicable annexes. Acceptance of these terms alone does not authorise sensitive-data processing or replace international-transfer requirements.

6. Employers and what administrators can see

6.1 The Service lets administrators see the member list and roles, their general activity, usage and Credit statistics and the audit log of administrative actions, and excerpts of the questions the knowledge did not cover (Privacy Policy, section 7.3), according to their permissions.

6.2 The organisation, as employer, must tell its employees of this and of its policies on use of work tools, and comply with the labour, data-protection and privacy rules that apply to it when it looks at its employees' activity.

6.3 Review of employees' use is limited to lawful, disclosed and proportionate administration of the Service for work purposes. The Service must not be used for covert or unlawful monitoring or purposes outside those disclosed.

7. Billing and tax invoices for organisations

7.1 Organisations provide accurate billing data; we issue appropriate documents under applicable requirements.

7.2 Errors are corrected using lawful procedures/documents, not record changes to conceal transactions.

7.3 Terms of Service payment, renewal and refund provisions apply. Offers disclose fees, taxes and Seats; a general clause does not transfer our statutory tax duties to customers.

8. Support and service levels

8.1 Support follows channels/features in the accepted offer. A specific response-time or availability guarantee arises only where included in the accepted offer or a binding agreement, subject to mandatory rights.

8.2 A binding SLA requires a specific agreement defining measurement, business hours, time zone, priority, exclusions and remedies; initial response is not resolution.

8.3 Planned maintenance impacts are explained where possible. Failures follow Terms section 18 without making fee refunds an exclusive remedy removing other rights.

9. Enterprise plan and special contracts

A signed enterprise agreement may set specific terms subject to mandatory rights. Subscription alone creates no custom-development or ownership-transfer obligation.

If custom development is offered, a separate statement of work must define deliverables, acceptance, dates, dependencies, changes, fees, background/new IP, licences, support and termination.

10. Ending and export

Terms section 16 governs termination/export; section 5 here and the Privacy Policy govern return/deletion. Contractual breach does not automatically remove data rights.

11. Supporting documents and order of precedence

Read these terms with the Terms of Service, Privacy Policy, AI Usage Disclosure and any effective processing agreement or specific contract. Conflicts follow the document order in Terms section 2.5, with mandatory law taking precedence. An incomplete or unagreed annex does not constitute an effective specific commitment; its absence does not remove statutory duties or established customer or data-subject rights.