جاري التحميلLoading

Terms of Service

2026-09-10

This document is a binding contract between you and the provider. Read it before you pay. It sets out what you receive, what you undertake, what we do not warrant, and where any dispute is heard.

This document is read together with the Privacy Policy and the Refund and Exchange Policy as a single agreement. Where a clause in one conflicts in meaning with a clause in another, the document more specific to the subject prevails.

1. Definitions

1.1 Provider: Simplock, a trading name operated by an individual established in Libya. The words we, us and our mean the provider.

1.2 Customer: the holder of the account that created the subscription and paid for it. The words you and your mean the customer.

1.3 Service: everything the provider supplies over the internet under the subscription, including the instance, the dashboard, support and updates.

1.4 Instance: the bot, its database and its storage running for the customer's account alone, shared with no other customer.

1.5 Dashboard: the online control interface through which the customer manages the instance's systems.

1.6 Members: the users of the Discord server in which the customer runs the instance. They are not a party to this contract.

1.7 Term: the prepaid period during which the service runs, starting from the moment payment is confirmed.

1.8 Helper bots: additional Discord applications owned by the provider and licensed to the customer for the length of the subscription to perform specific functions.

1.9 The three documents: these Terms, the Privacy Policy, and the Refund and Exchange Policy.

1.10 Business day: any day other than Friday, Saturday, and public holidays in Libya.

1.11 Written notice: a message sent to the provider's address published in clause 22, or published to the customer in the dashboard, depending on the sender. A notice is deemed received when sent or published.

2. Acceptance of these terms

2.1 Creating an account, paying, or using the service in any form constitutes full and unconditional acceptance of the three documents. No separate signature is required.

2.2 If you do not accept a single clause of this document, do not create an account, do not pay, and do not use the service. There is no partial acceptance.

2.3 If you subscribe on behalf of a company, a team, or any legal person, you confirm you are authorised to bind it, and you and it are jointly and severally responsible for performing this contract.

2.4 Use of the bot inside Discord is also subject to Discord's terms and policies, which prevail over any promise in this document as regards the platform itself.

3. Eligibility and the account

3.1 To create a subscription the customer must have reached the age of eighteen and have full legal capacity to contract. Creating the account is your representation that this is so.

3.2 The minimum age for server members is thirteen, or the higher limit Discord imposes in the member's country. Verifying this is the customer's responsibility as the server's administrator, not the provider's.

3.3 The provider may at any time request evidence that the age requirement is met, and may suspend the account immediately until the request is satisfied. An account whose holder is shown to be under eighteen is terminated, and the Refund and Exchange Policy applies to it.

3.4 The customer is fully responsible for all activity carried out from the account and for protecting the means of access to it: the linked Discord or Google account, the email address, passkeys, the emergency code, and the two step code. Whoever holds those means holds control of the instance.

3.5 Team members granted permissions in the dashboard by the customer act in the customer's name, and their acts are attributed to the customer without distinction.

3.6 You undertake that the information you provide is accurate, complete and current. An account opened with misleading information, or to circumvent an earlier suspension, is terminated without refund.

4. Who you are contracting with

4.1 The party contracting with you is Simplock, a trading name operated by an individual established in Libya. No registered legal entity is a party to this contract unless its name appears expressly in this document.

4.2 The provider's establishment and centre of management are in Libya, and clause 21 on governing law and jurisdiction rests on that basis.

4.3 The provider's formal contact details are set out in clause 22. Those channels alone are valid for any notice or claim relating to this contract, and no correspondence through another channel is recognised.

5. What you receive

5.1 For the length of the term you receive an independent instance with its own database and storage, a dashboard, technical support, and the updates issued during the term.

5.2 The bot's identity, being its name, avatar, banner, description and status, is your choice and remains so while the subscription is live, within what Discord permits and within the name change limits published in the dashboard.

5.3 The service is supplied exclusively over the internet. The provider does not deliver a copy of the software, its source code, or any part of it. The subscription is a temporary licence to use, not a sale of a product nor a transfer of ownership.

