Production Terms of Service
Version 3.0.0
Effective: November 11, 2026

Terms of Service

These Terms of Service (“Terms”) form a legally binding agreement governing access to and use of AMARACUS cryptographic infrastructure, post-quantum APIs, developer consoles, and software development kits (SDKs).

Version 3.0.0 applies to accounts created on or after November 11, 2026. For accounts created earlier, it takes effect on December 11, 2026, after 30 days' notice (Section 11.3); until then the previous version applies.

1. Contracting Parties, Acceptance & Authority

These Terms are entered into by and between you (“Customer”, “User”, or “you”) and Amaracus Technologies (corporate registration pending), operating from Bengaluru, Karnataka 560103, India (“AMARACUS”, “we”, “us”, or “our”). We will publish our registered office address here once registration is complete; until then, notices go to the email addresses in Section 14.

1.1 Binding Acceptance: By creating an account, checking the acceptance box during registration, calling our APIs with generated API keys, or executing an Order Form, you confirm that you have read, understood, and agree to be bound by these Terms and all incorporated policies (including our Privacy Policy, Acceptable Use Policy, and Cookie Policy).

1.2 Organizational Representation: If you accept these Terms on behalf of an entity, company, or organization, you represent and warrant that you possess full legal authority to bind that organization to these Terms. If you lack such authority, you must not access the Services.

1.3 Age & User Eligibility (13+ Requirement): AMARACUS welcomes students, researchers, software engineers, and commercial organizations. You must be at least thirteen (13) years of age to establish an account or access the platform. If you are between 13 and 17 years of age, you represent and warrant that your parent or legal guardian has reviewed and agreed to these Terms on your behalf, and consents to your use of the Services. Paid enterprise subscriptions, corporate billing agreements, and team administration require legal age of majority (18+ or local age of majority). Children under the age of 13 are strictly prohibited from creating accounts or submitting personal data. If you suspect an unauthorized account belonging to a child under 13 has been established, review our expedited containment and parental deletion procedures in Section 11 of our Privacy Policy.

1.4 Definitions: “Services” means the AMARACUS website, developer console, REST APIs, SDKs, CLI and related documentation. “Customer Data” means data you or your users submit to the Services, including payloads, certificates, CSRs and uploads. “Key Material” means cryptographic keys created in or registered with the Services. “Organization” means the workspace an account belongs to, to which plans, keys and API credentials are attached. “Preview Features” means features labelled “preview” in the console or API. “Plan” means the subscription tier described in Section 6.

2. Platform Architecture & Permitted Uses

AMARACUS provides an enterprise-grade Universal Cryptographic Operating System designed to secure software applications against quantum and classical threats. Our platform capabilities include:

  • Post-Quantum Cryptography (PQC): FIPS 203 (ML-KEM-768 key encapsulation) and FIPS 204 (ML-DSA digital signatures).
  • Advanced Cryptographic Schemes (preview): Fully Homomorphic Encryption (Microsoft SEAL BFV, with server-held keys) and Schnorr/Pedersen Zero-Knowledge Proofs. Preview features are provided for evaluation and are not intended for production use.
  • Automated PKI & Certificate Lifecycle: Certificate Signing Request (CSR) generation, X.509 validation, and CBOM manifest generation.
  • Key Custody: Managed keys whose material is stored only in encrypted form, wrapped by a platform master key (not held in a hardware security module); on Business and Pay-As-You-Go plans, optional keys held in AMARACUS's Azure Key Vault or Managed HSM where available; and Bring-Your-Own-Key (BYOK) use of keys in your own Azure Key Vault or Managed HSM, accessed only with your own credentials.
  • Developer Infrastructure: Canonical REST APIs (/api/v1), official SDKs (@amaracus/sdk), and webhook event streaming.

Permitted Use: You are granted a non-exclusive, non-transferable, revocable license to access and integrate AMARACUS APIs and SDKs solely for lawful software engineering, internal encryption, data security, and testing purposes in compliance with your subscribed tier entitlements.

