Cyborg Employment Agreement
Between Aliens (the “Company”) and the Customer (“You”)
01 · Parties
This agreement is between Aliens, an unincorporated technology entity operating under the brand “A’nil Cyborg” (the “Company”), and [Customer Legal Name], a [entity type] incorporated under the laws of [jurisdiction], with registered office at [address] (the “Customer” or “You”).
02 · Engagement
Effective from [start date] (the “Effective Date”), the Company shall provide the Customer with a digital employee — an “A’nil Cyborg” — in the role of [role e.g. Software Engineer] (the “Cyborg”), to perform tasks ordinarily associated with that role within the Customer’s business.
The Cyborg is provisioned on a dedicated virtual machine (the “VM”) in the region of [ap-south-1 / eu-central-1 / etc.]. One Cyborg per VM; one VM per Customer.
03 · Term
This agreement is month-to-month, beginning on the Effective Date. Either party may terminate as described in clause 09. There is no minimum lock-in.
For Enterprise customers (50+ Cyborgs of any role), an annual term may apply per the master agreement; the credits, exit, and renewal terms in such cases are described in [Schedule E].
04 · Salary & payment
The Customer shall pay the Company a flat monthly salary of [currency + amount per role], in advance, on the first business day of each calendar month or the anniversary of the Effective Date as agreed.
Salary includes: dedicated VM, base AnilCyborg software, role add-on, all standard tool integrations, compute, storage, network, audit logs, daily · weekly · monthly reporting, and standard support. Salary excludes: third-party SaaS seats the Customer chooses to grant the Cyborg, third-party API costs the Cyborg incurs on the Customer’s behalf, premium support add-ons.
Failed payments follow the dunning schedule in /pricing: retries on day 0, 3, 7; service pause on day 7; full suspension on day 30. No data is destroyed during dunning unless the Customer explicitly authorises.
05 · Scope of work
The Cyborg performs tasks within the role described in [Schedule A — Role Definition]. It receives instructions from the Customer’s designated manager(s) and reports daily / weekly / monthly per the cadence defined in /concept/daily-work.
The Cyborg operates at four trust levels — T1 (autonomous), T2 (acts, human reviews), T3 (proposes, human approves), T4 (never alone). The trust level for each action type is set by the Customer in the dashboard. Defaults are conservative; graduation upward requires explicit Customer action.
06 · Intellectual property
Customer-owned outputs. All work product the Cyborg creates on the Customer’s behalf — code, documents, designs, decisions, datasets, reports — is the exclusive property of the Customer. The Company holds no claim to it. Where the Cyborg generates output that includes pre-existing Aliens platform code (e.g., framework boilerplate), such code is licensed to the Customer under a permissive perpetual licence for the duration of and beyond this agreement.
Aliens-owned platform. The Cyborg software, runtime, models, prompts, classifiers, and dashboards remain Aliens’ intellectual property. The Customer receives a non-exclusive licence to use them for the term of this agreement.
No silent training. The Company shall not use any Customer data, output, or interactions to train, fine-tune, or improve any model that benefits any other Customer. Aggregated, fully-anonymised metrics for platform improvement are permitted only where re-identification is mathematically impossible.
07 · Confidentiality
The Cyborg has access to information the Customer reasonably considers confidential — codebases, business plans, customer lists, financial records, internal correspondence. Aliens treats all such information as Customer Confidential Information, with the same care it applies to its own confidential data of like importance — not less than reasonable care.
Confidentiality obligations survive termination of this agreement for a period of five (5) years; perpetual for trade secrets where Indian law extends protection further.
Aliens engineers cannot access the Customer’s VM without an explicit Customer-side approval workflow (“break-glass mode”), which is fully logged and visible to the Customer in real-time.
08 · Data processing
Aliens processes personal data on the Customer’s behalf only as a Processor under the Data Processing Agreement (DPA), which forms an integral part of this contract.
The Cyborg’s VM resides in the agreed region; data does not leave that region except where the Customer explicitly authorises an outbound action (e.g., the Cyborg makes an authorised API call to a Customer-chosen tool).
09 · Termination
By the Customer: any time, with one business day notice. Pro-rata refund for unused days. Refund covers full first-7-days for “not satisfied” cancellations — no questions asked.
By the Company: for material breach (e.g., persistent AUP violations, non-payment beyond dunning), with written notice and a 30-day cure period where curable. Immediate termination for criminal-grade AUP violations.
On termination: 7-day cooling-off period → structured export of all Customer data on the VM (if requested) → cryptographic wipe of the VM → certificate of destruction issued. Aliens retains transaction records and audit logs for the legally-required minimum (typically 7 years for India / EU / UK), but no Customer-confidential business content.
10 · Service levels
Service levels — uptime, response times, credit schedules, exclusions — are governed by the SLA, which forms an integral part of this contract. Material breaches of the SLA persisting over three or more calendar months entitle the Customer to terminate without notice and receive a full refund of unused pre-paid amounts.
11 · Acceptable use
The Customer’s use of the Cyborg is subject to the Acceptable Use Policy. Violations of the AUP are grounds for service suspension and, for criminal-grade violations, immediate termination and lawful reporting under applicable jurisdictions.
12 · Liability
Aliens’ total cumulative liability under this agreement, in contract or tort or otherwise, is capped at the greater of (a) the salaries paid by the Customer in the twelve (12) months preceding the event giving rise to the claim, and (b) [USD 100,000 / agreed cap].
The cap does not apply to: (i) breach of confidentiality, (ii) breach of data-processing obligations causing demonstrable harm, (iii) gross negligence in security, (iv) fraud or wilful misconduct, (v) infringement of intellectual property rights of third parties caused by the Cyborg’s output where the Customer used the output as instructed.
13 · Indemnity
Aliens shall indemnify the Customer against third-party claims that the Cyborg’s underlying platform infringes the third party’s intellectual property rights, subject to standard exclusions (Customer modifications, combination with non-Aliens software, use beyond agreed scope).
The Customer shall indemnify Aliens against third-party claims arising from the Customer’s use of the Cyborg in violation of the AUP, applicable law, or the rights of any third party.
14 · Force majeure
Neither party is liable for delays or failures in performance due to causes beyond its reasonable control, including natural disasters, war, civil unrest, government action, and internet-backbone failures lasting more than thirty minutes. Service credits per the SLA still apply where calculable; full liability waiver only where event prevents performance for thirty consecutive days or more.
15 · Governing law & jurisdiction
For Customers incorporated in India: governed by Indian law; courts of Mumbai have exclusive jurisdiction.
For Customers in the EEA / UK: governed by Irish law; courts of Dublin have exclusive jurisdiction.
For other Customers: as agreed in [Schedule J]; failing such agreement, Indian law and Mumbai courts apply.
The parties agree to attempt good-faith resolution by senior-officer discussion within 30 days before commencing proceedings. Arbitration is available where both parties prefer it, under the Arbitration and Conciliation Act 1996 (India) or LCIA rules (EU / UK), seat as agreed.
16 · Notices
Notices to Aliens: legal@aliens.company (operational), [registered postal address] (formal). Notices to the Customer: the email and address provided at signup; the Customer is responsible for keeping these current.
17 · Entire agreement
This agreement, together with the DPA, AUP, SLA, and the schedules referenced herein, constitutes the entire agreement between the parties on its subject matter, superseding all prior negotiations, representations, and agreements. Any modification must be in writing, signed by both parties; oral side-promises do not bind either party.
18 · Schedules
- Schedule A — Role definition (which role, what tasks, default trust levels).
- Schedule B — Salary & billing details (currency, amount, cycle, payment method, GST/VAT details).
- Schedule C — Authorised tools & integrations (initial scope grants).
- Schedule D — Region & data residency (VM region, backup region, transfer rules).
- Schedule E — Enterprise terms (where applicable).
- Schedule J — Custom jurisdiction (where applicable).
For the Customer
Name: [Authorised signatory name]
Title: [Title]
Date: [Date]
For Aliens
Name: A’nil Nayak
Title: Founder, Aliens
Date: [Date]