5.4 The features and limits included in your plan are those shown on the plans page at the moment of payment, and those alone are binding. No description in marketing material or in a support conversation that contradicts them is recognised.

6. Subscription and billing

6.1 The subscription is prepaid for a term chosen by the customer. There is no automatic renewal and no recurring charge against any payment method. The service runs to the end of the term and then stops under clause 18 unless the customer renews it.

6.2 On renewal, or on moving between plans, the new term is added on top of whatever remains of the current term, so no paid day is lost.

6.3 The price that applies is the one displayed at the moment payment is completed. No later price change applies retroactively to a term already paid.

6.4 Payment in digital currency: the amount due is the amount stated in the order when it was created, and network fees and exchange differences are borne by the sender. Sending to an address or a network other than those stated in the order may mean the amount is lost permanently. That is beyond the provider's power to recover and creates no obligation.

6.5 An order not paid within the window stated in it lapses automatically, and a new order must be created at the price then in force.

6.6 Any taxes, duties or customs obligations imposed by the customer's country on the purchase are borne by the customer alone and are not deducted from the amount due to the provider.

7. Refunds and payment disputes

7.1 Each customer's first subscription is covered by a full money back guarantee for 5 days from payment. Its details and its excluded cases are in the Refund and Exchange Policy, which forms an integral part of this contract.

7.2 Apart from that guarantee, the customer's termination of the subscription by choice gives rise to no refund of the remaining term.

7.3 Every refund of an unused term in this document is caused by an act of the provider alone, and is confined to four cases: removal of a material feature under clause 17, complete discontinuation of the service under clause 18, a force majeure event that persists under clause 20, and a change to these terms that the customer rejects under clause 21. No other case is analogous to these.

7.4 Because payment is made in digital currency or by direct transfer, the only recognised channel for requesting a refund is the account page or writing to the support address in clause 22.

7.5 If the customer opens a payment dispute or a forced reversal claim with any processor or platform without first writing to support and allowing seven days for a reply, that is a breach of this contract. The provider may then suspend the instance immediately until the dispute is resolved.

7.6 Suspension under clause 7.5 stops the instance running but does not delete its data, which remains stored for the whole retention period stated in clause 18. The suspension is lifted as soon as the dispute is resolved in favour of either party.

7.7 Attempting to collect the same amount twice, by requesting a refund and opening a payment dispute over the same transaction, is abuse that warrants termination of the subscription without refund.

8. Availability and service credit

8.1 The provider undertakes to use the means necessary to keep the instance running at a monthly availability of not less than 99.9 per cent, measured over the calendar month.

8.2 Availability is measured by the instance's ability to connect to Discord and respond to commands. Minor slowness is not an outage, nor is a fault in a single feature while the instance keeps running, nor is any interruption of two consecutive minutes or less.

8.3 The following are excluded from the availability calculation: outages at Discord or at any third party on which the service depends; scheduled maintenance announced twenty four hours in advance, provided it does not exceed four hours in a month; emergency maintenance required to close a security vulnerability; the customer's own error, configuration, revocation of the bot token or change to its permissions; suspension of the account for non payment or for breach of these terms; force majeure as defined in clause 20; and network interruption outside the provider's data centres.

8.4 If availability falls below the threshold in a given month, the customer is entitled to a credit in days added to the subscription term: one day for each hour of complete outage beyond the threshold, up to a maximum of fifteen days for any one month.

8.5 The credit is added to the term. It is not paid in cash and is not convertible into any monetary value, and it is the sole and exclusive remedy for a failure to meet the availability commitment.

8.6 The credit is claimed by written notice within thirty days of the end of the month claimed for, and the right to it lapses on expiry of that period. The provider's monitoring records are the reference for calculating outage.

8.7 Apart from this clause, the provider gives no express or implied warranty as to availability or continuity of the service.

9. The service's dependence on third parties

