Terms of Service

These Terms of Service explain the general conditions for using the DigiCareHouse website and making enquiries about our digital services. In this document, “DigiCareHouse,” “we,” “us,” and “our” refer to the business operating this website. “You” refers to the person using the site and, where relevant, the organization that person is authorized to represent.

Please read these terms before relying on website information or submitting a request. They should be read with our Privacy Policy, which describes the handling of information associated with website visits and communications. If you do not agree to the conditions for using this website, please discontinue its use. A paid project is subject to a separate agreement, proposal, statement of work, or other written terms accepted by the parties; browsing this website does not create a paid engagement.

You may use this website to learn about our services, read our articles, contact our team, and explore a possible business relationship. You are responsible for making sure you have authority to act for an organization when you submit information or discuss a project on its behalf. Please provide accurate contact details and correct material errors that may affect a conversation, proposal, or delivery.

Our website is intended for a business audience. If you cannot legally enter into an agreement in your location, you should involve an appropriately authorized person before arranging services. Information on this site is provided for general guidance about our work and does not replace advice suited to your particular legal, financial, medical, security, or operational circumstances. You remain responsible for deciding whether a service is appropriate for your needs and for obtaining any specialist review your organization requires.

DigiCareHouse provides services relating to AI automation, web development, mobile application development, software development, and associated digital work. Website descriptions explain the types of work we can discuss. They are not a complete specification, a binding delivery schedule, or a commitment to accept every project. Availability, technical feasibility, and the proposed approach need to be assessed for the relevant engagement.

A project agreement should identify the scope, deliverables, responsibilities, fees, payment schedule, assumptions, acceptance process, and any ongoing support. Where a signed or otherwise accepted project agreement conflicts with these general terms on a project-specific matter, the project agreement takes priority to that extent. Any promises about a particular integration, service level, certification, migration, or result should be recorded in that agreement. A conversation or website enquiry alone does not authorize us to start chargeable work.

Submitting a form, requesting a quote, or booking an initial conversation allows us to evaluate your requirements and respond. We may ask for more information about your objectives, existing systems, audience, budget, and timeline. Please share materials you have permission to provide and tell us about relevant restrictions, dependencies, or deadlines at an early stage.

Unless stated in an accepted agreement, an estimate is an initial assessment based on the information available at that time. Discovery, changes in requirements, third-party limitations, or previously unknown technical issues may affect effort, cost, and scheduling. A proposal may specify its own validity period and acceptance method. If it does not, ask us to confirm that the proposal is still current before relying on it. We aim to explain material assumptions so both parties can make informed decisions before work begins.

Successful delivery often depends on timely cooperation. For an agreed project, you may need to provide approved content, brand assets, business requirements, access to systems, test data, feedback, and decisions from an authorized contact. You are responsible for the accuracy and legality of materials you supply and for obtaining necessary permissions from owners, users, employees, customers, or other relevant people.

Please tell us about accessibility requirements, industry rules, security standards, data residency needs, and internal approval processes that apply to your organization. Do not assume that a general service description includes an audit or certification against a particular standard. Delayed access, incomplete content, or conflicting instructions can affect the schedule. Any resulting changes to cost or delivery should be addressed through the project process rather than assumed. Keep appropriate copies and backups of information you provide unless the agreement assigns that responsibility differently.

Requests that add functionality, change an approved design, introduce a new integration, or alter an agreed deliverable may affect the scope. A project agreement should explain how such requests are assessed and approved. Before additional work begins, the parties should confirm any material effect on fees, timing, testing, and responsibilities. A small visible change can sometimes involve underlying technical work, so the impact needs to be assessed in context.

Where review or acceptance milestones are used, provide clear feedback against the agreed requirements within the relevant review period. Report reproducible defects with enough detail for them to be investigated. Acceptance criteria, revision allowances, and any treatment of delayed feedback belong in the project agreement. These general terms do not create an automatic acceptance deadline or a right to unlimited revisions. Approval of one milestone should not be treated as approval of unrelated work that has not been presented for review.

Fees, currency, taxes, deposits, recurring charges, and payment dates should be stated in the accepted project agreement or invoice arrangements. Third-party expenses such as hosting, domains, paid plugins, API usage, messaging services, app store accounts, and software subscriptions may be separate from our professional fees. The agreement should identify which costs are included and who is responsible for each account.

Cancellation, refunds, payment disputes, and the treatment of work already completed should be handled under the applicable agreement and any mandatory legal rights. These website terms do not impose a universal no-refund rule, an automatic cancellation fee, or an undisclosed recurring subscription. Please raise billing questions promptly so they can be reviewed against the agreed scope and records. Payment instructions should be verified through a trusted communication channel if they change unexpectedly or appear inconsistent with earlier arrangements.

The website's original text, visual identity, layouts, and other materials are protected by the intellectual property rights of DigiCareHouse or the relevant owners. You may view the site and use reasonable extracts for internal evaluation of our services, subject to applicable law. You must not present our work as your own, remove ownership notices, or reproduce substantial website content commercially without permission.

Ownership of project deliverables, source code, design files, documentation, and working materials must be addressed in the project agreement. Do not assume that a general service fee transfers every right in all tools used during delivery. Pre-existing materials, reusable components, open-source software, and licensed third-party assets may remain subject to their original ownership and license terms. The agreement should explain the rights you receive, any conditions attached to transfer, and what files or access are included in the handover.

