Effective August 3, 2026

Your Builder artwork stays in your browser.

The public Theme Builder and Pet Studio have no account requirement and never send the wallpaper or spritesheet selected there to the server. Community reactions store only an anonymous functional token and aggregate likes.

Native iOS app

The native iOS app is local/offline. PhotosPicker input is processed transiently on the device. Save Project stores project settings locally in Application Support, along with a source-theme label, and does not store the selected photo. The local Project Library can list, open, and delete those on-device settings records. Opening a saved project restores settings, not a photo. The library is offline and is not live compatibility verification. Recipe export and saved projects contain settings and metadata only, not image bytes. The native iOS app has no account, sign-in, subscription, IAP, analytics, or network client. Optional website account, subscription, and payment processing described on this page are a separate website service and are not part of the native iOS app.

Builder images

Images selected in the public Builder are read with browser Object URL and Canvas APIs. The Builder does not transmit or store them and does not use them to train models. Closing or reloading the page releases the in-memory Object URL.

Theme suggestions and optional Grok proposals

The free quick preset suggestion in the Builder runs only in your browser: it recognizes a limited set of supported words and creates an editable review. If you separately choose a paid Grok theme proposal, only the text you enter for that request is sent to Grok through our owned gateway. The Builder image, preview, and exported files are not sent. You can check a successful validated proposal for 24 hours; after that it is no longer available and is cleaned up when our system next processes it. We keep the necessary account and credit records to handle charges and refunds. We do not make claims about Grok's own retention or training practices. Generation and applying a proposal are separate actions.

Palette Bridge extension

CodexTheme Palette Bridge scans visible computed colors, derives four color roles, and lets you edit swatches and contrast locally in the browser. Only after you choose Open in CodexTheme Builder does it navigate to this first-party Builder with a settings-only URL containing the four current role colors and fixed theme settings. That navigation may enter normal server or CDN request logs. It does not include the scanned page URL, text, images, markup, form values, identifiers, or raw color-count list. Choosing Copy CSS or Copy JSON writes only the current four color roles to the system clipboard. Closing the popup clears its palette and edits, but copied data may remain in your system clipboard or clipboard history until you replace or clear it. If clipboard access is blocked, the extension shows the same text for manual copying. This disclosure describes the extension handoff; the rest of this policy describes this site's normal request handling.

Pet Studio files

Spritesheets and pet.json files selected in Pet Studio are decoded, previewed, validated and packaged in the browser. They are not transmitted to this site, or used to train a model. A user can separately choose to email a public source link and review manifest to the community address.

Exports

Wallpapers and recipe files are generated locally and downloaded directly by your browser. The JSON recipe contains the values visible in the builder, its generation time and the site URL.

Analytics and regional suggestions

Codex Theme uses first-party, cookie-free aggregate analytics to count page views and product events such as opening the builder, accepting an image or exporting a recipe. It stores daily counters and allowlisted dimensions such as route, locale, Cloudflare's two-letter country code, source hostname, platform, format and built-in theme slug. It does not store IP addresses, User-Agent strings, session identifiers, wallpaper content, file names, user-entered theme names, API keys or full referrer URLs. The request-level country code can choose a broad marketplace region and, only after a minimum anonymous cohort exists, reorder themes from aggregate applies, favorites and downloads. It is never used for precise location, individual profiling or cross-site tracking; manual region choices stay in the browser. Global Privacy Control and Do Not Track signals disable analytics in the browser.

Likes and favorites

Favorites stay in this browser. A random browser token is used only to keep one community like per theme; the server stores a one-way hash of that token with the liked theme. It is not an account, is not joined to analytics, and does not store your IP address, email, wallpaper, or profile.

Community publishing

Creator files are packaged in the browser and are not uploaded by the public form. Email submissions and rights notices are processed by the relevant mail providers. Separately, operator-published community assets are stored so they can appear in the public catalog; access-control IPs are checked only at request time and are not written into theme or pet records.

Optional account

Google sign-in stores your account ID, name, email, profile image URL, session data, and AI-generation allowance history. Codex Theme takes no payments and does not process card or billing data. Earlier test-order records are kept in a private database only as required for accounting. These records are not joined to Builder images, local recipes, Codex conversations, browser history or project files.

Retention, deletion and your rights

Builder images and local favorites remain only in this browser until you clear them. Account, allowance, support, and security records are retained only as needed to provide the service, prevent abuse, meet tax, accounting, and legal obligations, and resolve support requests; they are then deleted, anonymized, or archived where law requires continued retention. Where applicable law provides these rights, you may request access, correction, deletion, restriction, portability, or an objection. Some transaction and security records may need to remain after account closure for legal, fraud-prevention, accounting, or dispute purposes.

Security and children

Codex Theme uses HTTPS, server-only credentials. No online service can guarantee absolute security. Account features are not intended for children under 13.

Data sales

Codex Theme does not sell user data.

External links

GitHub and other linked sites apply their own privacy policies. Review those policies before using external services.

Contact

For privacy or deletion requests, email hello@codextheme.tools.