Data Privacy: What We Collect and Why
IP Snare is built to work with the data you already share during traffic disputes. We don't ask for anything new or sensitive — just the click metadata that vendors and publishers routinely exchange when reconciling billable traffic.
No revenue figures. No CPC rates. No client names. Ever.
What We Collect
Every click sent to IP Snare includes 13 mandatory fields. Each one serves a specific purpose in classifying traffic as billable or non-billable.
Click Identification
These fields let us match, deduplicate, and trace every click across both sides of a partnership.
| Field | What It Is | Why We Need It |
|---|---|---|
click_id | Unique identifier for the click | Core reference for tracking and deduplication |
source_click_id | The click ID assigned by the traffic source | Links the click back to the originating publisher for reconciliation |
source_id | Identifier of the traffic source or publisher | Groups traffic by source so you can evaluate quality per partner |
destination_id | Identifier of the destination or vendor | Routes the click to the correct partner report |
User Signals
These fields help us detect bots, flag suspicious patterns, and verify geographic targeting.
| Field | What It Is | Why We Need It |
|---|---|---|
user_ip | The IP address of the user who clicked | Core signal for bot detection, proxy identification, and geo-validation |
user_agent | The browser and device string of the user | Identifies known bot signatures and headless browsers |
user_country | The country of the user | Validates whether the click matches the expected geographic targeting |
Job & Timing
These fields let us check whether a click is valid in context — right job, right country, right time, not a duplicate.
| Field | What It Is | Why We Need It |
|---|---|---|
job_id | Identifier of the job listing clicked | Ties the click to a specific job for expired-job and duplicate-click checks |
job_country | The country the job is posted in | Cross-referenced with user_country to flag geographic mismatches |
click_time | Timestamp of when the click occurred | Used for time-based validation, deduplication windows, and trend analysis |
expired_at | Expiry timestamp of the job listing (if applicable) | Determines whether the job was still live at the time of the click |
is_bot | Whether the source flagged this click as a bot (0 or 1) | Lets publishers pass their own bot assessment for comparison against our detection |
final_click | Whether this is the last click in a redirect chain (0 or 1) | Identifies the billable click when traffic passes through multiple hops |
What We NEVER Collect or Ask For
IP Snare is deliberately designed to work without commercial data. We will never ask you for:
- Revenue or earnings — your financial data stays in your systems
- CPC, CPM, or CPA rates — we don't need pricing to classify traffic
- Client or advertiser names — we identify partners by ID, not by name
- Campaign budgets or spend — irrelevant to traffic quality
- Bid data or margins — your commercial strategy is yours alone
- Candidate or applicant data — we never see who applied or their personal details
There is nothing commercially sensitive on our platform. If there were ever a breach, an attacker would find click metadata — the same data that already flows between partners during routine reconciliation.
Partner-Isolated Reports
Every report on IP Snare is scoped to a single partner:
- Vendors see only the traffic their publishers sent them
- Publishers see only the traffic they sent to their vendors
- No partner can access another partner's data, reports, or traffic breakdown
You can create custom reports for each partnership, and each report is only accessible by the partners involved. Your data is safe, secure, and completely siloed.
This Is Data You Already Share
When a billing dispute happens today, both sides pull logs and compare click-level data — IPs, timestamps, user agents, job IDs. That's exactly what IP Snare collects. The difference is that we do it in real time, so disputes don't happen in the first place.
No new data exposure. No commercial risk. Just the metadata you already exchange, working harder for you.
Ready to see it in action? Book a demo and we'll walk you through exactly how your data is handled.