What we store, what we read, and what we leave alone.

Who we are

KeySend is a web application at keysend.app that reads your Google Ads every day and tells you what changed, why, and what to do.

KeySend is run by ALPLUS TECHNOLOGIES S.R.L., a company registered in Romania. For anything about your data, email [email protected]. A person reads it.

Company details: ALPLUS TECHNOLOGIES S.R.L., registration number (CUI) 55013997, trade register number J2026041446003, registered at Bd. Dâmbovița, nr. 60, sc. A, et. 4, ap. 14, Timișoara, Timiș, Romania.

What we store

When you sign in

You sign in with Google. We receive and store your Google account ID, your email address, and your name. We never see or store a password.

When you connect Google Ads

This is a second, separate consent. It uses the Google permission https://www.googleapis.com/auth/adwords. We store the Google account ID and the email address of the login you connect, and the refresh token that Google gives us. The refresh token is encrypted with AES-256-GCM. The encryption key is kept apart from the database and is not in the database backups.

The Ad Accounts you add

For each Ad Account you choose to add, we store its Google Ads customer ID and its name. When access goes through a manager account, we also store the manager account ID.

Your monitoring data

For each Ad Account we store the Account history (the daily numbers of each Campaign, and the Account changes that Google reports), the search terms, keywords, landing pages, and ads with the most spend from the weekly Deep check, the Updates and Recommendations we write, and the Branding you gave us: the name, the logo, and the accent colour.

Card details

We never see or store them. Payments happen on Stripe's own pages. We store whether a Subscription is active.

What we read from Google Ads

We read two things:

• The list of accounts that the connected login can open.
• Performance data for the Ad Accounts you added: metrics such as impressions, clicks, cost, and conversions, with breakdowns by campaign, keyword, search term, ad, device, day, location, and landing page, plus the account change history.

We send read requests only. We never change a campaign, an ad, a budget, or a billing setting.

Google's permission is broader than what we use, because Google Ads offers no read-only permission. If you want a hard limit, connect a Google login that has Read-only access to the account.

Google API Services User Data Policy

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

In plain words, for the data we get from Google:

• We use it only to provide the features you see in KeySend.
• We don't use it to train AI models.
• We don't use it for advertising.
• No person reads it unless you give us permission, we need to for security, or we are required to.

How Updates are written

To write an Update or a Recommendation, we send OpenAI, through the OpenAI API, the numbers and the changes that KeySend detected, the names of your Campaigns, the search terms, keywords, ads and landing pages of a Finding, and the note that you wrote about a Campaign. Each request tells OpenAI not to store the answer. We don't send your Google account details, and we never send the refresh token.

Cookies

We set two cookies, and both are for signing in.

There are no advertising cookies.

Email

We send two kinds of message: the Weekly email, and an Alert the next morning when a Campaign stops, spend doubles, or conversions go to zero. They go to your own address, and you can turn each of them off for an Ad Account in its Settings. We never email your clients.

Where it lives and who helps us

KeySend and its database run on a server in Canada. We make an encrypted database backup each hour and store it in Cloudflare R2 in the United States. R2 is configured to expire hourly backups after 48 hours and daily backups after 30 days. Deleted data can remain in existing backups.

These companies help us run the service:

We don't sell your data, and we don't use it for advertising. We don't share it with anyone except the services above, and only as needed to run KeySend.

Who can see your data

Your data sits in your own Workspace, apart from every other Workspace. A person who signs in sees only their own Workspace.

How long we keep it

• We keep the Account history, Updates, Findings and Recommendations of an Ad Account for 24 months. Each day we delete what is older.
• When your Trial or your Subscription ends, we keep your Workspace for 12 months, so that you can come back. Then, once you have not signed in for 30 days, we delete it as if you deleted it in Settings.
• When a Workspace is deleted, we keep a one-way hash of your Google account ID and the date your Trial started, so that a new Workspace does not get a second Trial. We delete it 24 months after the Trial started.

Removing access and deleting your data

You can remove KeySend's Google permission at any time on Google's own page: myaccount.google.com/connections. This stops us reading your Google Ads, but it deletes no data. The data we already have stays until you delete it in KeySend.

Use Settings to delete your User account and Workspace. This removes your Google Connections, Ad Accounts, Account history, Updates, Recommendations and Branding, revokes Google permission, and cancels your Subscription. Stripe retains payment history. You can also remove a Google Connection in Settings, and an Ad Account in the Settings of that Ad Account.