uallak Privacy Policy

Last updated: October 21, 2026 (Merchant Center connection removed)

In short: uallak connects to a client's Google accounts only when the client chooses to connect them, uses that data only to provide the marketing features the client sees in their uallak dashboard, never sells it, never uses it for advertising profiles or to train generalized AI models, and deletes our access and stored data when the client disconnects or asks us to delete their account.

1.Who we are

This policy describes how uallak ("uallak", "we", "us") handles information in the uallak application at app.uallak.com, including the sales chat, the client dashboard and every integration a client connects. uallak is an AI-assisted digital marketing service for small and medium-sized businesses, operated from Israel.

Contact for privacy questions and data requests: johnny_support@uallak.com.

2.Information we collect in general

Account and business details you give us: name, email address, phone number, business name, address and tax ID (for invoices), and a profile picture if you upload one.
Sales chat and onboarding answers: what you tell us about your business, goals and budget, and the proposal we prepare from it.
Messages you exchange with uallak's assistants in the dashboard chat.
Payment status from PayPal (subscription id, status, transactions). Card details are entered at PayPal and never reach us.
Connected accounts you choose to link (Google services described in section 3, and non-Google services such as Meta, TikTok and your WordPress site), and the access credentials those connections issue.
Leads submitted through contact forms we place on your website or landing pages, so you can see them in your dashboard.

Your online store (WooCommerce), if you choose to connect it

Why: to answer your questions in the chat and on the Performance page about orders, sales, revenue and refunds from your store's real data.
Access: read only. We recommend a key you create in your store with "Read" permission only, which you can revoke there at any time. We never create, change or delete anything in your store. The key is stored encrypted, like all access credentials (section 7).
What is read: order details: number, status, date, amount, products, shipping method and refunds. Your customers' names, addresses, phone numbers and e-mail addresses are read only when you explicitly ask for the customer details of one specific order, and only for that order.
What is kept: your customers' personal details are not kept by us: not in our database, logs, alerts, cost records or analytics. They are shown to you once in the chat, and the copy kept in the chat history is masked. Aggregates (for example total sales for a period) are held in server memory for at most 20 minutes.
Who processes it: the customer details of an order you asked about are shown to you by our own code and are not sent to our AI provider. Order data without personal details (amounts, products, statuses) is sent to our AI provider (Anthropic) only to answer the question you asked. We do not pass store data to anyone else.
Disconnecting: the store card's "Disconnect" button deletes the stored key.

3.Google user data we access

Each Google connection is a separate Google consent screen that asks only for the permissions that one feature needs. Nothing is accessed until you approve it, and you can disconnect each one separately at any time (section 9). These are the only Google permissions (OAuth scopes) the uallak application requests:

Connection	Permission (scope)	Google user data we access
Sign in with Google	`openid` `https://www.googleapis.com/auth/userinfo.email`	Your Google account identifier, your email address and whether Google has verified that email. We do not request your name, profile photo, contacts or any other profile data.
Google Ads	`https://www.googleapis.com/auth/adwords`	The Google Ads accounts your login can access (account id, name, status, currency, whether it is a manager account); in the account you select: campaigns (name, status, budget), campaign performance (impressions, clicks, cost, conversions by day), keywords and their performance, ad text (headlines, descriptions), ads' landing-page URLs, and ad policy and approval status.
YouTube	`https://www.googleapis.com/auth/youtube.readonly` `https://www.googleapis.com/auth/youtube.upload`	Your own channel's id, title and uploads list; for your recent uploads: title, publish date, privacy status, and view, like and comment counts. We do not read comment text, subscribers, watch history or private messages. The upload permission lets us add videos to your channel (see section 4).
Google Tag Manager	`https://www.googleapis.com/auth/tagmanager.edit.containers` `https://www.googleapis.com/auth/tagmanager.edit.containerversions` `https://www.googleapis.com/auth/tagmanager.publish`	Your Tag Manager accounts and containers (names, ids such as GTM-XXXX), their workspaces, and the tags and triggers in the container's published version.

What we do not access. uallak does not request access to your Gmail, Google Calendar, Google Contacts, Google Analytics, Google Search Console, Google Business Profile, Google Merchant Center, or your personal Google Drive.

A note on Google Drive. uallak stores the media and documents it prepares for you in uallak's own Google Drive folders, using uallak's own service account. This is not access to your Google account: we never ask for a Drive permission on your account and cannot see your personal Drive. When we share a folder or document with you, Google receives your email address so it can grant you access.

