Privacy Policy
Urlaunch analyses a website you submit, measures where it appears in search compared with the business rivals you choose, proposes changes ranked by the visits they should bring, and prepares search and social ad campaigns. If you connect your ad accounts, it creates the campaigns you approve and turns them on or off when you tell it to. In this policy, "we" and "us" mean Urlaunch. Questions and requests: privacy@urlaunch.com.
Anyone with a Google account can sign up. Urlaunch is in early access, so its features and this policy can change.
What we collect
- The website you submit. Its URL and the public pages we fetch from it: text, titles, headings and links. We never sign in to a website or fetch pages behind a login.
- Business rivals' public pages. When you choose business rivals, up to 25 public pages of each rival's website (respecting its robots.txt): titles, headings, text and links.
- Analysis results. The business profile, queries, market map, coverage and gaps, content plan and ad plans generated from those pages.
- Search Console data. When you connect Google Search Console (read-only) and agree to Urlaunch storing it, the list of properties your Google account can read and, for the site you analyse, its queries, pages, clicks, impressions and average positions for the last 56 days, read again every Monday until you delete the stored data or disconnect. We also receive your email address from Google.
- Google Analytics data. When you connect Google Analytics (read-only), the list of properties your Google account can read with their web addresses and, for the property of the site you analyse, each day's sessions, key event rate and revenue by channel, landing page and campaign over the last 180 days. We also receive your email address from Google. Matomo or Plausible, when you enter their key instead, give the same for their own data.
- Revenue cohorts. If you set up a Stripe or Shopify revenue feed, we use payment times, amounts, refunds, currency and the campaign tags available for the purchase. We turn the provider's payment and customer identifiers into site-specific codes so repeat purchases can be counted. The cohort records do not store names, email addresses, card numbers, addresses, raw provider identifiers or ad click identifiers.
- Ad platform connections. When you click Connect and approve access on a platform (Google, Meta, Microsoft, TikTok, LinkedIn, Pinterest, Reddit or Snapchat), the platform gives us an access token and, where it offers one, a refresh token. We also receive your name or email as the platform returns it, and the IDs and names of the ad accounts and Pages you granted.
- Campaign records. The campaigns, ad sets, ads and budgets created on your instruction, their platform IDs, and the actions you took (validate, create, go live, pause).
- Optional Meta conversion forwarding. When a site owner enables this and a visitor has agreed to advertising measurement, the site's server can send a confirmed outcome to the owner's Meta Pixel through Urlaunch. We forward the event name, time and opaque event ID, the approved outcome URL, the browser's user agent and Meta browser or click identifiers, and an amount and currency where applicable. We use a hashed event receipt to prevent duplicate sends and do not store the browser identifiers or user agent. The site's advertising consent controls whether it sends an event.
- Your account. When you sign up with Google, your email address and name as Google returns them, and when you signed up.
- Your progress, if we invited you personally. During early access we invite some site owners by a personal link. If you received one, we keep the name and email address we invited and when the link's page was opened in a browser. Once you accept it, we also keep the Google account that accepted it and the first time each of these happened: you signed up, an analysis finished, you connected Search Console, you approved an action, and you came back in a later week. Only Urlaunch's operator sees this, one row per invited person, to learn where the product loses people and whom to help. We do not share it with anyone or use it for advertising. If you sign up without an invitation, no such row exists for you.
- The ad click that brought you, if any. When you reach urlaunch.com from one of Urlaunch's own Google ads, the link carries a click identifier Google adds to it (gclid, gbraid or wbraid). Your browser keeps it for that visit only. If you then sign up, we keep it with your account and send it, with the time you signed up, to Urlaunch's own Google Ads account, so that Google counts the ad click as a sign-up. We send Google nothing else about you. urlaunch.com sets no cookies and loads no analytics or advertising tags.
- Page views on urlaunch.com. Each page you open sends Urlaunch's own server the page's address, the name of the site that linked to it (such as google.com) and whether an ad brought you. We add one to that day's count for the page and keep nothing else: no cookie, no IP address, no browser details, nothing that tells one visitor from another.
We do not collect payment card details. You pay ad platforms directly through their own billing.
Data we receive from Meta
With your permission, Urlaunch uses ads_management, ads_read,
business_management, pages_show_list and
pages_read_engagement to:
- list the ad accounts and Pages you granted, so you can choose where a campaign runs;
- create the campaigns you approve, paused, with the Page you chose as the advertiser;
- turn those campaigns on and off when you ask, including through the kill switch;
- read their status and results to report them back to you;
- verify the selected Pixel and forward consented outcomes when you enable this for your site.
We use Meta data only for these purposes. We do not sell it, use it to profile people, share it with other advertisers, or send it to AI model providers.
Data we receive from Google
With your permission, Urlaunch uses the Google Search Console scope
webmasters.readonly to measure how your site appears in Google results and rank the
changes worth the most visits, the Google Analytics scope analytics.readonly to judge
changes made to your pages against your site's own visits before and after, and the Google Ads scope
adwords to list your ad accounts, check their billing, advertiser verification and
conversion tracking, create the campaigns you approve, turn them on and off, and read their status
and results.
Urlaunch'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 do not sell Google user data, use
it for advertising to you, or let people read it except to operate Urlaunch, for security, or where
the law requires it.
How we use data
To produce your analysis, to create and control the campaigns you approve, and to show you the results. We do not sell personal data and do not use it to advertise to you.
Who processes data for us
- Anthropic provides the AI model that reads the public pages of the submitted website and of the rivals you choose, and writes the analysis, suggestions and ad text. It receives page text and analysis context. When your site's Search Console data is stored, it also receives the text of its search queries, without clicks, impressions or positions, to sort them by how relevant they are to your business; and when Urlaunch drafts a change to one of your pages (for example a new title), that page's own Search Console queries. It never receives your ad platform tokens, your ad account data, your Google Analytics data or other sites' Search Console data.
- OpenAI and Perplexity, when AI-answer measurement is enabled, receive questions built only from public sources (your site's and rivals' public pages, search autocomplete and Wikidata), never Search Console or ad account data.
- DataForSEO, when enabled, returns search volumes and rankings for queries, including your rivals' positions. It receives queries, domains and the target country.
- The ad platforms you connect receive the campaigns you approve, and process them under their own terms.
- Google Ads, for Urlaunch's own ads, receives the click identifier and sign-up time described above.
Storage, security and retention
- Tokens are encrypted at rest with AES-256-GCM. All calls to ad platforms and Google use HTTPS.
- Query lists are turned into embeddings by a model that runs on Urlaunch's own server; they are not sent to an embeddings provider.
- Tokens are kept until you disconnect the platform; disconnecting deletes them at once.
- Search Console data is kept for at most the six most recent measurements of each site, and is deleted within 30 days of your request.
- Analyses, rivals' pages and campaign records are kept until you ask us to delete them.
- Disconnecting a revenue feed deletes its provider credentials and stops new collection. You can erase the stored cohort history in Urlaunch.
- A personal invitation that is never accepted is deleted 90 days after it expires. An accepted one, with the progress shown for it, is deleted with your account, or earlier if you ask.
- An ad click identifier is deleted once Google Ads has counted the sign-up, and after 90 days at the latest.
Your choices and rights
- Disconnect any platform in Urlaunch at any time, and remove Urlaunch's access in that platform's own settings.
- Ask us by email to see, correct or delete your data. We answer within 30 days.
- If you are in the EU or UK, you also have the rights the GDPR gives you, including the right to complain to your data protection authority.
How to delete your data: data deletion instructions.
Children
Urlaunch is not intended for anyone under 18.
Changes
When this policy changes, we update this page and its effective date.