Acceptable Use Policy

Effective Date: pending activation (not set reserved for release).

Last Updated: pending activation (not set reserved for release).

Draft prepared and revised: 7 October 2026. Pending activation.

Non-binding summary. Use OwlMeans only for lawful work you are authorised to perform. Do not generate harmful code, infringe rights or bypass access and spending controls. You can report harmful content and challenge restrictions through support. This summary is outside the operative policy.

1. Scope and responsibility

1.1. This Policy is incorporated into Terms & Conditions, whose definitions and mandatory protections apply. The supplier is Igor Tkachenko OwlMeans Software (trading as “OwlMeans Software, JDG”), ul. Ariańska 9/5, 31-505 Kraków, Poland; NIP 6772507251; EU VAT identifier PL6772507251; REGON 527979906; support@owlmeans.com; +48 780 256 571. It covers website/inquiry use, Platform accounts, AI operations, APIs/MCP, connected repositories, previews and hosted applications to the extent supplied by OwlMeans.

1.2. The Customer shall instruct authorised Users, protect access and obtain rights to submitted material and connected resources. Customer application operators remain responsible for their lawful end-user rules. This allocation does not waive OwlMeans’ own legal, security, moderation or data-protection duties.

2. Prohibited activity

2.1. Do not use the Service for illegal activity; infringement of intellectual property or privacy; fraud, impersonation or deceptive reviews/testimonials; spam or unlawful solicitation; harassment, threats or discriminatory abuse; exploitation or sexual abuse of children; trafficking, terrorist support or other unlawful violence. Do not upload or generate material you lack authority to use, including confidential third-party records or unnecessary sensitive personal data.

2.2. Do not generate, deploy or distribute malware, ransomware, credential theft, unauthorised exploits or code intended to compromise others’ systems. Do not access accounts, repositories, infrastructure or personal data without authority, bypass authentication or safety controls, exfiltrate secrets or conceal malicious workloads. Legitimate security testing requires prior authority for the target and scope and must avoid harm, unlawful disclosure and disruption. Report discovered vulnerabilities privately to support with proportionate evidence; do not send live credentials or exploit unrelated accounts.

2.3. Do not conduct AI uses prohibited by applicable law, including unlawful manipulation, exploitation, discriminatory processing or surveillance. Regulated uses need their own lawful basis, safeguards and specialist assessment. Do not misrepresent AI Output as verified professional advice or remove legally required provenance/markings. Customer consent or third-party model availability does not legalise a prohibited use.

2.4. Do not evade payment, allowance, rate, token, compute, API, concurrency or storage controls; create deceptive accounts to multiply limited promotions; knowingly overload the Service; run unapproved mining, botnets or unrelated abusive compute; or probe another tenant. Disclosed purchased entitlements and valid spending authority govern ordinary usage. A restriction must be explained and proportionate, rather than an undisclosed reduction of agreed supply.

3. Detection, restrictions and review

3.1. OwlMeans may use automated checks and proportionate human investigation to detect unsafe inputs/workloads, malicious files and security or rights violations. Google reCAPTCHA supports bot, fraud and abuse prevention in selected workflows. Privacy and Cookies describe data/device processing; checks do not grant independent improvement, training or marketing permission. Automated checks can make mistakes and do not certify that accepted content or code is safe.

3.2. Measures can include refusing an operation, restricting affected content or access, requesting correction, temporarily suspending a workload or terminating a material breach under Terms section 20. Consider severity, context, repetition, affected rights and less restrictive measures. Give the Customer the applicable reason, scope and challenge channel; offer a reasonable cure opportunity where appropriate. Urgent risk may require immediate action, but does not remove mandatory reason-giving duties. Unused credits, prepaid supply and export follow the billing/refund rules and mandatory law, without punitive forfeiture.

3.3. Challenge a restriction at support@owlmeans.com, identifying the decision, affected account/content and relevant explanation. OwlMeans shall arrange review by a person with authority to reconsider it and communicate the result without undue delay. Necessary security or legally protected information may be withheld only to the extent lawful. Statutory courts, regulators and applicable external dispute routes remain available.

4. Illegal-content and copyright reports

4.1. Send a sufficiently precise report to support@owlmeans.com: explain the illegality or infringed right; identify the exact URL or other electronic location; supply necessary supporting particulars; give your name/email where required; and state your good-faith belief that the information is accurate and complete. Applicable child-sexual-offence reporting exceptions to notifier identification are preserved. Do not include unnecessary sensitive material. OwlMeans shall confirm electronic receipt, assess reports objectively and notify its decision and available redress without undue delay where required, including use of automated decision-making where applicable.

4.2. Where the Service qualifies as DSA hosting, applicable contact, notice-and-action and statement-of-reasons duties apply. Reasons shall identify the measure, relevant facts, contractual/legal basis, any automation and available redress and be supplied no later than imposition when Article 17 requires. Intermediary-service moderation-reporting duties have their own Article 15 scope and size exemptions; they are not limited to online platforms. Additional online-platform duties, including statutory internal complaints and certified out-of-court settlement, depend on the actual role and valid exemptions. If Article 20 applies, its complaint mechanism is free, available electronically for at least six months and decided with qualified human supervision. No automatic small-provider exemption or universal online-platform classification is claimed. A reporting form alone does not establish operational compliance.

4.3. Copyright reports should identify the work and alleged infringement, the reporter’s authority, location, contact information, good-faith basis, accuracy and signature. OwlMeans shall assess the report and afford the affected Customer an appropriate response route. Repeated established infringement may justify proportionate termination, with lawful exceptions and the Terms’ procedural protections. Do not submit knowingly false claims.

4.4. If OwlMeans establishes a US DMCA designated-agent process for a covered service, its actually registered agent’s name and contact details shall be published before that process is represented as operational. Any claimed safe harbour also requires the applicable repeat-infringer policy, standard-technical-measure, knowledge and financial-benefit conditions. A Section 512 notice additionally requires the statutory good-faith and accuracy/authority-under-penalty-of-perjury statements and physical/electronic signature. Under that process, OwlMeans shall act expeditiously on valid notices and promptly notify the affected User of notice-based removal or disabling. The support channel above is a general copyright-reporting channel, not a claim of registered-agent status or safe-harbour eligibility.

4.5. In an applicable DMCA counter-notice process, a counter-notice must contain the sender’s signature, identification and former location of removed material, the statutory good-faith mistake/misidentification statement under penalty of perjury, name/address/phone, and the required US federal-court jurisdiction and service-of-process consent. That procedural consent is separate from general consumer venue. OwlMeans shall promptly forward a valid counter-notice to the original notifier, informing it of restoration after 10 business days, and restore material within the statutory 10–14 business days after receipt unless the original notifier reports filing a court action seeking restraint, subject to Section 512 and any independently lawful restriction. No restoration promise overrides a binding order or other lawful content restriction.

5. Data, changes and contact

5.1. Report records and investigations shall be limited to legitimate handling, security and legal needs under the Privacy Policy/DPA. Confidential project material is not public merely because it is investigated. Changes follow Terms section 22, with applicable notice and rights. Contractual acceptance does not authorise retroactive data reuse or remove mandatory consumer protections.

5.2. Contact support@owlmeans.com, +48 780 256 571 or the address in section 1 for reports, challenges and assistance. Company information supplies the trader’s regional contact particulars. Account access and optional consent are not prerequisites for statutory reports or complaints.