Information we process
Evargo may process account profile data, login/session information, connected account identifiers, listing data, product details, inventory quantities, order records, order items, fees, shipping snapshots, COGS, sync logs, settings, billing status, support questions, and operational diagnostics.
Why the data is used
We use this information to authenticate users, connect seller accounts, sync marketplace and store data, display inventory and orders, calculate operational analytics, preserve settings, prevent unsafe requests, diagnose integration issues, provide support, and understand whether new users complete the launch funnel.
Connected platforms
When you connect eBay, Shopify, or another service through Evargo, data may be requested through that platform's APIs and stored so the workspace can show listings, orders, products, account state, sync history, and related operational context. You can remove connected accounts from Profile, which deletes the synced data Evargo stores for that channel.
Billing and authentication
Stripe handles Growth checkout, subscription, invoice, trial, and billing portal workflows. Authentication providers may process login and session data. Evargo stores the identifiers and status needed to connect those services back to your workspace.
Support and deletion requests
Questions submitted through Evargo are stored in the support inbox and may trigger an operational alert to the team. You can use the support form to request account deletion, workspace data deletion, or help disconnecting marketplace accounts. We may need to verify ownership before completing a request.
Privacy-light launch tracking
During soft beta, Evargo records limited server-side funnel events such as public page visits, signups, channel connections, sync starts, checkout starts, and support submissions. These events are used to improve onboarding and do not rely on advertising pixels or retargeting cookies.
Retention and security
Evargo keeps operational records for as long as needed to provide the workspace, diagnose sync issues, support users, meet legal or billing obligations, and protect the service. Security controls include session protection, CSRF checks, account ownership checks, webhook validation, and credential protection services.
AI Listing Assistant beta. When an authorised user starts an AI review, Evargo sends the selected eBay listing facts and up to four current product-image URLs to OpenAI. The assistant may use web search to find supporting evidence. OpenAI response storage is disabled for these requests. Evargo stores only parsed suggestions, approved citations, the model and prompt version, latency, token/tool counts, and a privacy-preserving user hash; it does not store the full prompt or raw model response. AI suggestions never publish automatically and require human review.
Cookies
Evargo uses necessary cookies and browser storage for login, session, security, and marketplace connection flows. Advertising and retargeting cookies are not used unless a separate consent flow is added.