Privacy Policy

CatalogRoute is responsible for the personal data described here. Write to the privacy address below with any question about your data.

CatalogRoute is for businesses and is not meant for anyone under 18.

When you open a supplier file, the tool reads and converts it inside your browser. No server receives the file itself.

An unfinished run is kept in this browser until you finish it or start over.

Connecting is optional. Nothing happens until you press Connect Square and approve the permissions on Square.

What we read

Your item library, with its prices, costs, barcodes, categories and stock. The catalog pages pass through our server in memory and are never stored.

What we write

The rows you approved, when you press Send to Square. Nothing is written on its own, and a push does not delete anything. Undo, when you press it, restores the values from before that push and removes the items it created.

What we keep

Your Square tokens, encrypted at rest with a key kept apart from the database. Next to them we keep your Square merchant id, your shop name and locations, when you connected and when the catalog was last read, and a short record of each push so Undo and the Single File Pass work.

Retention

The tokens are kept until you disconnect. Disconnect revokes our access at Square and deletes them here. It is in Settings and in the tool.

Your rows

Processed in your browser and never stored on our servers. Optional AI features send only the details they need.

Your email address

Stored so the sign-in link can reach you, and so we can answer a support email.

Sign-in and usage records

The IP address and browser type of each signed-in session, and how many AI rows you use each month. If you sign in with Google, also the name and profile picture Google shares.

Export and send times

We record the time of your last export and last send to Square, never the file.

Supplier settings

The name you give each supplier, its column layout and your pricing rules. No product rows.

Run counts

Totals from each run, such as the number of rows and price changes, with the date and a short summary line. No row content.

Item keys, if you switch it on

Short hashes of SKU and GTIN values, so next time the tool can say which products disappeared. The codes themselves are not stored.

Billing records

Your plan, its status and dates, any Single File Pass, and the Stripe customer and subscription ids. Card details stay with Stripe.

Without an account we keep no account data. Our servers keep your IP address in rate limit records, and your email address if you asked for a sign-in link. If you ask us to email you a link to the tool, we send it to the address you type and keep only a rate limit record, which holds a one-way code made from the address, not the address. These records expire, and we delete them after they expire. The tool keeps your saved suppliers and the matches you confirm in this browser.

We use this data to run the service you asked for and to bill you, and, as our legitimate interest, to keep the service secure and to see which features are used.

We use service providers for hosting and the database, payments (Stripe), email delivery, bot checks on sign-in and the forms that send email (our server passes your IP address to the check), analytics, error reports and AI features. Each receives only the data its job needs. Write to the privacy address below for the current list.

Like any web service, each provider your browser contacts receives your IP address and browser details. Our providers may process data in the United States and other countries.

We do not sell your personal information or share it for advertising.

We use only the cookies the site needs to work, such as the one that keeps you signed in. Our analytics sets no cookies.

The tool also saves data in this browser's storage, such as your suppliers, settings and confirmed matches, and an offline copy of the app. You can delete it in the tool or by clearing the site's data.

We count page views and feature use, such as files converted and plans started, with an analytics service. It sets no cookies and keeps nothing in your browser. If your browser sends Do Not Track or asks for reduced data, no event is sent.

Events hold counts, size bands and fixed words, plus the first page of your visit and the campaign name from the link you arrived by, a short word. The service may also add the page address, your browser and device type, and an approximate location based on your IP address. Events do not include a cell, a header, a file name, a supplier name or an email address. A signed-in visitor is counted by account id, never by email address.

Every sign-in link carries those two, so we can count which pages bring new accounts. For Google sign-in, a sign-in record that holds them is kept for up to 10 minutes. Neither is stored in your browser or with your account.

AI features are optional. With the AI switch off, nothing is sent to an AI provider. If you turn AI on for a saved supplier, it stays on for that supplier's next files until you turn it off.

When you use an AI feature, for example matching, name cleanup or SEO fields, we send the details that task needs, such as column headers, product details and a few sample rows, to third-party AI providers, which return a suggestion.

We leave out the columns the tool reads as prices, costs, quantities, SKUs or barcodes, and our server refuses values that look like a barcode or an email address. Other cells, such as product names or an extra price column, can still carry that kind of detail.

These providers may keep the data for a short time under their own terms, for example to prevent abuse. AI answers are suggestions and can be wrong, so review them before you use them.

When the app crashes, an error reporting service receives the error message, where in the code it happened, the page address and your browser type, so we can fix it.

We set it to strip request bodies, cookies and headers, to remove file names, and to drop any report that looks like it holds an email address or a barcode.

Stripe takes the payment and holds the card details. We store the Stripe customer id and the subscription id, which is what the billing portal needs.

We never see or store a card number.

Account data lives in our hosting provider's database, in one region. Our hosting provider also sees the usual request data a web host sees, such as your IP address, to serve the page and to block abuse, and keeps short-lived request logs.

Every connection to the site uses HTTPS. No way of sending or storing data is fully secure, so we cannot promise that data will never be exposed.

We keep account data until you delete your account. To delete it, open Settings and choose Delete account. That removes your suppliers, run history, billing records and sign-in records from our database straight away, and ends any subscription at once.

Backups of our database are deleted on a rolling schedule within about 30 days. Stripe keeps its own payment records as the law requires. Analytics events carry your account id, not your email address, and expire on the analytics service's own schedule.

Data saved in this browser is not affected. Delete it in the tool or by clearing the site's data. Write to the privacy address below if you want confirmation.

You can ask for a copy of your account data, ask us to correct or delete it, or object to how we use it. Write to the privacy address below and we answer within 30 days. You can also complain to your local data protection authority.

When this policy changes, we update the date at the top and email account holders about a material change.