Published legal document
User Agreement
Effective date18 August 2026
Last updated17 August 2026
Document size3,151 words · 39 sections
VERSION 3.1This User Agreement describes the practical responsibilities of a person who interacts with SRCAI.co. It complements the Terms of Service rather than repeating them. It applies to Website browsing, public forms, newsletter actions, the public AI Assistant, SRC Launch enquiries, SRC Mentor information and any future authenticated service that expressly links to it.
1. Honest participation#
Provide accurate, current and relevant information. Do not impersonate another person, manufacture credentials, misstate your authority or knowingly omit a fact needed to assess an enquiry. Correct material errors promptly. You are responsible for obtaining permission before submitting information about another person or organization.
2. Choosing the correct channel#
Use public forms only for ordinary enquiry information. Do not upload or paste identity documents, payment details, confidential access credentials, protected educational records, confidential legal files or other sensitive material into the AI Assistant or a general form. Wait for SRC AI or an approved Provider to identify a secure channel when a legitimate workflow needs stronger protection.
3. Website and content use#
You may read, link to and internally evaluate public Website content for lawful purposes. Do not copy substantial parts to create a competing database, remove ownership notices, misrepresent a page as your own, frame the Website deceptively or use SRC names in a way that suggests endorsement. Accessibility tools, ordinary search indexing and reasonable personal research are not prohibited by this rule.
4. Contact and enquiry responsibilities#
A contact or SRC Launch submission is a request for review, not an accepted engagement. Monitor the contact method you supplied, respond to reasonable clarification and tell SRC AI if you no longer want the enquiry pursued. Do not submit repetitive, deceptive or abusive enquiries or use a form to send unsolicited promotions.
6. AI Assistant responsibilities#
Ask questions within the Assistant’s public SRC information scope, review linked sources and apply independent judgment. Do not attempt prompt injection, secret retrieval, unpublished-content access, unauthorized access or conversion of the Assistant into an unrestricted service. Treat an answer as orientation, not as legal, tax, financial, investment, medical or other professional advice.
7. SRC Mentor information#
Public SRC Mentor material describes product direction and intended audiences; it does not admit a user to a pilot or create a learning or safeguarding relationship. Adults must not submit a child’s personal information through public channels. Parents, guardians, teachers and learners retain responsibility for consequential education, wellbeing and safety decisions.
8. SRC Launch enquiries#
Provide a lawful business purpose and accurate jurisdictional context. Do not use SRC Launch to conceal beneficial ownership, evade sanctions, mislead a registry, facilitate fraud or obtain a structure for unlawful conduct. Availability, customer checks, documents, fees and Providers are confirmed only after review. Never treat an enquiry response as a filing receipt or approval.
9. Future accounts and credentials#
If a future public service issues credentials, protect them, use the security options offered to you and report suspected compromise promptly. Do not share an individual account unless the service expressly supports delegated access. You may not access another user’s record or alter identifiers to test authorization.
10. Third-party services#
A Provider may impose separate eligibility, acceptable-use, identity, payment and privacy requirements. Review them before proceeding. Do not assume SRC AI can override a registry, government agency, payment service or independent professional decision. Report a material Provider problem through the SRC AI contact route so the coordination record can be reviewed.
11. Communications and records#
Keep copies of important confirmations and check that the sender and reference are genuine. Email can be delayed or impersonated. SRC AI will not ask for confidential access credentials through ordinary email. If a message appears suspicious, do not use its links; contact SRC AI through SRCAI.co.
12. Misuse, restriction and termination#
SRC AI may reject content, preserve proportionate evidence or suspend access when reasonably necessary to protect people, systems, legal duties or Providers. You may stop using a Public Service at any time. Ending use does not erase records that must be retained for security, disputes, legal obligations or a valid continuing request.
13. Disputes and policy hierarchy#
Raise a concern with enough detail for SRC AI to investigate. The Terms of Service establish the general legal framework; the Privacy Policy controls personal-information practices; the Acceptable Use Policy gives more detailed misuse rules; SRC Launch terms control formation-support matters; and a signed or accepted Service Confirmation controls the specific paid service. Mandatory law prevails where it cannot be varied.
14. Contact#
Questions, notices, complaints and requests may be sent through the SRC AI contact form. Use the category that best matches the request and provide enough information for SRC AI to identify the relevant interaction. Do not send account credentials, payment-card data, identity documents or other sensitive records through a public form. SRC AI may ask for proportionate evidence of identity or authority through an appropriate protected channel before acting on a request.
15. Consent and preference choices#
When a workflow asks for consent, make a genuine choice and use controls only for an address, device or person you are authorized to manage. Optional analytics and newsletter choices are separate from an enquiry that can be handled without marketing consent. Do not manipulate another person’s cookie preference, confirmation link or unsubscribe action, and do not claim that a pending subscription is confirmed.
You may change an available preference prospectively. A withdrawn preference does not erase a security record, completed transaction or other information retained on a separate valid basis. If the available control does not address your request, use the contact route and provide enough detail to locate the relevant interaction.
16. Reliance and consequential decisions#
You are responsible for deciding when an answer or public description is sufficient for low-risk orientation and when independent verification is required. Do not rely solely on the public Assistant or an undated page for a filing deadline, legal structure, tax position, visa, investment, health, safeguarding or other consequential decision. Linked sources can change and may apply only in a particular territory.
SRC AI welcomes corrections supported by a source, but a correction request does not authorize editing, scraping or security testing. If you believe a material public statement is wrong, identify the page and concern without sending unrelated personal data.
17. Respect for other people and their information#
Do not submit another person’s email, child information, ownership record or dispute narrative unless you have a lawful reason and appropriate authority. Minimize third-party details and tell SRC AI when authority is limited or contested. Public forms must not be used to shame, threaten, surveil or publish allegations about another person.
If an enquiry involves several founders, family members or representatives, each person remains responsible for their own representations. SRC AI may request a common authorized contact or pause until authority is clear. It will not disclose a separate user’s record merely because the requester claims a relationship.
18. Automated access and fair use#
Ordinary browsers, accessibility technology and recognized search indexing may access public pages. High-volume extraction, repeated form submission, credential attempts, evasive rotation, synthetic traffic and automation that burdens the service or defeats limits are prohibited without written permission. Public availability does not grant a licence to build a competing dataset or train a model on protected content.
If SRC AI offers an API, feed or export, use the documented interface, rate and purpose. Do not bypass a disabled control, alter identifiers to reach another record or treat a visible value as authorization. Public interface availability never grants access to protected information.
19. Payment and instruction safety#
A future payment request should identify the contracting party, service, amount, currency and approved method. Verify unexpected changes through a known channel. SRC AI is not responsible for money voluntarily sent to an impersonator where reasonable verification would have revealed the fraud, subject to applicable law and SRC AI’s own security responsibilities.
Do not initiate a duplicate payment or provide card or bank credentials through the Assistant or public contact form. Report a suspected duplicate or incorrect charge promptly with a non-sensitive transaction reference. Chargeback rights and deadlines are determined by the payment method and law; a user should not make a knowingly false chargeback claim.
20. Account delegation and future team access#
If a future service supports organizational roles, use named access rather than shared credentials. Administrators must grant the least access reasonably needed, review membership and remove access when responsibilities change. A role in the customer’s organization does not grant authority over SRC AI systems.
A delegated user must follow this Agreement and any role-specific terms. The customer remains responsible for lawful instructions from its authorized users, while SRC AI remains responsible for protecting service authorization boundaries. Suspected role escalation or misdirected access should be reported immediately and not explored further.
21. Cooperation with safety and compliance checks#
SRC AI or a Provider may request proportionate clarification where a submission appears inconsistent, unlawful, sanctioned, fraudulent or outside supported scope. Respond truthfully and use the secure channel identified for sensitive evidence. Do not split transactions, conceal ownership, submit altered documents or pressure personnel to bypass a Provider or authority rule.
A request, screen or pause is not a determination that misconduct occurred. SRC AI may be unable to explain confidential risk indicators or Provider criteria. If service is declined, the applicable terms govern records, charges and refunds, and the user may use the complaint route for a review that is available.
22. Updates and continued participation#
SRC AI may update this Agreement when public workflows, safety controls or linked policies change. The version and dates show the current publication. Material changes apply prospectively unless a lawful urgent security response requires immediate protection. An accepted paid service remains governed by its Service Confirmation where separate agreement is required.
Continuing to browse after a change does not create consent to an unrelated paid service, marketing message or new sensitive-data use. Where express agreement is needed, SRC AI should request it separately. Stop using the relevant workflow and contact SRC AI if a change is unacceptable or unclear.
23. Device and browser security#
Use a supported, reasonably updated browser and protect the device and email account used for SRC AI communications. Lock shared devices, review downloads and do not install software or browser extensions from an unverified message. A compromised device can undermine a valid SRC AI confirmation link or other trusted interaction.
If you suspect compromise, stop using affected links, secure the affected account through the relevant Provider and contact SRC AI through the genuine Website. Do not send confidential access credentials as evidence.
24. Confidential and commercially sensitive information#
Do not assume a preliminary enquiry is confidential. Share only enough non-sensitive context for routing until SRC AI accepts an engagement and identifies appropriate confidentiality and document controls. Marking a public-form message confidential does not change the channel’s design or create a professional privilege.
When an accepted service permits confidential material, disclose only information relevant to the scope and ensure you have authority to share it. Do not upload another company’s trade secrets, customer list or legal advice without permission.
25. Intellectual-property responsibilities#
Submit only text, names, logos, documents and other material that you own or may lawfully use. Tell SRC AI about material licence limits and do not ask it to remove ownership notices, copy a protected competitor experience or register a name known to infringe another person’s rights.
A company-name availability check is not a trademark clearance. Public SRC AI content may be quoted to the extent law and fair attribution allow, but substantial republication, resale, deceptive framing and removal of source context require permission.
26. Complaints and respectful communication#
A user may criticize a service, dispute a charge or make a rights request. Communicate relevant facts and requested resolution without threats, harassment, discriminatory abuse, doxxing, spam or deliberate falsehood. SRC AI may protect personnel and other users while preserving a legitimate complaint channel.
Repeated messages may be consolidated and an abusive channel may be limited without dismissing an unresolved legal or safety issue. Emergency services, courts and regulators should be contacted directly where they are the appropriate authority; the public Assistant is not an emergency channel.
27. Organizational users and internal approvals#
An organizational user must identify the correct customer and ensure instructions have necessary board, partner, member, guardian, budget or compliance approval. Do not use a personal relationship or job title to imply authority you do not have. Notify SRC AI when the authorized contact or ownership changes.
SRC AI may request evidence and may refuse conflicting instructions. It is not responsible for resolving an internal governance dispute and will not expose one representative’s communications to another without a valid basis.
29. Regulatory and territorial responsibility#
You remain responsible for laws that apply to your use, location, industry, communications and submitted information. Public availability does not mean every feature or service may lawfully be used in every territory. Do not use a VPN, proxy, nominee or false information to conceal a restricted location or purpose.
If a rule is uncertain, pause and seek qualified advice. SRC AI may request clarification or decline a path but does not provide a comprehensive legal determination through this Agreement.
30. Service completion and record keeping#
Review delivered work promptly and report a specific error within any approved review period. Keep independent copies of invoices, filings, confirmations, ownership records and compliance dates. Do not rely on an email inbox or SRC AI dashboard as the sole statutory record unless an accepted service expressly provides that function.
Completion of one task does not imply continuing monitoring, renewal, tax, filing or advisory responsibility. Continuing work requires a stated scope.
31. Children and family participation#
Adults must not direct a child to enter personal, educational, health, location or family information into the public Assistant or general forms. General public information may be reviewed together, but a future account or mentoring interaction requires the dedicated age, guardian, safety and privacy controls described in the Children & Family Privacy Notice.
A parent or guardian should use proportionate authority and respect a young person’s developing rights. SRC AI may refuse a request that appears unsafe, excessive or outside a verified guardian relationship.
32. Acknowledgement and updates#
By using the relevant public workflow, you acknowledge the practical responsibilities in this Agreement and the linked Terms and policies. You do not acknowledge a paid scope, marketing choice or future feature merely by browsing. Separate acceptance is required where the service or law calls for it.
Review the version and dates when returning after a material change. Contact SRC AI if a responsibility is unclear rather than guessing or attempting to test a restriction.
33. Form validation and anti-abuse controls#
Public forms apply proportionate validation and abuse protections. Do not disable, forge or evade those safeguards. A validation error asks you to correct the submission and does not prove that SRC AI assessed the underlying enquiry.
Repeated malformed or automated attempts can be rejected without creating a support record. If an accessibility tool or legitimate workflow is blocked, report the barrier through an available route rather than trying to bypass the protection.
34. Accuracy of translations and converted files#
If you provide a translation, scan, conversion or transcription, you are responsible for verifying that it is complete and corresponds to the source. Identify who prepared or certified it where that fact matters. Do not alter a document to hide a restriction, ownership fact, date or authority requirement.
Automated translation and optical recognition can make mistakes. SRC AI may request the source or an approved professional version, and a Provider or authority can reject a format even when it appears readable.
35. Names, domains and public representations#
Do not announce a company, product, domain or regulatory status as approved before the responsible registry, owner or authority confirms it. A public SRC Launch discussion, name search or domain availability display is provisional. You bear the risk of branding, printing or contracting before confirmation.
Do not register a domain or social profile that impersonates SRC AI or suggests a relationship that does not exist. A customer’s own approved company identity remains its responsibility.
36. Provider accounts and separate credentials#
A Provider may require you to create a separate account and accept its terms. Protect those credentials and do not send them to SRC AI unless a secure delegated-access workflow expressly requires it. SRC AI will not ask for confidential Provider access credentials through a public channel.
Removing SRC AI from a service does not automatically close a Provider account, and closing a Provider account does not automatically terminate every SRC AI obligation. Follow each applicable process and preserve confirmations.
37. Deadlines and reminders#
You must identify legal, government, payment, renewal and commercial deadlines and maintain your own calendar. A reminder is a convenience and can be delayed, filtered or based on incomplete facts. Unless a Service Confirmation assigns monitoring expressly, SRC AI has no continuing duty to identify a deadline after a discrete task ends.
Notify SRC AI promptly if an active request has a deadline, but do not assume it is accepted until confirmed. Seek urgent professional help where delay can affect rights.
38. Corrections and disputed instructions#
Review your submission and delivered records for spelling, addresses, ownership, dates, amounts and other material facts. Report an error clearly and distinguish a correction from a later change. SRC AI may require new authorization before changing a filing instruction.
When representatives give conflicting instructions, SRC AI may suspend work, preserve the record and require evidence or agreement. It does not decide a family, partnership, board or ownership dispute through support correspondence.
39. Survival and responsible exit#
After you stop using a service, duties concerning unpaid charges, intellectual property, confidentiality, security, record integrity, disputes and lawful use continue where their nature requires it. You must return or delete material you were not entitled to retain and stop representing an active relationship.
SRC AI may retain proportionate records under the Privacy Policy and provide an approved export or transition within scope. Ending one interaction does not unsubscribe an address or close an independent Provider automatically unless the relevant workflow says so.

Work with SRC AI