3. Shared Responsibility Model & Security Custody

Cryptographic security operates under a strict Shared Responsibility Model between AMARACUS and the Customer:

AMARACUS Responsibilities
  • • Correct implementation of the published algorithms we offer.
  • • Isolation of each Organization's keys, credentials and data from other Organizations.
  • • Storing Key Material only in encrypted (wrapped) form, never in plain text.
  • • An audit log of security-relevant account events, kept for at least 180 days.
Customer Responsibilities
  • • Safeguarding API secret keys and never committing secrets to public code repositories.
  • • Setting a spending limit appropriate to your budget.
  • • Enforcing key rotation schedules and revoking compromised credentials immediately.
  • • Ensuring legal authority and non-infringement of uploaded certificates and payloads.
  • • Keeping accurate account details and telling us promptly at [email protected] if you suspect unauthorized access.
3.1 Backups and Irrecoverable Keys: AMARACUS does not hold plaintext copies of your data or keys outside the Services. Data encrypted under a key cannot be decrypted by anyone, including AMARACUS, once that key is destroyed, its BYOK vault key is deleted or access to it is revoked, or your account is erased. You are responsible for keeping any data you will need and for deciding before destroying a key or deleting your account. Ciphertext you store elsewhere remains your responsibility.

4. Prohibited Activities & Immediate Enforcement

You must not under any circumstances utilize AMARACUS services for:

• Malicious Software: Encrypting, signing, obfuscating, or distributing ransomware, trojans, rootkits, or keyloggers.

• Unauthorized PKI: Generating fraudulent SSL/TLS certificates or impersonating domains, organizations, or individuals.

• System Abuse: Conducting denial-of-service (DoS/DDoS) attacks, automated brute-force probing, or exploiting API race conditions.

• Circumvention: Bypassing spending limits, plan entitlements or rate limits, accessing another Organization's data, or probing the Services for vulnerabilities outside our vulnerability disclosure process.

• Crypto-Mining: Using FHE or ZK proof engines for cryptocurrency mining or resale of compute.

• Unlawful Use: Any use that violates applicable law, including export control and sanctions law (Section 12).

Enforcement & Law Enforcement Referral: A violation of this Section may result in immediate revocation of API keys and suspension or termination of the account, without prior notice where the violation threatens the Services or others, and in reporting to the relevant authorities where the law requires it (including the Indian Computer Emergency Response Team, CERT-In, under the Information Technology Act, 2000).

5. Intellectual Property & Customer Content Ownership

5.1 Complete Customer Ownership: You retain exclusive ownership of all right, title, and interest (including all patent, copyright, and trade secret rights) in and to your customer data, private cryptographic keys, encrypted payloads, CSR inputs, and software applications. AMARACUS acquires no ownership rights in your cryptographic assets or source code.

5.2 Absolute Zero-AI Training Warranty:

AMARACUS warrants that your cryptographic keys, payloads, CSR submissions, and data transmissions are NEVER used to train, test, or evaluate artificial intelligence or machine learning models.

5.3 AMARACUS Intellectual Property: All software, user interfaces, trademarks, documentation, and designs comprising the AMARACUS platform are the intellectual property of AMARACUS and its licensors. The SDKs and CLI are licensed separately under the Apache License 2.0, as stated in their packages; that licence governs your use of their source code.

5.4 License to Operate the Services: You grant AMARACUS a limited licence to host, process and transmit Customer Data only as needed to provide the Services to you, to secure them, and to comply with law. This licence ends when the data is deleted.

5.5 Feedback: If you send us suggestions or feedback about the Services, we may use them without restriction or obligation to you. Feedback does not include Customer Data.