We also search public YouTube videos about your industry (not your account) to find examples of content that works in your niche. This uses a YouTube API key, not your Google account.

4.How we use Google user data

We use Google user data only to provide and improve the user-facing features below, which you see in your uallak dashboard. We do not use it for any other purpose.

Sign in with Google (`openid`, `userinfo.email`)

To sign you in to an existing uallak account. We match your Google account identifier, or your Google-verified email address, to your uallak account and remember the identifier so future sign-ins work. The first time you sign in with a Google account, we email a one-time code to your uallak account's address and link the two only after you enter it. Signing in with Google never creates a new account.

Google Ads (`adwords`)

Reporting: showing your campaign results on the dashboard's performance page, answering your questions about your campaigns in the dashboard chat, and sending you an email when your campaigns produced conversions the day before.
Campaign management in your own account, as part of the service you purchased: creating search campaigns. A new campaign is always created paused, so nothing is spent until it is enabled.
Account health: checking account status and ad approval status so our team is alerted to problems early. These checks only read; they do not change your account.
Budget transparency: showing what you spent on Google Ads next to the marketing budget you told us about.
Suggestions: using your recent campaign totals when preparing weekly marketing suggestions for you.

YouTube (`youtube.readonly`, `youtube.upload`)

youtube.upload: to upload videos to your own channel — videos uallak produced for you, or a video from your uallak media folder that you asked for in the dashboard chat and approved with one click. Every upload is set to Private; you decide whether to make it public in YouTube Studio.
youtube.readonly: to identify your channel when you connect it, and to show view, like and comment counts for your recent videos on your performance page.

Google Tag Manager (the three `tagmanager` permissions)

To find the Tag Manager container installed on your website and check whether lead-conversion tracking is already set up.
When it is not, to add to that container, for each kind of enquiry you chose, one trigger and one Google Analytics 4 event tag: a form submission (generate_lead), a click on a WhatsApp link (click_whatsapp) or a click on a phone link (click_to_call); then create a container version and publish it, so the enquiries your website receives are counted. We do not change or remove your existing tags.

AI processing

Some of these features use artificial intelligence. To write answers in the dashboard chat, draft new ad text and campaigns, and prepare suggestions, the relevant Google Ads data (for example campaign totals, converting keywords, existing headlines) is sent to our AI provider, Anthropic, only for that one request, and the result is returned to you. Each request contains one client's data only.

Who at uallak can see your data

