Privacy
The service is designed around public links, redacted materials, and small task records so useful work can happen without unnecessary private data.
Updated May 21, 2026We receive the information a client chooses to send: name, email address, company or store name, public links, screenshots, files, exports, copied snippets, task notes, and delivery feedback.
Payment processing is handled by Stripe, Gumroad, or another approved payment provider. We do not store full card numbers or bank credentials.
Client information is used to scope the task, check feasibility, create a checkout, deliver the agreed artifact, provide one bounded correction when included, and keep a practical customer record so we do not duplicate outreach or miss follow-up context.
We may keep internal notes about source URL, task type, payment status, delivery status, and next action. Sensitive client materials should not be posted publicly or committed to public repositories.
Send only the materials needed for the task. Prefer redacted screenshots, small exports, copied snippets, sample rows, public URLs, or synthetic examples when possible.
Do not send customer lists, passwords, private keys, payment data, medical records, legal files, financial records, employee data, or other regulated private information unless a secure handling plan has been agreed in writing.
We do not sell client data. We share information only with the tools needed to operate the service, such as email, payment processors, hosting, file storage, or development tools, and only as needed for the task.
If a task requires using a new third-party tool with sensitive materials, we will ask first or request a safer redacted version.
We keep task records long enough to support delivery, refunds, accounting, customer history, duplicate-contact prevention, and future follow-up context. Private materials can be deleted on request unless retention is required for payment, dispute, security, or operational reasons.
Privacy questions or deletion requests can be sent to hello@codekidz.ai. Include the relevant task, checkout, or email thread so we can identify the record.