Vasadeploy is operated by VASASU PRIVATE LIMITED (the “Company,” “we,” “us,” or “our”). These Terms of Service govern your access to the Vasadeploy website, applications, and related build and deployment services (the “Service”). By using the Service, you agree to these terms. If you use the Service for an organization, you confirm that you have authority to accept these terms on its behalf.
1. Eligibility and accounts
You must be at least 18 years old and legally capable of entering into a binding agreement. Provide accurate account and billing information and keep it up to date. You are responsible for protecting your sign-in credentials and for activities you authorize through your account. Notify us promptly if you suspect unauthorized access.
Organization owners are responsible for assigning appropriate roles and managing membership. An authorized member may initiate builds or other actions that use the organization’s credits or connected accounts. Removing a member does not reverse actions already completed or charges already incurred.
2. The Service
Vasadeploy helps you connect repositories, configure and execute build workflows, follow progress, download generated files, and use supported publishing integrations. Available operating systems, build resources, integrations, limits, and features are described in the Service and may vary by account or workflow.
You are responsible for your source code, dependencies, workflow instructions, credentials, and release settings. A successful build does not certify that your software is secure, accurate, lawful, or suitable for distribution. Review and test generated software before installing, publishing, or distributing it.
3. Your content and permissions
You retain ownership of your source code, project materials, and generated files to the extent you hold those rights. You grant us a limited, non-exclusive permission to access, copy, process, execute, store, transmit, and display those materials as needed to provide the Service, carry out your instructions, maintain security, and respond to support requests. This permission does not transfer ownership to us.
You must have the rights and permissions needed to submit materials, connect accounts, use dependencies, and distribute the resulting software. You remain responsible for third-party licenses, intellectual property rights, privacy obligations, and any consents required for information you submit.
4. Acceptable use
You must not use the Service to:
- Violate applicable law, infringe intellectual property or privacy rights, or distribute unlawful or deceptive software.
- Create or distribute malware, steal credentials, or access accounts, repositories, systems, or information without authorization.
- Disrupt the Service, evade access controls or usage limits, exploit vulnerabilities, or interfere with other users’ builds or data.
- Run cryptocurrency mining, unrelated compute workloads, or other activities that misuse resources provided for build and deployment workflows.
- Abuse free allowances, create accounts to evade restrictions, or submit fraudulent payment or account information.
We may investigate suspected misuse and restrict affected access where reasonably necessary to protect the Service, other users, or legal rights.
5. Connected accounts and publishing
When you connect a repository, provide credentials, or enable publishing, you authorize the actions required by the permissions and settings you select. Review the destination, application identity, release mode, and workflow before starting a build or publishing operation. Publishing may create submissions or release software through your connected account.
Third-party services operate under their own terms, policies, fees, and availability. You are responsible for maintaining the accounts and permissions they require. We do not guarantee store approval, certification, publication, or continued availability of an integration. Revoking a connection does not necessarily cancel an action already submitted to another service.
6. Credits, prices, and payments
Paid usage is funded by prepaid credits associated with the selected personal or organization account. Purchase prices, currency, taxes, and applicable limits are shown before payment. Review the selected account and billing details before completing a purchase. Credits are available after payment is confirmed; a pending payment or bank transfer may require verification before credits are added.
Build charges depend on the applicable resources, rates, and usage recorded by the Service. Starting a paid build may reserve credits, with final usage settled after execution. Resources can be consumed even when a build fails, is cancelled, or produces no usable output; a failed build does not automatically entitle you to a refund.
Purchased credits do not expire. Credits are for use within the Service and are not a bank deposit or an interest-bearing balance. Any automatic top-up feature requires your authorization through the applicable payment process. Revoking a payment authorization does not reverse completed payments.
Purchased credits, including unused credits, are non-refundable except for billing errors or where a refund is required by applicable law, as described in our Refund Policy. For an incorrect charge, missing credits, or a refund request, contact [email protected] with your account email and transaction reference. Nothing in these terms removes a refund or remedy required by law.
We may change prices for future purchases or usage with notice through the Service before the new rates apply. Changes do not retrospectively alter completed purchases or charges.
7. Free builds and usage limits
Free builds, where available, are subject to eligibility, daily and monthly allowances, resource limits, and execution deadlines shown in the Service. Unused free allowances do not carry forward. A free build may stop when its time limit is reached, including during setup or file upload.
We may adjust free offerings and operational limits with notice where appropriate. Free access does not create an entitlement to unlimited capacity or continued availability of a particular allowance.
8. Files, retention, and backups
Generated files are stored for the retention period and limits applicable to your account and may be deleted after expiry. Certain files may remain available longer while a publishing operation is unresolved. You are responsible for downloading and maintaining your own copies of source code, generated files, signing material, and other important project data. The Service is not a permanent archive.
9. Privacy and confidentiality
Our Privacy Policy explains how we handle personal information. Access to organization information depends on member permissions. You are responsible for deciding what to share with members and connected services, and for keeping sensitive information out of build output. We use reasonable safeguards to protect information entrusted to us, but cannot guarantee that every workflow or third-party dependency will preserve the confidentiality of information you give it.
10. Availability and changes
We aim to provide a reliable Service, but builds may be delayed, interrupted, or unsuccessful because of maintenance, capacity, software errors, network issues, or connected services. We do not promise uninterrupted availability, a particular completion time, or a successful result unless expressly agreed in writing.
We may modify or discontinue features. For a material change that significantly affects active use, we will provide reasonable notice where practicable, except where urgent security, legal, or operational circumstances require immediate action.
11. Suspension, termination, and account closure
We may suspend or terminate access for a material breach of these terms, fraudulent activity, a legal requirement, or a substantial risk to the Service or other users. Where practicable, we will explain the reason and allow an opportunity to resolve the issue. Immediate restrictions may be necessary for urgent risks.
You may stop using the Service or request account closure by contacting [email protected]. Before closure, download needed files, review pending builds and publishing operations, and revoke any recurring payment authorization. Account closure does not automatically undo completed publishing actions or charges. We will address remaining paid credits and any refund entitlement under the applicable purchase conditions and law.
An organization owner should transfer ownership or arrange organization closure before deleting their personal account. Information may be retained as explained in our Privacy Policy. Provisions concerning accrued payments, ownership, liability, and dispute resolution continue to apply where relevant after termination.
12. Disclaimers and liability
To the extent permitted by applicable law, the Service is provided on an “as is” and “as available” basis, without warranties of uninterrupted operation, fitness for a particular purpose, or error-free results. You remain responsible for assessing and testing your software and for maintaining appropriate backups.
To the extent permitted by applicable law, we are not liable for indirect or consequential losses, such as lost profits or business opportunities arising from use of the Service. Nothing in these terms excludes liability for fraud, wilful misconduct, or any liability or consumer right that cannot lawfully be excluded or limited.
13. Governing law and disputes
These terms are governed by the laws of India, subject to any mandatory protections that apply where you live. Please first contact us with details of a dispute so we can attempt to resolve it. This does not restrict your right to seek relief from a competent court, consumer forum, or other authority under applicable law.
14. Updates and contact
We may revise these terms and will publish the updated version with a revised effective date. We will give notice of material changes through the Service or your account email where appropriate. Changes apply prospectively; if you do not agree to the updated terms, stop using the Service and contact us about closing your account.
For questions about these terms or Vasadeploy support, email [email protected]. For company correspondence, contact VASASU PRIVATE LIMITED, the operator of Vasadeploy, at [email protected].