uallak is a managed marketing service: managing your campaigns is the work you hire us to do. Because of that, authorized uallak staff can see your connected Google Ads account and its campaign performance (in uallak's internal admin dashboard and in an internal weekly performance report), manage campaigns in it for you, and approve actions such as creating a campaign or publishing a video. Before you can connect Google Ads, the connection card in your dashboard asks you to tick a box agreeing to exactly this; we record that agreement, and the connection cannot start without it. Apart from that, no person reads your Google user data unless (a) you ask us to, for example in a support request, (b) it is needed to investigate abuse or a security incident, or (c) it is required by law.

5.How we share, transfer and disclose data

We do not sell Google user data or any other personal data. We share it only with the service providers that run uallak for us, and only as needed to provide the features above:

Google Cloud (Cloud Run and Secret Manager): hosting of the uallak application and storage of our encryption key.
Supabase: our database, where account records, connection credentials (always encrypted, see section 7) and activity history are stored.
Anthropic: the AI provider that processes the data described under "AI processing", under commercial terms that do not allow it to use our data to train its models.
Google (Gmail): delivery of the emails we send you and our team (for example conversion alerts and internal reports).
Google itself, when we act on your Google accounts at your request (for example uploading a video or publishing a Tag Manager version).

We may also disclose data if the law requires it, to protect against fraud or security threats, or as part of a merger or acquisition of uallak, in which case this policy continues to apply to it.

6.What we never do with Google user data

We do not sell it.
We do not use or transfer it to serve advertising, including retargeting, personalized or interest-based ads. (Running your own campaigns in your own Google Ads account, at your direction, is the service itself, not advertising to you.)
We do not use it to determine creditworthiness or for lending.
We do not use it, and do not allow anyone else to use it, to develop, improve or train generalized or non-personalized AI or machine-learning models.
We do not transfer it to data brokers or information resellers.
We do not let people read it except as described in "Who at uallak can see your data".

7.How we protect data

Encryption in transit: the application is served only over HTTPS, and every call we make to Google, our database and our AI provider uses TLS.
Credentials encrypted at rest: Google refresh tokens and every other connection credential are encrypted with AES-256-GCM before they are stored. The encryption key is kept in Google Cloud Secret Manager, never in our code or database. If the key is unavailable, the credential is not stored at all.
Per-client isolation: each encrypted credential is cryptographically bound to the client and the service it was issued for, so it cannot be decrypted for any other client. Every request to the dashboard is tied to the signed-in client's own account.
Credentials never leave the server: they are decrypted only at the moment of a call to Google and are never shown on any screen, returned to a browser, written to logs or sent to the AI provider. Messages that look like passwords or keys are not stored.
Limited access: administrative access is limited to authorized uallak staff and requires a separate admin sign-in.

8.How long we keep data

Google access tokens (refresh tokens): kept, encrypted, only while the connection is active. They are revoked at Google and deleted when you disconnect, close your account or ask us to delete your data.
Live Google data (campaign numbers, YouTube counts, Tag Manager status): read from Google when a feature needs it and held in server memory for at most one hour.
Records derived from Google data (the connected account's id and name, your Google account identifier for sign-in, chat answers about your campaigns, activity history such as "video uploaded" or "campaign paused", weekly suggestions, internal weekly reports and internal alerts): kept while your account is active so the service and its history keep working, and deleted as described in section 9.
Emails already sent: emails that contain campaign figures (conversion alerts to you, and the internal weekly report to our team) stay in the mailboxes they were delivered to; they are not part of our database.

9.Disconnecting, deleting and your other choices

Disconnect any Google connection at any time from your uallak dashboard (Google Ads, YouTube and Tag Manager each have their own "Disconnect" button). Disconnecting revokes uallak's token at Google and deletes the stored connection. It changes nothing in your Google accounts: your campaigns, videos and tags stay as they are.
You can also remove uallak's access from your Google Account at any time at myaccount.google.com/permissions.
Download your data from your profile page in the dashboard (this download is complete, including your Google Ads figures).
Closing your account from your profile page stops billing and, in the same step, revokes every Google token at Google and deletes it; deletes all Google-sourced data from our database (activity history, our chat replies, weekly suggestions, lead counts derived from your ad conversions, internal staff notes); removes your entry from our internal weekly reports; and deletes earlier internal alerts about your account (the alerts the closure writes about its own outcome stay, and contain no Google data). The system then checks that nothing is left and alerts our team if anything is. Your other data is removed from our live systems once the archive copy below is saved. A copy of your account record is emailed to you, and an archive copy is kept in uallak's own storage as a record of the account. Neither copy contains Google user data: they hold your account, billing and lifecycle records, the messages you wrote to us, and the leads from your website, but no campaign figures, no Google account ids and none of our replies. Your Google data stays in your own Google accounts.
Request deletion of all your data by emailing johnny_support@uallak.com from the email address on your account. We reply within 7 days and complete the deletion within 30 days. Deletion revokes every Google token at Google and permanently deletes your account, stored tokens, Google-derived records and all other data tied to your account from our database, removes your entry from our internal weekly reports and deletes internal alerts about your account. The system checks every one of these places afterwards; if anything is left, the deletion is reported as incomplete and your account record is not removed until a re-run finds nothing. All that remains are internal log entries about the deletion itself, identified by your account number only. Any backup made just before the deletion contains no Google user data. Payment records held by PayPal are governed by PayPal's own privacy policy.
You may also ask us to see or correct the personal data we hold about you, at the same address.

10.YouTube API Services

uallak uses YouTube API Services. By connecting your YouTube channel you agree to the YouTube Terms of Service, and Google's handling of your data is described in the Google Privacy Policy. You can revoke uallak's access to your YouTube data at any time from the uallak dashboard or from Google's security settings page.

11.Cookies

The uallak application uses one sign-in session cookie to keep you signed in, and your browser's local storage to remember settings such as your display language. We do not use advertising or third-party tracking cookies in the application.

12.Google API Services User Data Policy

uallak'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.

13.Changes to this policy

If we change how we use Google user data, we will update this page and tell active clients before the change applies, and ask for your consent again where required.

14.Contact

Privacy questions and data requests: johnny_support@uallak.com. See also our Terms of Service.