Deduplication Vault FAQ: Common Questions and Usage Guide

In bulk number screening scenarios for overseas customer acquisition, data operations often face a headache: the same batch of numbers gets repeatedly checked by different tasks, resulting in fast balance consumption, redundant results, and an inability to accurately count unique valid numbers. The Deduplication Vault is designed to solve this problem. This article will use a Q&A format, focusing on Deduplication Vault FAQ, to explain its working principles, usage conditions, best practices, and how it integrates with KK-DATA’s generation and screening features, helping you maximize screening cost savings.

What is the Deduplication Vault? What is its core purpose?

The Deduplication Vault is an internal cross-task data pool within the KK-DATA platform. When your account completes a number check (e.g., Telegram valid check), the system automatically records that number along with the corresponding platform and check type. Later, when you submit other tasks, the system compares against the history records and automatically skips numbers that have already been checked (same platform + same check type), thus avoiding duplicate charges.

The core purpose is clear: save money + improve efficiency. Without the Deduplication Vault, if you accidentally submit the same batch of numbers for the same type of check twice, you get charged twice. The Deduplication Vault ensures you only pay once for each number’s check type.

Why must you use the Deduplication Vault when bulk screening numbers?

Bulk number screening is usually not a one-time task. You may need to:

• First generate a batch of global numbers, then submit them for Telegram and WhatsApp checks separately;
• Or import CSV files in batches and screen them gradually;
• Or have multiple team members collaborate under the same account.

In these scenarios, not using the Deduplication Vault leads to typical duplicate check waste. For example:

Scenario	Without Deduplication Vault	With Deduplication Vault
Submit 100k numbers for Telegram valid check	Charged for 100k numbers	Charged for 100k numbers
Submit the same 100k numbers again for Telegram valid check	Charged another 100k (waste)	Skip already checked numbers, charge 0 or very few
Total charges	200k numbers	100k numbers

As you can see, the Deduplication Vault directly saves you half of your balance.

Which scenarios are most prone to duplicate checks?

1. Same batch of numbers checked sequentially on different platforms: Generate a batch of numbers, first do Telegram check, then WhatsApp check. Although platforms differ, if you didn’t mark the checked numbers after Telegram, submitting a WhatsApp task later might still lead to waste (if cross-platform dedup is not available). But the most common case is repeated submissions on the same platform.
2. Multiple imports of similar CSVs: Team members collect numbers from different sources but there is significant overlap. If each person submits a task separately, the overlapping part gets charged repeatedly.
3. Accidental duplicate submissions: Network lag or operational mistakes cause the same task to be submitted twice. Without a dedup mechanism, you get charged twice.

What are the consequences of not using the Deduplication Vault?

• Fast balance consumption: The same number gets charged multiple times, quickly depleting available balance and affecting larger screening plans.
• Redundant results: The check report will contain many duplicate rows, increasing the cleanup work after data export.
• Inability to accurately count unique valid numbers: Duplicate checks distort your judgment of “valid number count,” potentially overestimating actual reachable users.

How does the Deduplication Vault work? Does it deduplicate across tasks?

The underlying logic of the Deduplication Vault is simple: each account has a global dedup record table. When you submit a screening task, the system first queries historical records based on the “platform + check type” specified in the task, filters out already checked numbers, and charges only for the unchecked numbers. After the check is complete, the newly checked numbers are written back into the dedup record for future tasks.

This is automatic cross-task deduplication—you don’t need to manually deduplicate or import/export. As long as you are under the same account, all tasks share the same dedup pool.

How to use the Deduplication Vault in KK-DATA?

