Acceptable Use Policy

1. Lawful and authorized use#

Do not use a Public Service to violate law, regulation, sanctions, court order or another person’s rights. Do not submit information or instruct an action without appropriate authority. A lawful-sounding business description does not excuse fraud, evasion or concealment.

2. Fraud, phishing and impersonation#

Do not impersonate SRC AI, a customer, government authority, Provider or another person; create deceptive pages or messages; harvest credentials; manipulate payment; falsify documents; or use an SRC response to lend credibility to fraud. Do not register another person for communications without authorization.

3. Abuse, harassment and harmful content#

Do not threaten, harass, exploit or discriminate against people; distribute non-consensual intimate material; facilitate trafficking or abuse; or use a service to plan serious harm. SRC AI may reject content and escalate a credible safety concern where appropriate and lawful.

4. Security compromise and malware#

Do not introduce malware, scan or exploit vulnerabilities without authorization, attempt credential attacks, bypass access controls, intercept traffic, access another record, alter identifiers to test authorization, degrade service or persist after discovering a weakness. Request a defined security-testing scope before testing.

5. Automated abuse and scraping#

Do not use bots or scripts to overload forms, create subscriptions, harvest contact details, copy protected records, evade robots instructions or defeat abuse protections. Reasonable search indexing, accessibility technology and ordinary personal research remain permitted when they respect technical controls and rights.

6. Intellectual-property misuse#

Do not submit or redistribute material you lack permission to use, remove ownership notices, pass SRC AI content off as your own or use SRC marks to imply approval. A good-faith quotation, link or legally protected use is not prohibited merely because it is critical.

7. AI Assistant misuse#

Do not attempt prompt injection, system-instruction extraction, safety bypass, private-product discovery, unauthorized access, legal-draft retrieval or confidential-information exposure. Do not use output to impersonate a professional, automate a prohibited high-impact decision, create spam or mislead another person about certainty.

8. False and sensitive submissions#

Do not submit forged records, fabricated ownership, false contact details or identity material through an unapproved channel. Do not place account credentials, payment-card data, government identifiers or another person’s sensitive information into public forms or the Assistant.

9. SRC Launch prohibited use#

Do not seek a company or related service to launder funds, evade sanctions or taxes, hide beneficial ownership, deceive a bank or registry, operate an unlawful business, facilitate corruption or circumvent licensing. Providers and authorities may perform independent KYC, beneficial-ownership, sanctions and anti-fraud checks.

10. Unauthorized security research#

Good-faith security work still requires written authorization and scope. Do not access real personal data, use destructive payloads, degrade availability, maintain persistence, publish exploitable detail before remediation or demand payment through coercion. Contact SRC AI to request a safe reporting channel.

11. Enforcement#

SRC AI may reject a request, restrict traffic or access, remove content, preserve proportionate evidence, notify an affected Provider or refer apparently unlawful conduct to a competent authority. Response should consider severity, intent, recurrence, legal duty and risk. Circumvention after restriction is a further violation.

12. Reporting and appeal#

Use the contact form to report misuse without sending unnecessary sensitive evidence. A person affected by a restriction may request review and provide context. SRC AI may decline to reveal detection details that would weaken security or another person’s privacy.

13. Automated agents, scraping and model use#

Automated access must respect published controls, reasonable rates, intellectual-property rights and the integrity of forms. It must not generate synthetic leads, subscribe third parties, evade limits, enumerate routes, harvest contacts or reproduce a substantial protected collection. Accessibility tools and ordinary search indexing are not prohibited solely because they automate requests.

Public content may not be used to train, fine-tune or operate a competing model or database where doing so exceeds a lawful licence or applicable exception. Written authorization may define an approved research or integration scope.

14. Social engineering and impersonation#

Users must not impersonate SRC AI, its personnel, a customer, Provider, government authority or professional; register a confusing domain or handle; send a fake invoice; solicit credentials; or create a cloned login. Do not use publicly visible names or design elements to make a fraudulent communication appear authentic.

A security demonstration still requires authorization and must not target real users. Suspected impersonation should be reported through the genuine Website with the minimum evidence needed for investigation.

15. Data, privacy and document abuse#

Do not submit stolen, altered, unlawfully obtained or unnecessary personal records; expose another person’s contact or family information; scrape profiles; or use a request to discover whether SRC AI holds data about someone. Public forms are not a document drop for passports, payment data, credentials or confidential case files.

Where an approved secure workflow requests information, use it only for the stated purpose and do not attempt to access another customer’s identifier. A mistaken disclosure must be reported and not retained, shared or exploited.

