List up to five factual claims, where you plan to use them, and any relevant public source links. Remove personal details and confidential material.
Get the right help.
Keep private details private.
ProofTTL routes customer, payment, and account questions through private product flows. Public channels are reserved for reproducible website defects that can be described without exposing customer information.
Existing Rapid purchase support.
Rapid is retired for new purchases. Do not pay through old Rapid links. For a separate human Fact Audit, request scope review and wait for reviewer assignment and a written deadline before any payment. If you already paid, contact support to confirm the next step for your up to five public, redacted, or de-identified claims. Use the email address you entered at Stripe checkout; a ProofTTL account is not required.
Check your inbox and spam folder for the ProofTTL intake message. Send your claims and context in that thread.
Email ProofTTL.Support@gmail.com from the address used at checkout. Include your purchase date and public or redacted claims. Do not send card details, passwords, or confidential files. If you already have an intake thread, reply there.
Legacy Rapid Claim Check support
Rapid is retired for new orders. If you previously paid, contact ProofTTL support using your original purchase email address; do not send new payments.
Existing Fact Audit
Check ownership, payment, fulfillment, and delivery state in the signed-in audit status flow.
Before you buy
Review the method and scope before using the audit control in the header.
Account or security
Use the private account path first. Do not place cookies, tokens, identifiers, or private customer material in public channels.
Public website bug
Use GitHub only for reproducible public-site defects after removing secrets and customer information.
Customer support should not create a second security problem.
Use the private audit and account flows for anything connected to a real customer, payment, or verification request.
Review request state, payment readiness, fulfillment, and delivery without exposing the request publicly.
No card is required at intake. Stripe checkout is created only after the Fact Audit scope is confirmed.
If sign-in is required, ProofTTL routes you through the account flow and back to the private customer surface.
Never post publicly
Card details, session cookies, auth tokens, private claims, or customer documents.
A public bug report should contain only the minimum reproduction needed to explain a public website defect. Remove identifiers, screenshots with customer data, payment references, and private source material before posting.
Start where the problem actually lives.
For a legacy Rapid Claim Check, reply in your ProofTTL intake email thread. For a full Fact Audit, open the private audit status page.
Use the single audit control in the top-right header after reviewing scope.
Review the Trust Center and use the signed-in account flow.
Use GitHub only after stripping all private information.
Need customer help now?
Email support ↗Talk to ProofTTL Support.
For legacy Rapid support, Fact Audit questions, account access, and billing or cancellation requests, contact ProofTTL.Support@gmail.com. No ProofTTL login is required to email us.