Skip to content
Legal

Privacy policy

Last updated: 19 November 2026

What AuditRoger collects, why, who processes it for us, how cookies are used, and how to see, change or delete your data.

1. Who we are

AuditRoger is owned and operated by Roger Tech LLC, a Wyoming limited liability company based at 1309 Coffeen Avenue, STE 1200, Sheridan, Wyoming 82801 (“we”, “us”, “our”). We decide how the personal data described here is used, except for the information about other people that you add to AuditRoger, which we handle on your behalf (see section 3). Privacy questions go to hello@auditroger.com, and you can call us at +1 (307) 445-3601. Roger Tech LLC also operates “AuditRoger Social Studio”, its LinkedIn content tool, which this policy covers.

2. What we collect

  • Your account. Your email address and name, when you confirmed the address and, if you sign in with a password, a one-way hash of it, never the password itself. We also keep your plan, credits and team, and any API keys you create, stored as a short prefix and a hash rather than the key. If you sign in with Google, Google shares your name, email address, whether Google has verified it and a link to your profile picture, which our sign-in provider Supabase keeps for sign-in. Signing in with Google gives AuditRoger no access to your Google Ads or Google Analytics accounts, and we never see your Google password. If you turn on two-step sign-in, our sign-in provider keeps your authenticator app's secret; we keep only whether it is on for your account and when it was turned on, off or reset. A workspace owner can require it of their teammates, and can see which of them have turned it on.
  • Connected ad accounts. The ID and name of each Google Ads, Google Analytics, Meta or Amazon Ads account you connect, and the access tokens the platform issues, which we encrypt before storing. With them we read campaigns, ad groups, ads, keywords, search terms, conversion settings and performance figures, and we keep the audits and reports built from that data. For Google Ads, we also read the account's change history: what changed, when, and whether a person, an automated rule, a script or Google made the change. We don't keep the email addresses of the people who made changes: each one is replaced by “Editor 1”, “Editor 2” and so on. If you change the brand words for a Google Ads account, we keep them with the account to split its results into brand and other searches. If you save a selection of campaigns or ad groups to audit again, we keep its name and the IDs and names of the campaigns or ad groups in it, or the campaign type, label or words you chose them by, with the account, until you remove it or the account. If you mark a kind of finding as an accepted practice for your workspace, or for one of your clients, we keep that choice, your reason and who set it, and show matching findings as accepted on later audits of those accounts. We also read how Google rates your landing pages (speed and mobile-friendliness), the sites, apps and content your account excludes, your experiments, your account budget (its spending limit, how much has been spent against it, and its start and end dates, but not its name, notes or purchase order number), and, for Shopping, each product's status and results. For Google Ads accounts that advertise products, we also read the results of each product (its ID, title, brand and type, and what it cost and earned), to show which products spend without selling. For Google Ads, we also read Google's own estimates of what a campaign that is limited by its budget, or bids to a target, would get with a different budget or target. For Google Ads and Meta audits, we keep the account's daily totals of spend, impressions, clicks and results for the audited period (at most its last 365 days), to draw its trend. For Google Ads, we also read how Google's Quality Score for your 50 top-spending keywords, and its three parts (expected click-through rate, ad relevance and landing page experience), changed week by week over the last 13 weeks. For a Google Analytics property, we read its settings, including its data streams, key events and the rules that create them, attribution and reporting-identity settings and calculated metrics, and the notes your team adds to its reports, with their dates. For a Google Analytics property, we also count the page views whose addresses look like they carry an email address, a phone number or a name, to warn you that personal data is reaching Google Analytics. Google returns only those counts; we never receive or keep the addresses. For a Google Analytics property with e-commerce, we read purchase transaction IDs only to count duplicate and blank ones; we don't store or show them. If you switch on monitoring for a Google Analytics property, we read its visits and key events for each of the last 16 days once a day, to tell you when tracking stops or traffic falls sharply. When you audit a Google Ads account and you have also audited a Google Analytics property linked to it, or you monitor one for the account's client, we read that property's visits, engagement and key events for each landing page from that account's ads during the audit's dates, to show what visitors did on the pages you pay for. That property is one you audited in the last 90 days whose audit lists the link to the Google Ads account, or else the one Google Analytics property you monitor for the account's client. We read each landing page's path only, never the rest of its address. If you make a client report for a Google Analytics property, we read the property's visits, users, key events and revenue by channel, by campaign and by landing page, and, for an online shop, the products sold with their revenue and units, for the report's period and the period it is compared with, and show them in the report and send them to the recipients you choose. We read each landing page's path only, never the rest of its address. If you add the 13-month trend to a client report, we also read the account's or property's monthly totals for the 13 calendar months up to the day the report ends, and show them in the report. If you add account activity to a client report for a Google Ads or Meta Ads account, we also read that account's change history for the report's period (for Google Ads, at most the last 30 days) and show how many changes were made to campaigns, budgets, bids, keywords, ads and targeting, and for Google Ads whether a person, an automated rule or tool, or Google made them. For the report, we never read or show who made a change. A client report can also show the account's latest audit score, how it changed since the audit before, how many findings were marked fixed in the period and how many from the latest audit are still open, from the audits you have already run. When a client report's share link is opened, we record when it was first opened in each period, not who opened it, their IP address or device, and we can email you that it was opened. If you add “Where the ads ran” to a Meta Ads client report, we also read the period's results for the whole account split by platform and placement (for example Instagram Stories) and by age group and gender, as totals Meta has already added up.

    For a Meta ad account, we read its campaigns, ad sets and ads with their settings and results, including who each ad set targets (countries, age range, gender, and how many custom audiences and interests it uses), how many people it reached and how often, and Meta's totals by age band, gender, country, placement, device and hour of the day: totals for each group, never the people in them. We also keep the ID Meta gives your Facebook login for AuditRoger, so that disconnecting Meta in one AuditRoger workspace doesn't remove access that another of your workspaces still uses. For a Meta ad account, we also read its status and any spending limit; its brand safety content filter levels, the setting that decides how careful Meta is about the content your ads appear next to; why Meta has paused, limited or rejected an ad or ad set (Meta's reason codes, not the wording of its review); each ad set's learning status and what it optimises for; the account's activity history (what changed and when), where each person who made a change is replaced by “Editor 1”, “Editor 2” and so on (we don't keep their names or Facebook IDs); Meta's own recommendations for the account and its Opportunity Score; the health of your Pixels, datasets and custom conversions (when each event last arrived and whether it came from browsers or from your server, not the visitors behind those events); your custom audiences' names, types, approximate sizes and status, never the people in them; for ads that mix several headlines, texts, images or videos, how each one performed, with the first 125 characters of each text; how much of an Advantage+ sales campaign's spend reached existing customers rather than new ones (Meta's totals, never the people); and the links and tracking parameters your ads use. To check that those pages work, our server visits up to ten of them for each audit, as AuditRoger's link checker, and keeps only whether each loaded, where it redirected and how fast. For the images in your live Meta ads, we also read each image's width and height, to check that it fits the placements it runs on. We don't keep the images. When you open an ad's preview in a report, Meta shows it directly and we don't store it.

  • TikTok Ads. Connecting a TikTok Ads account gives us its advertiser ID and name and the access token TikTok issues, which we encrypt before storing. With it we read the ad account's status and balance, and your campaigns, ad groups and ads with their settings and results, including your results by day and by hour and TikTok's totals by age band, gender, location, placement, operating system, interest category, language and device brand, and your list of audiences: each audience's name, type, size and status, TikTok's breakdown of each audience by age band, gender and interest, given as shares, and TikTok's estimate of how far your audiences overlap. We receive only those details, not the people in an audience or in any of those totals, and we never upload customer lists to TikTok. For lead ads, we read how your Instant Forms perform: how many times each form was opened and submitted, how many submissions TikTok filtered out, and what each lead cost. These are totals: an audit never receives the people who filled in a form or their answers. We also read the videos, images and text your ads use, with their results, to spot creatives that have stopped performing: each video's name, size, length and format, how many viewers stayed and left at each second, TikTok's comparison of your ads with similar ads, its creative fatigue flags, what each creative did inside Upgraded Smart+, week by week, and which of its ad texts and calls to action did best, and whether an ad or a Smart+ creative passed review and why not. We also read the website address each ad links to, with its tracking parameters. To check that those pages work, our server visits up to ten of them for each audit, as AuditRoger's link checker, and keeps only whether each loaded, where it redirected and how fast. If your TikTok ads show in TikTok search results, we also read the search terms that showed them, with their spend and results. We also read your Pixel and conversion event setup, such as which events are set up and whether TikTok is receiving them, how many of each event it counted from browsers and from servers, and your Custom Conversions and apps, to check that conversions are tracked. We don't receive the individual visitors those events record. We also read TikTok's diagnosis of your ad groups, including its estimates at other bids and budgets; your automated rules, their settings and how they last ran; your GMV Max results and the names of the TikTok Shops you can use with it; and your change log, keeping when something changed, what it was and where the change was made from, and counting how often leads were downloaded or a form was connected to a CRM. We don't keep who made it. If you make a TikTok Ads client report, we read that account's spend, impressions, clicks and conversions for the report's dates, per campaign and per day, the account's name and currency, and how many leads your Instant Forms and website forms collected: counts only, never the people who filled in a form or their answers. If you switch on monitoring for a TikTok Ads account, we also read each of its campaigns' spend, impressions, clicks, conversions and purchase value once a day, for the last 14 days and, if you set a monthly budget, for the month so far, to send you alerts, and we run its audit on the 1st of each month.
  • LinkedIn Ads. Connecting a LinkedIn ad account gives us its ID, name and currency and the access tokens LinkedIn issues, which we encrypt before storing. With them we read your campaign groups and campaigns with their settings, including who they target, and results (impressions, clicks, spend, conversions, lead form opens, leads and approximate reach); the name, status and review status of each ad, with its results; for the ads that spend most, each ad's format, how long its text is, its button label and the website it links to; your conversion setup and when each conversion and your Insight Tag last reported; your list of audiences: each audience's name, type, status and approximate size; for each Lead Gen Form your ads use, its name, status and review status and how many questions and hidden fields it has, but not the wording of its questions or anyone's answers; and LinkedIn's estimates for your largest campaigns: their approximate audience size, suggested bid range and minimum daily budget. We also read how many results each of your LinkedIn conversions recorded. We also read LinkedIn's approximate breakdowns of who your ads reached by job seniority, job function, industry, company size and job title: totals for each group, never individual members, and never where they are or which company they work for. We receive counts, not the people behind them: not the members of an audience, and not the people who fill in your lead forms, unless you turn on lead sync once it is available (see section 4). We don't keep the text or images of your ads. To check that the pages your LinkedIn ads link to work, our server visits up to ten of them for each audit, as AuditRoger's link checker, and keeps only whether each loaded, whether it redirected to another site and how fast, with the page's domain. We also note whether each ad's link carries tracking parameters, never the parameters themselves. When you open an ad's preview in a report, LinkedIn shows it directly and we don't store it. If you switch on monitoring for a LinkedIn ad account, we also read each of its campaigns' spend, impressions, clicks, website conversions, Lead Gen Form leads and conversion value once a day, for the last 14 days and, if you set a monthly budget, for the month so far, to send you alerts, and we run its audit on the 1st of each month. If you make a LinkedIn Ads client report, we read that account's spend, impressions, clicks, landing page clicks, website conversions, conversion value and Lead Gen Form lead counts for the report's period and the period it is compared with, per campaign and per day, with each campaign's name and status and the account's name and currency. A LinkedIn Ads client report never has a public link or an AI summary.
  • Microsoft Advertising, once it opens. Microsoft Advertising audits aren't available to customers yet. When they are: if you connect a Microsoft Advertising account, we receive its ID, the ID of the manager account it sits under, its name, currency and time zone, and the tokens Microsoft issues, which we encrypt before storing. With them we only read your campaigns, ad groups, ads and their ad strength, keywords and their Quality Scores, search terms, negative keywords and where they block your keywords, budgets, bid strategies, conversion goals, whether your UET tags are receiving data, whether Microsoft applies recommendations to the account by itself, and any import from Google Ads set up on the account and its results. With your Microsoft Advertising account connected, we also read Microsoft's own recommendations for it and its estimates of their effect (we never apply or dismiss them), its explanations of sudden changes in your results, its estimates of results at other budgets, how often your ads showed, and showed at the top of the page, out of the times they could have, your results by country, region, device and by the websites and apps where your ads appeared, and the account's change history (what changed and when, never who made the change). We also read Microsoft's auction insights for the account and its five top-spending campaigns: the website domains of other advertisers in the same auctions and how often their ads appeared alongside or above yours. These are businesses, not people, and we never combine them across customers. They stay in your audit: we don't log them, share them by link or send them anywhere else. With each audit we also read the account's structure: campaigns, ad groups, keywords and whether Microsoft approved them, ad text (only to count headlines and descriptions, see which are pinned and how Microsoft rates each; we don't keep it) and extensions, negative keywords including shared lists, audiences (names, types and sizes, never the people in them), Shopping products, Performance Max asset groups, your Microsoft Merchant Center stores (whether each is active and has a catalog), experiments, and targeting settings such as locations and ad schedules. We also read your results by audience and by Shopping product, and the search terms of your Dynamic Search Ads. We also read the account's tracking settings (auto-tagging, tracking templates and URL suffixes, view-through conversion settings), whether Microsoft reports a billing problem on it (never your payment details), how many offline conversions you uploaded and how many Microsoft accepted or rejected each day (counts only, never the uploaded files), and any data exclusions or seasonality adjustments. We also read the role your Microsoft sign-in has on the account, to tell you whether it can only view. We never change anything in the account, and we don't keep the names or email addresses of the people on it. If a client in AuditRoger has both a Google Ads and a Microsoft Advertising account, we compare their campaign settings using the audits already stored in your account, to show where the two differ. For this, a Microsoft Advertising audit keeps each campaign's name, status, type, daily budget, bid strategy and spend, the share of its impressions lost to budget, and whether an import from Google Ads updates its bids or budgets. If you add a Microsoft Advertising account to a client report, we read that account's spend, impressions, clicks, conversions and revenue for the report's dates, per campaign and per day, and per campaign for the period it is compared with, with each campaign's name, status and type and the account's currency, to build the report. Microsoft Advertising client reports have no public share link and aren't written by AI: you send them to your client as a PDF, by download or on a schedule. If you turn on monitoring for a Microsoft Advertising account, we read its results and settings once a day to send you alerts by email: each campaign's spend, impressions, clicks, conversions and revenue for the last 14 days and, if you set a monthly budget, for the month so far; whether the account and its campaigns can run and whether Microsoft reports a billing problem (never your payment details); whether your UET tags and conversion goals are recording; and whether Microsoft applies recommendations to the account by itself. When a spend, cost or conversion alert fires, we may also read Microsoft's own explanation of changes in the account's results over the last 7 days, as an audit does. To tell what changed since the day before, we keep only each tag's, goal's and auto-apply setting's status with the account's monitoring settings. We also run its audit on the 1st of each month. Microsoft Advertising alerts aren't posted to Slack, Teams or webhooks. Microsoft Advertising data is not sent to an AI provider, can't be shared by public link and isn't available through our API. When you disconnect, we delete the tokens straight away, and the account's audits are deleted on the same 12-month rule as Meta Ads, TikTok Ads and Amazon Ads. You can also remove our access at account.live.com/consent/Manage (personal Microsoft accounts) or myapps.microsoft.com (work or school accounts).
  • Monitoring and alerts. If you switch on monitoring for an ad account, we also check once a day whether its ads can still run: the account's status, any spending limit, budget or balance, and which of its ads were rejected, so we can tell you the same day when they stop. We also check once a day when its conversion tracking last reported: when each Google Ads conversion action, Meta Pixel or dataset, TikTok Pixel event and LinkedIn conversion or Insight Tag last received data. We read only these dates and counts, never the visitors behind them. When a monitored Google Ads account's conversions drop and its client has a monitored Google Analytics property, we also read that property's sessions and key events from Google Ads clicks for the same two weeks, to tell you whether the drop shows in Google Analytics too. If you give a monthly budget for a monitored ad account, we also read its spend for the month so far once a day and compare it with that budget, to tell you when it is likely to overspend or underspend. We keep the budget you enter with the account's monitoring settings. If you have made a client report for the account with a spend target, we start from that target until you enter a budget of your own. We keep the latest month-so-far figure we compared with it, for the Monitoring page. If you give a client a monthly budget, we also read the month-so-far spend of each of that client's monitored ad accounts once a day, add up the accounts in the same currency and compare the total with that budget. We keep the budget and the latest total with the client, and each account's month-so-far spend with its monitoring settings. If a monitored account has neither a budget of its own nor a client report spend target, we start from the monthly budget in its pre-flight questionnaire. For monitored Google Ads and Meta Ads accounts we also read the end date of each campaign or ad set that is running, so we can tell you a few days before one that is spending stops. If you switch on monitoring for a Google Ads or Meta Ads account, we also read its change history once a day: what changed the day before, when, and whether a person, an automated rule, a script or the platform made it, so we can tell you about large changes the same day. For Google Ads we check whether the person who made a change is a member of your workspace and keep only that yes or no, never their email address. If you switch on monitoring for a TikTok Ads account, we also read its change log once a day: what changed the day before and when, never who made it, so we can tell you about large changes the same day. If you switch on monitoring for a Meta Ads or TikTok Ads account, we also read its ads' results week by week, once a week, to tell you when an ad that spends is wearing out. If you switch on monitoring for a Google Ads, Meta Ads or TikTok Ads account, our server also visits up to ten of the pages its ads link to once a day, as AuditRoger's link checker, taking the pages from the account's latest audit, and keeps only whether each loaded, where it redirected and how fast, so we can tell you the same day when a page stops working. If you switch on monitoring for a Google Ads account, we also read its search terms once a week, to list the searches that cost money without a conversion and suggest negative keywords. We keep that week's list with the account's monitoring settings until the next week's replaces it. If you turn on the weekly summary, we email the workspace owner once a week with each monitored account's results for the last 7 days, the alerts it raised and its latest audit score. You can turn it off in Settings. For monitored Google Ads and Meta Ads accounts we also read, once a week, the platform's own score for the account (Google's optimisation score or Meta's Opportunity Score), the kinds of change it recommends and the campaigns its budget suggestions name, to show them in the weekly summary. We keep only the score and the kinds of change, with the account's monitoring settings, to compare them with the next week's. If someone in your workspace assigns you a finding, we email you its title, its account and when it is due, and on Mondays a list of your tasks due that week; for TikTok Ads, LinkedIn Ads and Microsoft Advertising findings, we email only that a task is due. You can turn these emails off in Settings. If you connect a Slack or Microsoft Teams channel, we post your Google Ads, Meta Ads and Google Analytics alerts to it: the account's name and what the alert says. We never post TikTok Ads, LinkedIn Ads or Microsoft Advertising data there. Slack or Microsoft keep those messages under their own terms, and we keep the channel's webhook address encrypted until you remove it. If you add a webhook address of your own for alerts, we send it the alerts for your Google Ads, Meta Ads and Google Analytics accounts: the account's name, the platform and what the alert says, signed so your system can check they came from us. We store the address encrypted. TikTok Ads and LinkedIn Ads alerts are never sent to a webhook. If you choose to, your webhook also receives a short summary when a Google Ads, Meta Ads or Google Analytics audit finishes (never an audit of chosen campaigns), or when a scheduled client report for one of them is emailed. For an audit, that is the account's name, the platform, its score and grade, the change since the audit before, the number of findings, how many are new, how many of those are critical and how many were fixed. For a report, it is the account's name, the platform, the period and how many people it went to. Each has a link to it in AuditRoger, which needs a sign-in. Your webhook never receives the findings themselves, a share link or a recipient's address. If you choose a teammate for a client, we also email them that client's alerts: what each alert says for Google Ads, Meta Ads and Google Analytics, and for TikTok Ads, LinkedIn Ads and Microsoft Advertising only that an alert was raised. If you choose a teammate for a client, we can also email them, once a week, the weekly summary for that client's monitored accounts: for Google Ads, Meta Ads and Google Analytics each account's results for the last 7 days and the alerts it raised; for TikTok Ads, LinkedIn Ads and Microsoft Advertising only how many alerts were raised. They can turn it off in Settings. When you ask us to check a finding again, we read only what confirms the fix: for a broken landing page, our server visits the page again as AuditRoger's link checker; for Google Ads, when each conversion action last received data or whether auto-tagging is on; for Meta, when a Pixel last received an event. We keep only whether the problem was fixed and when we checked.
  • YouTube channels, once YouTube channel audits open. YouTube channel audits aren't available yet. When they are, you name a YouTube channel by its link, @handle or channel ID, and tell us whether it is yours (or a client's you manage) or someone else's. We read that channel's public information through YouTube API Services: its name, handle, description, keywords, country and public counts of subscribers, views and videos; its public playlists; and, for up to 200 of its most recent public videos, the title, description, tags, publish date, length, caption and picture quality settings, thumbnail sizes, and public view, like and comment counts. Nobody signs in to YouTube, so we receive nothing from anyone's Google account and nothing that isn't public, and we receive nothing about the people who watch. Some parts of the audit stay off until Google has accepted them. When they are on, we also read the public page and recent videos of other channels you name to compare; the top search results for keywords you name, or for the channel's main topics; and public comments on up to 10 of the channel's most-viewed recent videos. From a comment we keep its words and its like and reply counts, never who wrote it, and we don't try to work out anything about the person writing. For a channel you say is yours or a client's, we also check whether the links in its descriptions work; and if you choose a Google Ads account or GA4 property you have connected, we read that account's results for each video and that property's visits from YouTube, for the last 30 days.
  • LinkedIn profile audits. If you run a LinkedIn profile audit, you upload the PDF that LinkedIn's Save to PDF makes of a profile, and you can add a target role, an industry, a goal and the profile's address. We read the PDF and don't keep the file. What we read from it (the name, headline, location, About section, roles with their dates and descriptions, education, top skills, languages and certifications) is kept only until the audit finishes, or 24 hours if no audit is run. We don't keep the email addresses or phone numbers the PDF shows, and we only count honours, publications and patents. The report keeps what it shows: the name, the headline, the opening of the About section, each role's title, company and dates, top skills, education, certifications, languages and the profile's address, with the findings and suggested rewrites. We never connect to LinkedIn or open the profile's address to do this.
  • Ad library searches. A search you make in the competitor ad library (the words, Facebook Page ID or Ad Library link you type, and the country you choose) is sent from our server to Meta's Ad Library API with AuditRoger's own access token, and we show you the public ads Meta returns. You don't connect a Facebook account or grant any permission for this, so nothing is sent from your Facebook account. We don't keep your searches or record what you searched for, and we don't keep the ads a search shows you unless you save one. These ads are public information that Meta publishes in its Ad Library. Links to an ad or a search in Meta's Ad Library open Meta's own website, where Meta's privacy policy applies.
  • Ads you save from the ad library. When you save an ad, we keep its Ad Library ID and link, the advertiser's Facebook Page name and ID, the dates it started and stopped running, the platforms it ran on, the first 500 characters of its text and its headline, Meta's figure for how many people it reached in the EU and UK, the country you searched, and your notes and board name. We keep them until you delete the saved ad or your account is deleted. We don't keep the ad's images or videos, who paid for it, or who it was shown to.
  • Tags on saved ads. You can add up to five tags of your own to a saved ad. We keep them with the saved ad, for as long as it is kept.
  • Advertisers you follow in the ad library. On the plans that include it, you can follow an advertiser. We keep its Facebook Page ID and name, the country you follow it in, when you followed it and when we last checked it, and the Ad Library IDs of its ads we have already seen, so we can tell which ads are new. We don't keep those ads' text, images, videos or anything else about them. Once a week our server makes one request to Meta's Ad Library API for each advertiser you follow, with AuditRoger's own access token, to find the ads it started since the last check. When you open the list of advertisers you follow, we ask Meta for their new ads at that moment and show them to you without keeping them.
  • The weekly ad library email. If your workspace follows advertisers, we email its owner once a week. For each advertiser that started new ads, it says how many started and shows up to three of them: the advertiser's name, the first line of the ad's text, the date it started and a link to the ad in Meta's Ad Library. We don't send it in a week with nothing new. It is on from your first follow, and you can stop it at any time with the link at the bottom of the email, which works without signing in, or on the Following page of the ad library.
  • Advertiser analysis and comparisons. When you ask for an analysis of an advertiser, or compare two or three, our server reads up to 100 of each advertiser's active ads from Meta's Ad Library API at that moment and works out the figures you see: how many ads are running, how many are new, which have run longest, where and in which languages they run, when they started and an estimated spend range. We work them out each time you ask and don't keep the ads or the figures.
  • Links to other ad libraries. Beside a search, buttons open the same brand in Google's Ads Transparency Center, TikTok's Ad Library, LinkedIn's Ad Library and Meta's own Ad Library, in a new tab, with the brand or website you typed in the link. Neither our server nor the page fetches anything from those sites, and their own privacy policies apply there.
  • Landing pages. The addresses of the landing pages your ads send people to, which we test for speed. To show how fast the pages your Meta, TikTok and LinkedIn ads link to load for real visitors, and a page your Google Ads link to when Google's PageSpeed test of it takes too long, we send up to ten of their addresses for each audit, without the part after any question mark (for LinkedIn Ads, only the site's address), to Google's Chrome UX Report API, using AuditRoger's own key, and keep the speed figures it returns.
  • Uploaded reports. Amazon reports you upload (search term, placement, advertised product and budget reports) are read for the audit and not stored.
  • Information about other people that you add. Leads you enter or import for client reports (a name, a phone number or email address, the date, form, channel, status, value and notes); the name and email address of a client you send a pre-flight link to, and their answers; the email addresses you schedule reports to; and the email addresses of team members you invite. We encrypt lead names, contact details and notes before storing them. Once lead sync is available, if you turn it on for a client report, the leads people send through your LinkedIn Lead Gen Forms are added the same way: their name, contact details and answers to the form.
  • Payments. Stripe takes payment. While your account exists we keep your Stripe customer ID and a record of what you bought. Card details stay with Stripe and never reach us.
  • Usage and technical data. A record of events on your account, such as payments, refunds and credit changes, and the IP address of each request, which we use to limit how often sign-in and other actions can be tried. Our hosting providers also keep technical logs of requests. The owner of a workspace can see what its teammates did in AuditRoger in the last 90 days, such as running an audit, marking a finding done or muting an alert, with their names but not their email addresses. The owner can also see how quickly each teammate closes the tasks assigned to them, and how many are overdue.
  • Analytics, only if you agree. If you choose Accept analytics, Google Analytics records the pages you visit and how you use the site. See cookies and local storage.
  • LinkedIn, if you connect it. Your LinkedIn member ID and basic profile (name, headline and profile photo link), and the access tokens LinkedIn issues, which we encrypt before storing; the posts, comments and replies we publish for you, and their IDs; statistics for your own posts and for the Page you manage (impressions, members reached, reactions, comments, reshares, saves, sends, link clicks, profile views and followers gained); and, to let you answer them, the comments other members leave on those posts, with the commenter's name and member ID.

