StealthBypass
Privacy Policy
Last updated: September 20, 2026
StealthBypass processes text you submit so we can humanize it, score before/after AI detection, enforce quotas, prevent abuse, improve product quality, and understand conversion funnels.
Transformation Data
By default, we may store original text, transformed text, provider/model details, token and character counts, duration, detector scores, text category, language, reading metrics, session attribution, referrer, UTM data, device/browser details, and coarse Vercel-provided country/city.
Raw Text Retention
Raw original and transformed text is purged after 30 days by default. Detector scores, hashes, lengths, classifications, and aggregate metadata may be retained for analytics and service improvement.
You can disable raw text retention in account settings. When disabled, future transformations store only hashes, lengths, classification, metrics, detector scores, and operational metadata, and existing retained raw text is purged.
User Interaction Tracking
We record product events such as transform, copy, regenerate, edit, download, share, feedback, scroll depth, and time on result. Browsers cannot reliably tell us whether copied text was pasted into another app, so any paste-out signal is best-effort and based on explicit copy intent.
Advertising Measurement and Cookies
With your permission, we load the Google tag and use Google Ads measurement cookies to understand whether an advertisement led to a successful transformation, signup, checkout, or purchase. We may preserve campaign parameters and Google click identifiers with the related account and checkout so those outcomes can be attributed correctly.
Google advertising storage is denied by default. You can decline optional analytics without losing access to the product, and you can reopen Cookie settings at any time to change your choice.
Deletion Rights
You can request account deletion from the product. Deletion removes user-scoped transformations, usage logs, sessions, events, chats, and account records, then deletes the authentication user.
Questions? Signed-in users can contact support through the Feedback & Contact form. You can also return to the home page.