Legal

Terms and conditions

Terms of Service, Acceptable Use Policy and Support Agreement (United States and Colombia)

Last updated: 10 min read19 sections

Courtesy translationThis is a courtesy translation. In case of any discrepancy, the Spanish version prevails. Read the Spanish version

On this page
  1. 1) Key definitions
  2. 2) Scope of service by plan (summary)
  3. 3) Requests and operating limits
  4. 4) Security, vulnerabilities and responsibilities
  5. 5) Backups and restoration
  6. 6) Acceptable use (AUP)
  7. 7) Common exclusions
  8. 8) Service levels and response times (SLA)
  9. 9) Pricing, billing and renewals
  10. 10) Intellectual property
  11. 11) Confidentiality and access
  12. 12) Warranties, disclaimers and limitation of liability
  13. 13) Effective date, suspension and termination
  14. 14) Governing law and jurisdiction
  15. 15) Changes to these Terms
  16. 16) Privacy and personal data (non-EU)
  17. 17) Contact
  18. Annex A — Examples of basic changes (for guidance)
  19. Annex B — Security incident workflow

DAPSITE (We Are Datalab S.A.S.) — Terms of Service, Acceptable Use Policy and Support Agreement (United States and Colombia).

1) Key definitions

  • “DAPSITE” or “Provider”: DapSite is a brand that belongs to We Are Datalab S.A.S. (Tax ID/NIT 900.480.799-9). For the purposes of this Agreement, the Provider is We Are Datalab S.A.S. and/or its affiliates and subcontractors.
  • “Customer”: the individual or legal entity that contracts the Services.
  • “Services”: maintenance, support, administration, optimization, monitoring, and content tasks for websites (in general, regardless of the technology or content management system they are built with), according to the current plan and/or scope documents.
  • “Basic change”: a request that does not require graphic design with mockups, does not involve integrations or custom development, and does not exceed 2 hours of total work.
  • “Security incident”: hacking, malware, exploitation of vulnerabilities, severe service outage, or data loss.
  • “Third-party elements”: hosting, domains, SSL certificates, themes, templates, extensions, libraries, payment gateways, analytics, CDNs, etc., provided by third parties.
  • “Platform”: the ticketing system and Customer panel where requests, reports, and communications are recorded.

2) Scope of service by plan (summary)

  • Periodic updates of the core software, themes, extensions, and components; 24/7 uptime monitoring; automatic backups; firewall/antimalware; performance optimization; reports and support according to the plan.
  • Unlimited basic content changes, handled one at a time in order of arrival. Tasks that require complex design, integrations, development, or that exceed 2 hours are excluded. Those tasks are quoted separately or declined.
  • Hack cleanup and restoration from backups when the contracted plan includes it.
  • Any specific promise (e.g., a “Good” Core Web Vitals rating) only applies if it is expressly agreed in the plan or an annex.

The exact details of each plan (Basic, Standard, Pro/multisite) are set out in the commercial proposal and/or service annex and may be updated without affecting rights acquired during the prepaid period.

3) Requests and operating limits

3.1. Single point of contact. All requests must be filed through the Platform. Only one request may be active at a time. When one is completed, we start the next.

3.2. Excess complexity. We reserve the right to decline requests that exceed the concept of a Basic change or that, at our technical discretion, compromise stability, security, or best-practice guidelines. Alternatively, we may propose a quote outside the plan.

3.3. Priority. Critical incidents (total outage, active hack, data loss) are handled with priority over content changes.

3.4. Maintenance windows. Major updates may be carried out during scheduled windows (off-peak hours) to mitigate risk.

4) Security, vulnerabilities and responsibilities

4.1. Nature of the risk. On any website, much of the risk comes from third-party components, extensions, libraries, and themes. The Provider does not guarantee the complete absence of vulnerabilities.

4.2. Provider practices. We apply security patches, scans, firewall, hardening, dependency review, and monitoring. When critical vulnerabilities are detected, we may temporarily disable third-party components to protect the site.

4.3. Customer responsibilities. (i) Maintain strong passwords and 2FA on the accounts under its control (hosting, email, CDN, payment gateways, etc.). (ii) Not install extensions, themes, or components without the Provider's validation while the service is in effect. (iii) Provide up-to-date administrative access at the start of the service.