3. Why we use it, and our legal bases

  • To provide AuditRoger (performing our contract with you). Running audits and client reports, Roger AI, team seats and the API; billing; and the emails the service sends, such as the link to confirm your email address, alerts, scheduled reports, invitations, password resets and billing notices.
  • To keep it secure and working (our legitimate interests). Rate limits and preventing abuse, investigating errors, and understanding from our own records how the product is used (such as sign-ins, audits run and errors) so we can improve it. Those records don't include the data in your ad accounts, which we use only to provide your own audits and reports.
  • Analytics (your consent). Google Analytics runs only if you accept it, and you can withdraw that consent at any time.
  • To meet legal obligations. Responding to lawful requests (see Requests from public authorities, in section 5). Invoices and payment records are kept by Stripe, which processes our payments.

Information about other people that you add (leads, pre-flight answers, report recipients, team invitations, and a LinkedIn profile you audit that isn't your own): you decide what goes in and why, and we process it on your behalf to provide the service. You need a lawful basis to share it with us, and you should upload someone else's LinkedIn profile only with their permission. Someone whose details a customer has added can contact that customer, or us, and we'll help.

Public YouTube channel data about a channel that isn't yours is processed on the basis of legitimate interests: yours in learning from public channels, and ours in providing the audit. We use only what the channel shows publicly, keep it for less than 30 days (section 7), and delete it sooner if the channel's owner asks.

Public ads from Meta's Ad Library, including the name of the Facebook Page that ran them, are processed on the basis of legitimate interests: yours in researching advertising, and ours in providing the ad library. They are what Meta publishes for anyone to see, and we keep only the ads you save (section 7).

Advertisers you follow and the weekly ad library email are part of the service you ask for when you follow an advertiser (performance of a contract). You can stop the email at any time.

We don't sell personal data, use your advertising data for advertising, or use it to train AI models.

What you have to give us. To open an account we need your name, your email address and a password, or your Google sign-in. To buy a plan, Stripe needs your payment details. Connecting an ad account or uploading a report is your choice, but without one there is nothing to audit. Everything else is optional.

No automated decisions about you. Scores, findings and alerts describe your ad accounts. None of them is a decision that has legal or similarly significant effects on you.

4. Access to your ad accounts and LinkedIn

AuditRoger reads your advertising accounts. It never creates, changes, pauses or deletes your campaigns, ads or budgets, never combines one advertiser's data with another's, and never shows your data to anyone outside your AuditRoger workspace except where you choose to: a share link you create, a client report you send or schedule, a file you export, or our API with a key you create. AuditRoger Social Studio, our LinkedIn tool, is different: it publishes to LinkedIn, but only content you have approved. What each permission can do, and what we use it for:

  • Google Ads: Google's Ads permission (adwords) does not come in a read-only version, so Google's consent screen says an app with it could manage your campaigns. AuditRoger uses it only to read, and contains no code that writes to the Google Ads API.
  • Google Analytics: read-only access (analytics.readonly), which can't change your properties. Google asks for both Google permissions whenever you connect a Google account.
  • Meta: ads_read, to read your ad accounts and their results, and business_management, to see which business each ad account belongs to. Meta's business permission can also be used to manage a business; AuditRoger only reads with it. We do not request Meta's ad management permission.
  • Amazon Ads: you can upload a search term, placement, advertised product or budget report, which is read for the audit and not stored. If you connect an Amazon Ads account directly (not yet open to all customers), you sign in with Login with Amazon and grant Amazon's advertising permission (advertising::campaign_management). Like Google's, it has no read-only version; AuditRoger uses it only to read, and never changes: your advertising profiles; your Sponsored Products, Sponsored Brands and Sponsored Display campaigns, ad groups, ads, targeting and portfolios, with their settings and budgets; your budget rules and the last 90 days of changes to your campaigns; Amazon's own recommendations and its calendar of shopping events; and performance reports. We do not ask for your Amazon profile, and we never see your Amazon password, orders or payment details. Our AI provider never receives Amazon Ads data: an Amazon Ads audit's analysis is written from the audit itself, and Roger AI doesn't read it.
  • TikTok Ads: you connect a TikTok Ads account through TikTok for Business and approve AuditRoger's access. We ask only for TikTok's read permissions: Read ad account information; Read campaigns, Read Ad Groups and Read ads; Change log and GMV Max Store management; Read custom audiences; Read pixels and Pixel level reporting; Get creative report, Creative asset tagging report and Read video library; Read apps; Read automated rules and execution results; Read custom conversion; Get and adopt diagnosis suggestion, which we use only to read TikTok's diagnosis and never to adopt a suggestion; and its reporting permissions (Consolidated report, Ad insight report, Creative fatigue insight, GMV Max reports and Upgraded Smart+ report). AuditRoger uses them only to read, and none of the calls it makes can create, change or delete anything in your account. A few of these reads ask TikTok to prepare something first, such as a file of your change log or of a report, or the breakdown of an audience; preparing it changes nothing in your account either. It reads your account's status and balance, your results, the settings of your campaigns, ad groups and ads, how your ad creatives and Instant Forms perform, your audience list and its make-up, and your Pixel and event setup, so an audit can check why ads aren't delivering, creatives that have stopped performing, how your ads compare with similar ads, what your leads cost, retargeting, exclusions, lookalike audiences and conversion tracking. If you switch on monitoring for the account, the same read permissions are used once a day for its alerts and on the 1st of each month for its audit. Alerts are worked out by fixed rules, not by an AI provider. It never creates, changes or deletes your campaigns, ads, creatives, audiences or Pixels, never adopts TikTok's suggestions, and never uploads customer lists. TikTok's comparisons are read separately for each account and are never pooled with another account's data. We don't send TikTok Ads data to an AI provider: a TikTok Ads audit's analysis is written from the audit itself, and Roger AI doesn't read it or TikTok Ads client reports. TikTok Ads client reports have no public share link: you send them to your client as a PDF, by download or on a schedule. You can disconnect it at any time in Settings → Integrations, which deletes the stored access token.
  • LinkedIn Ads: to connect a LinkedIn ad account, you sign in with LinkedIn and approve AuditRoger's access. We ask only for r_ads, to read your ad accounts, campaigns, ads, lead form settings (not their responses), conversions and audiences, and LinkedIn's audience and bid estimates, and r_ads_reporting, to read their results, including the approximate breakdowns of who your ads reached. Both are read-only: AuditRoger can't create, change or delete anything in your LinkedIn ad accounts. This is separate from AuditRoger Social Studio, below, and uses a different LinkedIn app. As LinkedIn's terms require, we use this data only to show you, and the team members you invite, your own audits, to send the client reports you make for it to the recipients you choose, and, if you switch on monitoring for the account, to email the workspace owner alerts and, if you turn it on, a weekly summary about its results. Alerts are worked out by fixed rules, not by an AI provider. We don't send it to an AI provider: a LinkedIn Ads audit's analysis is written from the audit itself, and Roger AI doesn't read it. We don't create public share links for LinkedIn Ads audits, and we don't sell the data or use it for anything else. You can disconnect it at any time in Settings → Integrations, which deletes the stored access tokens. Lead sync, once it is available, is separate and off unless you turn it on for a client report. It asks for LinkedIn's lead permission (r_marketing_leadgen_automation) and reads the responses to your Lead Gen Forms, so those enquiries count in that report. They're handled like the leads you enter yourself, and never sent to an AI provider.
  • YouTube: YouTube channel audits aren't open to customers yet. They use YouTube API Services (the YouTube Data API) with AuditRoger's own API key, so there is no YouTube sign-in and no permission to grant: AuditRoger reads only what anyone can see on the channel, and can't change anything on it. By using YouTube channel audits you agree to be bound by the YouTube Terms of Service. How Google handles data is described in the Google Privacy Policy. We show figures combined across a channel's videos, such as how its recent views compare with earlier ones, only when you tell us the channel is yours or one you manage for its owner, because YouTube's rules keep them for the channel's owner, unless Google has accepted our use of them for comparing channels. Scores, ratios, estimates and topic tags appear only once Google has accepted them, and each is labelled as AuditRoger's own: they aren't YouTube metrics, and an estimate isn't what a channel really earns or charges. Results from your Google Ads account and GA4 property stay in their own labelled columns and are never added to YouTube's figures. We don't send YouTube data to an AI provider: a channel audit's analysis is written from the audit itself, and Roger AI doesn't read it. We don't create public share links for YouTube channel audits, and we don't sell the data, use it for advertising or use it to train AI models.
  • Meta Ad Library: the competitor ad library uses Meta's Ad Library API with AuditRoger's own access token, so you don't connect a Facebook account or grant any permission for it, and it reads only ads that Meta publishes in its public Ad Library. We don't send ad library data to an AI provider: Roger AI doesn't read it and no analysis is written from it. We don't share it or put it behind a public share link, use it for advertising or targeting, or sell it, and searching is free on every plan.
  • Meta Ad Library, followed advertisers and analysis: the same rules apply to advertisers you follow, the weekly email about them, and advertiser analyses and comparisons. None of it goes to an AI provider, Roger AI, a public share link, the public API, or a PDF or PowerPoint export. Paid plans add our own analysis, comparisons and follows; they don't sell Meta's ads, which every plan can search.
  • LinkedIn: AuditRoger Social Studio is Roger Tech's tool for publishing and managing LinkedIn content for the AuditRoger LinkedIn Page and for the personal LinkedIn profiles of Roger Tech team members who connect it. It is not offered to AuditRoger customers yet. It asks for w_member_social and w_member_social_feed, to publish posts, comments and reactions as you; we publish only content you approved, one item at a time. r_member_postAnalytics, to read the statistics of your own posts. r_organization_social, r_organization_social_feed, w_organization_social, w_organization_social_feed and rw_organization_admin, only when you connect a Page you administer, to publish on the Page, read and reply to comments on its posts, and read Page statistics. r_member_social and r_member_social_feed, only if LinkedIn grants them, to read comments on your own posts so you can reply to them. We never send connection requests or messages, never scrape LinkedIn, never post without your approval, and never use LinkedIn data for advertising, for selling or to train AI models.

Google user data. What AuditRoger receives from Google APIs, through the Google Ads permission (adwords) and read-only Google Analytics (analytics.readonly), is used only to provide the features you use: your audits, client reports, monitoring alerts and Roger AI's answers about them. It is only read, never used to change your accounts. To write the analysis in audits and client reports, and Roger AI's answers, audit findings and report figures built from it are sent to our AI provider, Anthropic, which processes them to generate that text; Anthropic does not train its models on data sent through its API. We don't sell Google user data, use it for advertising, or use it to train AI models.

AuditRoger's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

You can stop our access at any time by disconnecting an account in Settings → Integrations, which deletes the stored access token, or by removing AuditRoger from your Google, Facebook or Amazon account. On Facebook, that is Settings & privacy → Settings → Business integrations. On Google, it is your Google Account → Security → Third-party apps & services (myaccount.google.com/connections). On Amazon, that is Your Account → Manage your data → Manage apps & services with data access. You can disconnect LinkedIn in AuditRoger at any time, or remove AuditRoger Social Studio in LinkedIn under Settings & Privacy → Data privacy → Permitted services. LinkedIn Ads access is removed the same way: remove AuditRoger from that list. On TikTok, remove AuditRoger in TikTok For Business under User Settings.

5. Who processes your data for us

These providers run parts of AuditRoger. Each receives only what its part needs.

  • Supabase, for sign-in and the database that holds your account, connected accounts, audits and reports
  • Railway, which hosts the service that runs audits
  • Vercel, which hosts the website
  • Stripe, for payments, subscriptions and invoices
  • Resend, which sends AuditRoger's emails
  • Anthropic (Claude), which writes the analysis in audits and client reports and answers Roger AI, on paid plans. For a Google Ads or Meta Ads audit it receives the audit's findings and the account's totals (or, for an audit of chosen campaigns, those campaigns' totals), with its top three campaigns and their results; for Google Ads, also its three weakest keywords and the landing page addresses we tested. For a GA4 audit it receives the audit's findings, the property's name and settings (data streams, key events, linked Google Ads accounts, data retention, attribution and audiences) and its traffic figures: channels, sources, devices, top landing pages, paid campaigns and the sales funnel. Roger AI reads one ad account at a time: that account's name, its latest audits' findings and up to ten campaigns with their figures. Client report commentary is written from the report's figures. The names and contact details in lead lists are never sent. Before you connect Google, the app shows you this and asks you to accept it. To draft a reply for you to review, it also receives the text of a LinkedIn comment and the post it is on. To suggest rewrites in a LinkedIn profile audit on a paid plan, it receives the profile's headline, About section, three latest roles with their descriptions, top skills, certifications and degrees, with the target you gave and the audit's findings; we remove the person's name, email addresses, phone numbers and web addresses from that text first, and never send their location, schools, honours or contact details. Roger AI can read a profile audit's score, target and findings, but not the profile's text or the person's name. It never receives Amazon Ads data, LinkedIn Ads data, TikTok Ads data or YouTube channel data. Nothing from the ad library is sent to it. Anthropic does not train its models on data sent through its API.
  • Google APIs: the Google Ads API and Google Analytics APIs, to read the accounts you connect, Google sign-in to connect them, and the PageSpeed Insights API, which receives your landing page addresses to test their speed, and the Chrome UX Report API, which receives up to ten landing page addresses for each Meta, TikTok or LinkedIn Ads audit (for LinkedIn, only the site's address), and for a Google Ads audit the address of a page PageSpeed couldn't test in time, to look up how fast they load for real visitors
  • Google Analytics, for analytics on this website, only if you accept it
  • Amazon Ads API and Login with Amazon, for Amazon Ads accounts you connect directly
  • Meta Marketing API, for Meta ad accounts you connect, and Meta's Ad Library API, for the competitor ad library. The Ad Library API receives your searches (the words or Facebook Page ID and the country you choose) from our server with AuditRoger's own access token, never from your Facebook account.
  • TikTok Marketing API (TikTok API for Business), for TikTok Ads accounts you connect
  • LinkedIn Marketing APIs (Community Management API), to publish to and read from the LinkedIn profile or Page you connect
  • LinkedIn Marketing APIs (Advertising API), to read the LinkedIn ad accounts you connect
  • YouTube API Services (the YouTube Data API), to read the public data of the YouTube channels you audit, once YouTube channel audits open. YouTube receives the channel link, @handle or ID you enter, any channels and keywords you name, and our API key, never your Google account.
  • The websites your Meta ads link to, when we check that up to ten of them load. They receive a request from AuditRoger and nothing about you.
  • The websites your TikTok ads link to, when we check that up to ten of them load. They receive a request from AuditRoger and nothing about you.
  • Slack (Salesforce) and Microsoft, when you connect a Slack or Teams channel for alerts: the account's name and the alert sentence only.
  • The websites your YouTube descriptions link to, once YouTube channel audits open, when we check that a link works. They receive a request from AuditRoger and nothing about you.

Requests from public authorities. We disclose your data to a public authority, such as a court, regulator, police force or other government body, only when the law requires us to, in answer to a valid legal demand such as a subpoena, court order or warrant. We don't answer informal requests. Before we answer, we check that the demand is lawful; we challenge it if it is unlawful or asks for more than it should; we disclose only the minimum it lawfully requires; and we tell you first, unless the law forbids it. We keep a record of every demand and our response. We never use data from Meta, Google, LinkedIn, TikTok, Amazon or YouTube for surveillance or law enforcement purposes.

6. International transfers

Roger Tech LLC is based in the United States, and so are the providers above, so your data is processed in the United States and wherever those providers operate, even if you live elsewhere. Today the service runs on servers in the Netherlands and its database is in the United Kingdom. Where the law requires a safeguard for transferring personal data out of your country, such as from the EU or the UK, we rely on the transfer safeguards these providers offer, such as the European Commission's Standard Contractual Clauses. Email hello@auditroger.com for a copy of the safeguard that applies.

7. How long we keep it

  • Your account, audits, reports and the information you add are kept for as long as your account exists, so each audit can be compared with the ones before it. They are not deleted on a schedule, except LinkedIn Ads audit reports, LinkedIn Ads client reports, YouTube channel audits, what we read from LinkedIn profile PDFs, Meta Ads, TikTok Ads and Amazon Ads audit reports, and Meta Ads, TikTok Ads and Microsoft Advertising client reports, below. You can delete any report yourself, with Delete report on the report: its contents are deleted at once, and it still counts as the audit it used.
  • Disconnecting an ad account deletes its stored access token straight away. Audits you already ran stay until you delete them or ask us to, except as below.
  • A monitored account's monthly budget, and the latest month-so-far figure we compared with it, are deleted when you switch monitoring off for the account or disconnect it. A Slack or Microsoft Teams channel's webhook address, and our record of which alerts we posted to it, are deleted when you remove the channel or delete your account. A monitored Google Ads account's weekly search term list is replaced each week and deleted when monitoring is switched off. The platform's score and kinds of recommended change kept for the weekly summary, and a monitored Microsoft Advertising account's tag, goal and auto-apply statuses, are deleted when monitoring is switched off.
  • For Meta Ads, TikTok Ads and Amazon Ads, an audit's report, analysis and score are deleted automatically 12 months after you disconnect the ad account, or after 12 months in which your account runs no audit at all, whichever comes first; the audit stays in your history with its date. Meta Ads, TikTok Ads and Microsoft Advertising client reports are kept on the same rule: they are deleted 12 months after you disconnect the Meta, TikTok or Microsoft Advertising account they are built on, or after 12 months in which your account creates or refetches no client report, whichever comes first; the leads you entered stay. We email the account owner at least 30 days before any of these reports are deleted, with the client reports attached as PDFs or a link to download them. If you switch on monitoring for a TikTok Ads account, its monthly audits follow the same rule, and each alert we send about the account is deleted 12 months after it was sent. The same goes for a monitored Microsoft Advertising account.
  • For LinkedIn, we follow LinkedIn's data storage requirements. Profile data of other members (for example, people who comment) is cached for at most 24 hours and not stored. The content of other members' comments and posts is kept for at most 48 hours. Statistics for your posts and Page are kept for up to one year. IDs of posts, comments and members are kept while LinkedIn stays connected. Disconnecting LinkedIn deletes the stored access token at once, and we delete your LinkedIn data when you ask.
  • For LinkedIn Ads, we follow LinkedIn's data storage requirements. A LinkedIn Ads audit's report, analysis and score are deleted automatically one year after the audit ran; the audit stays in your history with its date. LinkedIn Ads client reports are cleared one year after their last refetch. If you switch on monitoring, its monthly audits are kept and deleted the same way, and each alert we send about the account is deleted one year after it was sent. Disconnecting a LinkedIn ad account deletes its stored access tokens at once. If you, or whoever controls a LinkedIn ad account, ask us to delete its data, we do so within 10 days: use Delete report on each report, or email hello@auditroger.com.
  • For YouTube, we follow the YouTube API Services rules. Everything a YouTube channel audit read from YouTube, and the report, analysis and any score built from it, is deleted automatically before it is 30 days old; the audit stays in your history with its date and the channel link or @handle you typed. There is one exception, only once Google has accepted it: to show growth over time, we read the public subscriber, view, like and comment counts of channels a customer has named once a day, and keep those numbers with the channel and video IDs for up to 36 months. We stop reading a channel when nobody has asked about it for 90 days. Titles, names, descriptions and comment text are never kept past 30 days. Deleting our copy doesn't change anything on YouTube. If you own a YouTube channel and want us to delete what we hold about it, email hello@auditroger.com and we will delete it within 7 days.
  • For LinkedIn profile audits, the PDF you upload isn't stored. What we read from it is deleted as soon as the audit finishes, and in any case within 24 hours of the upload, whether or not you run the audit. The report stays until you delete it, with Delete report on the report, or your account is deleted. Deleting a report removes its contents at once; it still counts as the audit it used.
  • Ads you save from the ad library are kept until you delete them, with Delete on the saved ad, or your account is deleted. Your ad library searches aren't kept at all, and neither are the ads a search shows you unless you save one.
  • Advertisers you follow in the ad library are kept until you unfollow them, with Unfollow on the Following page, or your account is deleted. For each one we keep the IDs of at most its 500 most recent ads we have seen, and nothing else about those ads. Advertiser analyses and comparisons aren't kept at all.
  • Password reset links expire an hour after they are sent.
  • To have everything deleted, email hello@auditroger.com from the address on your account. We remove your account, connected accounts and their tokens, every audit and report, client reports and their lead lists, pre-flight answers, saved ads, followed advertisers, team seats and API keys, and your sign-in, and confirm by email within 30 days. We keep a one-way fingerprint of the deleted email address, with nothing else about you, as a record that the request was carried out. Deleting your account doesn't cancel a subscription, so cancel it first under Billing & credits → Manage billing. Step-by-step instructions are on our data deletion page.
  • Deleting your account also deletes our own records of your payments, plan and credits. Stripe, which processes payments, is separate: Stripe keeps its own payment and invoice records, under its own privacy policy, for as long as the law requires.
  • Our providers keep backups and logs for their own periods, so deleted data can remain in those copies until they expire.

8. Your rights

Under data protection laws such as the GDPR in the EU and the UK GDPR, and similar laws elsewhere, you can ask us to:

  • give you a copy of the personal data we hold about you (access);
  • correct anything that is wrong (correction);
  • delete it (deletion);
  • give it to you in a machine-readable form to take elsewhere (portability);
  • stop using it where we rely on our legitimate interests, or limit how we use it (objection and restriction);
  • and you can withdraw consent, such as for analytics, at any time. Withdrawing doesn't affect what happened before.

To exercise any of these, email hello@auditroger.com from the address on your account; we may need to confirm the request is yours. Deletion is explained on the data deletion page. Some you can do yourself: disconnect accounts in Settings → Integrations, export audits as PDF or PowerPoint, client reports as PDF or CSV and saved ads as CSV, and change your analytics choice with Cookie settings.

If you're unhappy with how we've handled your data, you can complain to a data protection supervisory authority: in the EU, the authority in the country where you live or work; in the UK, the Information Commissioner's Office (ICO). Please tell us too, so we can try to put it right.

9. Cookies and local storage

AuditRoger uses no advertising cookies. This is what the site keeps in your browser:

  • Staying signed in (necessary). When you sign in, Supabase keeps your session in your browser's local storage, and the app keeps a few entries beside it: your user ID, name, email address and plan, and choices such as the account and date range you picked and the CPM you enter in the ad library. A cache of screens you've opened is kept in session storage, which the browser clears when you close the tab.
  • Your cookie choice (necessary). Your answer to the cookie banner, and when you gave it, stored in local storage as ar_consent_v1 so we don't ask again.
  • Google Analytics (only with your consent). Until you choose Accept analytics, its script isn't loaded at all. If you accept, Google Analytics sets its cookies (_ga and _ga_ followed by an ID) and records the pages you visit. We send page addresses without their query strings, send nothing from private links (shared audits, client reports, pre-flight forms, team invitations and password resets), and turn off Google signals and ad personalisation. Google explains how it uses this data in How Google uses information from sites or apps that use our services.
  • Stripe. Checkout and the billing portal are pages on Stripe's own site, where Stripe's cookies and privacy policy apply.

You can change your choice at any time with Cookie settings in the footer of this site's public pages, with the button below, or, once you're signed in, in Settings → Privacy. If you withdraw consent, analytics stops, the Google Analytics cookies on this site are deleted, and it doesn't load again.

10. Security

Access tokens for your ad accounts, and the names, contact details and notes of the leads in client reports, are encrypted before they are stored, passwords and API keys are kept only as hashes, and connections to the website, the service and its database are encrypted. Only you and team members you invite can see your audits and reports; team members see lead names and contact details masked. Share links are signed, expire and can be revoked, and client report links leave out lead names and contact details.

Our staff can see an account's name, plan, audit dates, scores and error messages, and use them only to support you, keep the service secure and fix problems. We don't open the contents of your reports unless you ask us to help with one.

To report a security problem, email hello@auditroger.com; our security.txt says the same.

11. Children

AuditRoger is a business tool for people aged 18 or over, as our terms of service require. We don't knowingly collect data from children. If you think a child has given us personal data, email us and we'll delete it.

12. Changes to this policy

We'll update this policy as AuditRoger or the law changes, and change the “Last updated” date above. For material changes, we'll tell account holders by email or in the app before they take effect.

13. Contact us

For privacy questions and requests, email hello@auditroger.com. Our terms of service and contact page have more about Roger Tech LLC.

Roger Tech LLC, 1309 Coffeen Avenue, STE 1200, Sheridan, Wyoming 82801.
Phone: +1 (307) 445-3601