Private AI search
Privacy controls
Delete, suppress, or opt out without guessing which policy page to read first
This hub turns the retention windows, deletion boundaries, and request paths into one public control surface. Use it when the job is data control rather than search execution.
30 days
temporary fallback copies
Local fallback copies used for support or incident recovery do not stay indefinitely and are cleared on the short window.
180 days
optional analytics
Analytics stay optional and follow a separate lifecycle from operational case records.
365 days
operational case records
Orders, transactions, and delivered result packages can stay longer because refunds, chargebacks, abuse review, or legal holds sometimes require it.
Control model
Choose the right privacy action for the job
This hub separates the three main control questions so users do not have to infer the right path from scattered trust, security, and policy pages.
Delete operational case data
Deletion is available when the requestor wants OopsBusted to clear the case record after the active business or legal reason to keep it has ended.
- Best fit for old search, order, or results packages tied to your own case history.
- Deletion can be delayed by refunds, chargebacks, abuse review, or legal-hold requirements.
- Deletion here applies to OopsBusted-controlled records, not to source-platform profiles on Tinder, Bumble, Hinge, or other third-party services.
Request suppression where appropriate
Suppression is the narrower path when the immediate need is to stop operational resurfacing or reuse before a full deletion decision is possible.
- Useful when the request is valid but a finance, support, or legal dependency still blocks immediate purge.
- Lets ops review whether the material can be removed from normal operational reuse while the case is being resolved.
- Does not overpromise removal from systems OopsBusted does not control.
Marketing opt-out stays separate
Promotional opt-out should not require a full compliance case. Marketing messages use unsubscribe controls, while transaction and case updates stay available when required.
- Use the unsubscribe link on marketing emails for the fastest opt-out path.
- Transaction receipts, privacy-request replies, and required operational notices can still be sent when needed.
- If the email channel itself is the problem, include that detail in the privacy request reason so the team can review it with the rest of the case context.
Public request path
Start a deletion or suppression review
Submit the request here and it will enter the same audited compliance queue the ops team already uses for workflow review, legal hold, and completion logs.
Deletion review
Use this when you want OopsBusted to clear case data after the operational record is no longer needed for payment, dispute, abuse, or legal obligations.
Suppression review
Use this when you want OopsBusted to stop operational reuse or resurfacing of case material where we control that behavior, even if third-party source platforms still exist.
What happens next
How a privacy-control request moves through review
The workflow matters because privacy trust breaks when users cannot tell whether a request vanishes into support or enters a real audited process.
Step 1
Submit the request
Choose deletion or suppression, identify the case, and explain what you want changed so the request enters the same audited compliance queue used by ops.
Step 2
Identity and scope review
The privacy team may need enough detail to confirm the request belongs to you or that you are authorized to make it.
Step 3
Operational hold check
Refunds, chargebacks, abuse review, or legal-hold requirements are checked before the case is cleared or suppressed.
Step 4
Close with a recorded outcome
The request is completed or denied with an explicit workflow log so privacy handling stays auditable instead of disappearing into general support notes.
FAQ
Privacy-control questions answered
These answers keep the request path realistic so the page promises what ops can actually fulfill.
01What is the difference between deletion and suppression?
Deletion is the full request to clear OopsBusted-controlled case data once no active business or legal dependency remains. Suppression is the narrower review path for stopping operational reuse or resurfacing where appropriate when immediate purge is not yet available.
02Can you remove a profile from Tinder, Bumble, or Hinge?
No. This control hub only covers records OopsBusted controls. It does not remove or edit source-platform profiles that still exist on third-party services.
03Why might deletion take longer than the headline retention window?
The retention windows are defaults, not a promise that every case disappears instantly. Payment disputes, abuse review, chargebacks, or legal holds can require a case to remain longer until the operational obligation is resolved.
04Do I need a separate request for marketing opt-out?
Usually no. Marketing opt-out should use the unsubscribe path on the email itself. The privacy-request form is for case-data deletion or suppression questions that need a reviewed compliance workflow.
Use the surrounding trust pages for the full control picture
The control story should line up across the legal notice, the trust pages, the self-audit lane, and the live search flow instead of sending users into disconnected explanations.
Privacy policy
Read the formal legal notice that defines the retention windows and user-rights language this hub is built from.
Transparency report
See the public explanation of the no-alert workflow and why the product keeps privacy boundaries explicit.
Security protocol
Review the transport, access, and abuse controls that sit underneath the privacy lifecycle.
Exposure check
Use the self-audit lane when the question is visible profile exposure rather than case-data control.