DROP cycles that start on their own
With your DROP API key connected, the batch is downloaded on schedule and matched on our server against SHA-256 hashes of your file, uploaded from your browser. The action list is waiting when you sign in, and nothing is sent to DROP until you confirm.
Batch of Nov 20, 2026
43 days
to report 3,066 work items
30-day window from Jan 1, 2027 already applied
Downloads on schedule
A daily job checks each connected workspace and downloads a new batch before the access window closes: every 45 days, 30 from 1 January 2027.
Matching from hashes
Your browser hashes your file and uploads only the hashes with your own person IDs. A new upload replaces the last one. Names, emails and phone numbers are never uploaded.
You still confirm
The schedule downloads and matches. Deleting in your systems and confirming stay with a person who has the owner or admin role, and every confirmation is logged.
Reminders that escalate
Emails go out as each report-by date comes closer, and the dashboard shows every open batch with its days left.
Plans: Growth and Scale. See pricing
Questions
Something else? Write to us and a person answers within one working day.
Do you need our DROP API key?
What if the hashes are out of date?
Can we switch back to browser matching?
What if DROP's API is down?
The rest of the product
Answer your next DROP batch on time
14-day trial on every plan. Run the practice batch first if you like.