5.6 Infringement Notices: If you believe content made available through the Services (for example a hackathon submission or uploaded file) infringes your copyright or other rights, write to [email protected] with: the work you claim is infringed; where the content is; your contact details; a statement that you believe in good faith the use is not authorized; and a statement, under penalty of perjury where applicable, that your notice is accurate and that you are the owner or authorized to act for the owner. We will review the notice and may remove or disable the content and notify the person who provided it, who may respond with a counter-notice.

6. Subscription Plans & Billing

Plans are sold through two payment routes. Polar.sh, our Merchant of Record, sells every paid plan in US dollars. Razorpay (Razorpay Software Private Limited, India) processes monthly payments in Indian rupees (INR) for the Starter, Pro and Business plans, by UPI Autopay or card. Pay-As-You-Go is sold only through Polar.sh. The plans, allowances and entitlements below are the same whichever route you pay through:

TierMonthly BaseIncluded OpsOver-Limit Unit RateEntitlements
Starter$2.0015,000 ops/mo$0.14 / 1,000 ops, only with authorized overage (6.2)2 Projects, 20 Keys, 1 Member, PQC (ML-KEM, ML-DSA); no FHE or ZK
Pro$20.00150,000 ops/mo$0.14 / 1,000 ops, only with authorized overage (6.2)10 Projects, 100 Keys, PQC, preview FHE and ZK
Business$99.001,000,000 ops/mo$0.10 / 1,000 ops, only with authorized overage (6.2)50 Projects, 500 Keys, PQC, preview FHE and ZK, preview BYOK, keys in AMARACUS's Azure vault where available
Pay-As-You-Go$0.00Continuous metering$0.150 / 1,000 opsMetered usage up to your spending limit (default $250 per month)

No Free Plan: AMARACUS has no free plan or free tier. Creating an account costs nothing, but the API, managed keys and API keys are available only while your organization has an active paid plan from the table above. Without one, your account, keys and data are kept, and API requests are refused (HTTP 402, Payment Required) until you buy a plan.

6.1 Plan Changes Only With Your Action: Your plan changes only when you buy a plan through checkout or cancel it. AMARACUS never moves you to a higher-priced plan or charges you for one without your action.

6.2 When Included Operations Run Out: On the Starter, Pro and Business plans, operations stop when the month's included operations are used up, unless an administrator has authorized overage and set an overage spending limit in the Billing Console. With authorized overage, operations continue at the over-limit rate above until that limit is reached, and then stop.

6.3 Pay-As-You-Go Spending Limit: Pay-As-You-Go usage is metered continuously and capped by your spending limit (default $250.00 per month, adjustable in the Billing Console). When metered charges reach the limit, metered operations stop until the next period or until you raise it.

6.4 Taxes & Merchant of Record: The fees in the table above are in United States Dollars (USD).

(a) Purchases through Polar.sh: USD fees exclude local indirect taxes. Polar.sh serves as our Merchant of Record and calculates, itemizes, and collects applicable indirect taxes (such as Value Added Tax [VAT] in the European Union, Goods and Services Tax [GST] in India, and State/Local Sales Taxes in the United States) at checkout based on your billing address and tax jurisdiction. Eligible business entities may supply valid VAT/GST identification numbers during checkout to apply reverse-charge treatment where applicable law allows.

(b) Purchases through Razorpay (INR): Razorpay processes the payment but is not a Merchant of Record; AMARACUS is the seller. The INR amount shown on the Billing Console before you pay is the full amount charged each month, and nothing is added to it at checkout. Reverse-charge treatment is not offered on this route.

6.5 Zero Payment Surcharges: AMARACUS does not assess mandatory administrative fees, checkout handling fees, or credit card surcharges on customer invoices. All merchant payment-processing fees are 100% absorbed by AMARACUS.

6.6 Pre-Purchase Disclosures & Automatic Renewal: Before you complete a purchase, the checkout shows the base charge, billing interval, included operations, and applicable taxes. Paid plans renew automatically each monthly billing period unless cancelled before renewal in the Billing Console or, for Polar.sh purchases, the Polar.sh Customer Portal. Razorpay subscriptions renew through the UPI Autopay or card mandate you approve at checkout and are cancelled in the Billing Console.

