Website and service terms · Updated 16 September 2026
Terms of Service
These terms explain the basic conditions for using the ReddyStack website and requesting scoped digital service work.
Website use
The ReddyStack website explains a proof-first digital growth method, connected capabilities, ways to work, portfolio items, and practical insights. A proposal selects only the web, search, paid acquisition, creative, tracking, automation, or product work required by the agreed problem.
Information on the website is not a guarantee of results, rankings, revenue, traffic, or platform approval.
Project scope
Submitting an enquiry starts a scope discussion; it does not automatically start a paid project. Service work should be confirmed through an agreed scope, timeline, deliverables, exclusions and price before work starts. The agreement should identify the content and access required from the business and the person responsible for approval.
Changes outside the agreed scope may require a revised quote, timeline or separate phase. Describe the additional work and its effect before proceeding. A website build, an advertising campaign and an ongoing support arrangement are different scopes, even when they relate to the same business.
Business identity
ReddyStack is currently presented as an founder-led proof-first digital growth studio operated by rahul reddy adelli based in Hyderabad, India.
ReddyStack is not registered as a private limited company, llp, or opc. GST details will be provided when applicable. Udyam or MSME details will be shown only after registration is completed.
Communication, approvals, and third-party tools
Project communication may happen through email, WhatsApp, calls, documents or shared workspaces depending on the agreed scope. Keep approvals and material changes in an identifiable written record. Content, feedback and account access are dependencies to agree before a timeline is confirmed; do not send passwords or private customer records through the public enquiry form.
Some projects may depend on third-party services such as hosting platforms, analytics, forms, payment providers, email tools, automation tools, AI services, or domain providers. Those services remain subject to their own terms, pricing, limits, outages, and approval rules.
Content, claims and supplied assets
Business details, prices, service areas, product claims and supplied assets need approval for the intended use. Identify any licensing or permission limits before production. A generated presenter or demonstration should not be presented as a real customer's experience when it is not.
The portfolio currently contains personal and demo projects. Guide examples and calculations illustrate a method; they are not paid client results or forecasts. Platform references should be checked for the specific live use because requirements can change.
Ownership, handover and continuing costs
The proposal should state account ownership, required access and the files or information included at handover. Domains, hosting and advertising accounts should remain accessible to the business. Source files, licences and third-party assets may have specific delivery or usage conditions that need to be identified in the scope.
Advertising spend, domain renewal, hosting, paid tools and usage-based services are separate costs unless expressly included. Ongoing maintenance, new content, monitoring and optimisation should also be agreed explicitly rather than assumed to continue after a one-time project.
Ask Rahul directly. Policies are part of the written scope for every project.