Privacy

Privacy Policy

This policy describes the categories of information handled by CodeUnlim and the controls currently implemented. Last updated: October 14, 2026.

Information we handle

Account and authentication data, including email address and sign-in/session records.
Package selections, booking dates, access windows, time zones, reservation and subscription status.
Payment/order metadata needed to verify payment and fulfill a package. Card entry is handled in Stripe Checkout when Stripe is available; CodeUnlim uses provider references and payment status for fulfillment.
API credentials, entitlement identifiers, request timing/status, usage counters, and security or abuse-prevention metadata needed to operate and protect the service.
Essential cookies for authentication and security. Locale preferences may be stored in browser storage.
Optional page and package-selection analytics through Google Tag Manager and Google Analytics only after a visitor allows analytics.

Prompts, code, and model processing

CodeUnlim does not use customer prompts or source code to train a model. API content is transmitted to the configured inference runtime to produce responses. Repository tests verify that prompt/source content is not written into the durable gateway request records covered by those tests. This does not establish that every infrastructure component or worker operator has zero transient processing, logging, or retention. Those upstream operational details and retention periods require confirmation and are not represented here as a guarantee.

Do not send secrets or personal data in prompts unless you have authority and have considered the applicable risks.

Payments and service providers

Stripe processes card checkout when enabled. The service receives order, amount, currency, session/payment references, and verified payment outcomes. Stripe’s own privacy terms also apply to its processing. Hosting, email delivery, inference runtime, and analytics providers may process data to provide their functions. Exact provider locations, subprocessors, and retention schedules are not fully documented in this repository and are listed as owner follow-up below.

Use, storage, and retention

Data is used to authenticate customers, administer package access and bookings, process payments, provide support, prevent abuse, secure the API, troubleshoot incidents, and meet legal obligations. Operational records are retained as needed for those purposes. Specific retention periods have not yet been formally established for each data category; do not interpret this statement as a fixed retention schedule.

Cookies and analytics choice

Essential authentication/security cookies support requested account features. Optional analytics tags are not loaded before consent. If you allow analytics, GTM container GTM-PM54VFK8 loads the existing GA4 tag; the site does not separately install gtag.js. You can reject analytics or reopen Cookie settings from the footer. UTM attribution is stored only after analytics consent and contains campaign parameters, not account identifiers.

Rights and requests

Depending on applicable law, you may have rights to access, correct, delete, restrict, or object to certain processing. Contact [email protected] with a privacy request. We may need to verify account ownership before acting. Applicable law and response deadlines depend on facts that must be confirmed for the seller.

Security and updates

We use access controls, authenticated sessions, API-key handling, payment-provider verification, and operational security measures appropriate to the service. No online system can be guaranteed completely secure. We may update this policy; the revised date will be shown above.

Seller: individual seller in Thailand, operating publicly as CodeUnlim. Contact: [email protected] · +66 85 698 0824 · WhatsApp +66 85 698 0824 · Telegram contact number +66 85 698 0824 (no public username/link supplied).