Does SAM connect directly to my Google Ads account?

SAM is a building and editing workspace. You design your campaign on the canvas, then export it and bring it into Google Ads.

Can I edit campaigns I've already launched?

Yes. Import an existing campaign, restructure it on the canvas, and export the updated version.

Do I need Google Ads experience to use SAM?

No. The canvas shows you how a proper Search campaign is structured, so you learn the right shape while you build.

Is there a learning curve?

Almost none. If you've used a visual workflow tool, you'll feel at home immediately. If you haven't, it still reads like a map.

Can I manage multiple clients in one account?

Yes. Keep every client's campaigns and assets organized in the same workspace.

Your subscription stops at the end of the period. No lock-in.

Privacy policy

Last updated 11 September 2026

SAM (Search Ads Maker) is a tool for building Google Ads Search campaigns. It is operated by RoiEnv at sam.roienv.com. This page explains what SAM stores about you, what it does with the Google account you connect, and what you can do about either.

What SAM stores about you

Your account. Your email address, and if you sign in with Google, the name, profile picture and Google account identifier that Google provides. SAM has no passwords. Signing in uses a one-time code sent to your email, or Google sign-in.
Your work. The campaigns, ad groups, keywords, ads, extensions and reusable assets you build in SAM, and the layout of your canvas.
Sign-in protection. The network address a sign-in code was requested from, kept briefly so the sign-in form cannot be abused.

The Google Ads connection, only if you choose it

Exporting a campaign as a file needs no Google account at all. Connecting Google Ads is a separate, optional step you take from the export dialog, and it asks Google for one permission: https://www.googleapis.com/auth/adwords. When you grant it, Google gives SAM a refresh token for the Google account you signed in with. Here is everything SAM does with it.

What SAM reads from Google

Your identity on that connection. The email address and account identifier of the Google account you connected, so SAM can show you which account is connected and keep one connection per person.
The Google Ads accounts that login can reach. For each one, its customer id, its name, its currency, and whether it is a manager account or a test account. SAM shows you this list so you can pick where a campaign goes.
Whether a campaign of the same name already exists in the account you picked, and how many ad groups, keywords and ads it has, so SAM can warn you instead of creating a duplicate.
The contents of that one campaign, and only if you choose Replace. To show you exactly what would change before anything is sent, SAM reads that campaign's settings, budget, locations, languages, ad schedule, ad groups, keywords, negative keywords, device bid adjustments, ads and extensions. It reads nothing outside the single campaign you are replacing.

What SAM writes to Google

Only the campaign you asked it to publish, and only when you press the button that says so. A new campaign is created paused. When you replace an existing one, SAM shows you the full plan first, including every item that would be removed, by name, and sends it as a single all-or-nothing request. Nothing is removed unless you choose the mode that removes, on that export, that time.

What SAM never touches

SAM does not read your performance data, statistics, spend, invoices, billing details or payment methods. It does not read or change any campaign other than the one you are publishing. It does not create, change or remove anything in your account on its own, on a schedule, or in the background. Every call to Google happens because you pressed something.

How SAM protects it

The refresh token is the one piece of data that could spend money, so it is treated accordingly. It is encrypted before it is stored, using AES-256-GCM under a key that exists only on SAM's server and is separate from every other secret SAM holds. It is never sent to your browser, never written to a log, and never included in an error message. The short-lived access token Google issues from it lives in memory for the length of one request and is never stored. All traffic between you, SAM and Google travels over HTTPS. Database rows are protected by row level security and are reachable only by the application itself.

Who else sees it

SAM does not sell your data, does not share it with advertisers or data brokers, and does not transfer Google user data to anyone. Three providers process data solely in order to run SAM: Supabase hosts the database in Frankfurt, Germany, Hostinger hosts the site and the application, and Hostinger's mail service delivers sign-in emails. Nobody at RoiEnv reads your Google user data except with your consent, to investigate a security problem, or where the law requires it.

Limited use of Google user data

SAM's use and transfer to any other app of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. SAM uses Google Ads data for the single purpose of placing and updating the campaigns you build, in the account you choose. SAM does not use Google user data for advertising of its own, and does not use it to develop, improve or train any artificial intelligence or machine learning model, personalized or otherwise.

How long SAM keeps it

Your account and your campaigns stay until you delete them or ask for your account to be deleted.
The Google Ads connection stays until you disconnect it. Disconnecting deletes the stored token and tells Google to revoke it, so even a copy in an old backup stops working.
A record of each publish stays: which campaign went to which account, when, and how many changes it made. It holds no campaign content.
Sign-in addresses and one-time codes are kept only as long as the abuse limits need them.

Cookies

SAM sets one cookie, your session, so you stay signed in, plus a short-lived cookie during a Google sign-in round trip to confirm the reply came back from where it was sent. There is no advertising cookie, no analytics cookie, and no third-party tracker.

Your choices

Disconnect Google Ads at any time from the export dialog. The token is deleted and revoked immediately. You can also remove SAM's access from your Google account's permissions page.
Sign out from the library to end your session on that device.
Ask for your account and everything in it to be deleted by writing to the address below. It is done within 30 days.

Changes to this policy

If SAM starts reading or writing something this page does not already describe, this page changes first and the date at the top changes with it. Material changes are announced in the app.

Contact

Questions about this policy or your data: privacy@roienv.com.