WirefoldBack to Wirefold

Your work. Your information.

Privacy policy

Effective October 31, 2026

This policy explains how Wirefold handles information on wirefold.app and in its desktop coding workbench. Wirefold is operated by Jesus Mendoza. For privacy questions or requests, contact contact@wirefold.app.

Account information

When you create or use an account, our hosted service stores your name, email address, verification status, account identifiers and timestamps. Email/password accounts store a password hash, not your plaintext password. We also process session credentials, expiration times, browser or device information, IP addresses where available, and abuse-prevention records.

We use this information to sign you in, protect and manage your account, verify your email, reset your password, and support account access from the desktop app. Signing in does not start a coding Run or apply project changes.

Google sign-in

If you choose Google sign-in, Wirefold requests only the basic identity scopes: email, profile and OpenID. Google provides your account identifier, name, email address, email-verification status and, when available, profile picture. Our authentication service may store the associated OAuth tokens; stored OAuth tokens are encrypted.

We use Google information to authenticate you and manage your Wirefold account. We do not request access to Gmail messages, Google Drive files, contacts or calendars. Google sign-in information is not used for advertising or AI model training, and account session credentials are not sent as coding-model context.

Wirefold’s use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements. You can unlink Google in account settings when another usable sign-in method remains, or revoke Wirefold’s access through your Google Account. Revocation does not itself delete your Wirefold account.

Local projects and model providers

Repositories, session sandboxes, contracts, conversations and execution artifacts are managed locally on your computer. The hosted account service does not store your repositories, Review snapshots or coding-provider API keys.

Local-first does not mean local-only processing. Your chosen model provider receives the prompts, code and tool results included in task context. Screenshots, page observations, selected field values, logs and other captured application data can contain private information. That data can be saved in local artifacts and transmitted when included in model context. Wirefold does not automatically scan or redact application data or mask screenshots.

Choose the projects, connected services, credentials and data that are appropriate for your task. A sandbox isolates source changes; it does not isolate every connected database or external effect. Your selected provider’s privacy, processing and retention terms apply to the context it receives. Wirefold does not promise that provider copies are ephemeral.

Optional model balance

Wirefold balance is in testing. Live top-ups are unavailable. Data-use disclosure version: wirefold-credit-data-2026-10-22.

Your Run context travels from this Mac through Vercel AI Gateway to the model provider. It can include prompts, code, screenshots and tool results. Wirefold's account service does not receive this context. Balance models require zero data retention. If a compliant route is unavailable, the request stops. Usage and billing records are retained. You accept this data use in Settings before enabling balance-funded models. BYOK keeps using the provider you choose and that provider’s terms.

Vercel describes its gateway as deleting request content after completion. Wirefold requests zero data retention on every balance-funded call and offers only its certified model catalog. The gateway restricts those calls to providers covered by its retention agreements. See Vercel’s zero data retention policy. Local Run history and usage and billing metadata remain subject to their own retention rules.

The app records Run tokens and actual gateway cost locally. Wirefold’s billing service stores gateway key identifiers, cumulative spend, paid credit lots, expiry dates, terms acceptance and payment references to maintain the balance. It delivers a key to the Mac once; the key is encrypted in local protected storage and is not saved in the hosted database. Stripe Checkout collects your billing address to calculate tax and saves it to your Stripe customer record. It is not stored in the credit ledger.

Anonymous usage

The desktop app can send anonymous usage events to Wirefold. This is off until you turn it on in the app. You can change that choice in Settings at any time. While it is off, the app does not send these events and does not keep them to send later.

If you turn it on, the app sends batches over HTTPS. Each event is one of: app opened, project connected, element selected, run started, run finished, diff reviewed, apply done, apply discarded, or error shown. A finished run includes whether it ended ok or with an error, and how many milliseconds it took. An error shown event includes a category: run, apply, review, project, preview, account, or provider. It does not include the error message.

Every event includes a random install id, the app version, the operating system version, the CPU architecture, and the time the app recorded the event. On a Mac, the operating system version is the macOS version. An event does not include your code, file paths, file contents, prompts, model output, project names, URLs, email addresses, or API keys.

You can reset the install id in Settings. Resetting replaces that id. Events the server has already accepted stay stored. The website receives the batches on Vercel and stores accepted events in their own table in the hosted database on Railway. That table stores the fields above and the time the server received the batch. It does not store your account, email address, or IP address. Hosting logs may still include an IP address for the request, as they can for other requests to this site. A failed send does not change how the app runs. Events still waiting when you quit the app are dropped.

Service providers and sharing

Vercel hosts the website and account APIs. Railway hosts the account database. Resend processes recipients, subjects and message content for account verification and password-reset emails, as well as delivery information. Cloudflare manages domain DNS and forwards messages sent to our public contact address to the operator’s inbox. We process your email address and the information you include to respond to support and privacy requests. Google processes the sign-in flow when you choose it and receives forwarded contact emails through Gmail. Your selected coding-model provider processes the task context described above.

Stripe processes subscription and credit checkout, payment methods, tax calculation, invoices and billing management under its privacy policy. Wirefold stores billing associations, provider identifiers, subscription eligibility, timestamps and bounded event-routing records to confirm access and recover billing operations. We do not store card details or raw payment-event bodies. Completed webhook routing receipts are retained for 90 days; unresolved records remain available for recovery. Required billing records can remain after account deletion.

These providers process information to deliver their respective services and may process it in countries other than yours. We may also disclose information when required by law or when necessary to address fraud, protect account security or respond to your request. We do not sell Google sign-in information or use it for advertising.

Cookies, logs and email

Authentication uses secure cookies and related session records to keep you signed in and protect login flows. Browser sessions expire after seven days without automatic renewal. Verification and password-reset links expire after 30 minutes. Blocking necessary cookies can prevent sign-in.

Hosting services may process technical request information, such as IP address, browser information, requested page, timestamps and errors, to operate and protect the service. Wirefold’s account emails do not enable Resend open or click tracking. Account recovery links and session credentials should be kept private.

Retention and security

We retain account information while it is needed to provide your account and address security, support or legal requirements. Sessions and recovery credentials stop being usable when they expire or are revoked; expiration is not a promise that every associated database record, provider log or backup is immediately erased. Local project records remain on your computer until you remove them.

We use HTTPS, certificate-verified database connections, password hashing, encrypted stored OAuth tokens and restricted server credentials. No storage or transmission method is completely secure.

Your choices and requests

You can sign out, revoke other sessions, manage linked login methods and delete your hosted account from your account. Deletion requires recent sign-in and explicit confirmation. We cancel recurring Stripe subscriptions before removing login access, retain required billing records, and leave local projects and sandboxes untouched. If a cancellation or payment is unresolved, your account stays available while we resolve billing. For access, correction or deletion assistance, email contact@wirefold.app. We may need to verify your identity before acting. We handle requests subject to applicable law and any records that must be retained for security or legal obligations.

Deleting a hosted account does not delete project files, sandboxes or artifacts on your computer, or copies already held by your selected model provider. Direct requests about that provider’s copies to the provider.

Changes to this policy

We will update this page and its effective date when our practices change. We will provide an additional notice or obtain consent where required before using information for a materially different purpose. New paid services or additional hosted AI processing require their own disclosures before activation.