4.4. Security incidents. If an incident occurs: (i) Containment (isolation, blocking, deactivation of compromised components), (ii) Remediation (malware cleanup, patching, hardening), (iii) Restoration (from valid backups), (iv) Lessons learned (recommendations). If the plan does not include hack cleanup, or the cause originated from actions of the Customer or unauthorized third parties, remediation costs will be invoiced.

4.5. Content and data. The Customer owns its content/data and is responsible for its lawfulness. The Provider is not responsible for losses when the cause is beyond its control (hosting, email provider, registrar, CDN, widespread cloud failures, acts of God/force majeure, actions of third parties, Customer errors, etc.).

5) Backups and restoration

5.1. Coverage. We make automatic backups according to the plan; however, by their nature, no backup is infallible.

5.2. Customer copies. The Customer must keep additional external copies. Upon request, we can deliver available snapshots. We are not responsible for losses if the last complete backup does not contain the exact desired version.

5.3. RPO/RTO. Recovery point and recovery time objectives are reasonable efforts; they will depend on the size of the site, the hosting, the traffic, and the health of the database.

6) Acceptable use (AUP)

6.1. Prohibitions. The following are prohibited: (i) malware, phishing, mass spam, botnets, attacks (DDoS, brute force, port scanning), (ii) illegal content (e.g., child pornography), (iii) infringement of copyrights or trademarks, (iv) distribution of illegal software or circumvention of security, (v) any use contrary to the applicable law in the United States or Colombia.

6.2. Enforcement and suspension. The Provider may suspend the Services in whole or in part in the event of AUP violations, serious incidents, or legal requirements. In serious or repeated cases, it may terminate the service without a refund of the current period.

6.3. Email and marketing. Spam and the use of the infrastructure for unauthorized campaigns are prohibited. Cleanup charges and third-party costs may apply for abuse.

7) Common exclusions

  • Custom development, integrations, advanced e-commerce, complete redesigns, branding, video editing, photography, illustration, strategic copywriting, managed SEO, ad campaigns, complex migrations, and legal or compliance audits (unless expressly agreed).
  • Tasks that exceed 2 hours of work or require design with mockups.
  • Repairs or refactoring caused by interventions of third parties or by the Customer outside the agreed workflow.
  • Guarantees of uptime, SEO rankings, business results, or specific metrics, unless explicitly committed in writing.

8) Service levels and response times (SLA)

8.1. Priorities. Critical (site down, active hack): immediate best effort. High (severe functional failure): first 4–24 business hours. Medium/Low (content changes, minor adjustments): standard queue.

8.2. Windows and coordination. Changes with an impact on UX or sales funnels may be scheduled to minimize disruption.

8.3. Reporting. On applicable plans, we deliver monthly reports on updates, status, performance, and security.

9) Pricing, billing and renewals

9.1. Prepayment. All plans are prepaid for monthly or annual periods. Renewal is automatic until cancellation.

9.2. Price changes. We may adjust prices, giving notice before they take effect. Changes do not apply retroactively to periods already paid.

9.3. Refunds and 30-day guarantee. If, during the first thirty (30) calendar days from the start of the service, the Customer is not satisfied, they may request cancellation within that period by writing to soporte.web@wearedatalab.co, and 100% of the amount paid will be refunded. Outside this case, there are no refunds for periods already started or for partially used months, and cancellations apply to the following period.

9.4. Late payment. Non-payment may lead to suspension and/or termination of the service, with removal of access and temporary licenses (e.g., premium extensions or tools provided by the Provider).

10) Intellectual property

10.1. Customer's. The Customer retains ownership of its content and trademarks. It is responsible for having all licenses and permissions.

10.2. Provider's. The Provider retains rights over tools, scripts, configurations, and know-how. It may license premium extensions or tools for use while the plan is in effect; upon termination, the Customer must purchase its own licenses or accept their deactivation.

11) Confidentiality and access

11.1. Access. The Customer will provide the necessary administrative access (hosting, control panel, CMS, DNS, CDN) and will keep the list of authorized contacts up to date.

11.2. Confidentiality. Each party undertakes to protect the other's confidential information and to use it only to perform the service.

