Privacy policy
Last updated: 6 November 2026
This policy explains what data Veralogue ("we", "us") collects, why, and how it is protected. It covers this website (getveralogue.com) and the Veralogue service we provide to agencies and merchants ("clients").
Veralogue is operated by [LEGAL ENTITY NAME], [REGISTERED ADDRESS]. Questions about this policy can be sent to privacy@getveralogue.com.
1. This website
The website doesn't use advertising or analytics cookies and doesn't ask you to create an account. Our hosting provider (Vercel) keeps standard server logs, such as IP address, browser type and the pages requested, to run and secure the site. If you email us, we keep your message and contact details to reply and to manage our relationship with you.
2. Data we process for clients
When a client uses Veralogue, we process the following on their behalf:
- Product data: titles, descriptions, attributes, identifiers, prices and links from the client's store, product feed or Google Merchant Center account.
- Performance data: product-level impressions, clicks, conversions and similar metrics from Google Merchant Center and, where connected, Google Ads.
- Public search data: search suggestions, common shopper questions and public Google Shopping listings related to the client's products. These are not personal data.
- Account details: names and work email addresses of the people at the client who use the service.
We don't collect data about the client's own shoppers or customers, such as names, addresses or order histories, and we ask clients not to send it to us.
3. How we use it
- To write and check product titles, highlights and answers to shopper questions.
- To publish that content to a supplemental data source in the client's Merchant Center account, when the client asks us to.
- To measure the effect of changes by comparing test and control products.
- To produce reports for the client, operate and secure the service, and provide support.
We don't sell client data, we don't use it for advertising, and we don't use it to train AI models.
4. Google user data
When a client connects a Google account, Veralogue requests access to the Google Merchant Center (Content / Merchant API) and, where needed, Google Ads data for the accounts the client authorizes. We use this access only to read product and performance data and to write to the supplemental data source Veralogue manages for that account. We never change the client's primary product data.
Veralogue's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We don't use Google user data to develop, improve or train generalized AI or machine-learning models, we don't transfer it to third parties except as needed to provide the service or as required by law, and people at Veralogue read it only with the client's permission, for security, or to comply with the law.
A client can revoke our access at any time from their Google account permissions or by contacting us.
5. Service providers
We use these providers to run the service. Each processes data only on our instructions and under contract.
| Provider | Purpose |
|---|---|
| Vercel | Website and application hosting |
| Supabase | Database, authentication and secure storage (United States) |
| GitHub | Running processing jobs |
| Anthropic | AI model that writes and reviews product copy. Data sent through Anthropic's commercial API isn't used to train its models. |
| SerpApi and DataForSEO | Public search suggestions, shopper questions and shopping listings. Only product names and search phrases are sent. |
| Google Workspace |
6. Where data is stored
Client data is stored in the United States. If you're outside the United States, your data may be transferred there; where the law requires it, we rely on appropriate safeguards such as standard contractual clauses.
7. How long we keep it
We keep client data for as long as the client uses Veralogue. Within 30 days of a client ending the service or asking us to delete their data, we delete it, except where we must keep limited records by law. Cached public search data may be kept for up to 12 months to avoid repeating paid lookups.
8. Security
Data is encrypted in transit and at rest. Credentials and API keys are stored in encrypted secret storage, never in code. Each client's data is kept separate, and access is limited to the people who need it.
9. Your rights
Depending on where you live, you may have the right to access, correct, delete or export your personal data, or to object to how we use it. To make a request, email privacy@getveralogue.com. If we process your data on behalf of a client, we'll pass your request to them and help them respond.
10. Changes
We'll update this page if our practices change and revise the date at the top. Significant changes will be communicated to clients directly.