Privacy notice

Effective October 23, 2026

This notice covers the website at enruta.ai. It is short because the site collects very little.

What the site collects

• Server logs. Our hosting provider, Vercel, records the IP address, browser type, requested page and time of each request to serve the site and to defend it. These logs are kept briefly and are not joined to any other data.
• Page statistics. Vercel Web Analytics counts page views and a few clicks, such as playing a film or opening an e-mail link. It sets no cookies, and the counts are not tied to your IP address: each visitor is counted with a hash of the request that is discarded after 24 hours. We see totals by page, referrer, country, browser and device type.
• Nothing else. The site sets no analytics or advertising cookies and loads no third-party trackers. The documentation search runs entirely in your browser.
• What you send us. If you write to hello@enruta.ai or security@enruta.ai, we keep your message and address to answer you. Our e-mail runs on Google Workspace.

What we do with it

We use server logs to operate and protect the site, page statistics to learn which pages and films people find useful, and your messages to reply and to follow up on what you asked. We do not sell personal data and we do not use it for advertising.

Product data

Data processed by the Enruta product on behalf of a customer, such as policies, mandates and Evidence Records, is governed by that customer’s agreement with Enruta, not by this notice. How the product handles data is described on the security page. For the AI discovery pilot, the pilot agreement refers to this notice for how we protect store data, and so do the Enruta Discovery Terms that stores accept when they set the service up themselves; that is described in the next section.

AI discovery pilot

When a store joins the AI discovery pilot, or sets up Enruta Discovery itself, we process the following on the store’s behalf.

• Catalog data. Product titles, descriptions, prices, availability, identifiers such as GTIN, and page addresses, read from the store’s public pages, its feeds or our store app.
• Order attribution data. For each order: the date, total, products, and the fields that show where the visit came from, such as landing page, referrer, campaign tags and the platform’s channel label. We do not ask for shoppers’ names, e-mail addresses, phone numbers, street addresses or payment details. If a platform sends any of them with an order, we discard them on receipt. Order and customer identifiers are kept only as one-way hashes.
• Reports the store shares with us from its own accounts, such as Google Merchant Center or Search Console exports.
• Public AI answers to shopping questions about the store’s category, collected through data providers.
• AI visit records. If the store turns on AI visit tracking: for each visit that arrives from an AI assistant, the page, the time and the assistant or search that referred it, for visitors who allow analytics under the store’s privacy settings. No IP address and no customer identity.
• Store staff. When the store’s staff open our app in the Shopify admin: the name and e-mail address Shopify gives us, to show each person what they may see and to record who approved a change. The name and e-mail address are cleared a day after the person’s Shopify session ends, and the record of the visit after 90 days without one; the e-mail address of whoever decided a change stays with that change.
• Store policies and answers. After the store’s ownership is verified, the policies and the answers to frequently asked questions that the store publishes through its public Storefront MCP endpoint. We read them to check that the store’s own information is consistent and to check drafts of store assistant answers against them.
• Billing records. If the store approves per-use billing: for each order we charge for, its date, net merchandise value and currency, the commission and how it was computed, any refund that reduced it, and the invoice it appears on. Card details are entered with Stripe and never reach Enruta. A store that installed through the Shopify App Store is billed by Shopify.
• Ad accounts. If the store links an ad account or uploads its reports: the account’s campaigns, spend, clicks and conversions, and the changes the store approves. Uploaded report files are deleted 13 months after they are imported; previews that are not imported are deleted after 24 hours.

Why. Only to run the service for that store: to measure how AI assistants show its products, to prepare the changes it approves, and to attribute orders that come from AI channels. We do not sell this data, use it for advertising, use one store’s data for another store, or train machine-learning models on it without the store’s written consent. We may publish de-identified, aggregated results that cannot be linked to a store. Once a store approves per-use billing, we also use its order data to compute and collect the commission.

Who else handles it. Our hosting and storage providers (Vercel, Neon), the AI model providers we reach through the Vercel AI Gateway to read public AI answers and match them to products (they receive product information and public answers, never order data), the data providers that collect public AI answers for us (DataForSEO, cloro; they receive our questions, not store data), our billing providers (Stripe, for stores billed by card, and Shopify, for stores billed through the Shopify App Store), and our e-mail providers (Google Workspace, Resend).

How long. While the store uses the service. When our app is uninstalled, we delete the data that came from the store, at the platform’s request two days later and in any case within 30 days. When a pilot ends, we delete it within 30 days if the store asks. The record of who decided each change, the public AI answers we collected, de-identified aggregates and records we must keep by law are kept. Billing records are kept for as long as tax and accounting law requires, even after the store’s other data is deleted.

Safeguards. Only the store’s own team, the partner it chooses to share with, and the Enruta staff who run the service can see a store’s data. Access tokens a store grants us are encrypted, and access is logged. If we learn of a breach that affects a store’s data, we tell the store within 24 hours.

Requests. A store can ask what we hold, ask for a copy, or ask us to delete it at legal@enruta.ai. A shopper who bought from a store that uses the service can ask that store, or write to us at the same address.

Your choices

You can ask what we hold about you, ask us to correct or delete it, or object to how we use it, by writing to legal@enruta.ai. We answer within thirty days. Where the law where you live gives you further rights, you have them too.

Changes

If this notice changes, the new version appears here with a new effective date.

Who we are

Enruta, Inc., a Delaware corporation. Contact: legal@enruta.ai.