Security and trust
Security and trust
How ecentic handles your catalog, your store access and your customers’ data. We update this page as we grow, and the date below changes when we do.
- Read-only imports
- Public data first for pilots
- Discuss DPA requirements
- Documented provider purposes
Last updated 12 November 2026
This page describes controls in the current product. Confirm the deployment, processing locations and contractual requirements for your account before sharing non-public data.
How we touch your store
Importing product content does not rewrite it. Apply generates and publishes a title and description on a directly connected Shopify or WooCommerce store. Structured data uses a separate publish action. Connecting Shopify also installs the visit-tracking script.
Shopify access uses the Shopify Admin API and the permissions shown on the install screen. You can uninstall at any time. WooCommerce connects through the ecentic plugin or REST API keys that you create and can revoke.
On Shopify, a storefront script records visits when it detects an AI assistant referrer or a known agent user-agent. It sends the full page URL, browser user-agent, referrer, page type, detected agent and detection method, and an available product identifier. The record includes the store and the time received.
This browser script observes visits that run JavaScript. It does not measure every crawler request or establish that a later order came from the same shopper.
If you connect Merchant Center for Shopify, ecentic adds a supplemental data source for published fixes and checkout attributes. It does not replace your main feed.
When you enable agent checkout on WooCommerce, the checkout bridge creates real orders in your store. Your gateway takes payment and you remain merchant of record. Agent checkout supports signed requests, agent allow-lists and configurable rate limits; enforcement follows your store settings.
Import and publish
Enterprise pilots can start from public pages and product data, without access to your systems.
Infrastructure and data protection
- Application hosting
- Vercel: application hosting, scheduled jobs and AI Gateway routing.
- Database
- Neon PostgreSQL on AWS us-east-1 (Northern Virginia).
- Encryption
- Data is encrypted in transit (TLS 1.2+) and at rest (AES-256) by our hosting and database providers.
- Account passwords
- Passwords are hashed with scrypt through Better Auth.
- Webhooks and OAuth
- Shopify webhooks use HMAC verification. OAuth callbacks validate state; supported checkout requests can use HTTP message signatures.
AI models and your data
- Connected store catalog
- AI providers
- Comparisons and listing fixes
The product catalog you connect is sent to AI providers to compare listings and write fixes. Store scans use ChatGPT, Claude and Gemini. GPT also generates listing rewrites and structured data. Perplexity is used in the separate comparison and discovery tools, not store scans.
Data read from a connected Google Merchant Center account is kept separate from the store catalog used for AI work, as described in the privacy policy.
GPT runs through Azure OpenAI when an Azure deployment is configured. Anthropic, Google and Perplexity requests use the Vercel AI Gateway; GPT can use that gateway as a fallback.
Provider retention policies apply to requests. Some providers retain requests for abuse monitoring; we do not promise zero retention across every model route.
Privacy and GDPR
- Operating company
- ecentic Inc · Delaware, United States
- Agent checkout data
- You are the data controller and ecentic is your processor for shopper details handled to carry out checkout.
- Data requests
- Request access, correction or deletion through privacy@ecentic.ai. We respond within one month.
Providers used by the product
Providers and purposes identified in the product code, reviewed November 12, 2026. Contracted processors and processing locations are confirmed for the relevant service and agreement.
| Provider | Purpose |
|---|---|
| Azure OpenAI | GPT simulations, listing rewrites and structured data. |
| Anthropic | Claude listing comparisons through Vercel AI Gateway. |
| Gemini listing comparisons through Vercel AI Gateway. | |
| Perplexity | Separate comparison and discovery tools through Vercel AI Gateway. |
| Vercel | Application hosting and AI Gateway request routing. |
| Neon | Application records, connected catalog data and credentials. |
| Upstash | Redis caches, session data and rate-limit counters. |
| Sentry | Error monitoring and application telemetry. |
| PostHog | Product analytics after analytics consent. |
| Google Analytics 4 | Website analytics after analytics consent. |
| Resend | Transactional email delivery. |
| UploadThing | Storage for uploaded files. |
| Stripe | ecentic plan and performance-fee billing. |
| SerpAPI | Product offer lookups. |
| Chatwoot | Website support chat. |
| BabyLoveGrowth | Editorial blog content. |
| Clearbit | Company logo images. |
| Google Merchant API | Optional Merchant Center connection. |
| Shopify Catalog MCP | Product measurement in Shopify’s catalog. |
| x402 | Payment facilitator for supported routes. |
| ScrapeLLM | Internal capture tooling; not a customer feature. |
Data processing agreement
A DPA is arranged on request before personal data is shared. We can sign your own DPA; the contracting entity and signatory are confirmed in the agreement.
We sign a mutual NDA before receiving non-public data. The public-data first phase does not need one.
Compliance roadmap
SOC 2 is not available today. We do not claim a certification or a completed audit. Discuss your security requirements before agreeing a pilot.
Alvi, our CTO, handles security questionnaires after an NDA. We do not offer a pre-approved security pack.