Terms & Conditions

1. Who these terms apply to

These Terms & Conditions apply to your use of anna360dev.site and to your initial communications with ANNA360 -Dev. They are intended to help visitors and prospective clients understand how we handle an inquiry before a project is agreed.

A website visit, form submission, advertisement click, phone call, email, WhatsApp message, meeting, or preliminary discussion does not by itself create a contract for services, an appointment, a confirmed proposal, or a promised result. A project engagement begins only when both parties agree in writing to the applicable proposal, statement of work, service agreement, or other contract document (together, the Project Agreement).

If a Project Agreement contains terms that differ from this page, the Project Agreement takes priority for that project.

2. About ANNA360 -Dev and our services

ANNA360 -Dev provides the following service categories:

• Custom app development
• Web development
• Digital marketing

We are located at:

The exact work offered for a project depends on the information provided during the inquiry and the written scope later agreed. A general service description on this website is not a promise that every feature, platform, integration, marketing activity, deliverable, or support arrangement is included in every engagement.

3. Service inquiries: what to send and what happens next

A useful inquiry helps us understand whether a proposal discussion is appropriate and what questions need clarification. To begin, please share as much of the following as is relevant:

What to include in an inquiry

• Your name, business or organisation name, and preferred contact details.
• The service you are considering: custom app development, web development, digital marketing, or a combination of these.
• A clear description of the business need, intended users or audience, and the outcome you want to work toward.
• Any existing website, app, brand materials, campaign materials, or references that help explain the starting point.
• Required functions, content, integrations, platforms, or marketing channels, if known.
• Important constraints, such as an intended launch date, internal review process, or required approvals.
• A budget range, if you are comfortable sharing one, so that a proposed scope can be discussed realistically.
• The person who can make or coordinate decisions, provide feedback, and arrange access to required materials.
• Any data, regulatory, confidentiality, or approval considerations that may affect the work.

Before you send sensitive information

Please do not send passwords, bank details, card details, or other sensitive credentials in an initial form, email, or WhatsApp message. Access requirements, if needed, should be discussed and handled through an agreed process after the project scope is confirmed.

After receiving an inquiry, ANNA360 -Dev may ask follow-up questions to understand the requirements. An inquiry does not guarantee that a proposal will be issued or that a project will be accepted. We may need to clarify fit, available information, access requirements, or other practical considerations before discussing next steps.

4. Proposals, scope, and project authorisation

Where ANNA360 -Dev decides to prepare a proposal, it is intended to give the prospective client a transparent basis for deciding whether to proceed. Depending on the project, a written proposal or Project Agreement may identify:

• The agreed service category and project objectives.
• The specific deliverables and any stated acceptance or handover criteria.
• The work included in scope and any exclusions, assumptions, dependencies, or client-provided items.
• The project approach, communication points, review or approval stages, and any planned milestones.
• The applicable fees, payment schedule, taxes, approved expenses, and any third-party costs that are included or excluded.
• Timing considerations or target dates, where they can reasonably be discussed, together with the dependencies that may affect them.
• The ownership, licence, confidentiality, support, change-control, and termination terms that apply to the particular work.

Only the terms documented in the mutually accepted Project Agreement are part of the engagement. Statements made in an advertisement, on this website, in an early discussion, or in an informal message should not be treated as a final scope, quote, timeline, or commitment unless they are incorporated into the Project Agreement.

Work should not be treated as authorised until the required written approval and any agreed pre-commencement requirements are complete.

5. How work and deliverables are managed

Project work is planned around the scope agreed for that engagement. Depending on the service, the work may involve discovery and requirements clarification, planning, design or content review, development or campaign activity, testing or quality checks, feedback, agreed revisions, and handover. The actual sequence, deliverables, and client involvement are defined in the Project Agreement.

ANNA360 -Dev will use reasonable professional effort to perform the agreed services. Project timing and progress can depend on matters outside our control, including the completeness of requirements, the speed of client feedback and approvals, availability of third-party platforms or services, content readiness, and changes requested after work begins.

A target date, estimate, or project plan is not a guarantee of a fixed completion date unless a Project Agreement expressly says otherwise. If a dependency or issue may materially affect the agreed plan, it should be discussed with the client so that the next practical step can be considered.

