What the site collects and where it goes.

Forms and bots use the details you choose to provide

The quote form asks where you are starting, your business name, email address, and project notes. It can also accept a current website address, service area, and phone number. The current request handler uses those details to compose an email to admin@pixelforged.com. Your email is placed in the reply-to field so PixelForged can answer the request. Submitting the form does not subscribe you to marketing messages.

Design Bot accepts website questions and limited recent user messages needed for context. If you choose Send Conversation, your email address and up to twelve user and assistant messages are sent through the email feature. Website Draft Bot asks for business type, town or service area, business name, desired customer action, and visual direction. Draft revisions also send the current sanitized draft and your requested change.

Quote request

Business and contact details, project notes, and any optional website, service-area, or phone details you enter.

Design Bot

Your question and limited recent user messages. A transcript is emailed only when you request it.

Website Draft Bot

Five intake answers, a starting color, generated draft content, and revision instructions.

The application uses identifiers to keep features working

Interactive requests use a random signed session identifier. The browser receives it in a Secure, HttpOnly, SameSite=Lax cookie with a maximum age of thirty days. The application also creates keyed, pseudonymous values from coarse network information and from a verified email address. These values support rate limits, one-draft rules, verification, revision credits, and abuse prevention. They are not plain email addresses or plain IP addresses.

Website Draft Bot stores draft progress in localStorage when available and uses sessionStorage as a fallback. Saved state can include the five answers, generated HTML and CSS, palette, labeled stand-ins, summary, server signature, verification status, and remaining revision count. It does not save the verification email or six-digit code in that browser record. The Clear Saved Draft control removes the saved browser draft and resets the visible draft state.

Information supports the action you requested

Quote details are used to deliver and answer the request. Bot inputs are used to return an answer or create the rough draft you asked for. Email addresses are used to send a requested transcript, deliver a verification code, connect verified revision credits to a session, or let PixelForged reply to a quote request. Session and rate data keep the tools within their published limits and help prevent automated abuse.

Current form and verification flows contain no marketing opt-in. This page therefore does not treat a quote request, transcript request, or verification email as permission for unrelated promotional mail. It also does not claim that information is used for product training, customer profiling, or advertising. Website code does not establish what independent providers retain for their own security and operations.

Hosting, email, storage, and AI services process different parts

The current application uses Vercel for hosting and API execution, Upstash Redis for server-side session-related records, Resend for quote and bot email, Vercel AI Gateway for AI routing, Anthropic as the default model provider in code, and Google Fonts for font files. A runtime model setting can change the model used without changing the public page. External portfolio links lead to websites controlled by other parties.

Application source shows what PixelForged sends to these services, but it does not prove their production log settings, backup schedules, processing regions, contractual terms, or deletion behavior. Email content can remain with Resend and in sending or receiving mailboxes. AI prompts and outputs pass through the configured gateway and model provider. Do not submit information that should not be handled by those services.

Some records expire automatically and some do not

Current server code gives the signed session cookie and anonymous-draft session record a maximum life of thirty days. A coarse network allowance can last up to twenty-four hours. Verification codes expire after ten minutes. Verified email hashes and revision-credit records can last up to ninety days. Rate counters and short request locks have shorter technical expiries. Those periods do not describe provider logs, backups, or delivered email.

A saved localStorage draft has no separate calendar expiry. It can remain until you use Clear Saved Draft, clear site data in browser settings, the browser removes it, or the application rejects and removes invalid saved state. Clearing the session cookie may disconnect a restored draft from its prior signature, verification state, or revision credits. You can avoid these records by not using the interactive tools.

Use the tools without sending sensitive material

The server validates request shape and length, rate-limits public routes, signs session and draft data, sanitizes generated drafts, and returns public errors that avoid exposing internal provider details. Generated previews run in a sandboxed frame. These measures reduce risk, but ordinary email, browser storage, internet transmission, and third-party processing are not risk-free.

Do not send passwords, payment-card data, government identifiers, health information, private customer records, confidential contracts, or proprietary code through the quote form or bots. You can email admin@pixelforged.com with a privacy question. No identity-check process, deletion service, appeal route, regulator route, or response deadline is promised on this page.