When submitting a screening task in the KK-DATA console (https://app.kkdata.cc/), the system automatically enables the dedup function without requiring you to check a box. You just need to:

1. Log in to the console and go to the “Number Screening” page.
2. Select the screening platform (Telegram, WhatsApp, etc.) and check type (valid, active, gender, etc.).
3. Upload a number file or paste a list of numbers.
4. Submit the task. The system automatically compares against the Deduplication Vault and displays “estimated check count” and “estimated charge amount.”
5. After the task completes, you can view the “deduplicated count” and “actual charge count” on the task details page.

Tip: If you are using numbers generated by the global number generation feature, simply submit them for screening. Generation itself is free, and the Deduplication Vault will automatically take effect during screening.

What is the coverage of the Deduplication Vault?

Since each platform has different check logic and pricing, the Deduplication Vault currently deduplicates at the granularity of “platform + check type”. Specifically:

• One Telegram valid check will be automatically skipped by subsequent Telegram valid check tasks in the same account.
• One WhatsApp valid check does not affect the dedup decision for Telegram valid check, because these are independent check items.
• Different check types on the same platform (e.g., Telegram valid check vs. Telegram active check) are also separate records and require separate charges.

If you want to avoid duplicate checks across platforms (e.g., checking the same number for Telegram and WhatsApp), it is recommended to first complete a full check on one platform, then use the export feature to extract unchecked numbers, and then submit them to the other platform. This maximizes the single-platform dedup capability of the Deduplication Vault.

How long does the Deduplication Vault retain data?

Based on the current KK-DATA design, dedup records are stored long-term and do not expire automatically. You can check the dedup savings of a previous check anytime in the history tasks. Therefore, even if you perform the same type of check after several months, the system can still recognize previously checked numbers and save you costs.

How does the Deduplication Vault connect with the number generation and global number screening features?

KK-DATA’s core workflow is “Generate → Screen → Export”. The Deduplication Vault sits in the middle of this pipeline as a “cost filter.”

Workflow example:

1. Generate numbers: Use the global number generation feature (free) to generate a batch of random numbers for a target country/region, e.g., 100k US numbers.
2. First screening: Submit these numbers for a Telegram valid check task. The system will charge for 100k numbers (assuming all are new). After completion, the Deduplication Vault records the Telegram valid status of these 100k numbers.
3. Second screening: You need to perform a WhatsApp valid check on the same batch. Since the platform is different, the system will not automatically skip them (because the Deduplication Vault only applies to the same platform and same type). However, if you had created unique identifiers for the numbers during generation, or manually removed numbers already checked on Telegram, you can avoid duplicate submissions. A simpler approach: complete the Telegram check first, then export the results and only take the unchecked numbers (e.g., only upload invalid numbers), but this would miss the WhatsApp check for valid numbers. Best practice: consolidate all screening tasks under one account, perform the most important platform first, then use the “export unchecked” feature (if available in the console) to export remaining numbers and submit them to other platforms. If unsure, contact customer support for the optimal solution.

In this process, the Deduplication Vault ensures that the same platform and same type of check will not be charged twice.

Common Limitations and Notes for the Deduplication Vault

Although the Deduplication Vault is very useful, pay attention to the following points to avoid pitfalls:

1. Dedup only applies to the same check type: As mentioned, Telegram valid check and Telegram active check are different types and will not deduplicate each other. You need to ensure that the task types submitted multiple times are identical to benefit from dedup.
2. Task submission fails if balance is insufficient: Even if there are many already-checked records, a new task still requires balance to pay for unchecked numbers. If balance is zero, you cannot create a task, but existing dedup records remain.
3. Multi-account isolation: Deduplication Vaults are independent across different accounts. If your team has multiple accounts, it is recommended to use one master account for all screening tasks to maximize dedup benefits. If separate accounts are necessary, each account must be recharged separately and cannot share dedup records.
4. Lack of cross-platform dedup: Currently, the Deduplication Vault does not merge across platforms. Therefore, if you plan to check the same batch of numbers on multiple platforms, it is advisable to complete one platform first, then export unchecked data and submit to the next platform to avoid duplicate charges.

Does the Deduplication Vault affect task concurrency?

Basically, no. When the system processes concurrent tasks, it independently compares the numbers in each task. However, if you submit a large number of duplicate numbers (e.g., the same CSV submitted simultaneously by multiple tasks), the system’s automatic filtering reduces the actual number needed for checking, which may actually speed up task completion. But note: if you submit two identical tasks at the same time, although the Deduplication Vault prevents duplicate charges, both tasks will attempt to check the same unrecorded numbers, potentially causing resource contention. It is recommended to stagger submission times.

How to check how much balance the Deduplication Vault has saved?

On the task details page after completion, there is usually a display of “deduplicated count” and “actual charge count”. Simply subtract the actual charge count from the original submission count to get the number of saved numbers. Then multiply by the unit price for that check type (see real-time pricing in console) to get the amount saved.

Frequently Asked Questions

Below is a summary of high-frequency questions about the Deduplication Vault FAQ for quick reference.

Q: Can the Deduplication Vault be shared across users or teams?
A: No. The Deduplication Vault is based on a single account; the dedup records of different accounts are independent. It is recommended that a team use one master account for screening to maximize duplicate detection savings.

Q: If I submit the same CSV for both Telegram valid check and WhatsApp valid check, will the Deduplication Vault skip the second one?
A: No. The two checks belong to different platforms (Telegram vs WhatsApp), so the Deduplication Vault will not cross-platform deduplicate. However, the same platform with the same check type (e.g., two Telegram valid checks) will be automatically skipped.

Q: Will the records in the Deduplication Vault expire and be deleted automatically?
A: According to the current KK-DATA design, dedup records are stored long-term and do not expire automatically. You can view the dedup savings for each check in the console’s task history.

Q: If a submitted task contains a large number of numbers already recorded in the Deduplication Vault, will the task complete faster?
A: Yes. The system automatically skips already-checked numbers, usually significantly reducing task processing time because the actual number of numbers to check is smaller.

Q: How can I verify that the Deduplication Vault is actually saving me balance?
A: On the task details page after completion, you will see “deduplicated count” and “actual charge count.” Compare the original submission count to calculate the saved amount.

---

Summary and Next Steps

The Deduplication Vault is an indispensable cost-control tool in bulk number screening scenarios. It automatically records checked numbers, preventing duplicate charges for the same check type, so that every bit of your balance is spent on new numbers. Combined with KK-DATA’s global number generation and global number screening features, you can build an efficient, low-cost customer acquisition data pipeline.

Try the effect of the Deduplication Vault now! Log in to the console and submit a task containing duplicate numbers to see how much lower the actual charge count is compared to the submission count.

👉 Log in to the console to start screening
Contact customer service via https://t.me/kkdata_robot
For more usage details, refer to the official documentation https://docs.kkdata.cc/ or visit the website https://kkdata.cc/ to view billing information https://kkdata.cc/billing/.