6. Changes to the agreed scope

Requests often evolve after a project begins. A scope change can include a new feature, a material alteration to an approved requirement, additional pages or content, a new integration, an added marketing activity, a changed platform requirement, or work that falls outside the written scope.

When a change is requested, ANNA360 -Dev will review the request and, where appropriate, explain its likely effect on deliverables, dependencies, timing, fees, and/or other terms. The change should be documented and agreed in writing before the additional or changed work is treated as part of the project.

We are not required to begin changed work based only on an informal request. Keeping changes in writing helps both parties avoid misunderstandings about what will be delivered and how it will affect the project.

7. Fees, invoices, taxes, and third-party costs

Fees are proposal- and contract-based. ANNA360 -Dev does not publish a universal fixed price for custom app development, web development, or digital marketing because the scope, responsibilities, access requirements, and deliverables may differ from project to project.

Before a project begins, the Project Agreement should state the relevant commercial terms, including the agreed fees, currency, payment schedule, invoice timing, payment method, applicable taxes, approved expenses, and any consequences of late payment or non-payment.

Where a project involves advertising spend, platform fees, domain or hosting charges, software subscriptions, licences, payment-processing charges, stock assets, or other third-party products or services, their treatment should be stated clearly in the Project Agreement. They are not assumed to be included in ANNA360 -Dev's service fees unless the written scope says so.

If payments, approvals, information, or access required from the client are delayed, this may affect the ability to continue work according to the planned schedule. Any pause, resumption, payment remedy, cancellation amount, or refund arrangement must be handled in accordance with the Project Agreement and applicable law.

8. Client responsibilities

A collaborative project depends on timely and accurate client participation. The client is responsible for:

• Providing information that is accurate, complete, and sufficiently detailed for the agreed work.
• Nominating an authorised point of contact for decisions, feedback, approvals, and project communications.
• Responding to review requests within the timeframes stated in the Project Agreement, where applicable.
• Providing agreed content, brand assets, access, permissions, credentials, and other materials through an appropriate and secure method.
• Ensuring it has the necessary rights, permissions, and authority to provide any content, data, logo, image, copy, account access, or other material supplied to ANNA360 -Dev.
• Reviewing deliverables and providing clear, consolidated feedback where that is part of the agreed process.
• Making payments as set out in the Project Agreement.
• Remaining responsible for the accuracy, legality, and substantiation of its own business information, offers, claims, products, services, and instructions.

For digital marketing work, the client should not ask ANNA360 -Dev to publish or promote misleading, unlawful, unsubstantiated, infringing, or platform-prohibited content. External advertising, search, social, and app platforms apply their own policies and review processes, and the client remains responsible for its business, its offers, and the truthfulness of claims made about them.

9. Results, third-party platforms, and external factors

ANNA360 -Dev does not guarantee any particular search ranking, advertising approval, traffic level, lead volume, conversion rate, revenue, return on investment, app-store approval, download figure, or business outcome.

Custom development and digital marketing can be affected by factors that are outside ANNA360 -Dev's control, such as client approvals, market conditions, user behaviour, competitor activity, platform policies, algorithm changes, account status, third-party service availability, content quality, budgets, and technical constraints.

Where reporting, optimisation, or performance-related work is included in a Project Agreement, the agreed activities and reporting approach will be set out there. A business objective or performance target may guide the work, but it is not a promise of a specific result.

ANNA360 -Dev is an independent service provider. We do not represent ourselves as Google, Meta, Apple, or any other third-party platform, and use of a platform or reference to its services does not imply an affiliation, endorsement, partnership, or guarantee from that platform.

10. Intellectual property and project materials

Intellectual-property rights should be clearly addressed in the Project Agreement. Unless that agreement says otherwise:

• Each party keeps ownership of the materials, information, branding, content, code, tools, templates, methods, and other intellectual property it owned or created independently before the project.
• The client gives ANNA360 -Dev the limited right to use client-supplied materials only as reasonably necessary to perform the agreed services.
• Rights in custom project work, and the point at which those rights are assigned or licensed, will be stated in the Project Agreement and may be conditional on full payment of all amounts due for that work.
• Third-party software, open-source components, stock assets, fonts, plug-ins, platforms, and services may be governed by their own licences and terms. Those terms are not replaced by these Terms & Conditions.
• ANNA360 -Dev will not use a client project as a portfolio example or public case study without the client's prior permission.