9.1 The service rests first on the Discord platform, and on hosting and network providers, payment processors, compute capacity providers, audio and media sources, and certificate and anti abuse services.

9.2 A fault, outage or slowdown at any of them affects the service even when the provider's own systems are sound. That is beyond the provider's control, the provider is not liable for damage arising from it, and it does not enter the availability calculation under clause 8.3.

9.3 A third party may change its terms, prices or interfaces, or discontinue a service on which a feature depends. A feature may then stop, change how it works, or be removed, without that being a breach by the provider.

9.4 In return the provider undertakes to monitor faults and restore service as quickly as it can, and to look for a substitute for a discontinued service where a practical substitute exists.

9.5 If Discord restricts the customer's account, server, or the application itself, that is Discord's decision alone and imposes no obligation on the provider.

10. Server growth and platform limits

10.1 Discord sets a limit on the size of servers an application may operate in. As a server approaches ten thousand members, some of the bot's capabilities become conditional on formal approval from Discord, which Discord alone grants, and neither the provider nor the customer can guarantee that it will be granted or when.

10.2 If that approval is not granted or is delayed, the systems that depend on it stop. They are: welcome and farewell messages, automatic roles on join, invite tracking, auto replies, the counting system, AI conversation, and everything that reads message text or tracks members joining and leaving.

10.3 Everything else keeps running, including: commands, buttons, menus and modals; tickets; role panels; protection systems; voice and music; economy and games; and scheduled messages.

10.4 The provider notifies the customer as the server approaches this limit, and handles filing and following up the request.

10.5 The stopping of the features listed in clause 10.2 for this reason is not a breach of this contract, gives rise to no refund and no credit, and does not enter the availability calculation. The customer remains free not to renew.

11. The customer's responsibilities and server content

11.1 The customer decides everything in the server: which systems are enabled, what is logged and stored, what replies and messages are written, and who is granted permissions. The provider supplies the tool, and the customer decides how it is used.

11.2 In respect of member data the customer is the controller and the provider is a processor acting on the customer's behalf and on the customer's instructions. The customer must inform members what the bot collects, comply with the data protection laws applicable to the customer and to the members, and answer their requests for access, deletion or objection.

11.3 Content the customer uploads or writes in the dashboard is the customer's sole responsibility: images, files, text and links. The customer grants the provider a limited, non exclusive licence to host, display and transmit that content to the extent necessary to deliver the service, and for nothing else, and that licence ends when the content is deleted or its retention ends.

11.4 The customer undertakes not to make the bot an instrument for breaking the law or Discord's terms, and bears alone whatever arises from doing so.

12. Acceptable use

12.1 The following are strictly prohibited: unlawful content; any sexual content involving minors in any form; attacking servers or accounts by flooding, spam or impersonation; circumventing a ban or a suspension; and harvesting member data to sell or leak it.

12.2 Also prohibited: attempting to uncover, decompile or reverse engineer the source code; penetration testing or vulnerability scanning without prior written permission; exploiting a fault in the currency, the shop or payment instead of reporting it; reselling, renting or sharing the instance with a third party; presenting the service as the customer's own product; and imitating the provider's brand.

12.3 Resources are shared, so unfair use is prohibited: excessive automated requests against the dashboard or the interfaces, running tasks unrelated to administering the server, and consuming AI or media quotas in a way that degrades the service for others. The provider applies fair technical limits and warns the customer before restricting, unless the harm is immediate.

12.4 Reporting a security vulnerability in good faith is welcome and the reporter will not be pursued for it, provided the vulnerability is neither exploited nor published before it is fixed.

12.5 A breach is met with a warning, a restriction, or immediate suspension without refund, according to its gravity and repetition, and the provider states the reason in a written notice.

13. Artificial intelligence features

13.1 The artificial intelligence systems in the service run on models belonging to the provider and operated by the provider. The customer needs no key and no account with any other party, and is never asked for one.