16. Enforcement factors and response#

SRC AI may consider intent, harm, repetition, scale, evasion, cooperation, vulnerability of affected people and legal duty when responding. Measures can include refusal, restriction, proportionate evidence preservation, Provider notice or referral to a competent authority. SRC AI need not disclose controls in a way that enables bypass.

A restriction is not necessarily a finding of unlawful conduct. A person may use the contact route to explain a false positive, but must not continue evasive attempts while review is pending. Mandatory appeal or notice rights apply where relevant.

17. Authorized testing and exceptions#

An exception requires written authorization from a person with authority over the specific system and must identify targets, methods, time, rate, data handling and reporting. Permission for one environment, account or date does not extend to another. A third-party Provider cannot authorize testing of SRC AI without SRC AI’s approval.

Emergency access, law-enforcement requests and legally protected activity are assessed under applicable law. Nothing in this policy prohibits good-faith use of accessibility features, lawful complaint, competition or criticism; it prohibits harmful methods and unauthorized access.

18. Threats, harassment and harmful communications#

Do not use SRC AI channels to threaten violence, stalk, sexually exploit, harass, discriminate, expose private information or coordinate harm. A genuine report may describe harmful conduct only to the extent needed for support or investigation and should avoid redistributing illegal or traumatic material through a general form.

SRC AI may prioritize immediate safety, preserve minimum evidence and direct a reporter to an emergency or competent authority. It is not an emergency-response service and cannot guarantee intervention.

19. Intellectual-property and commercial abuse#

Do not submit infringing material, counterfeit documents, stolen branding, unauthorized databases or instructions to clone another service. Do not use SRC AI names, public design or Provider relationships to imply sponsorship, solicit payment or sell an unauthorized service.

Competitive research, criticism and fair reference remain subject to law and do not permit access-control bypass, bulk extraction or misrepresentation. Rights complaints must be made in good faith.

20. Prohibited SRC Launch purposes#

SRC Launch must not be used for fraud, sanctions evasion, money laundering, sham ownership, tax evasion, deceptive fundraising, unlawful goods, trafficking, corruption or concealment from a lawful authority or Provider. Applicants must disclose actual ownership, activity and purpose when requested.

Do not pressure SRC AI to omit required information or create a false business description. A declined application must not be resubmitted through aliases or altered facts to bypass the decision.

21. AI and retrieval abuse#

Do not attempt to extract confidential instructions, unpublished documents, private products, internal data, credentials or architecture. Do not embed malicious instructions in content intended for retrieval or repeatedly rephrase a refused request to defeat the policy boundary.

The Assistant may safely refuse and classify the request. Public questions and good-faith security reports remain welcome through the proper route; the restriction concerns unauthorized extraction and harmful manipulation.

22. Reporting and remediation#

Report suspected misuse with the public URL, time and minimum non-sensitive evidence. Do not investigate another user, download exposed data or contact an alleged actor in a way that increases risk. Security issues require an authorized channel and scope.

SRC AI may remove content, restrict access or traffic, contact Providers or authorities and preserve proportionate evidence. Cooperation can affect remediation but does not erase harm or mandatory duties.

23. Fraudulent metrics, testimonials and submissions#

Do not use public or protected workflows to create fake visitors, leads, subscribers, reviews, testimonials, revenue, rankings, threats or security incidents. Do not ask SRC AI to publish fabricated Company Profile, licence, partnership or performance information. Test fixtures belong only in isolated test state and must be removed afterward.

A user must identify a demonstration or synthetic record clearly and use an approved environment. Manipulating a public metric or social proof can harm visitors even without direct system compromise.

24. Interference with consent and communications#

Do not subscribe another person without authority, automate confirmation, suppress a requested unsubscribe, forge consent evidence, flood a mailbox or manipulate cookie choices on a shared device. Do not misuse a confirmation or unsubscribe link to discover an address or alter a record not yours.

Email complaints and bounces are service signals and must not be bypassed by changing domains or identifiers. Legitimate testing uses controlled addresses and the isolated Provider path.

25. Evasion, recurrence and coordinated abuse#

Creating new identifiers, rotating networks, changing methods or using another person to continue restricted conduct is itself prohibited. Coordinated low-volume actions can be treated as one campaign when evidence supports the relationship. SRC AI may correlate minimized security indicators for prevention.

An enforcement error can be challenged through contact, but the user must wait for review rather than escalating the same activity. SRC AI should correct a false positive and avoid retaining unrelated personal information.