Terms
Document version: 2026-10-12.2
Archived version. Open current version
1. Provider and scope
SeniAI is provided by freelancer Saeed Moradtalab, Paul-Jäkel-Straße 46, 09113 Chemnitz, Germany. These terms apply to public briefing and enquiry forms and project collaboration features on SeniAI. For offers published by other account holders, the provider identified on the offer is responsible for those services.
2. Enquiries and separate contracts
Submitting a brief, message or callback request is a non-binding enquiry. It does not place a paid order or confirm an appointment. Scope, fees, duration and any cancellation conditions are agreed separately before a paid contract. Statutory consumer rights, including any applicable withdrawal rights, remain unaffected.
3. Use and content
Provide accurate information and only content you may lawfully share. Do not upload credentials, malware or unnecessary personal information about others. You retain the rights to your content. It may be used only as necessary for the enquiry, the relevant project, communication and secure operation. This does not authorise publication of your answers.
4. AI agents and MCP
Submitting a form does not automatically send its contents to an external AI provider. Account holders can connect their own AI agents or applications through MCP to read and edit project data within their permissions. The account holder is responsible for selecting applications, setting permissions and ensuring lawful use. Keep access keys confidential and revoke them when necessary. AI output and customer input require expert review before binding adoption.
5. GitHub and payments
GitHub sign-in is optional. Payments may be processed through Stripe. The respective service terms also apply. Briefing forms require neither GitHub sign-in nor payment.
6. Availability, liability and statutory rights
Maintenance, technical faults and further development may temporarily affect availability. Statutory liability rules apply; liability for intent, gross negligence or injury to life, body or health is not excluded. Individual agreements take precedence. Mandatory statutory rights remain unaffected.
7. Accounts, authority and access security
Anyone acting for an organisation may make declarations and provide content only within their authority. Account holders must protect credentials, shared links, portal passwords and MCP keys against unauthorised use. If misuse is suspected, affected access must be blocked or revoked promptly and support informed. A recipient label or possession of a link does not establish a person’s identity or authority.
8. Public pages and rights to materials
Account holders select profiles, offers and materials for publication. Public content can be accessed, copied or indexed by third parties. Copyright, trademark, image and privacy rights must be checked before publication. SeniAI receives only the non-exclusive rights necessary to store, technically process, display and share content as instructed by the user. This does not transfer ownership or grant general advertising rights. Third-party open-source projects and materials remain subject to their respective licences.
9. Briefings, requirements and project approvals
Responses are assigned to the selected offer or project. Structured project briefings record the form version, answers, recipient assignment and receipt time. Amendments should remain identifiable. Receipt, a comparison table, a notification or an AI assessment alone does not constitute order confirmation, a binding scope change, acceptance or approval. Separate agreements and declarations by authorised participants govern these matters. Timestamps and checksums are technical evidence, not qualified electronic signatures or qualified electronic timestamps.
10. Data protection and connected applications
Account holders must have a lawful basis for processing personal data and inform affected individuals about their own processing. Where SeniAI processes data on an account holder’s instructions, a GDPR Article 28 agreement is required; these terms do not replace it. Account and project MCP access must be limited to necessary permissions. Read-only customer access does not permit changes to project data. Revoking a key does not automatically delete copies previously lawfully transferred to external services. The applicable responsibilities for retention and deletion must be observed.
11. Security measures and ending use
Where there are concrete indications of unlawful content, unauthorised access or threats to operations, affected content or access may be restricted to the necessary and proportionate extent. Where protection of those involved and the law allow, the affected person will receive reasons, ways to remedy the issue and an opportunity to respond. Paid services follow their contractual term and cancellation provisions. Account closure, data return and deletion requests may be sent to benmoradtalab@gmail.com. Statutory retention obligations and legitimate evidence requirements must be considered.
12. Versions, individual agreements and statutory rules
The version displayed at submission is recorded with that submission. Publishing new terms does not automatically amend existing contracts; a valid agreement or legal basis is required. Individual agreements take precedence. Statutory rules, particularly Section 306 BGB, govern provisions that are invalid or do not form part of the contract. These terms impose no exclusive jurisdiction and do not restrict mandatory consumer rights.