Privacy and data

What DropSlop keeps, what is public by link, and when your text goes to another company.

This is a short summary. The full privacy policy is the one that counts.

What we keep

Checking a draft doesn't save it. Text you check is scored and sent back to you.
What you save: drafts and their versions (only when you press Save), voices, API key names and connected platforms. Only you can open your drafts.
Your email address, to send sign-in links.
Usage counts: how many words you used, and when. Not the text.
Without an account: a one-way hash of your IP address, to apply the free daily limit.
Rewrites are kept for a few days so you can come back to a running or finished job.

Site audits. Anyone with an audit's link can open the report. The pages it reads are public already.
Certificates. Anyone with the link can see the certificate page, including its scores and a short preview of the text.

Saved drafts are never public.

Checks (the X-Ray, the detector, site audits) run on DropSlop's own servers.
Rewrites run on a GPU server DropSlop rents for this (see the policy for the provider).
Certificates send the text to two outside detectors, GPTZero and Pangram, to record their scores. The API's stricter verified modes do the same, and the verified rewrite mode also uses OpenAI to put back facts and handle lists. Nothing on the website sends text to them except a certificate.
Connected platforms receive only what you choose to send, always as a draft. Google Docs, Notion and HubSpot connections go through Composio.

DropSlop doesn't sell your data, show ads, or use your drafts to train its models.

Delete a draft from the Library, a voice from Voices, a key from API keys, or a platform from Connections. Delete your whole account from the Account page. For a copy of your data or a correction, email [email protected].