7. Cancellation, Non-Refundable Compute & Mandatory Consumer Rights

7.1 Self-Service Cancellation (Click-to-Cancel): You may cancel your subscription at any time directly through the Billing Console in your dashboard or via the integrated Polar.sh Customer Portal (Razorpay subscriptions are cancelled in the Billing Console only). A cancellation takes effect at the end of the active billing cycle, so you keep full access to what you have paid for until that date. After it, your organization has no active plan: its account, keys and data are kept, but API requests are refused until you buy a plan again. A Polar.sh subscription can be resumed before that date; Razorpay does not allow a cancelled subscription to restart, so to continue on Razorpay you subscribe again. Cancelling your subscription never deletes your organization, cryptographic keys, or project assets.

7.2 Consumed Server Compute Policy: Because cryptographic operations (such as ML-KEM encapsulation, SEAL BFV polynomial multiplication, and key wrapping) consume irreversible cloud compute and dedicated hardware cycles, fees paid for elapsed subscription periods and utilized cryptographic operations are generally non-refundable.

7.3 Mandatory Statutory Consumer Rights:

Nothing in this Section or these Terms limits or waives any statutory cancellation or refund rights that cannot be excluded under applicable consumer law, including the 14-day statutory right of withdrawal for European Union consumers under Directive 2011/83/EU, or statutory protections under the Indian Consumer Protection Act, 2019. Where an immediate performance waiver was provided at checkout, consumer rights apply strictly as governed by statutory provisions.

7.4 Dispute Resolution & Refund Request Procedure:

To request a refund, dispute an unexpected charge, or report billing discrepancies, contact our billing desk directly at [email protected] with your Organization ID and invoice number. Refund inquiries receive an initial acknowledgment within 24-48 business hours and formal determination within 5 business days.

8. Service Availability, Upstream Outages & Inability to Encrypt

AMARACUS works to keep the Services available but, unless a separate written service level agreement is signed with you, makes no uptime commitment and offers no service credits. Customer explicitly acknowledges and agrees that the delivery of real-time online cryptographic services relies upon complex public networks, international internet backbones, and upstream hosting providers:

8.1 Upstream Infrastructure Outages (Hosting, Database, Edge & Cloud Providers)

The AMARACUS platform depends on external providers, including Render (API hosting), Supabase (PostgreSQL database), Cloudflare (website hosting, DNS, edge routing and DDoS protection), the cloud infrastructure those providers run on, and Microsoft Azure (only for Azure-held and BYOK keys).

Customer recognizes that there can and will be times when these providers, or regional internet exchange backbones experience service disruptions, fiber cuts, BGP routing errors, data-center power outages, or catastrophic downtime completely beyond the reasonable control of AMARACUS. During any such upstream provider outages, the AMARACUS platform, dashboard, and cryptographic API endpoints may be inaccessible, unresponsive, degraded, or temporarily offline.

8.2 Inability to Perform Cryptographic Operations During Downtime

IMPORTANT NOTICE REGARDING ENCRYPTION & DATA PROCESSING: When upstream infrastructure providers or AMARACUS itself experience an outage, service degradation, emergency security patching, network partition, or unscheduled downtime, live cryptographic operations cannot be executed, processed, or performed. This includes, without limitation:

  • Real-time AEAD symmetric envelope encryption and decryption requests (/v1/encrypt, /v1/decrypt);
  • Post-quantum lattice key encapsulation and decapsulation operations (ML-KEM-768 / FIPS 203);
  • Digital signature generation and verification (Ed25519, ML-DSA-65 / FIPS 204);
  • Hashing, HMAC, data key derivation, and Zero-Knowledge Proof generation;
  • Real-time X.509 PKI certificate generation, rotation, CSR signing, and automated mTLS validation.

Customer applications attempting to call AMARACUS APIs during such downtime windows will receive network connection errors, HTTP 502/503/504 status codes, or connection timeouts.

