Everything you need to understand before sending your first proof.
Still have a question? Contact us and tell us about your workflow.
Using Proof Approve
No. The client uses the private proof link from the email and can review and respond without registering.
The current application accepts PDF, PNG, JPG, and JPEG proof files, subject to the configured upload size limit.
A client can view the delivered file in the browser. Browser behavior may also allow saving or printing, so subscribers should avoid uploading anything the intended client should not possess.
Yes. You can resend the existing active link when the client needs a reminder.
Yes. Revoking the link prevents further access through that proof token.
The decision, typed signature, notes, time, and audit event are stored with the proof, and the subscriber receives an email notification.
Notes are optional for approval but required when a client denies a proof so the shop receives usable revision direction.
The current workflow records the first submitted response as the decision. The shop can create and send a revised proof when another approval is needed.
Plans and billing
A send is counted when a new proof request is emailed to a client.
Monthly usage is tracked by calendar month in the current application.
Yes. Select the plan that fits now and move to a higher-capacity plan as your proof volume grows.
No. Only the business using Proof Approve subscribes. Clients do not pay to view or respond.
The proposed plans are monthly subscriptions. Annual options may also be offered with a discount.
Security and records
The current workflow uses long, randomized private links rather than a separate client password. A subscriber can revoke the link.
Proof Approve records the typed name and surrounding audit information, but legal requirements vary. Businesses should use agreements and legal guidance appropriate to their jurisdiction and transactions.
The application can record events such as creation, sending, opening, resending, approval, denial, and revocation, along with timestamps and technical context.
Retention depends on the plan and the cleanup policy configured for the production service.