Privacy controls
Delete, suppress, correct, or opt out without guessing which policy page to read first
This hub turns the retention windows, deletion boundaries, correction review, and request paths into one public control surface. Use it when the job is data control rather than search execution.
Default retention windows
These are defaults, not a promise that every case disappears instantly.
- 30 daystemporary fallback copiesLocal fallback copies used for support or incident recovery do not stay indefinitely and are cleared on the short window.
- 180 daysoptional analyticsAnalytics stay optional and follow a separate lifecycle from operational case records.
- 365 daysoperational case recordsOrders, transactions, and delivered result packages can stay longer because refunds, chargebacks, abuse review, or legal holds sometimes require it.
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.
Correct profile-subject context
Correction review is the self-service path when the issue is inaccurate OopsBusted-controlled profile context rather than deletion of the whole case.
- Best fit for profile subjects disputing a name, age, city, app, screenshot interpretation, or identity signal in OopsBusted records.
- Ops can preserve the request, review evidence, and record a correction or denial outcome without changing immutable reports silently.
- Correction review does not edit third-party dating-app profiles or guarantee removal from source platforms.
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.
Start a deletion, suppression, or correction 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.
Privacy-control questions answered
Use the surrounding trust pages for the full control picture
Privacy policy
Read the formal legal notice that defines the retention windows and user-rights language this hub is built from.
Read privacy policyTransparency report
See the public explanation of the no-alert workflow and why the product keeps privacy boundaries explicit.
Review transparencySecurity protocol
Review the transport, access, and abuse controls that sit underneath the privacy lifecycle.
Review securityExposure check
Use the self-audit lane when the question is visible profile exposure rather than case-data control.
Open exposure check