How SitePunch handles your information.

SitePunch is offered only to people located in the United States and supports only U.S. phone numbers. It is not offered to people located in the European Economic Area, United Kingdom, or Switzerland. Public informational pages may remain visible outside the United States.

SitePunch uses network-location and phone-number country signals to enforce these limits. Location signals can be inaccurate, so you may contact support if you believe access was blocked by mistake.

SitePunch is built and operated by Hawkee, an independent software studio, which is responsible for the data described in this policy. Privacy contact: [email protected].

• Phone numbers used for login and project access.
• Profile data you choose to add, such as your display name.
• If you choose to add one, an email address, whether it is confirmed, your email notification preferences, and your language preference.
• Project content, including punch list items, messages, uploaded photos, and timestamps. To diagnose upload problems, we retain limited technical details about the received file, such as its name, size, format, dimensions, image entropy, and a cryptographic fingerprint.
• Questions asked of the AI assistant (Ask AI), its answers, and a usage record of each request: who asked, the project and item, the question, and the size, cost, and timing of the request.
• App usage records from signed-in people: which pages and project items you open and when, and requests that fail with an error. They hold the page type and project and item identifiers, not what you type. We also keep each item's status history: who created it, marked it done, verified it, or rejected it, when, and the reason given for a rejection.
• Security and operational data such as one-time code records, emailed sign-in and confirmation link records, session records, administrator passkey public keys and usage metadata, invite token records, IP addresses associated with login requests, SMS logs, and records of which notification emails were sent.
• For confirmed U.S. visitors on selected public pages only: the page address, referrer, browser and device type, approximate location, and page-load timings, without cookies or identifiers stored in your browser.
• When an unexpected error occurs: the error type, a technical stack trace, a generalized route, the application release, and basic browser or system details needed to diagnose the failure.

A project owner can post a QR code that lets anyone report an issue without an account. If you send a report, we collect the photo, your description, and, if you choose to give them, a location and your name. We don't ask for a phone number or email. Photos go through the same processing as all others: they are resized and their metadata (such as GPS location) is removed.

To limit abuse we use Cloudflare Turnstile and store only a keyed hash derived from your network address, never the address itself. Report pages don't use analytics. If you give your name, your own browser remembers it for your next report; it stays on your device, and you can tap Forget to remove it. Only the project owner and collaborators see your report; they can accept it as a project item or dismiss it. Dismissed reports are deleted right away along with the photo, and reports nobody reviews are deleted after 30 days. An accepted report becomes part of the project and follows its retention. The QR code doesn't give you access to the project, and the report page doesn't send updates.

SitePunch uses a strictly necessary session cookie that lasts while you keep using SitePunch (up to one year), a 15-minute sign-in cookie when you request an emailed sign-in link so that opening it in the same browser signs you in directly, a 2-hour cookie when you scan a QR code to report an issue so that the report form can confirm the code without keeping it in the page address, and a language-preference cookie for up to one year when you select a language. These cookies support access, security, and a preference you requested.

SitePunch uses Cloudflare Web Analytics to count visits to the homepage, About, FAQ, and Field Notes. It loads only when Cloudflare confirms that a visitor is in the United States and the browser does not send a Global Privacy Control signal, and it does not load on login, contact, legal, account, dashboard, project, upload, or API routes. It sets no cookies, stores nothing in your browser, and does not create an identifier for you; Cloudflare gives SitePunch only aggregate reports of visits and page speed.

SitePunch does not track visitors across other websites over time and does not use advertising cookies or cross-site tracking tools. Because there is no common standard for browsers' Do Not Track signal, SitePunch does not respond to it; it honors Global Privacy Control instead, as described above.

If you try SitePunch without an account, your items and photos are kept only in your browser, on your device, and aren't sent to SitePunch unless you sign in to save them. They're removed from your browser when you save them or choose Start over, or the next time you open the trial after 7 days without using it.

SitePunch uses Sentry to detect unexpected failures on public pages and in the authenticated product. This monitoring is operational and is not used for advertising, profiling, or behavioral analytics.

The integration is configured not to send request or response bodies, cookies, headers, query parameters, user identity, database content, session replays, or local variables. Project, item, invite, and file identifiers, along with phone numbers, login codes, and token-like values, are generalized or removed before transmission.

Error reports are kept in Sentry for up to the event-retention period configured for SitePunch's account and no longer than reasonably needed to investigate, remediate, and prevent recurring failures. SitePunch may delete reports sooner; limited data may be kept longer only when required by Sentry's agreement or applicable law. Sentry's Data Processing Addendum describes Sentry's role and the safeguards that apply to service data.

A project's owner and collaborators can ask an AI assistant about an item. AI runs only when someone taps the AI button; SitePunch never sends project content to AI on its own. Contractors and view-only participants can't use it.

When someone asks, SitePunch sends Anthropic, the company behind the Claude AI models, the question and the item's context: the project's name and description and, if set, its city and state, building type, and year built; the item's title, description, location, and status; up to 8 of its photos; recent messages from both its shared discussion and its internal discussion; and any photo attached to the question. People are identified only by role, such as "Owner" or "Contractor A (plumber)", never by name, phone number, or email.

Under Anthropic's commercial terms, Anthropic does not use this content to train its models, and it deletes it within 30 days unless it is flagged as a possible violation of its usage policy, in which case it may keep it for up to 2 years. Anthropic's commercial terms

