What Rebilder stores about your visitors · Rebilder Help

Rebilder’s records are about requests to your site, not about the people making them. A recorded event contains a timestamp, who asked (an AI assistant, a Person, a Crawler or an Agent protocol client, plus the platform when it can be named), the URL requested on your own site, technical request context like the Accept header and referrer, what was served, and how long it took.

If you connect orders (through the Shopify app or the outcomes API), Rebilder also 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, only those fields are kept. The customer’s name, email and address in Shopify’s order message 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 visitors and no cross-site tracking: Rebilder observes requests to your site only.
• No shopper profiles: a visit from a person is recorded as Person, with no platform and no identity. Two visits by the same person are just two rows.
• If you add the Tag, it sends one small record per pageview, with no cookies and no fingerprints. It leaves out form contents and personal identifiers.

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.