Privacy Policy

Last updated: 22 October 2026.

Who is responsible?

unslop, Germany. Contact: [email protected]. Contact the operator with privacy requests.

What we process and why

• Website delivery and security: connection information, IP addresses, request times and technical logs help deliver the site, prevent abuse and diagnose faults. Our basis is legitimate interests under Article 6(1)(f) GDPR.
• Accounts and purchases: email address, login verification, session identifiers, word balances, transactions and support correspondence are needed to provide the service and fulfil purchases (Article 6(1)(b)). Statutory accounting obligations may require retention under Article 6(1)(c).
• Detection and rewriting: we process submitted text, uploaded documents, extracted features, scores, generated alternatives and repair decisions to supply the requested result. Some detection runs in the browser; server-side operations send the relevant information to our infrastructure and model providers. Do not submit confidential or sensitive personal information unless you are authorised to do so.

Google sign-in

If you choose to continue with Google, Google authenticates your account and shares an account identifier and verified email address with us. We use these to sign you in or create your unslop account. We request no access to Gmail, Drive or other Google content. Email-code login remains available.

Rewrite history and model improvement

We store rewrite history, including originals, outputs, accepted and rejected candidates, detector scores and workflow decisions, associated with an account or request. Rewrite history has a 180-day retention period. These records can support debugging, quality review and development of our rewriting and review models.

Service providers and transfers

Cloudflare provides hosting, security, account email, databases/storage and model inference. RunPod provides GPU inference. OpenAI provides model inference for some rewrite components. Stripe processes payments; we do not need to store full payment-card details. Only providers actually used for a request receive its relevant data.

Some providers may process data outside the EEA. Contact us for information about the providers involved in processing your request and applicable transfer safeguards.

Cookies, storage and optional tracking

Essential local storage supports sign-in, saved text and your privacy preferences. The session token is stored under unslop_session_token. Your consent choice is stored under unslop_consent_v1 for up to 180 days. These functions do not depend on accepting optional tracking.

Only if you consent to Analytics, Google Analytics and our anonymous usage events may measure page visits and product interactions. Google tags are blocked until consent. Our integration excludes submitted text, account email and query strings from event payloads. Google identifiers may use _ga cookies; the cookie lifetime is 180 days. The existing anonymous usage identifier uses us_sid.

Only if you consent to Advertising, the OpenAI Ads Measurement Pixel may measure page visits, completed registrations and confirmed purchases to help attribute advertising. Purchase events include the package, amount, currency and a pseudonymous order identifier. A local record under unslop_ads_orders_v1 prevents repeat purchase events for up to 30 days. The pixel can use __oppref (30 days) and __obref (365 days). We do not intentionally pass email addresses or manuscript contents to the pixel.

Optional processing relies on consent under Article 6(1)(a) GDPR and, where applicable, §25(1) TDDDG. Use “Cookie settings” on any page to reject, change or withdraw consent. Withdrawal does not invalidate processing already performed. Necessary storage is addressed separately under §25(2) TDDDG.

Retention and your rights

Account information is retained while needed to supply the account; transaction records may need to remain for statutory periods. You can request access, correction, deletion, restriction or portability where applicable, object to processing based on legitimate interests, and withdraw consent. Write to the contact above. We may need to verify your identity.

You can complain to a German data-protection supervisory authority, including the authority in the federal state where you live or work. Detector results are writing-pattern estimates, not proof of authorship; unslop does not make academic or disciplinary decisions about you.