Hamletak is an AI marketing platform that helps businesses create, launch, and measure advertising campaigns. The platform operator is the data controller for the processing described here. Contact: infosecengm@hamlet-ak.com.

• Account data: email, name, and a hashed password (via our authentication provider, Supabase).
• Business profile: information you enter about your business (description, services, prices, business knowledge) used to generate tailored campaigns.
• Ad-platform data: when you connect an ad account (Meta, TikTok, LinkedIn, Google, Snapchat, Microsoft) we store OAuth access tokens encrypted (AES-256-GCM) and read your campaign data (status, spend, results) to display and control it on your instruction.
• Your leads: lead and sales records you log or that your business chat agent collects — these belong to you.
• Technical data: security logs (IP address, request time) for protection and abuse prevention.
• Visit measurement: on our public pages only, Meta, Google and Snap tools record page views, WhatsApp button clicks, and account creation — see section 5.

• AI campaign and content generation (text is processed by an external AI model provider under confidentiality, and is not used for training).
• Launching campaigns and reading their results on connected ad platforms — only as authorized by you and within the permissions you granted.
• Running your customer chat agent and saving leads to your account.
• Billing and subscriptions (payments are processed by Paymob; we never store your card details).
• Platform security (human verification via Cloudflare Turnstile, rate limiting, audit logs).

We do not sell your data. Your account data — business profile, campaigns, leads, access tokens — is never shared for advertising, with one exception you ask for yourself and which section 6 describes: uploading your customer list to your own ad account. Visits to our marketing site are measured by Meta, Google and Snap tools; section 5 sets out exactly what is sent and how to stop it. Data is shared with the processors required to operate the service: Supabase (database & auth), our AI model provider (text processing), Paymob (payments), Hetzner (hosting), and the ad platforms you yourself connect — each under its own terms and limited to what is necessary.

Our public pages — the homepage, the country and sector pages, and the ad price index — load measurement tools from Meta, Google and Snap, plus our own. These tools do not run inside the platform once you sign in.

• Meta Pixel: records a page view, a click on the WhatsApp button, and account creation.
• Google Analytics 4 and Google Ads: record the same moments.
• Snap Pixel: records the same moments. If automatic matching is switched on in the Snap account, the pixel reads an email or phone number typed into a form on the page and sends it hashed from your browser, never in plain text.
• Our own measurement tag: the same code our clients put on their sites. It records the page view and clicks on WhatsApp, phone or email links on our server, and sends those same moments to Meta from the server (Conversions API) rather than the browser alone — the same events, no extra data.
• When you create an account, your email is sent to Meta and Google hashed, so they can match your signup to the ad it came from. Neither receives the address itself; hashing happens in your browser before anything is sent.

What we never send from these pages: your business profile, your campaigns, your leads, your access tokens, or anything inside your account.

Why we measure: so we know which ad brought a real client instead of spending with no measurement.

How to stop it: tracking protection in your browser blocks these tools. You can also control what reaches each platform from Meta ad preferences and Google My Ad Center, and from Ad Preferences in the Snapchat app's settings.

You can ask us to build a Custom Audience on your own ad account from your customers' phone numbers, so your ad reaches them or people who resemble them. This only ever happens when you ask for it; it is never automatic.

• What is sent: the number hashed (SHA-256), nothing else. The number itself never leaves our server; the ad platform receives the hash to match against its own accounts and cannot recover the number from it.
• Where: to your ad account alone, on the platform you connected yourself. It is not shared with anyone else, not with our other clients, and not sold.
• Your attestation first: we require an explicit confirmation that these are your customers and that you have their permission for marketing contact. We record who confirmed, when, and how many numbers — and no upload happens without it.
• What we do not keep: neither the uploaded numbers nor their hashes. Processing happens in memory during the upload only.
• Deletion: the audience lives inside your ad account, and you can delete it at any time from your own Ads Manager.

When you connect an ad account we use the official APIs (e.g., Meta Marketing API) and comply with each platform's terms (including the Meta Platform Terms). Platform data is used solely to provide the service to you and is not retained after you disconnect the platform or delete your account.

We touch Google in two separate places, each under its own consent you grant on Google's own screen:

• Sign in with Google: we receive only your email, name, and profile picture from Google, to create your account and sign you in through our authentication provider, Supabase. No other permission is requested.
• Connecting a Google Ads account: we request a single scope, https://www.googleapis.com/auth/adwords (manage your Google Ads campaigns). We do not request access to Gmail, Drive, Contacts, Calendar, or any other Google service.

What we read from your Google Ads account: the ad accounts available to you; your campaigns, ad groups, ads, and keywords with their results (impressions, clicks, spend, conversions); search terms; and keyword search-volume estimates (Keyword Planner).

What we write to it: creating the campaigns you approved, enabling or pausing them, adding negative keywords, and setting up conversion goals — each on your instruction, nothing automatically. A Merchant Center account id is something you type in for Shopping campaigns; we do not read Merchant Center content itself.

What we use it for: showing your accounts and campaigns inside the platform, launching campaigns you approved, tracking their results, and giving you optimization recommendations. Google Ads data is used for nothing else — not to target ads at you, not to train models, not to build profiles of you or your customers.

What we store: the access and refresh tokens, encrypted with AES-256-GCM, in your account's own connection record; and a copy of your campaign results (spend, clicks, conversions) to show in your reports.

Who can see it: you and the members of your workspace according to their roles, and the platform operator for support and operations only. It is never shared with a third party, sold, or transferred.

Disconnecting and deletion: pressing "Disconnect" on the Connections page deletes the tokens from our database immediately, and they are deleted with your account as well. To revoke the grant on Google's side: Google account permissions.

Google policy compliance: Hamletak'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.

We retain data for as long as your account is active. Safeguards include encrypted access tokens, HTTPS-only transport, per-client data isolation enforced server-side, least-privilege access, and audit logging.

At any time you may: access and correct your data, export your leads, disconnect any linked platform (which immediately deletes its stored access token), or permanently delete your account and all associated data.

To request deletion: email infosecengm@hamlet-ak.com from your account email with the subject "Delete my account". Deletion is completed within 30 days and covers your business profile, generated campaigns, access tokens, and leads.

We may update this policy; the "Last updated" date above will reflect it. Continued use of the platform after an update constitutes acceptance.