13.2 These models run on compute capacity supplied by external infrastructure providers. Those providers do not use customer content to train their own models and are contractually bound not to.

13.3 Model output is generated automatically and may be inaccurate or unsuitable. It must not be relied on as legal, medical, financial or professional advice. Decisions in the server are the customer's, and reviewing what the bot publishes is the customer's responsibility.

13.4 Enabling these systems means the text of the messages the bot processes and the media attached to them are processed for that purpose, and that the provider may use what is necessary from them to develop its own models and their dictionaries. The detail is in the Privacy Policy, and control rests with the customer, who may disable them wholly or partly from the dashboard.

13.5 Usage quotas may be restricted to preserve the stability of the service, and the models used, their names or their limits may change at any time without that amounting to removal of a material feature.

14. Helper bots

14.1 All helper bots are applications owned by the provider. The customer enters no token and is never asked for one, and ownership of those applications does not pass to the customer in any circumstances.

14.2 Helper bots are licensed to the customer for the length of the subscription alone and revert to the provider when it ends.

14.3 The number of helper bots is limited by the plan and by Discord's technical constraints, among them that one bot may occupy only one voice channel in a given server at a time.

15. Intellectual property

15.1 The software, the design, the interface, the documentation, the name and the logo, and all intellectual property rights attaching to them, belong to the provider alone. The subscription grants a personal, non exclusive licence to use, not transferable and not sublicensable, which ends when the subscription ends.

15.2 Customer content remains the customer's: settings, text, images and server data. The provider claims no ownership over them.

15.3 Suggestions and feedback the customer sends the provider may be implemented and used by the provider without compensation and without restriction, and create no right in the product and no claim for the customer.

16. Maintenance and backups

16.1 The provider carries out scheduled maintenance and emergency maintenance. Scheduled maintenance is announced at least twenty four hours in advance, and the provider seeks to place it in periods of low use.

16.2 The provider takes periodic backups for operational and disaster recovery purposes. Those backups are not a substitute for the customer's own backup and are not handed over on request.

16.3 The backup tool in the dashboard is available to the customer, and taking a backup before any major change is advised.

16.4 The provider does not guarantee recovery of data lost through an act of the customer, of a member of the customer's team, or through a deletion either of them carried out.

17. How the service evolves and features change

17.1 The provider continually adds features, alters others and improves the rest. The subscription is to the service as a whole, not to any particular feature nor to any particular interface.

17.2 The provider may remove or replace a feature if it becomes unsafe or unmaintainable, if the third party it rests on falls away, or if its use is negligible.

17.3 If the removal is material and affects the reason for the subscription, the provider announces it at least thirty days before it takes effect. The customer may then terminate the subscription and recover the value of the unused term. The cause of that refund is the provider's removal of the feature, not the customer's wish to leave the service.

17.4 Features marked as experimental may change or disappear without notice, do not enter the provider's obligations, and clause 17.3 does not apply to them.

18. Suspension, termination and the fate of your data

18.1 When the term ends without renewal a grace period of 3 days begins, during which the instance keeps running.

18.2 When the grace period expires the instance is stopped and the service ceases, and the data remains stored for a further 60 days, during which the customer may renew and recover everything as it was left.

18.3 When the retention period expires the instance, its database and its files are deleted permanently and irreversibly, and the provider cannot restore them thereafter by any means.

18.4 The provider may suspend immediately in the case of a serious breach, of use that threatens the service or other customers or exposes the provider to legal liability, or of a payment dispute under clause 7.5. The provider states the reason in a written notice.

18.5 The customer may terminate the subscription at any time from the account page. Any resulting refund is governed by clause 7 and by the Refund and Exchange Policy, and does not include the value of the remaining term once the guarantee period has expired.

18.6 The provider may discontinue the service entirely for any reason on written notice of not less than thirty days, refunding the value of the unused term and allowing sufficient time to take backups.

19. Disclaimer, limitation of liability and indemnity

