# [What Rebilder stores about your shoppers](https://rebilder.com/help/trust/shopper-data)

- **Summary:** Events describe requests, not people: no names, no emails, no payment data, no cookies, no cross-site tracking.

Rebilder’s records are about requests to your store, not about the people making them. A recorded event contains a timestamp, the requester’s classification (agent, human, crawler, or protocol, plus the agent platform when identifiable), the URL requested on your own store, technical request context like the Accept header and referrer, what was served, and how long it took.

If you wire the order join (the Shopify webhook or the outcomes API), Rebilder additionally stores what you report about each order: an order id, timestamp, order value, currency, the product URLs on it, and any attribution evidence you choose to send. From a Shopify order webhook, only those fields are extracted: customer name, email, and address in the webhook payload are discarded, never stored.

## Request data scope

- Send the documented request fields and keep personal information out of URLs and optional payloads.
- No cookies set on your shoppers and no cross-site tracking: Rebilder observes requests to your store only.
- No shopper profiles: a human visit is recorded as kind “human” with no platform and no identity. Two visits by the same person are just two rows.

## What this means for your privacy policy

Describe Rebilder as a service provider in your privacy notice, including the request and order information your integration sends. Keep personal information out of page URLs and optional event fields. Our Privacy Policy explains Rebilder’s processing.