11.3. Non-solicitation. During the service and for 12 months afterward, the Customer will refrain from directly hiring the Provider's staff/contractors involved in providing the service (unless agreed in writing). Penalty: 12 months of the annual compensation of the person involved, or whatever the applicable laws provide.

12) Warranties, disclaimers and limitation of liability

12.1. “As is”. To the extent permitted by law, the Services are provided “AS IS”, without implied warranties of merchantability, fitness for a particular purpose, or non-infringement.

12.2. No indemnification by the Provider. The Provider does not indemnify the Customer for third-party claims. The Customer does undertake to defend, indemnify, and hold the Provider harmless against claims arising from (i) the Customer's content, (ii) improper use, (iii) AUP violations, (iv) the Customer's breach of contract, (v) infringement of third-party rights by the Customer.

12.3. Limitation of liability. The Provider's total aggregate liability for any claim is limited to the amount actually paid by the Customer for the service that gave rise to the claim, either the last billed period or, at the Provider's choice, the amount paid in the last 3 months, whichever is lower. In no event are we liable for lost profits, data loss, reputational damage, business interruption, replacement costs, or indirect, special, consequential, or punitive damages.

12.4. Force majeure. Neither party will be liable for failures due to causes beyond its reasonable control (natural disasters, widespread cloud/infrastructure outages, war, embargoes, failures of critical providers, government actions, strikes, etc.).

13) Effective date, suspension and termination

13.1. Start. The service begins after payment confirmation and delivery of access.

13.2. Suspension. We may suspend the service for (i) late payment, (ii) serious security incidents, (iii) violation of the AUP or the law, (iv) imminent risks to the infrastructure.

13.3. Termination. Either party may terminate with prior notice according to the billing cycle. Obligations that by their nature must survive (intellectual property, confidentiality, non-solicitation, limitation of liability, governing law) survive.

14) Governing law and jurisdiction

This Agreement is governed by the laws of the Republic of Colombia for all Customers, regardless of their country of residence, including Customers in the United States. Jurisdiction: the courts of Bogotá D.C.

Alternatively, the parties may agree in writing to submit their disputes to commercial arbitration. With Customers outside Colombia, the arbitration may be international and administered by the AAA in English.

15) Changes to these Terms

We may update these Terms and publish them on the Platform or website. Continued use implies acceptance. We will notify material changes with reasonable advance notice.

16) Privacy and personal data (non-EU)

We process personal data in accordance with the applicable laws of the United States and Colombia. Personal data collected on this site is processed under our Personal Data Processing Policy. We do not incorporate obligations under the GDPR or other European Union regulations. For customers with an audience in the EU, regulatory compliance must be contracted as a separate service.

17) Contact

Data controller: We Are Datalab S.A.S., Tax ID (NIT) 900.480.799-9
Support and legal: soporte.web@wearedatalab.co · +57 305 452 8126
Address: Carrera 12 # 90-20, Office 309, Bogotá D.C., Colombia

Annex A — Examples of basic changes (for guidance)

  • Creating/editing blog posts, informational pages, text, and media already provided by the Customer.
  • Minor adjustments to existing CSS, margins, fonts, and colors.
  • Image replacement, simple optimization of file size and formats.
  • Adding tracking codes (Analytics, Pixel), Search Console verification.
  • Simple settings in existing extensions or modules (without new integrations).

Not basic: complete layout of new sections, redesigns, complex funnels, API integrations, e-commerce, custom features, hosting migrations, full multi-language setup, custom theme or template development, or tasks of more than 2 hours.

Annex B — Security incident workflow

  1. Detection (alert/monitor).
  2. Containment (block IPs, disable compromised components, maintenance mode).
  3. Remediation (malware cleanup, patches, hardening).
  4. Restoration (backup/snapshot).
  5. Verification (final scan).
  6. Report.
  7. Recommendations (updates, replacement of abandoned components, 2FA, key rotation).

Final note: this document is modular and may be adapted to framework agreements, service orders, and technical annexes per customer. It supersedes previous versions.

Questions about these terms?

In the Help Center we answer the most common questions about lock-in, included changes and personal data.

Go to the Help Center