Trust

Changelog

What actually changed here, in date order. Mostly for our own clients and anyone using the API, but it is public because there is no reason for it not to be.

Last updated 30 July 2026 Applies to everyone using azi.solutions

Recent changes

30 July 2026

Legal and trust pages expandedAdded cookie, acceptable use, refund, AI use, editorial, accessibility, security disclosure, sub-processor, data transfer, California, disclaimer and DMCA policies, plus this changelog and a trust centre. Every green button was darkened to pass WCAG AA contrast after measuring the old one at 3.37:1.

30 July 2026

Client dashboard rebuiltThe overview now leads with your active project rather than four counters. API keys gained live quota bars. Settings gained a security summary.

30 July 2026

API documentation rebuiltLanguage tabs for cURL, JavaScript and PHP, a sticky section index, per-endpoint cards and a real error table. Limits are read from configuration so the docs cannot drift from the API.

29 July 2026

Site-wide redesignNew header with a command-palette search across every service, tool and guide. New footer. Every service page rebuilt with published prices and an honest section on when not to buy.

29 July 2026

All 16 free tools liveMerge, split, compress and Word-to-PDF completed the set. Every one runs in your browser with no upload. Two tools that would have needed a full PDF rendering engine were removed rather than left as permanent “coming soon” cards.

29 July 2026

Public API openedFour endpoints, free keys, published rate limits. Same engine as the free tools.

28 July 2026

Client dashboard and monthly reportsProjects, milestones, file delivery and two-way messages. Monthly reports with score changes, drafted by the system and published by a person.

How we version things

The v1 API path will not change shape under you. New fields may appear inside data; existing fields will not be renamed or removed. Anything breaking ships as v2 with v1 left running. That commitment is repeated in the API documentation.

Policy pages carry a “last updated” date. If a change materially affects existing clients, we email them rather than expecting anyone to re-read a page.

Outages

We do not run an automated status page, and we would rather say so than publish a green tick that nobody is checking. If a site we host or maintain is down, email [email protected] with “site down” in the subject line and it jumps the queue. Response times are on the support page.

API documentationVersion stability policy SupportResponse times and quick fixes Trust centreEverything in one place