Private AI search
Security Protocol
Tactical data safety and privacy engineering
This page details how OopsBusted handles sensitive investigation data. We treat every search as a high-stakes operation where data security is non-negotiable.
HTTPS
transport security
Production traffic is intended to run over HTTPS so intake data is not submitted in plain text.
30 / 180 / 365
day windows
Temporary fallback copies can be retained for up to 30 days, consented analytics for up to 180 days, and operational orders or result packages for up to 365 days unless a dispute or legal hold requires longer.
No account linking
user exposure
The workflow does not require you to connect your own dating-app account to start an intake.
Safeguards
Defense-in-depth protocols
Our security architecture is designed to protect both the requester and the integrity of the search result.
Transport Layer Security (TLS)
Production deployments should enforce HTTPS/TLS so search forms and support requests are not submitted 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 intended for internal operational use only and should not be exposed publicly or indexed.
Abuse Controls
Search, upload, and payment-start activity are screened for obvious spam, blocked-use patterns, repeated submission bursts, and Turnstile challenge requirements.
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.
Transparency
Data handling disclosures
Security here means controlled retention, restricted access, and documented abuse handling rather than pretending no operational records ever exist.
- We do not sell user data to third-party marketing lists.
- Users should 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.
- Access to stored search and support records should remain restricted to authorized personnel only.
Next step
Validate the controls, then move into proof
Use the control model as a filter. If the safeguards are credible enough, move into the live intake or review the sample proof package first.
Complete the trust profile
Security is one layer of the trust model. From here, compare the transparency posture, inspect proof packaging, and review the ethical boundary before you buy.
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.
Transparency Report
See representative monthly search volume and the safeguards that prevent the target from being alerted.
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.