Evolve (evolvepages.com) is operated by Evolve LLC, a Utah limited liability company (“Evolve,” “we,” “us”). Evolve generates landing pages, measures how they perform, and runs experiments to improve them. This policy explains what data we handle in doing that — both data about you (our customer) and data we process on your behalf about visitors to the pages you publish.
The short version
- We collect the minimum needed to run the service. Page-visitor tracking uses a pseudonymous identifier — we never collect visitor names, emails, phone numbers, or payment details.
- Order attribution from connected stores reads only order totals and the attribution tags our pages add at click time — never customer identity fields.
- If you connect Google Ads, we read your ad results to learn which audiences convert, read-only, and use them only to suggest and build your pages. You can disconnect at any time.
- We do not sell personal data, to anyone, for anything.
- Data is encrypted in transit and at rest, and deleted on verified request.
Data we collect about our customers
- Account information — your name and email address, handled through our authentication provider.
- Billing information — subscriptions are processed by our payment processor. Card numbers never touch our servers.
- Content you create — page briefs, product selections, generated pages, and settings.
- Store connections — if you connect a commerce store, we store its domain and an encrypted access token scoped to the permissions you grant.
- Other connections— if you connect an ad account (Google Ads), a content library (Google Drive, Dropbox), or a form or analytics tool, we store an encrypted access token and the minimum account details needed to use it. See “Google user data” below.
- Support communications — messages you send us.
Data we process on your behalf (your page visitors)
When you publish a page built with Evolve, our tracking measures how it performs. For each visitor we process:
- A pseudonymous visitor identifier— a random ID stored in the visitor’s browser. It is not derived from the visitor’s identity, and we connect it to identity only when a visitor deliberately submits a form (see “Form submissions” below).
- Page interaction events— page views, how far down the page the visitor scrolled (including whether the page’s conversion element came on screen), focus on and clicks of the page’s conversion element, and which experiment variant the visitor saw.
- Context — referrer, campaign parameters (UTM tags and ad click identifiers), and coarse technical data such as browser type, device type, screen size, and approximate location (city/country) derived from the network address at the moment of the visit. The network address itself is discarded at ingestion and never stored.
Our passive analytics tracking does not collect visitor names, email addresses, phone numbers, precise location, or payment details.
Form submissions on pages you publish
When a visitor deliberately submits a form on a page you publish (for example an email sign-up), we store the submitted fields on your behalf and deliver them to the destinations you configure (your lead inbox, email notifications, webhooks). This is separate from the passive analytics described above: form submissions can include whatever the visitor typed, such as their email address. Each submission is stored together with the visitor’s pseudonymous identifier and experiment variant, so you can connect a lead to the visit that produced it. These submissions are covered by the same retention and deletion terms as the rest of your data.
Order attribution (connected stores)
If you connect a store and enable purchase attribution, links on your pages carry attribution tags (the pseudonymous visitor ID, the page, and the experiment variant). When an order is placed, the store platform notifies us and we record: the order ID and number, the order total and currency, and those attribution tags. We request only the minimum order data the platform allows and never receive or store customer names, emails, phone numbers, or addresses. We honor the platform’s customer data request and redaction webhooks.
Google user data
Evolve connects to Google only when you choose to. Here is exactly what each connection does.
- Sign in with Google — we receive your name, email address, and profile picture to create and secure your account.
- Google Drive— we can open only the files you pick in Google’s file picker. We copy the images you choose into your Evolve media library. We cannot see the rest of your Drive.
- Google Ads — when you connect an ad account, we read the list of ad accounts your Google login can reach, so you can pick one. For the account you pick, we read performance reports for the last 90 days: spend, clicks, and conversions by age range; the search terms that led to conversions; and the text of the ads that converted. We use these reports for one purpose: to learn which audiences buy from you and what they respond to, so Evolve can suggest pages, tests, and missing information to you and build pages for those audiences. Evolve never creates, changes, pauses, or deletes anything in your Google Ads account. Google offers only one Google Ads permission, which covers changes too, but we only read.
What we keep for Google Ads: encrypted access and refresh tokens, the list of reachable ad accounts (account IDs, names, currency, and whether each is a manager account), and the account you picked. We never store the reports themselves. From them we keep one summary of the account you picked, covering the last 90 days: audience figures by age range, your account’s total conversions and currency, up to 20 search terms that led to conversions and how many conversions each led to, the headlines and descriptions of up to 5 ads that converted and how many conversions each brought, how ready to buy those searchers were, and when we made the summary. We refresh it about once a week while Google Ads stays connected. A page you build from a suggestion keeps the direction it was built from, which can quote the wording of your own ads or converting searches but no ad figures (no conversions, clicks, or spend); it stays with that page until you delete the page.
We use that summary only to suggest pages, tests, and missing information to you (our suggestion planner) and to write your pages, with the help of the AI providers described below. The suggestions can quote your search terms and ads; we keep them with your store. A test you queue from a suggestion is kept on that page until Evolve writes the experiment or you remove it from the queue. When Evolve writes or edits a page, it also reads your reports fresh, and those reads are not stored. Pages Evolve writes with these insights may echo the wording of your converting searches, and an experiment written from a test you queued keeps that test’s direction; those pages and experiments are your content and stay in your account until you delete them.
Disconnecting Google Ads, or deleting your store or account, deletes the summary along with the connection’s tokens and account details, removes the suggestions that cite the summary, and takes any test queued from one of them off the queue. Disconnecting also asks Google to revoke Evolve’s access, unless Google Ads is still connected on another of your stores. Images you import from Drive stay in your media library until you delete them; disconnecting Google Drive deletes that connection’s tokens and account details. You can also remove Evolve’s access at any time from your Google Account’s third-party access page.
Evolve’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In particular:
- We use Google user data only to provide and improve the features you can see in Evolve. We never use it for advertising, including retargeting or interest-based ads.
- We do not sell Google user data. We transfer it only as needed to provide or improve the features you see in Evolve (for example to the AI providers described below), for security purposes such as investigating abuse, to comply with the law, or as part of a merger, acquisition, or sale of assets — and in that case only after getting your explicit consent first. We never use or transfer Google user data for advertising (including retargeting, personalized, or interest-based ads), to determine credit-worthiness, or for lending.
- No person at Evolve reads your Google user data unless you ask us to (for example for support), it is needed for security, or the law requires it.
- We do not use Google user data, including data from Google Workspace APIs such as Drive, to develop, improve, or train generalized AI or machine-learning models.
AI processing
Page briefs, page content, and (for connected stores) product data are processed by our AI infrastructure providers to generate and improve your pages. Visitor analytics summaries (aggregate counts and rates, not visitor identifiers) are processed by the same providers to propose experiments. If you connect Google Ads, the headlines of your converting ads, your converting search terms, and the audience figures we compute from your reports are processed by the same providers to plan your suggestions and to write and edit your pages. Images in your media library, including any you import from Google Drive, are processed by our AI providers to describe what they show and, when they’re on a page, as pictures the AI looks at while writing, editing, and testing that page. Our AI providers process this data to return results to us; under our terms with them they may keep it briefly for abuse monitoring, and they do not use it to train their models.
How we use data
- Provide the service: page generation, analytics, experiments, attribution.
- Billing, account management, and support.
- Security, abuse prevention, and service improvement.
We do not sell personal data, and we do not use your visitors’ data for advertising or cross-site profiling.
Cookies and local storage
- Dashboard — strictly-necessary cookies for authentication and account context. No advertising cookies.
- Published pages— a variant-stickiness value and the pseudonymous analytics identifier, stored in the visitor’s browser so experiments stay consistent between visits. No third-party advertising cookies. As the publisher of your site, you are responsible for any visitor-consent requirements that apply to it.
Sharing and subprocessors
We share data only with service providers that help us run Evolve: cloud hosting, database hosting, analytics processing, authentication, payment processing, AI model providers, and — when you connect one — your commerce platform, ad platform, or content library. Each processes data only to provide its service to us. A current list of subprocessors is available on request at support@evolvepages.com. We may also disclose data when required by law.
Retention
- Account data — kept for the life of your account, then as required for legal and tax purposes.
- Visitor analytics and attribution events — kept while your account is active; deleted within 90 days of account closure or a verified deletion request.
- Store connection credentials— deleted when you disconnect the store, and automatically on the platform’s post-uninstall redaction schedule.
- Ad account connections— the access tokens, the account list, and the 90-day ad summary we compute are deleted when you disconnect, delete the store, or close your account, and so are the suggestions that cite the summary. While you stay connected, the summary is replaced about once a week. Disconnecting also asks Google to revoke Evolve’s access, unless Google Ads is still connected on another of your stores. The raw ad reports are never stored.
Security
Data is encrypted in transit (TLS) and at rest. Access tokens for connected stores and services are additionally encrypted at the application layer (AES-256-GCM). Access to production systems is limited to those who need it to operate the service.
Your rights
You can request access to, correction of, export of, or deletion of your personal data by emailing support@evolvepages.com. We honor these rights for everyone where feasible, not only where the law requires it. If you are a visitor to a page published by one of our customers, that customer is the controller of your data — contact them first; we support their obligations as their processor.
International transfers
Data is processed and stored in the United States.
Children
Evolve is not directed to children under 13, and we do not knowingly collect their data.
Changes
We will post any changes to this policy here and update the effective date. Material changes will be announced in the product or by email.
Contact
Questions or requests: support@evolvepages.com