by Trivas.aiThis is Trivas's privacy policy, effective 2025. It covers anyone who signs up for a trial, uses the Trivas platform day to day, or just browses trivas.ai. If you connect an Amazon, Shopify, Meta, Google Ads, or GA4 account to Trivas, this is the document that governs what happens to that data once it hits our systems.
We'll say this plainly up front because it matters more than anything else on this page: Trivas does not sell personal or store data to third parties. Not to ad networks, not to data brokers, not to anyone. Our business is selling analytics software, not your sales numbers.
This /privacy-policy applies to three groups of people: registered Trivas users on paid or trial plans, anyone who signs up for a free trial, and general visitors to trivas.ai who haven't created an account yet.
For connected accounts, the policy governs any data pulled from or pushed to Amazon, Shopify, Meta, Google Ads, and GA4 through their respective APIs. That includes order histories, ad spend figures, campaign metadata, and traffic data. If you disconnect a platform, this policy still covers whatever data we already synced before the disconnection, until you request deletion.
One more scoping note. This policy doesn't cover the terms of using Trivas itself (pricing, cancellation, acceptable use). For that, see our terms of use.
We collect data in three buckets, and we try to keep each one as narrow as possible.
Account data. Name, email, company name, and billing details, collected when you sign up for a trial or create an account. This is standard SaaS stuff: we need it to bill you and to send you login credentials.
Connected-platform data. This is the bulk of what Trivas actually does. Once you authorize a connection, we pull order data from Shopify or Amazon, ad spend and campaign data from Meta and Google Ads, and session/traffic data from GA4, all via each platform's official API. We don't scrape anything. We don't ask for more permissions than the dashboard features actually require.
Usage data. How you click through dashboards, which features you use most, and query logs from Wingman, our AI insights layer. We collect this to fix bugs and figure out which parts of the product are confusing, not to build a profile on you for advertising purposes.
If you want the technical specifics on how any single integration pulls data, our data integration help docs break it down connection by connection.
Three things, mainly.
First, powering the dashboards and Wingman. Your Amazon, Shopify, and ad account data feeds the performance views you log in to see, and Wingman uses that same data to answer questions like "why did ROAS drop last week."
Second, forecasting. Our AI-driven forecasting models need historical sales and ad spend data to project anything useful. Without at least a few months of order and spend history, the forecasts are guesses, so this data use is foundational to the feature, not incidental to it.
Third, internal product analytics. We look at aggregated usage patterns to improve onboarding flows, speed up support responses, and catch reliability issues before they become support tickets. This is the least sensitive use case and the one most SaaS privacy policies bury. We're naming it directly instead.
Core analytics data lives in Amazon Redshift. We chose Redshift because it handles the volume and query complexity that ecommerce analytics demands, and access to raw customer data inside it is locked down by role, not open to the whole engineering team by default.
Data synced from connected platforms is encrypted both in transit and at rest. That's table stakes for anyone handling ad spend and order data, and we don't treat it as optional.
Inside your Trivas account, permissions are role-based. A support hire shouldn't see the same thing a founder or growth lead sees, and our account structure reflects that: team members only get visibility into the data relevant to their role, not a blanket view of everything in the account. For a fuller breakdown of our security posture, our trust center covers infrastructure and compliance details that go beyond the scope of this page.
You can request access to or deletion of your account data at any time. The fastest route is through our contact form, where privacy requests get routed directly to the team handling them, not into a generic support queue.
Marketing emails have an unsubscribe link in every send, and we honor opt-outs immediately. Non-essential analytics, the kind that tracks general product usage rather than anything required for the platform to function, can also be turned off from your account settings.
If you're in the EU or UK, GDPR gives you rights to access, correct, port, or erase your data, and we process these requests the same way regardless of where you're located. If you're a California resident, CCPA gives you similar rights plus the right to know what categories of data we've collected about you in the past 12 months. We don't gate these rights behind lawyers or forms longer than they need to be. Email us or use the contact form, and we'll handle it.
Trivas connects to ecommerce platforms (Shopify, WooCommerce), ad networks (Meta, Google Ads, TikTok, Reddit Ads), and marketplaces (Amazon, Walmart, eBay, Etsy, Target, and others). We're not going to list certifications we don't hold, so if a specific compliance badge matters to your procurement process, ask us directly rather than assuming.
Data shared with sub-processors, the vendors we use to run infrastructure like Redshift hosting, is limited to what's actually needed to deliver the integration. If a sub-processor is helping us sync Shopify orders, they see Shopify order data relevant to that job. They don't get a dump of your entire account.
Disconnect a platform, and future syncing from that source stops immediately. We don't keep pulling data after you've revoked access, and any historical data already synced stays subject to the deletion rights covered above. If you're setting up or reconsidering a Shopify connection specifically, our Shopify integration guide walks through what gets synced and what doesn't, and you can find the app itself listed as Trivas AI on the Shopify App Store.
When we make material changes to this policy, meaning changes to what we collect or how we use it, not just wording cleanup, we notify users by email and with an in-app notice. We don't bury changes in a changelog nobody reads.
The current version of this policy always lives at this URL, and we keep a revision history available so you can see what changed and when, rather than asking you to take our word for it.
For anything not covered here, privacy questions, data requests, or anything in between, reach out through our contact form and it'll get to the right person.
If you want to keep up with how Trivas handles data and product changes as we grow, our blog is where we post updates like this one as they happen.
explore more insights
3 min read
3 min read
3 min read
.d53b12e5.png&w=3840&q=75 "Trivas.ai")