8.3 Customer Architectural Responsibility & Failover Design: Because cryptographic microservices operate over distributed internet networks, Customer is solely responsible for designing adequate fault-tolerance and failover mechanisms within their own consuming applications. Recommended practices include implementing exponential backoff retries, dead-letter message queuing, client-side caching of ephemeral data keys (subject to customer regulatory requirements), circuit breakers, and graceful application degradation. Customer agrees that Customer software must not assume 100% uninterrupted real-time connectivity to AMARACUS or any third-party cloud provider.

8.4 Limitation of Liability for Downtime & Failed Encryption: To the maximum extent permitted by applicable law, and always subject to Section 9.3 and the Mandatory Statutory Invalidation Clause in Section 9, AMARACUS, its affiliates, directors, officers, employees, and licensors are not liable for indirect, incidental, consequential, special, or exemplary damages, including lost profits, delayed financial transactions, unprocessed business data, unauthorized exposure of unencrypted data resulting from customer systems “failing open”, SLA penalties imposed on Customer by third parties, or regulatory fines arising out of or related to:

  • Any outage, downtime, network partition, or packet loss caused by Render, Supabase, Cloudflare, Microsoft Azure, or any other upstream provider;
  • Any outage, downtime, or service degradation of the AMARACUS platform itself;
  • Any scheduled maintenance or emergency security remediation conducted by AMARACUS;
  • The temporary inability of Customer applications to encrypt, decrypt, hash, sign, or verify payloads during any service interruption.

Any other liability AMARACUS has for these events is limited by Section 9.3.

8.5 Status & Incident Transparency: Real-time platform health probes, incident retrospectives, scheduled maintenance windows, and sub-processor status alerts are publicly accessible 24/7 at /status.

9. Warranties & Limitation of Liability

9.1 Limited Technical Warranty: AMARACUS warrants that its cryptographic algorithms conform to published NIST and industry specifications under ordinary operating parameters. Except as expressly stated, the Services are provided “AS IS” and “AS AVAILABLE”.

9.2 Exclusion of Consequential Damages: To the maximum extent permitted by applicable law, neither AMARACUS nor its directors, employees, or sub-processors shall be liable for indirect, incidental, special, punitive, or consequential damages, including lost profits, loss of data, loss of goodwill, or business interruption.

9.3 Total Liability Cap: The aggregate liability of AMARACUS arising out of or related to these Terms shall not exceed the total fees paid by you to AMARACUS in the twelve (12) months preceding the event giving rise to liability, or one hundred US dollars ($100.00 USD), whichever is greater.

Mandatory Statutory Invalidation Clause: Nothing in these Terms shall limit or exclude liability for death or personal injury caused by negligence, fraud or fraudulent misrepresentation, intentional misconduct, or any other liability that cannot be lawfully excluded under the laws of the applicable jurisdiction.

9.4 Preview Features: Preview Features are provided for evaluation only, without any warranty or availability commitment, may change or be withdrawn without notice, and must not be used to protect production data.

9.5 Indemnification: To the extent permitted by law, you will defend and indemnify AMARACUS against third-party claims, and resulting losses, fines and reasonable legal costs, arising from (a) Customer Data you submit, (b) your breach of Section 4, the Acceptable Use Policy or Section 12, or (c) your violation of law. AMARACUS will tell you promptly about the claim, let you control its defence, and give reasonable help at your expense. This Section does not apply to consumers where local law does not allow it.

9.6 Security Incidents: No system connected to the internet can be made completely secure, and AMARACUS does not promise that the Services will be free of vulnerabilities, attacks or unauthorized access. AMARACUS keeps reasonable security safeguards suited to the Services, as described in the Privacy Policy, and will notify you and the competent authorities of a personal data breach as the law and the Privacy Policy require. To the maximum extent permitted by applicable law, AMARACUS is not liable for loss or damage caused by a cyberattack, intrusion, malware or other unauthorized access by a third party that occurs despite those safeguards, and any liability AMARACUS does have for a security incident is subject to Sections 9.2 and 9.3. AMARACUS is not responsible for incidents caused by the compromise of your credentials, API keys, devices, systems or BYOK vaults, or by your failure to meet your responsibilities under Section 3. Nothing in this Section limits liability that applicable law does not allow to be limited.

