Account
Verification or recovery failed
Use the application’s current resend or recovery action. Do not share a verification link, token, password, or session with support.
Return to sign inProofStrike Help
Understand the state. Take the safe next step.
Start with the exact screen message and record. If the application cannot offer a safe recovery, use support without sending sensitive evidence through a public channel.
Discovery
A scan failed or returned nothing
Read the run state and checked scope. Retry only when the application offers it. Failure is not “no copies”; zero results are not universal clearance.
Understand DiscoveryFindings
The media or decision changed
Refresh the authoritative Finding. Missing media stays unavailable; a stale decision should not be silently repeated.
Understand FindingsEnforcement
A Case or route is blocked
Use only the blocker and recovery shown for that exact Case. Do not guess a recipient or treat preparation as Send.
Understand EnforcementMonitoring
A source could not be checked
A source failure is unknown coverage, not proof that content disappeared. Keep the failed check visible and follow the offered recovery.
Understand MonitoringBilling
A limit or payment state is unclear
Do not repeat a consequential action blindly. Public plan quantities and refund terms are not yet approved; contact support for the controlled pilot.
See pricing statusSupport boundary
Send the problem, not the private record.
Email the outcome you need and the non-sensitive screen state. Do not send passwords, access tokens, payment details, copied-content URLs, recipient addresses, private media, or Case evidence.
Contact ProofStrikePlain-language glossary
The words that keep the workflow honest.
- Original
- The authorized work that anchors discovery, evidence, and later decisions.
- Candidate
- A possible machine observation that has not yet become a qualified customer-visible Finding.
- Finding
- A scoped possible copy presented for creator review. It is not an infringement ruling.
- Case
- The canonical record that owns governed enforcement continuation, route, package, Send, and outcome history.
- Route Truth
- A sourced and versioned determination of a supportable recipient route, including trust state and limits.
- Attestation
- The creator’s required declarations bound to a package. Attestation is not Send.
- Monitoring
- A stateful watch process whose configured, admitted, active, checked, and failed states remain distinct.
- Recurrence
- A newly observed possible copy after earlier history. It becomes a new decision, never an automatic resend.
Common questions
Answers without hidden promises.
Does my profile name get searched?
No. A display label is not an implicit identity-search query. Only an explicitly selected and supported alias may become a search input.
Does a Finding prove infringement?
No. A Finding is a possible copy for review. Similarity and identity leads are not legal conclusions.
Does READY mean sent?
No. READY means a package may be eligible for notice review. Attestation and explicit Send remain separate.
Does accepted mean removed?
No. Provider acceptance, delivery, reported removal, and verified removal are separate states.
Is monitoring continuous everywhere?
No universal 24/7 promise is approved. The application must show actual admitted scope, cadence, checks, and failures.