DraftVersion 0.1 · 2026-11-03
Acceptable Use Policy (AUP) — Tender CRM
DraftDraft v0.1 dated 2026-11-03. This text has not been reviewed by a lawyer and may change; values in [square brackets] are not yet defined. The Ukrainian version is the master text. Current prices and plan terms are on the Pricing page and take precedence over any mention of cost in these drafts.
| Item | Value |
|---|---|
| Version | [VERSION] |
| Effective date | [DATE] |
| Forms part of | The Agreement (Offer, clause 16; Annex 2) |
1. General
1.1. This Policy defines what is prohibited when using the Service. It applies to the Customer and all Users. A breach is a material breach of the Agreement.
1.2. The Customer is responsible for the actions of Users and for any actions performed through its accounts, API keys and integrations.
1.3. The Provider may update the Policy (Offer, section 26).
2. Prohibited activity
It is prohibited to:
2.1. Scraping and automated access. Collect, copy, index or extract data and the interface of the Service using bots, scrapers, crawlers, scripts or other automated means, except through a documented public API with a key and within limits issued by the Provider. Mass export of data, databases, tender compilations, structures, prompts or models is prohibited.
2.2. Resale and shared access. Resell, lease, sublicense, provide the Service or access to third parties as a service (service bureau/white-label), give access to a group of people through one account (one Seat — one person), circumvent payment for Seats.
2.3. Competitive use. Use the Service or its outputs to build a competing product or to train/distil AI models on the Service's source data; benchmark without written consent.
2.4. Unlawful and harmful content. Upload or distribute: content that infringes law, intellectual-property rights, trade secrets or confidentiality; malware; unlawful materials; data you have no right to process; content inciting hatred, fraud or deception. Do not upload special categories of data, state secrets, restricted-access information, banking secrecy, or data that may not be passed to AI vendors.
2.5. Infringing others' rights. Impersonate another person, deceive, submit false bids or documents; use the Service for malicious manipulation of procurements, collusion, corruption or violation of competition and anti-corruption law.
2.6. Sanctions. Use the Service by persons subject to sanctions [EU/Ukraine/US/UK — specify], or in the interests of such persons or the aggressor state (Offer, clause 4.4).
2.7. Security violations. Test for vulnerabilities, scan, probe, or run penetration tests without written consent; bypass authentication, limits, permission restrictions or isolation between Workspaces; access other Customers' data; exploit bugs.
2.8. Overload. Create excessive load (DoS, multithreaded requests, looping integrations) that harms the operation of the Service or other customers.
2.9. Violating Source rules. Use the Service in a way that breaches the terms, rules or laws of third-party platforms (including rules on automated access to accounts, restrictions on data use); use other people's credentials for platforms; provide credentials without the right to do so.
2.10. AI-specific. Use AI Features to: generate unlawful, deceptive or harmful content; attempt prompt injection, circumvent restrictions, extract system prompts, hidden instructions or models; create disinformation, fake documents or forgeries; run automated mass requests without need. Do not present AI output as professional advice.
2.11. Trial abuse. Create multiple trial Workspaces to circumvent the free period, use fictitious data, disposable e-mails or payment methods.
2.12. Payment abuse. Dispute payments without grounds, use other people's or stolen payment methods, circumvent billing.
2.13. Removing notices of rights, Service identifiers, or circumventing technical protection measures.
3. Fair use of AI Features and Credits
3.1. The volume of AI Features included in a plan is intended for normal business work of a single Workspace within the paid Seats. Use at a volume significantly exceeding the typical (automated batch tasks, forwarding large volumes of documents, use as a gateway to models or as an API for third parties) is considered abuse.
3.2. The Provider may: apply rate, volume and cost limits; limit context size and number of requests; queue requests; temporarily reduce quality/model; suspend AI Features on reaching budget limits; require purchase of AI Credits or a plan upgrade.
3.3. AI Credits (Offer, clause 7) are not transferable or resellable and are for use in one Workspace.
3.4. Circumventing limits by creating multiple accounts or Workspaces is prohibited.
4. Use of API and integrations
4.1. API access is only through issued keys and in accordance with documentation. Keys are confidential; they must not be shared or embedded in public applications.
4.2. Rate limits and 429/Retry-After response codes must be observed; retry with exponential back-off; no bypassing limits by rotating keys or addresses.
4.3. Integrations (e-mail, CRM, platforms) are configured only within the Customer's rights to the relevant accounts; the Customer is responsible for settings and consequences (including sending e-mails and actions on its behalf).
4.4. It is prohibited to use the API to build public mirrors of Service data or for its mass export.
5. Limits (indicative)
To protect stability, limits apply (examples; actual values may change): [30] AI requests per user per hour; [300] per Workspace per hour; [1] active request per chat; [3] concurrent requests per Workspace; [10] chat file uploads per user per hour; maximum file size [25] MB; maximum [10] files per chat; limits on frequency of manual refresh from platforms and API requests. Current values are on the pricing page or in the documentation.
6. Reporting violations and vulnerabilities
Report AUP violations or vulnerabilities to r.latypov@plenergy.co.uk / r.latypov@plenergy.co.uk. Researchers acting in good faith report without public disclosure before a fix and do not access other people's data; we will not pursue good-faith research within these bounds [owner decision — responsible-disclosure policy].
7. Enforcement
7.1. For a breach the Provider may, at its discretion and without notice where there is urgency or risk: warn; restrict features or speed; remove or block content; suspend or block a User/Workspace; terminate the Agreement (Offer, clauses 19–20); notify competent authorities; claim damages (Offer, clause 18).
7.2. No refund is made for a blocked period where blocking is due to a breach.
7.3. The Provider is not obliged to monitor Content but may check technical indicators of violations (automatically, without reading content where possible).