The client should not assume it receives rights in any item that is not expressly identified in the Project Agreement. If ownership, source files, licences, access, or post-handover use is important to the project, it should be discussed before approval.

11. Confidentiality and information handling

Each party should treat the other party's non-public business, technical, commercial, financial, customer, project, and access information as confidential when it is identified as confidential or would reasonably be understood to be confidential.

Neither party should disclose or use that information for a purpose outside the proposed or agreed engagement, except where disclosure is required by law, authorised by the other party, or necessary for authorised professional advisers or service providers who are bound by appropriate confidentiality obligations.

Confidential information does not include information that is already publicly available through no breach of these terms, was lawfully known before disclosure, is independently developed without use of the other party's confidential information, or is lawfully obtained from another source without a confidentiality restriction.

If a project requires handling personal data, sensitive information, or customer data, the required roles, safeguards, access controls, retention arrangements, and any data-processing terms should be confirmed in the Project Agreement before access is provided.

12. Website information and third-party links

We aim to keep the information on anna360dev.site clear and current. However, website content is general information and may be updated as our services or materials change. It is not a final proposal, legal advice, technical specification, or commitment to provide a particular service.

The website may refer to or link to third-party websites, platforms, tools, or services for convenience. ANNA360 -Dev does not control those third parties and is not responsible for their content, availability, security, policies, or terms. A client should review the relevant third-party terms before choosing to use those services.

13. Limitation of liability

To the extent permitted by applicable law and subject to the specific terms of a Project Agreement, ANNA360 -Dev will not be liable for indirect, incidental, special, consequential, exemplary, or punitive losses, or for loss of profits, revenue, data, goodwill, business opportunity, or anticipated savings arising from the use of this website or the services.

For a claim connected with a specific paid service, ANNA360 -Dev's total aggregate liability should not exceed the fees actually paid to ANNA360 -Dev for the specific service that gave rise to the claim, unless the Project Agreement or applicable law requires otherwise.

Nothing in these Terms & Conditions excludes or limits liability that cannot lawfully be excluded or limited. This clause should be confirmed by legal counsel before publication and aligned with each signed Project Agreement.

14. Suspension, termination, and outstanding obligations

The process for pausing or terminating an active project, including notice requirements, work-in-progress, delivery or handover, fees due, approved costs, and any refund treatment, will be set out in the Project Agreement.

If no Project Agreement has been signed, either party may stop an inquiry or preliminary discussion at any time. This does not create an obligation for ANNA360 -Dev to perform work or for the prospective client to proceed with a project.

On termination of an active engagement, obligations that are intended by their nature to continue—such as payment obligations for completed work, confidentiality, intellectual-property provisions, and liability limitations—will continue to the extent stated in the Project Agreement and permitted by law.

15. Governing law and resolving concerns

Before beginning formal proceedings, the parties should try in good faith to resolve a concern through direct written communication. For a contracted project, any additional dispute-resolution process in the Project Agreement will apply.

These Terms & Conditions are governed by the laws of India. Subject to applicable law and any different term in a Project Agreement, the courts of Guwahati, Assam, India will have jurisdiction over disputes relating to these Terms & Conditions.

16. Updates to these Terms & Conditions

ANNA360 -Dev may update these general website Terms & Conditions from time to time. Any revised version will be posted on this page with an updated Last Updated date. Continued use of the website after publication of an update means that the visitor is using the website under the revised general terms.

A signed Project Agreement is not changed merely because this webpage is later updated. Changes to an active project's scope, fees, timeline, or other contract terms should be agreed in writing by the relevant parties.

17. Contact ANNA360 -Dev

If you have a question about these Terms & Conditions or would like to discuss a potential project, contact us directly:

A request for a proposal is an opportunity to discuss requirements; it does not by itself confirm a contract, scope, appointment, price, timeline, deliverable, or outcome.