Skip to content

How your data is handled

A data broker using CalDrop Compliance holds two kinds of sensitive data: the deletion requests DROP sends, and its own customer file. The product is built so the second, by default, never reaches us. Here is what is stored, where, and what we do not claim.

Wooden card-index cabinets in a national archive reading room
Card index, National Archives of Finland

Where each piece of data lives

Your computer

  • Your customer file
  • Standardized values and hashes (browser mode)
  • The action list naming your people

Our server

  • Batch ZIPs, encrypted (AES-256-GCM)
  • Matched work item IDs and counts
  • Hashes and person IDs (automatic mode only)
  • The audit log

DROP

  • Your DROP account and API key, held by you
  • Id,Status response files we send for you

How it is protected

Your customer file

In browser mode, the default, the file is read, standardized and hashed in your tab. We receive matched work item IDs and how many people each matched. In automatic mode, the browser uploads SHA-256 hashes with your own person IDs; a new upload replaces the last. Names, emails, phone numbers and dates of birth are never uploaded.

DROP data

The batch ZIP is kept exactly as received, encrypted, because DROP will not send a lost batch again. Your DROP API key and webhook secret are encrypted the same way and shown only by their last four characters. DROP data is used only to process your requests and keep your records, never sold or shared (11 CCR § 7616).

The audit log

Every download, match, exemption, confirmation, upload and DROP response is appended to a log in which each entry stores a SHA-256 hash of its content and of the entry before. Editing or removing an entry breaks the chain, and the evidence packet says where.

Accounts

Email addresses are confirmed before sign-in. Passwords are at least 12 characters and stored as salted hashes. Two-step sign-in with an authenticator app is available to every user, with single-use backup codes. Only owners and admins can change the DROP connection, confirm deletions or manage billing.

Where it runs

The application and its database run on a dedicated virtual server operated by Contabo GmbH in the European Union, behind Cloudflare. The database is reachable only from the server. All traffic uses TLS, with HSTS. Payments go through Stripe; we never see card numbers. Nightly database backups are kept on the same server for 14 days.

What we do not claim

No SOC 2 report or ISO certification yet. CalDrop Compliance is run by Preptics LLC, a small company. The design aims to keep the data we hold small rather than to ask for trust.

Subprocessors

CompanyWhat forWhere
Contabo GmbHServer and database hostingEuropean Union
Cloudflare, Inc.DNS, TLS and network protectionGlobal
Stripe, Inc.Payments and billingUnited States
Zoho CorporationAccount and reminder emailNamed in the privacy policy

Report a security issue

Write to [email protected]. A person reads it within one working day. Our security.txt has the details.

See also the data processing terms and the privacy policy.

Questions

Something else? Write to us and a person answers within one working day.

Do you have SOC 2?
No, not yet. We say so here rather than imply otherwise. If your procurement needs a questionnaire answered, write to us and we will answer it honestly.
Can your staff see our matches?
We can see which work item IDs matched and how many of your people each matched, because the statuses are built from that. We cannot see who those people are in browser mode.
Are hashes personal information?
Treat them as such. DROP's hashes identify consumers to anyone holding the same data, which is why we encrypt batches and never sell or share them.
Can we delete our workspace?
Yes. Write to us and the workspace and its data are deleted. Download your evidence packets first: you must keep audit records for six years.

Answer your next DROP batch on time

14-day trial on every plan. Run the practice batch first if you like.