Privacy policy

Information used by the service

• Account information: your name, email address, account identifier, authentication records, profile information, and sessions used to sign in.
• Project content: company and office information, logos, addresses, phone numbers, team membership and roles, permissions, drawings, punch items, statuses, reports, comments, photos, and other files you provide.
• Billing information: billing addresses, subscription, customer, payment-status, and transaction references. Payment-card entry is handled by the payment provider.
• Technical information: connection and service logs, IP addresses, app-installation and device/browser identifiers, checkout interactions, and error diagnostics. Support correspondence may include information you choose to send.
• Collaboration safety: the version and time of terms acceptance. Content reports include your account ID and email, project and reported content or member identifiers, short text excerpts, a selected reason, and your explanation. Reports are forwarded privately to the support address above through our email-delivery service.
• Personal blocking: account identifiers for the member pair, each member's block choice, originating project identifiers, and revision counters used to enforce contact restrictions. Separate operation receipts contain the acting account identifier, hashed operation and request references, and the time of the action. These block records do not contain email addresses, session tokens or comment text.

How information is used

We use this information to authenticate users, operate projects and collaboration, enforce permissions, plan limits and collaboration terms, process subscriptions, generate reports, deliver requested messages, troubleshoot problems, protect the service, and handle content reports, support and privacy requests.

Personal blocks apply across projects to comments and new direct invitations, shares and assignments between the accounts. They do not remove team membership, existing assignments or shared construction records. Each person controls their own block; unblocking does not override the other person's choice. Selected changed shared text is screened for prohibited language on our backend without sending it to an additional moderation provider.

The website uses an essential session cookie to keep you signed in. Account deletion uses a separate encrypted, HttpOnly recovery cookie so you can check or continue the same operation after sign-out. This cookie lasts 30 days after preparation. The apps can store project content and pending work on your device so that supported features remain available offline.

Project sharing and service providers

Project access depends on the permissions assigned by its owner or administrator. People with access can see information shared with their project, and permitted users can download reports. Only upload information you are authorized to share.

Service providers process information needed for their functions. These include AWS for application and data hosting, Vercel for the website, Stripe for billing, and email-delivery services for account, invitation, and report messages.

Vercel receives hosting request metadata such as IP addresses, approximate city/country, usage information and diagnostics. Vercel uses applicable service metadata, and Twilio SendGrid, our email-delivery provider, uses applicable communications metadata and message data, for their own security, abuse prevention and service improvement. See Vercel's privacy notice and Twilio SendGrid's data-processing terms.

We send Stripe your name, email and account ID for billing, and use billing-address and transaction data to manage subscriptions. Stripe Checkout uses cookies, device/session identifiers and checkout interactions for payment functionality, fraud prevention and performance analytics. See Stripe's privacy information.

If Google Play alternative billing is enabled and used in the app, we send Google transaction identifiers and reporting tokens, amounts, tax, transaction times and tax-country information to meet its transaction-reporting requirements, including applicable renewals and refunds.

When you use AI text formatting, the selected text is sent to OpenAI for that request. Device speech-recognition services process voice input when used. Weather assistance may use an IP-derived location and third-party location or weather services. Existing reports can retain approximate weather location, which is sent back to the service when a report is edited. Availability and permissions depend on the app version and device.

Camera, photo-library, microphone, and speech permissions support the features you choose to use. You can manage device permissions in your operating-system settings.

Retention and deletion

Information remains in the service while it is needed to operate your account and projects. Signing out, uninstalling the app, or cancelling a subscription does not by itself delete account or project data.

Your active block choice remains until you unblock or account deletion removes it. Unblocking does not erase stored member-pair and originating-project references, revision counters or prior operation receipts. These records have no time-based expiry. Completed account deletion removes member-pair records involving your account, your account's safety revision record and your own operation receipts; it does not delete shared project records.

Database content-report records are scheduled to expire 30 days after creation, and reporting-rate records 48 hours after their latest recorded event. Report evidence is removed from the database when the delivery outcome is successfully recorded, including an unconfirmed outcome; if that recording fails, evidence may remain until expiry. Resolved report and support emails are retained for 12 months. A sent receipt means the email service accepted the message, not that support has reviewed or resolved it. Database expiry and account deletion do not recall email copies.

Archived projects are retained for 90 days from archiving, then their project records and exclusive attachments are removed. Restoring a project to Current before expiry stops that countdown. Existing archives receive a full 90-day window when this policy takes effect. Shared attachments, files whose references cannot be safely resolved, backups and limited project-usage records may remain. Archiving or expiry does not restore your annual project allowance.

Visit account deletion to delete your account directly from Profile when available, or check a saved deletion after sign-out. Current-password verification and explicit confirmation are required. Resolve owned projects and pending offline changes first. Billing safety checks can block admission. A saved operation is not confirmation that deletion has finished; only the service's deleted status confirms completion. Once admitted, deletion cannot be cancelled.

Account deletion removes credentials, private profile and account settings, unshared business profiles, and sign-in sessions. A minimal non-login "Deleted member" identity remains so existing shared authorship links stay intact. Shared project content, including your authored items, reports and comments, and shared business profiles and logos are retained rather than removed from collaborators' work.

Files are erased only when ownership and the absence of retained references can be verified. Shared files, legacy files without verified ownership, and files with uncertain references may remain. Historical uploads without ownership records cannot all be inventoried. Invitation and access history, device identifiers, minimal security and recovery records, and records needed for dispute handling or legal obligations may also remain. Contact our privacy address about retained personal information.

PDFs, email attachments, and other copies already downloaded or held by recipients are outside the service's control and are not recalled by account deletion. Device exports and provider backup copies may also require separate handling.

Your choices and requests

You can review available account settings after signing in and ask us to access, correct, or delete your personal information at info@pro-punch.co. We may need to verify your identity before acting. Do not send your password, payment-card details, or authentication tokens by email.

Project access changes are managed by the project owner or administrator. Billing changes and account deletion are separate actions; check the status of both when ending use of the service.

Policy changes

We will update this page when this policy changes. The date above identifies the current version. Contact Pro-Punch with questions about this policy or the handling of your information.