Connect

Home / Privacy

Privacy Policy

Version of October 8, 2026. Feedpipe is operated by the US limited liability company named on the Company page. That company is responsible for the personal information described here.

What this covers

This policy covers the website at feedpipe.app, the cabinet where you connect a feed, and the search API your agent calls. It does not cover a shop’s own website or the words an outside agent says to a customer.

Information we collect

  • Account email and a hash of the password. The password itself is not stored. If you sign in with Google, we receive the email Google marks as verified, and nothing else from the Google account.
  • The shop name you enter and the feed URL. The feed itself: product name, price, stock, SKU, and link. That snapshot is your catalog data, collected so an agent can quote it.
  • The fact of a search, so the monthly plan limit can be counted. A product card and the tool schema do not count as searches.
  • Billing records: plan, amount, currency, order id, and status. WayForPay processes the card. We do not store the full card number.
  • If you turn alerts on, the email address for those alerts and, if you add it, a Telegram chat id.
  • Technical data needed to run the service: session cookies, the time of a request, and error logs. We do not use advertising cookies or sell this data.

How we use it

We use this information to open and secure the account, collect the feed, answer search, count the plan, send a verification or password email, take payment, and tell you if a catalog is stale. We do not use it to build advertising profiles, and we do not sell or share personal information for cross-context behavioral advertising.

Who receives it

WayForPay receives the amount, currency, order id, and account email in order to charge the card. Google receives the sign-in only if you choose Google. The host that runs Feedpipe stores the account and the snapshot. Email is sent through the mail provider configured for the service. If you add Telegram alerts, Telegram receives the chat id you supply.

Search with a shop key returns snapshot rows to whoever presents that key. You give the key to your agent. The feed is read from the URL you provide. Feedpipe does not ask the shop for a separate login, and it rejects a password inside the feed URL.

Cookies

The cabinet uses a small set of cookies so you can stay signed in and so a payment or Google sign-in can finish. The list is on the Cookie page. There is no advertising cookie and no optional analytics cookie to accept.

How long we keep it

The account, the feed URL, and the snapshot stay while the account exists. A payment record stays so the plan and the charge can be shown and so the books can be kept. Session cookies end when you sign out or when they expire. A draft of a shop before registration lasts about a day.

Your requests

You can ask to see, correct, or delete the personal information in your account. Send the request from the account email. Deleting the account removes the shop, the snapshot, and the keys. A record of a charge that already happened stays for as long as the books need it.

If you live in California, the same requests cover the rights to know, to delete, and to correct under the California Consumer Privacy Act, as amended. We do not sell personal information and we do not share it for cross-context behavioral advertising, so there is no separate sale to opt out of. We will not discriminate against you for making a request. We answer a verifiable request from the account email.

If another US state gives you a right to access, delete, or correct personal information, send the same request from the account email and we will handle it under that law.

Children

Feedpipe is a business tool. It is not directed at children under 13, and we do not knowingly collect their personal information.

Where it is processed

The service is operated from the United States. If you connect a shop from another country, your account and catalog snapshot are processed in the United States.

Changes

We post changes on this page and change the date at the top. If a change materially reduces what you can ask us to delete, the previous version still covers data we already hold until the next time you pay or renew.