Your project. Your privacy.

Last updated 16 October 2026

This notice explains the information used when you create an account, post an app request, talk to a developer, or contact PatchDispatch.

Accounts and marketplace data

Accounts store your name, email, password hash, session information, and chosen Builder or Developer role. Profiles may include a bio, skills, and GitHub link. Apps, published requests, screenshots, private conversations, and price proposals are stored to provide the marketplace.

Builders can manage their own apps. Signed-in developers can see open requests and their screenshots. Conversations and proposals are available only to the participants. Your account email is not included in marketplace listings. Repository links are shown only to the app owner and the developer whose proposal is accepted; sharing a link does not grant repository access.

What the contact form collects

Your name, email address, requested service, app or repository link if supplied, the tool you used, budget range, and your description. Please do not include credentials, private customer data, or other sensitive material.

Why we use it

To assess the request, contact you, prepare a scope or quote, and handle any work you agree to. Contact about the request is separate from marketing. Submitting the form does not subscribe you to a mailing list.

Where it goes

The deployed website is designed for Vercel and a configured Postgres provider such as Neon. The local preview uses a database on this machine. When delivery is configured, the contact form uses Resend to send your request to the PatchDispatch service inbox and an acknowledgement to you. Request details are not intentionally written to application logs. Infrastructure providers may process technical request information such as IP addresses and access logs.

When enabled, Cloudflare Turnstile checks form submissions for automated abuse and processes the technical information needed for that check. These providers may process information outside your country under their applicable terms and safeguards.

Resend also sends account verification and password reset emails when configured. Passwords are hashed by the authentication library; they are not included in project messages or notification emails.

Project access

Repository, database, and hosting access is arranged separately after assessment. You keep ownership. Access is limited to the agreed work and support period. We will agree any additional handling needed before accessing sensitive project information.

Retention and your choices

We aim to remove unsuccessful enquiries from the active service inbox within 90 days. Information relating to agreed work may be retained for delivery, support, accounting, and dispute handling. Provider backups and statutory records may follow different retention periods.

You can ask to access, correct, or delete your enquiry information by replying to the acknowledgement email or using the request form. Some records may need to be retained for an applicable obligation.

Cookies and tracking

This initial site does not include advertising trackers or a marketing analytics SDK. Essential session cookies keep you signed in. Infrastructure and abuse prevention services may use technical storage required to operate their services.