Consent · Security · Transparency
How we handle this
This is a sensitive search, so here is exactly how we handle it: what we will and won't do, how your data is secured and how long we keep it, and the limits we hold ourselves to — all in one place.
Ethics & consent
What we will and won't do
We help people move from suspicion to clarity — not to harass, track, or access anything private. These are the lines we hold.
Zero Tolerance for Harassment
OopsBusted is for personal relationship verification. We do not support or tolerate the use of our tools for stalking or illegal harassment.
No Real-Time Tracking
Our technology is built for platform presence verification, not continuous real-time tracking, spyware behavior, or covert surveillance.
Asset Sovereignty
Users retain rights to their submitted content; we only use images for the duration of the matching workflow.
Reviewed visible capture only
Fresh capture workflows are limited to visible dating-app evidence. Contributor-assisted material must pass manual review before customer use or evidence reuse.
Permitted
Approved use
What the product is for.
- Verifying exclusivity in a committed relationship
- Validating profile activity after a breakup
- Confirming consistency in online dating behavior
- Requesting a fresh visible profile pass when the scope, privacy boundary, and review standard are clear
Prohibited
Zero-tolerance misuse
What we block and report.
- Targeting public figures for non-personal reasons
- Using results to facilitate physical stalking
- Attempting to bypass legal restraining orders
- Seeking hidden/private content, private messages, account credentials, account takeover, or notifications to them
Security & data
Technical safeguards
How your search data is protected in transit and at rest, and how little of it we keep.
Transport Layer Security (TLS)
Search forms and support requests are submitted over HTTPS/TLS, not in plain text.
Data Minimization
Forms request only the details needed to route a case, and the product tells users not to submit passwords, payment data, or unrelated sensitive information.
Access Restriction
Stored intake data is used for internal operations only — the product does not publish or index it.
Manual Check Boundary
Fresh visible capture can involve vetted human contributors or internal operators, but pending and rejected submissions are blocked from your results, exports, and AI summaries until a person approves them.
Abuse Controls
Search, upload, and payment-start activity are screened for obvious spam, blocked-use patterns, repeated submission bursts, and Turnstile challenge requirements.
Capture trust modules
The controls behind our manual checks
The practical controls behind our manual checks: evidence sources, contributor limits, status handling, refunds, and privacy boundaries.
Review-before-indexing
Customer evidence is reviewed before it can be reused
Review approval is the public trust boundary between raw capture and customer-facing evidence.
- Pending and rejected submissions stay blocked from your results, exports, and AI summaries until a person approves them.
- Manual review checks visible evidence quality, app/city fit, freshness, duplicate or tamper risk, and whether the packet is safe to show.
- Reusable evidence is promoted only after review approval, not just because a screenshot was uploaded.
Where evidence comes from
Reports distinguish where evidence came from
The trust model separates owned fleet, manual ops, contributor-assisted capture, and demand-triggered refreshes without exposing sensitive operational identities.
- Customer copy explains freshness and review status in plain language.
- We keep an internal record of where each screenshot came from so support and disputes stay traceable, without publishing contributor identity.
- The sample report shows confidence and uncertainty instead of treating a screenshot's source as a guarantee.
Contributor controls
Contributor-assisted capture has guardrails
When fresh coverage is needed, vetted human contributors or internal operators may collect visible dating-app evidence through controlled manual workflows. OopsBusted manually reviews every submission before customer use or evidence reuse.
- Contributor work is limited to visible profile evidence tied to controlled tasks.
- Contributors do not receive permission to access private messages, inboxes, passwords, hidden content, or account takeover paths.
- Review approval is required before customer use, evidence reuse, indexing, export, or payout.
SLA states
We keep priority-capture status easy to follow
Priority live capture is a fresh manual pass with visible status, not a guaranteed match.
- You always see one clear, current status for the add-on as it progresses.
- No-match and inconclusive outcomes remain possible even after a fresh pass.
- Support can explain your current status from the order and capture records.
Refund-pending handling
Missed-SLA refunds apply to the add-on boundary
We keep priority add-on SLA handling separate from your base report delivery.
- A missed priority live-capture SLA can trigger add-on refund review.
- The base report is not automatically refunded just because an optional add-on missed its SLA.
- Refund-pending status is visible so you know support is reviewing it.
Privacy boundaries
The product does not cross hidden-access lines
We state what we do not do as plainly as what we deliver.
- No notifications to them, direct outreach, bait-profile contact, private-message access, inbox access, password use, or account takeover.
- The workflow is evidence review, not real-time tracking, spyware, or hidden surveillance.
- Treat results as reviewed signals, not automatic legal conclusions.
Decide with the full picture
If you're weighing whether this is the right tool, these pages cover pricing, sample proof, and how the search actually works.
Priority Dating App Capture
Understand the optional priority live-capture add-on, fresh manual pass scope, SLA limits, and no-guarantee boundary.
Fresh Manual Profile Search
Use this when a no-match or inconclusive result still leaves a clear app/city decision gap.
Reviewed Dating App Evidence
See how screenshots, review status, confidence, and evidence sources work together before a result should be trusted.
Dating App City Coverage
Review why app/city scope affects no-match outcomes and when broader coverage or priority capture makes sense.
Start private search
Move into the live intake once the route, trust threshold, and evidence standard are clear enough to act.
Pricing
Compare one-time app checks, broader bundles, and proof-related add-ons before checkout.
Compare Alternatives
Use the comparison hub when the buyer still needs route-choice or competitor context before purchasing.
Sample Proof Package
Preview screenshots, confidence ratings, and no-match handling before money changes hands.
Before you buy
Resolve the last objections around scam risk, recurring billing, no-match outcomes, accuracy, and data removal before checkout.
Verification Hub
Narrow catfish, romance-scam, AI-image, and before-confrontation questions into the right proof route.
Privacy Controls
Review retention windows, deletion boundaries, correction review, and the public request path in one control hub.