10. Governing Law, Arbitration & Dispute Resolution

10.1 Governing Law: These Terms and any dispute arising out of or related to them are governed by the laws of the Republic of India, without regard to conflict of law principles.

10.2 Informal Resolution: Before starting arbitration, the parties will try in good faith to resolve any dispute through written negotiation for at least thirty (30) days from written notice sent to [email protected] (or, for notices to you, to your account email).

10.3 Arbitration: A dispute not resolved under 10.2 will be finally resolved by arbitration under the Arbitration and Conciliation Act, 1996, by a sole arbitrator appointed by agreement of the parties (or otherwise under that Act). The seat and venue of arbitration is Bengaluru, Karnataka, India, and the language is English.

10.4 Courts: Subject to 10.3, the courts at Bengaluru, Karnataka have exclusive jurisdiction, including for interim relief. Either party may seek urgent injunctive relief to protect its intellectual property or confidential information in any competent court.

10.5 Consumers: If you use the Services as a consumer, nothing in this Section removes protections you have under the mandatory law of the country where you live, including the right to bring proceedings before the courts or consumer commissions there (for example under the Indian Consumer Protection Act, 2019, or, for consumers in the European Union, the courts of your Member State) or to use an applicable online dispute resolution scheme.

11. Account Termination & Auditable Acceptance Records

11.1 Voluntary Account Erasure: Customers may terminate their account at any time using the self-service permanent erasure tool in the Account Settings console (/dashboard/settings), which irreversibly purges account records and destroys tenant cryptographic keys.

11.2 Acceptance Records: As evidence of electronic acceptance (including under the Indian Information Technology Act, 2000 and the US E-SIGN Act), AMARACUS records each acceptance of these Terms in its audit log with:

• Action: auth.universal_terms_agreed and privacy.consent_recorded at sign-up, legal.terms_accepted for later versions
• Terms Version: 3.0.0
• Timestamp: ISO-8601 UTC
• Originating IP Address
• Client User-Agent Header
• Legal Basis: Contractual Necessity

11.3 Modifications to Terms: AMARACUS may modify these Terms to reflect changes in law, security standards, or product capabilities. In the event of material amendments, we will provide at least thirty (30) days advance notice via email or an in-console notification banner. The version and effective date at the top of this page identify the current Terms. If you do not agree to a change, you may cancel before it takes effect; continuing to use the Services after that date means you accept it.

11.4 Suspension and Termination by AMARACUS: We may suspend or terminate access (a) immediately for a breach of Section 4, the Acceptable Use Policy or Section 12, or to protect the Services or other customers from harm; (b) for unpaid amounts after notice and at least seven (7) days to pay; (c) where required by law or a competent authority; or (d) for any other material breach not cured within fourteen (14) days of notice. Where we end the Services for reasons other than your breach, we will give at least thirty (30) days' notice so you can export your data and decrypt anything you need.

11.5 Effect of Termination: When your account ends, your right to use the Services ends and API keys stop working. Before deleting your account, export your data from Account Settings: after erasure, data and Key Material cannot be restored (see 3.1). Fees already due remain payable.

11.6 Survival: Sections 3.1, 5, 7, 9, 10, 12 and 13, and any other terms that by their nature should continue, survive the end of these Terms.

12. Export Control & Sanctions

12.1 Encryption Is Export-Controlled: The Services, SDKs and CLI provide encryption and may be subject to export control laws, including India's Foreign Trade (Development and Regulation) Act, 1992 and SCOMET list, the U.S. Export Administration Regulations, and the laws of other countries where you use them.