19.1 Apart from the availability commitment in clause 8, the service is provided as is and as available, with no express or implied warranty of any kind, including warranties of merchantability, fitness for a particular purpose, and non infringement. The provider does not warrant that the service will be free of errors or interruption, nor that it will produce any particular result in the server's growth or discipline.

19.2 The provider is not liable for indirect, consequential or incidental damages, for lost profits, for reputational harm, or for loss of data arising from causes beyond its control.

19.3 In every case, the provider's total aggregate liability to the customer for all claims does not exceed what the customer actually paid for the service in the twelve months immediately preceding the event giving rise to the claim.

19.4 Nothing in this clause is intended to exclude or limit liability that the applicable law does not permit to be excluded or limited, such as fraud, gross negligence, or personal injury.

19.5 The customer undertakes to defend and indemnify the provider against any claim, action, fine or legal cost arising from the customer's use of the service, the customer's server content, the customer's breach of these terms, or the customer's failure in its own data protection duties towards its members.

20. Force majeure

20.1 Neither party is answerable for delay or breach caused by an event beyond its reasonable control, including war and civil unrest, natural disaster, widespread loss of electricity or internet, large scale cyber attack, government decision or blocking, and the failure of a material third party.

20.2 The affected party notifies the other of the impediment as soon as it can, and does what it is able to mitigate its effect.

20.3 If the impediment persists for more than thirty consecutive days, either party may terminate the contract by written notice, and the customer is refunded the unconsumed part of the term. The cause of that refund is the stoppage of the service by the impediment, not the customer's voluntary termination.

21. General provisions

21.1 Changes: the provider may update these terms. Any material change is published here with an updated date and notified to the customer in the dashboard thirty days before it takes effect. Continuing to use the service after it takes effect is acceptance. If the customer rejects it, the customer may terminate and recover the unused term, and the cause of that refund is the provider's change to the contract, not the customer's wish to leave it.

21.2 Assignment: the customer may not transfer the account, its rights or its obligations to another party without the provider's prior written consent. The provider may transfer this contract in a merger or sale of the business, with the customer's rights unchanged.

21.3 No waiver: a party's forbearance in enforcing a clause once or more does not forfeit its right to enforce it later, and is not a waiver of any other right.

21.4 Severability: if a competent authority holds a clause invalid or unenforceable, the remaining clauses continue in full force, and the invalid clause is replaced by the closest valid clause to the parties' intention.

21.5 Entire agreement: the three documents are the entire agreement between the parties and supersede every earlier verbal promise, correspondence or offer.

21.6 Independence: the relationship between the parties is one of independent contractors. This contract creates no partnership, agency, employment relationship or joint venture.

21.7 Amicable resolution: the parties seek to resolve any disagreement amicably within thirty days of a written notice stating the subject of the disagreement and what is sought.

21.8 Governing law and jurisdiction: failing amicable resolution, this contract and any dispute arising out of or connected with it are governed by the law of Libya alone, and the courts of Libya, where the provider is established, have exclusive jurisdiction, to the exclusion of any other law and any other forum. By using the service the customer accepts that jurisdiction and waives any objection of venue or forum non conveniens. Conflict of law rules and the United Nations Convention on Contracts for the International Sale of Goods do not apply.

21.9 Language: this document is published in Arabic and in English, and the two versions carry the same meaning. Where an interpretation differs, the English version governs.

21.10 Notices: the provider's notices reach the customer in the dashboard and on the account and are deemed received when published. The customer's notices are sent to the address in clause 22 and are deemed received when sent.

21.11 Survival: clauses 11.3, 15, 19 and 21 survive the expiry or termination of this contract, as does every clause whose nature requires it to survive.

22. How to reach us

22.1 For formal contact on anything concerning these terms, and for notices and claims: support@simplock.net

22.2 For technical help and day to day questions, the support server on Discord: https://discord.gg/simplock

22.3 Support is also available from your account page after subscribing, and that is the preferred channel for anything concerning your instance.