Effective 27 August 2026.
Yakware acts as controller for account, billing, security, support, and service-improvement data. For repository metadata, deployment configuration, logs, artifacts, and target details submitted by a customer, the customer is generally the controller and Yakware acts as its processor.
We process data to perform the contract, secure and operate the service, meet legal obligations, support users, prevent abuse, and improve and measure the product. Campaign attribution is used to measure our own advertising and is not sold or used to build third-party advertising profiles.
We share data only with service providers needed for hosting, email, payments, monitoring, support, and customer-requested integrations, or where law requires it. Providers are bound by confidentiality and data-protection obligations. Where data crosses borders, we use an approved transfer mechanism where required.
Deployment logs and releases follow the retention limits shown for your plan or shorter settings you choose. Security, audit, billing, and backup records may be retained longer where needed for legal, fraud-prevention, or recovery purposes. Advertising attribution is retained only as long as needed to measure the associated conversion. Deleted data may remain in protected backups until those backups expire.
We use access controls, account-scoped authorisation, encryption for sensitive stored values, log masking, signed short-lived capabilities, isolated runners, audit records, and transport encryption. No service can guarantee absolute security; report suspected incidents to support@yakware.com.
Depending on where you live, you may request access, correction, deletion, restriction, portability, or objection, and may complain to your data-protection authority. Customers should direct end-user requests about customer-controlled deployment data to the relevant customer first.
Questions or data requests: support@yakware.com.