Digital Sustainability & Responsible Technology Policy

Tenth Tech designs, develops and supports websites, applications, software platforms and integrations. We recognize that digital services consume electricity, transfer data and depend on physical infrastructure. We commit to incorporating resource efficiency and digital sustainability into decisions where we can meaningfully influence them, while preserving accessibility, privacy, information security, reliability and the intended user experience.

Our approach is to measure where feasible, avoid unnecessary resource use, optimize based on evidence, and communicate results accurately. We do not equate a good performance score with a verified carbon-footprint calculation.

This policy applies to Tenth Tech's own digital services and, within agreed contractual responsibility, to work performed by employees and contracted contributors on client projects. It applies to design, engineering, hosting recommendations, operations, analytics, procurement decisions and technical QA.

The Founder & CEO is responsible for policy oversight, approval of material exceptions and periodic review. Project leads are responsible for applying the policy proportionately to the work, recording significant decisions and involving relevant engineering specialists.

We do not claim control over infrastructure, providers or configurations owned exclusively by clients. Where necessary, we provide recommendations and obtain approval before changing those arrangements.

Purposeful functionality. Define user tasks and information needs before adding unnecessary features, third-party scripts or resource-intensive interactions. Prefer existing, maintainable components over duplicate implementations where appropriate.

Efficient content and media. Use appropriately sized responsive images, compression and modern formats where compatible. Consider lazy loading, explicit media dimensions and user-initiated loading for heavy embeds, without hiding critical content or harming accessibility.

Frontend efficiency. Reduce unused or duplicate JavaScript and CSS, unnecessary font variants, avoidable network requests and excessive client-side processing. Prioritize useful content and progressively load nonessential functionality.

Backend and data efficiency. Profile significant database queries, remove repeated unnecessary processing, and use indexing, pagination, selective retrieval, caching and appropriately scheduled background work where justified by actual workloads and data-freshness requirements.

Mapping and data-heavy interfaces. Where relevant, limit spatial or application payloads to what the user needs, using techniques such as progressive loading, suitable clustering or geometry optimization without compromising data accuracy.

Third-party services and analytics. Assess the necessity and resource cost of scripts, plugins, analytics and integrations. Keep privacy and security requirements central. Avoid introducing tracking that does not serve a defined purpose.

Infrastructure and hosting. Assess resource sizing, caching, storage growth, retention and operational efficiency within our area of responsibility. Consider providers' verifiable environmental information when this is relevant and consistent with client requirements, data residency, resilience and cost.

For material projects or changes where measurement is proportionate, the delivery lead should:

1. Identify representative pages, transactions, APIs or workflows to be assessed.
2. Record a baseline using available measures such as transferred bytes, requests, Core Web Vitals, server timings, query profiles, third-party scripts and resource utilization.
3. Identify practical improvements and agree their priority against functionality, security, accessibility, reliability, cost and client requirements.
4. Include relevant checks in QA and compare the outcome against the baseline after implementation.
5. Record significant trade-offs, exceptions and improvements in project documentation or service reporting.

Tools may include browser developer tools, Lighthouse, WebPageTest, real-user performance data, hosting monitoring and database profilers as appropriate. Tool names describe available assessment methods, not a claim that every tool is used on every project.

Where carbon-estimation tools are used, outputs must be labeled estimates, with their assumptions, coverage and limitations recorded. Tenth Tech will not claim carbon neutrality, net-zero status, certified emissions reductions or compliance with an environmental certification without independent supporting evidence.

Where services are within our operating responsibility, teams should review recurring processing, unnecessary data retention, oversized assets, monitoring noise, inefficient jobs and preventable rework. Maintainability, documentation, reusable architecture and stable releases also support efficient use of engineering and computing resources.

Any modification to operational configurations, backups, retention, hosting or security controls remains subject to client approval and applicable contractual obligations.

Resource efficiency does not override essential user needs, accessibility, confidentiality, legal requirements, security or service continuity. Where goals conflict, project leads should document the decision and implement the proportionate solution approved by the appropriate owner.

The policy owner reviews this policy at least once per year. Project leads may use checklists, performance baselines, release evidence and improvement records to demonstrate implementation. Significant gaps should result in actionable improvements, with clear ownership and realistic follow-up.

Questions and feedback: info@thetenthtech.com.

Our approach is informed by, but does not imply certification against, the W3C Web Sustainability Guidelines, the Green Software Foundation Software Carbon Intensity specification, and established web performance practices.