Name, email, company or project details, URLs, factual claims, verification context, deadlines, support messages, and other information you intentionally submit.
Private information
stays on the private path.
This policy describes the information ProofTTL handles when you use the website, customer account, verification services, and related product surfaces.
ProofTTL receives payment status and transaction identifiers needed to connect a payment to the scoped request, not your raw full card number through its audit forms.
Unfinished audit intake state may be saved in browser storage so signing in does not erase work. Clearing site data removes locally stored values.
Only for operating, protecting, and improving the service.
Authenticate users and protect customer-only product surfaces.
Review, scope, perform, deliver, and support verification requests.
Connect audit, payment, fulfillment, and delivery state to the correct account.
Prevent fraud, abuse, unauthorized access, and investigate incidents.
Measure failures, debug product behavior, and improve ProofTTL.
Retain or process records where reasonably necessary to comply with applicable requirements.
Infrastructure providers process data only where the product needs them.
Depending on the feature used, information may pass through providers supporting hosting, runtime infrastructure, authentication, payment processing, source verification, or sign-in.
Hosting, edge/runtime, and related delivery infrastructure.
Payment processing for recurring monitoring subscriptions, accepted Fact Audits, and support of any legacy Rapid payments.
Providers such as GitHub, Google, or Discord process sign-in under their own terms and policies.
Transactional payment and intake notifications may be sent through Resend, which processes recipient email addresses, notification contents, and delivery metadata. Rapid Claim Check intake replies and support correspondence sent to ProofTTL.Support@gmail.com are processed through Google Gmail. Email may contain your address, submitted claim text, source context, and support messages. Submit only public, redacted, or de-identified material for the Rapid Claim Check.
Optional marketing tracking is paused.
The website shell does not load the previously used Metricool marketing tracker in this source version. Infrastructure providers may still handle ordinary hosting and security logs. Any future third-party marketing tracking must be accurately described here, with the required notice and consent or opt-out controls for applicable jurisdictions before activation. Sales correspondence may be handled through Gmail; requests to stop marketing should be sent to proofttl@gmail.com and will be recorded to prevent repeat outreach.
Operational records exist because the service has to be accountable.
ProofTTL may retain security, request, payment-state, verification, and operational records as reasonably necessary to provide the service, protect accounts, investigate abuse, preserve audit history, resolve disputes, or satisfy legal requirements.
Do not submit
Passwords, secret keys, auth tokens, or full payment-card details.
Never place credentials, private keys, authentication secrets, or raw full payment-card data into claim text, audit context, or support messages.
You control local state and account access.
You can sign out of your ProofTTL account at any time.
Browser-saved drafts and site state can be removed through your browser.
Email ProofTTL.Support@gmail.com for correction or deletion requests. Some records may need to be retained for security, contractual, payment, or legal reasons.
ProofTTL does not currently load third-party advertising on the public product or documentation experience.
No internet service can promise absolute security. ProofTTL uses access controls, server-side credentials, authenticated customer routes, and other safeguards intended to reduce risk.