AI answers are saved in the item's Internal tab, which contractors and view-only participants can't see, unless someone on the team chooses to share an answer with everyone. SitePunch also keeps a usage record of each request to apply limits and manage costs. SitePunch administrators can review those records, including the question and answer, to manage costs and investigate misuse.

AI answers are automated suggestions and can be wrong. Confirm prices, permits, and code requirements with licensed professionals.

• To send one-time login codes, confirm a new phone number, and, if you added a confirmed email, send sign-in links you request.
• To send the project notification emails you choose to receive, and service emails such as confirming your address or a security notice when your phone number changes.
• To authenticate users, maintain sessions, and prevent abuse or fraud.
• To operate the project workflow, including sharing project data with authorized users.
• To answer questions a project's team asks the AI assistant, apply its usage limits, and manage its cost.
• To understand how SitePunch is used, find where people get stuck, keep an audit trail of project changes, and investigate problems. SitePunch administrators can review app usage records; they are not shown to other project participants.
• To maintain records, troubleshoot problems, and comply with legal obligations.

SitePunch may use service providers needed to operate the product, such as hosting, storage, and authentication vendors acting on behalf of this deployment.

Project data is also shared with the people who are given access to the same project. If you are granted access to a project, the owner and other authorized participants may see the information you add within that project.

Cloudflare supports delivery, security, and the public-page analytics described above; the hosting provider stores and operates the application; Twilio delivers SMS messages; Resend delivers email; Anthropic answers the AI assistance requests described above; and Sentry processes the limited technical error reports described above.

Messages and photos you add to a project, including in its shared discussion, may be included when the project's owner or a collaborator asks the AI assistant about an item.

Text messaging originator opt-in data and consent are not sold, rented, or shared for marketing or promotional purposes. They may be provided only to service providers that help deliver or support those messages, subject to their service obligations. The same applies to your email address: it is not sold, rented, or shared for marketing, and it is not shown to other project participants.

Login codes become invalid after 10 minutes and their records are deleted after 1 day. Emailed sign-in links work once, expire after 15 minutes, and their records are deleted after 1 day; email confirmation links expire after 24 hours. You stay signed in while you keep using SitePunch; a session ends after 30 days without use or one year in total, and expired session records are deleted after an additional 7 days. SMS logs and revoked invitations are deleted after 90 days. AI answers stay in the item's Internal tab until someone deletes them or the item is deleted. AI usage records are kept to manage costs and investigate misuse; the question in each record is removed after 90 days, or sooner when its answer, item, or project is deleted. App usage records are deleted after 90 days, or sooner when their item, project, or your account is deleted; an item's status history is kept as long as the item exists. Active account, access, and project records are kept while the service or project remains active and longer when needed for backups, disputes, or legal obligations. Phone numbers are encrypted in the database and masked in activity records. Backups of the database and of uploaded photos are kept for 30 days, so information you delete is gone from backups within 30 days.

Phone numbers are stored encrypted, and login codes and sessions are stored only as one-way hashes. Sign-in forms use Cloudflare Turnstile to block automated code requests. No system is perfectly secure. You should avoid uploading information you would not want shared with the people who have access to the project.

You can change your display name, phone number, email address, and notification preferences in Settings at any time.

Deleting a project: the owner can delete a project from its settings. This immediately removes the project and all of its items, photos, messages, invitations, and notifications for everyone.

Deleting your account: you can delete your account in Settings, under Profile. This immediately removes the projects you own (with everything in them), your phone number, email address, name, sessions, invitations, notifications, preferences, and the SMS log entries sent to your number. Items and messages you added to other people's projects are part of those owners' job records, so they stay in those projects, but they are shown as "Deleted user" and are no longer linked to your phone number, email address, or name.

Deleted information leaves our live systems right away and is removed from backups within 30 days as those copies expire. The Sentry error reports described above expire on their own retention schedule.

You may also request access to, correction of, or deletion of your information by emailing the privacy contact above. SitePunch may request enough information to verify your identity and may retain records when needed for security, legal compliance, or dispute resolution.

Adding an email address is optional. SitePunch only emails an address after you confirm it using the link we send.

Notification emails tell you about activity in your projects, such as new items, messages, items ready for review, and verified items. You can turn each type on or off in Settings, and every notification email includes a one-click link to unsubscribe from all of them. Some types are batched to limit how many emails you receive.

Some service emails are sent even when notifications are off, because you requested them or they protect your account: confirming your address, sign-in links you ask for, and a security notice when your phone number changes. SitePunch does not send marketing email.

SitePunch currently uses service-related SMS text messages only for login and to confirm a new phone number when you change the one on your account. These messages include one-time login codes requested during sign-in. Message frequency varies. You will receive up to one message per login request. Message and data rates may apply.

Reply STOP to opt out. Reply HELP for help or email [email protected]. Carriers are not liable for delayed or undelivered messages.

Customer care email: [email protected].

Support hours: Mon-Fri 9am-5pm ET.

Because this product relies on SMS for account access, revoking consent for these service-related texts or blocking them may prevent you from signing in to projects you have been granted access to, unless you have confirmed an email address for sign-in links.

Some U.S. states require businesses to provide privacy notices or consumer privacy rights. If a state privacy law applies to this deployment, SitePunch will handle requests in the manner required by that law.

SitePunch does not sell personal information or share it for cross-context behavioral advertising, as the California Consumer Privacy Act defines those terms, and has not done so in the past 12 months. SitePunch treats a Global Privacy Control signal as a request to opt out of sale and sharing and, as described above, does not load analytics for that browser.

This policy may be updated as the product changes or legal requirements change. The current version will be posted on this page with a revised effective date.