Ethics, security & transparency
Consent, privacy, and partner surveillance ethics for dating-app verification
OopsBusted exists to provide clarity, not covert surveillance. This document explains the consent and privacy boundary, the ethics of partner-monitoring queries, and the safety limits of the service.
What this is for — and what it is never for
If your reason is not on the left, this is not the right tool. Requests matching the right-hand list are refused.
Permitted use
- 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 use
- 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
We may reject, suspend, or terminate access where a request appears to violate these boundaries or applicable law. See Terms of Service.
Our commitments
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.
Security protocol
How the data is protected
Five layers, each one describing real behaviour rather than an aspiration.
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.
- We do not sell user data to third-party marketing lists.
- Do not submit passwords, payment card numbers, or unrelated third-party secrets through the forms.
- Operational retention windows are disclosed in-product and in the privacy notice so the live flow matches the documented data lifecycle.
- Our manual check does not include hidden/private-content access, private messages, inboxes, passwords, or account takeover.
Transparency report
Where evidence comes from, and what gates it
Review approval is the boundary between raw capture and anything you see in a report.
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.
Figures below are rounded, representative operational snapshots. They are published to communicate relationship-transparency approach, privacy safeguards, and platform scale without exposing user-specific or target-specific information.
Decide with the full picture
If you are weighing whether this is the right tool, these guides cover priority capture, manual searches, evidence review, and app-city coverage.
Priority Dating App Capture
Understand the optional priority live-capture add-on, fresh manual pass scope, SLA limits, and no-guarantee boundary.
Read priority guideFresh Manual Profile Search
Use this when a no-match or inconclusive result still leaves a clear app/city decision gap.
Read manual search guideReviewed Dating App Evidence
See how screenshots, review status, confidence, and evidence sources work together before a result should be trusted.
Read evidence guideDating App City Coverage
Review why app/city scope affects no-match outcomes and when broader coverage or priority capture makes sense.
Read coverage guide