Data inputs
BulkChecker may process phone numbers, email addresses, CSV or TXT files, API request payloads, account settings, billing references, and support messages needed to operate the service.
Customers should upload only fields needed for the verification job. Avoid adding unnecessary names, notes, private comments, or unrelated customer attributes to verification files.
Verification outputs
Depending on the product, results may include validity status, carrier name, country, line type, routing context, platform availability signals, risk or confidence fields, timestamps, and segmented export files.
These outputs are signals for data quality and operational review. They should not be treated as proof of identity or as a substitute for legal, compliance, KYC, AML, or platform-policy review.
Privacy and security principles
- Use authorized data only.
- Keep uploaded files focused on the minimum data needed for the job.
- Use dashboard access carefully and limit team permissions where possible.
- Use API keys from server-side systems, not public client-side code.
- Delete local exports when they are no longer needed for your workflow.
BulkChecker uses technical and organizational safeguards designed to protect account and verification data. No internet service can guarantee absolute security, so customers should also protect credentials, API keys, and exports.
Customer responsibilities
Customers are responsible for consent, lawful basis, platform policy compliance, internal access controls, and correct use of verification outputs. BulkChecker does not authorize spam, scraping, harassment, or unauthorized messaging.
Security and privacy requests
For account-specific data handling questions, use the Support Center or dashboard support flow. For broader privacy details, read the Privacy Policy.