You retain the rights you hold in materials you supply. By providing materials for an agreed activity, you authorize their use to the extent reasonably needed to evaluate the request or carry out that activity, subject to any applicable confidentiality terms. You are responsible for confirming that supplied content does not infringe rights, mislead users, or disclose information without appropriate authority.

If a discussion requires confidentiality beyond ordinary business correspondence, ask for an appropriate agreement before disclosing sensitive material. A public contact form is not a secure repository for credentials, regulated records, or highly confidential documents. Neither party should assume permission to publish the other's confidential information. Any use of client names, testimonials, screenshots, or project work in a portfolio should be addressed through the relevant permissions or agreement. Tell us about publication restrictions before sharing material intended solely for private review.

Digital projects often depend on independent providers, including hosting platforms, cloud infrastructure, payment services, analytics tools, AI providers, application stores, and plugin developers. Those services have their own terms, pricing, availability, limits, and technical policies. An integration can be affected by changes to an API, provider approval, rate limit, account suspension, or the withdrawal of a product.

Unless the project agreement states otherwise, you should expect to maintain the licenses and accounts assigned to you and comply with their provider terms. We cannot bind an independent provider to a particular decision, price, or service level. Recommendations are based on the information and requirements considered during the engagement and should be reviewed when circumstances change. External links on our website are provided for convenience; linking to a service does not transfer responsibility for that provider's content or conduct to DigiCareHouse.

AI and automation tools can help perform tasks, connect systems, and produce suggestions, but their outputs can be inaccurate, incomplete, biased, or unsuitable for a particular use. Automated workflows can also fail when inputs, permissions, or connected services change. The suitability of a solution needs to be evaluated against the intended use, the data involved, and the consequences of an error.

You should maintain appropriate human review for material decisions and outputs, particularly in contexts affecting people, money, safety, legal rights, or access to important services. Testing, monitoring, approval steps, access restrictions, and rollback arrangements should be agreed where relevant. A service description is not a promise of error-free AI output, guaranteed business growth, or complete replacement of professional judgment. Any performance commitment, training-data permission, approved AI environment, or ongoing monitoring obligation must be specified in the project agreement.

You must not use this website or an agreed service for unlawful activity, harassment, fraud, infringement, or unauthorized access. Do not upload malicious code, attempt to bypass security controls, probe systems without permission, interfere with availability, or submit deceptive or automated spam. You must not collect information from the site in a way that violates applicable law or materially disrupts its operation.

If a project gives you access to an administrative account, protect its credentials and use the permissions granted for their intended purpose. Notify us promptly of a suspected compromise affecting a shared project environment. Security responsibilities, backup arrangements, vulnerability remediation, and incident response should be assigned in the project agreement. Do not treat the existence of a website or maintenance service as an unlimited security guarantee. Authorized testing of a client environment should have a clearly agreed scope and permission from the relevant owner.

We may update website content, change features, or carry out maintenance. Temporary errors or interruptions can occur, including those caused by hosting, communications networks, software updates, or third-party services. We do not promise that every part of this public website will be continuously available or that all historical content will remain online indefinitely.

For a delivered project, support hours, response targets, warranty periods, maintenance tasks, hosting responsibilities, and future updates must be defined in the applicable agreement. A completed development project does not automatically include indefinite maintenance, new features, content entry, or support for every future software version. If you need ongoing assistance, ask us to document an appropriate support arrangement. Where a project is handed over to your team or another provider, access, documentation, outstanding issues, and any continuing responsibilities should be made clear.

We aim to describe our services accurately, but general website information may contain errors or become outdated. To the extent permitted by applicable law, the public website and its general information are made available without a promise that they will meet every visitor's particular requirements. Any express project warranties, service commitments, liability limits, exclusions, or remedies should be set out in the agreement governing that work.

Nothing in these terms excludes rights or responsibilities that cannot lawfully be excluded, including mandatory consumer protections where they apply. These general website terms do not introduce an undisclosed monetary liability cap or an automatic indemnity for every possible claim. Responsibility for a particular loss depends on the relevant facts, applicable law, and agreed contract. If you believe information or work is defective, contact us with details so the matter can be assessed and the appropriate process followed.

We may restrict access to website features where reasonably necessary to investigate misuse, protect systems, or comply with applicable requirements. Ending or suspending an agreed project is a separate matter governed by its contract and mandatory law. The agreement should address outstanding payments, completed work, access removal, data handling, transition assistance, and the provisions that continue after termination.

If a concern arises, contact us first with a clear description, relevant dates, and the outcome you are seeking. We encourage a practical attempt to resolve issues through discussion. A project agreement may set out the applicable law, court jurisdiction, mediation, or another dispute process. In the absence of an agreed provision, the rules that legally apply will govern. This page does not impose mandatory arbitration, waive non-waivable rights, or select a jurisdiction solely because an address appears in the footer.

We may revise these website terms as our services and website evolve. The latest published version is identified by the date at the top. Changes to a signed project agreement require the process agreed by its parties; updating this page does not silently rewrite a separately accepted contract. Where additional notice or agreement is required, it should be obtained through an appropriate channel.

For questions about these terms or a possible engagement, email info@digicarehouse.com, call +1 (848) 384 3773, or use our contact page. Our website contact address is 493 Washington Ave, Albany, NY 12206, United States. Please identify the service, proposal, or project involved so your request can be directed appropriately. For questions about personal information, communication preferences, or privacy rights, refer to our Privacy Policy.