12.2 Your Commitments: You will comply with those laws. You represent that you are not located in, or ordinarily resident in, a country or region subject to comprehensive sanctions, and are not named on, or owned or controlled by anyone named on, a sanctions or restricted-party list maintained by India, the United Nations, the United States, the European Union or the United Kingdom. You will not use the Services for weapons of mass destruction, military end uses where prohibited, or to provide the Services to such persons or places.

12.3 Our Rights: We may block access from sanctioned locations and suspend accounts where we reasonably believe this Section has been breached.

13. General Provisions

13.1 Entire Agreement: These Terms, together with the policies they incorporate and any order form or written agreement signed by both parties, are the entire agreement between you and AMARACUS about the Services. A signed written agreement prevails over these Terms where they conflict.

13.2 Severability: If a court or arbitrator holds a provision unenforceable, it will be changed and interpreted to achieve its purpose as far as the law allows, and the rest of these Terms continues in effect.

13.3 Waiver: Not enforcing a right or provision is not a waiver of it. A waiver is effective only in writing.

13.4 Assignment: You may not assign these Terms without our written consent. We may assign them to an affiliate or to a successor in a merger, acquisition or sale of assets, with notice to you.

13.5 Force Majeure: (a) Neither party is liable for a delay or failure to perform caused by an event beyond its reasonable control that it could not have avoided by taking reasonable precautions. These events include natural disasters, fire, flood, epidemics, war, terrorism, civil unrest, widespread strikes, acts or orders of a government or regulator, sanctions, failures of power, internet or telecommunications networks, the outages described in Section 8.1, and cyberattacks, denial-of-service attacks and other malicious acts of third parties that occur despite reasonable safeguards.

(b) The affected party will tell the other as soon as reasonably practicable (AMARACUS may do so on its status page), will make reasonable efforts to limit the effects, and will resume performance as soon as it can. Its obligations are suspended only to the extent and for as long as the event prevents performance.

(c) This Section does not excuse payment obligations, or a failure that reasonable safeguards would have prevented.

(d) If the event stops the Services for more than thirty (30) consecutive days, either party may end the affected subscription by written notice, and no further subscription fees will fall due.

(e) Nothing in this Section limits Section 7.3 or any right that the law does not allow to be limited.

13.6 Third-Party Services and Links: The Services link to or work with third-party services (for example Polar.sh or Razorpay checkout, your own Azure vault, or integrations you connect). Those services are governed by their own terms; AMARACUS is not responsible for their content or practices.

13.7 Notices: We send notices to your account email or show them in the console. You send legal notices to [email protected]. Email notices are effective when sent, unless the sender learns they were not delivered.

13.8 Relationship and Third Parties: The parties are independent contractors. These Terms create no rights for anyone other than you and AMARACUS.

13.9 Language: These Terms are written in English. If they are translated, the English version prevails in case of conflict, except where mandatory law requires otherwise.

13.10 Matters Not Covered: Any matter, circumstance, situation, dispute, or eventuality not expressly addressed or covered under these Terms, the Privacy Policy, or any other applicable policy shall be subject to AMARACUS's determination and interpretation, exercised at its sole discretion, to the extent permitted by applicable law. AMARACUS reserves the right to establish additional rules, procedures, restrictions, and conditions to address such matters. Such determinations shall be binding on users, subject to applicable law.

14. Official Legal Inquiries & Grievance Contacts

For formal legal notices, contract inquiries, or statutory grievances, reach our designated teams below or review our official Contact & Company Information Register:

Legal & Regulatory Inquiries
Legal Notices: [email protected]
Security Incident Desk: [email protected]
Company: Amaracus Technologies (registration pending), Bengaluru, Karnataka 560103, India
Registered Office: To be published on registration
Statutory Resident Grievance Officer
Officer: To be named on appointment
Statutory Mandate: IT Act 2000 & DPDPA 2023 Compliance
Turnaround: 48h acknowledgment; 30d resolution