Private AI search
Transparency Report
Relationship transparency tools, AI privacy safeguards, and what we never do
This report is designed to answer the trust questions directly: what relationship transparency tools mean at OopsBusted, how AI is used without crossing privacy boundaries, and why the target is not alerted during the workflow.
1,000+
monthly search intakes
Representative monthly volume across focused platform searches, broader bundles, and follow-up investigation requests.
0
target alerts
The workflow is built so the target is not notified as part of the search or proof-delivery process.
No account
linking required
Users are not asked to connect the target’s dating profiles or log into accounts to begin the route.
Reporting note
How to read these numbers
Figures below are rounded, representative operational snapshots. They are published to communicate relationship-transparency posture, privacy safeguards, and platform scale without exposing user-specific or target-specific information.
Plain-English data handling
What we store, what we do not store, and when a case can be cleared
This summary is written for buyers who want the operational answer quickly. It matches the privacy notice, the live privacy receipts, the privacy-controls hub, and the documented retention model.
What we store
Only the case details needed to run the workflow
OopsBusted keeps the inputs and case state needed to review the request, deliver proof, and handle support or payment issues.
- Search clues you choose to submit, such as name, age range, city, optional clue fields, and any image you upload.
- Order, payment, and result-package state needed to unlock evidence, handle refunds, and resolve disputes.
- Support or compliance records tied to an access, deletion, or operational review request.
What we do not store
No credentials, no live tracking, and no hidden expansion of scope
The workflow is designed to stay privacy-bounded rather than becoming a general surveillance product.
- No target account passwords, no login bypass, and no requirement to link dating-app accounts.
- No live location tracking, no device surveillance, and no public posting of the results package.
- No optional analytics or preference storage before consent, and no resale of search data to marketing lists.
How long it stays
Different data categories follow different windows
Retention is tied to operational category instead of one blanket purge promise.
- Temporary local fallback copies used for support or incident recovery can be retained for up to 30 days.
- Optional analytics events can be retained for up to 180 days, and only after analytics consent is granted.
- Orders, transactions, and delivered result packages can remain in operational systems for up to 365 days unless a dispute or legal hold requires longer handling.
When it can be cleared
Deletion depends on whether the case is still operationally active
Purging is possible, but it is not instant if the case still has an open operational reason to exist.
- Deletion and suppression requests can be started through the privacy-controls hub, while export or access questions can still go to the privacy team.
- An operational record may stay longer when there is a refund review, chargeback, abuse investigation, or legal hold in progress.
- Backups and recovery copies are kept only for the minimum window needed to restore service after a failure.
Commitments
What we commit to operationally
These are the policy commitments that matter most to users deciding whether the workflow is legitimate and private.
We do not alert the target
Searches are designed to remain private-first. The workflow does not send messages, notifications, or visible signals to the person being searched.
We keep required input narrow
The process prioritizes only the details that improve matching quality instead of asking for unnecessary account access, surveillance permissions, or invasive data collection.
We deliver proof privately
Results are packaged for the requester, not broadcast publicly, and are structured around screenshots and reviewable context.
We round reporting figures on purpose
Operational counts are shared at a representative level so the company can be transparent about scale without exposing sensitive usage patterns.
Process
How searches are handled from intake to proof
The search process is designed to protect the requester while avoiding target notification throughout the workflow.
Stage 1
Private intake
The search starts with the smallest set of useful inputs: usually a recent image and the most relevant platform clues.
Stage 2
Platform-aware matching
The workflow stays narrow or broad depending on the suspicion pattern, which helps reduce unnecessary noise.
Stage 3
Evidence review
Likely matches are returned with screenshots and supporting context so the user can evaluate them privately.
Stage 4
No target notification
At no point is the target contacted, pinged, or otherwise alerted by the OopsBusted workflow itself.
Next step
Use transparency as a filter, then choose the next proof step
If the privacy boundary and retention model look credible, move into the live intake or preview the proof package before you pay.
FAQ
Questions about privacy and reporting
These are the trust questions that matter most when users are deciding whether the workflow is legitimate.
01Do you alert the target when a search is run?
No. The workflow is built specifically to avoid notifying the target as part of the search, review, or proof-delivery process.
02Are the monthly search figures exact?
They are rounded representative figures. The goal is to be transparent about scale without exposing sensitive operational detail or customer-specific patterns.
03Do users need to link accounts before starting?
No. The route stays private-first and does not require linking the target’s accounts or logging into dating platforms before intake.
04How long do you keep intake data and results?
Retention depends on data category. Temporary local fallback copies can be kept for up to 30 days, optional analytics for up to 180 days after consent, and operational orders, transactions, or result packages for up to 365 days unless a refund dispute, chargeback, deletion review, or legal hold requires different handling.
Use the transparency report to validate the workflow, then keep moving
These pages work together to answer the biggest objections: how the technology works, whether real users find proof, how privacy is handled, and where the ethical boundary sits.
AI and Privacy in Romantic Relationships
See how AI trust tools should stay privacy-aware and why legitimacy depends on staying out of surveillance territory.
Privacy Risks on Dating Apps
Understand the actual privacy risks users face on dating platforms before they turn uncertainty into more invasive behavior.
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 notes, 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.
Security Protocol
Examine the technical safeguards, encryption standards, and data residency protocols.
Privacy Controls
Review retention windows, deletion boundaries, and the public request path in one control hub.
Ethics & Safety
Understand our operational boundaries and zero-tolerance policy for harassment.
Start Search
Move directly into the intake flow when you already have the strongest photo and platform clue ready.