How order data is used

Account, order and payment information

The service uses your confirmed account identity and email, repository identity, requested outcome, allowed paths, acceptance criteria, permission records and order history to provide the work, prevent unauthorised access and handle payment or delivery issues. Supabase provides account authentication. Cloudflare hosts the service and its order ledger. Stripe processes payment and refunds; payment-card details are entered with Stripe.

Contract information is used to provide the requested service. Security and operational records support fraud prevention and reliable operation. Accounting and dispute records may need to be retained to meet legal obligations and resolve claims.

Repository permission and model processing

GitHub is used to authorise the selected repository and publish a bounded branch and pull request. Repository credentials are protected by the service and are not included in the public evidence. Source and task information are processed by the configured coding and review provider, which can be ChatGPT-authenticated Codex or Cloudflare Workers AI. Delivery records identify which provider was used.

These providers operate their own infrastructure and may process information in countries outside the UK. Their own privacy notices describe their processing. Do not submit personal customer data, secrets or confidential material to this public-repository service.

Public evidence is an explicit part of the service

The repository snapshot, requested outcome, acceptance criteria, proposed patch and review evidence are published as public GitHub Actions artifacts. The pull request is also public. Quote acceptance requires your explicit agreement to this disclosure. The workflow requests one-day artifact retention, but that does not guarantee that copies or public GitHub history disappear.

Access, retention and requests

Signed-in accounts can read their own orders. Account access uses your browser's authentication storage. The service retains order, consent, payment and audit records needed for delivery, recovery, accounting and disputes. Public repository evidence is separate from private account records.

For access, correction, deletion or other data-protection requests, email support@tailwaggingwebdesign.com. Requests are reviewed against applicable rights and retention obligations; deleting a private account record cannot remove copies made from public evidence. You can also raise a concern with the Information Commissioner's Office.