Privacy

Your account: name, email address, phone number, the language you chose and the country our host reports. Passwords are handled by Supabase Auth and we never see them.

How you found us: the advertising click identifier on your first visit (Google, Meta, TikTok, Snapchat or Microsoft), the page you landed on, and the site that referred you. This is how we know which advertising works. It is stored with your account when you sign up.

Your advertising data: once you connect an ad account, we read campaigns, ad groups, ads, spend, impressions, clicks and conversions, day by day. Connecting also gives King permission to make changes in that account, and King uses it in two cases only: when you approve a specific change, or when an automation you set to act on its own makes the change it describes. On Google, automations only propose, even one set to act on its own: it tells you the change, and nothing is sent to Google unless you make that change yourself.

Read live: when you ask how things stand now, or King's stored copy cannot answer, King reads the connected ad account through the network's own API at that moment. Besides what is listed above, that can include figures for each ad set and each ad, figures over a window you ask for, and figures broken down by audience, as each network offers them; the Google, Meta and Snapchat sections below name each one's own. On TikTok it can read today's figures for each ad group and each ad, figures over a window you choose, when you ask, broken down by day, hour, country, placement or operating system; hourly figures take one day at most; each ad group's figures by age and gender, country, placement and operating system, and each campaign's figures by age and gender, by country, by placement and by operating system over the seven days before today; the advertiser's TikTok pixels, by id, name and code, with the event types set up on each; the TikTok identities, by their id and type only, with their names, usernames and pictures left out before the model sees them, once TikTok grants that permission; the review reasons TikTok gives each ad group and each ad; TikTok's diagnoses and suggestions for each active ad group about creatives, bid and budget, and event tracking, once TikTok grants that permission; each ad's figures by age, gender, country, platform and placement over the seven days before today, with the ad's id; the change log, with only the columns TikTok documents kept, the operator column (which names who made a change) left out, and each change's before and after values kept only for settings such as status, budget, bid and schedule dates, never for names, targeting, creative text or links; one video's figures second by second over its first sixty seconds, for a video from one of this business's ads that you name; how each ad compares with TikTok's benchmarks for its category, in a campaign you name, over TikTok's seven-day comparison window; the events one of the advertiser's pixels recorded over a window you choose, by event type; and a report over a window you choose, once TikTok has run it.

Your files: the images and videos you upload to your library or ask King to generate, and the descriptions written for them.

What you tell King: your conversations, and the facts about your business you ask it to remember — margins, seasons, products, what you have already tried.

Support messages: what you send through the support chat in the product, and our replies.

Billing: your subscription state and payment records. Card details are handled by Stripe and never reach our servers.

To do the thing you signed up for: read your accounts, work out what to change, and make the change when you approve it, or when an automation you set to act on its own makes it. On Google, automations only propose.

To bill you, and to know which advertising brought a paying customer so we do not waste money on the advertising that does not.

To keep the product working — errors and failed jobs are recorded so they can be fixed.

To email you when paid places open, and about King's launch, only if you said yes to it at sign-up, in Settings or on the billing page; every such email carries a link that stops them, and so does the same switch in Settings.

These services receive data from King, each for the job named beside it.

Supabase — the database, the file storage and the sign-in system. Everything listed above is stored there.

Vercel — hosting. Every visit and request passes through it. Its AI Gateway also carries image requests to ByteDance, below.

Anthropic — the model that reads your data, writes King's answers and runs its web searches. Your data is sent to it to produce those answers and is not used to train it.

Google (Gemini) and ByteDance (Seedream) — the two image models. When you ask King for an image, your request and any reference images you chose are sent to the model that makes it: Google's Gemini directly, or ByteDance's Seedream through Vercel.

Stripe — payments. It receives your email address and your business's name, and handles your card.

Resend — delivers the emails we send you, so it handles your email address and what each email says, including the figures in a report.

Sentry — error reports, so we can fix what broke. Email addresses and keys are removed from them before they are sent, and so is any field labelled as a name, a phone number or a password.

PostHog — which pages and screens are used, and which steps you take, such as creating an account, connecting an ad account (and to which network) or paying (and how much), so we can see where people give up. On the public pages — the ones listed for the advertising tags below, including when you open one while signed in — it also records the visit itself: the page as it appears, and where you move, click and scroll. Everything you type is masked in your browser before anything is sent, and on the sign-up, sign-in and password-reminder pages all of the page's text is masked too. Nothing inside your account is recorded: there it records the step, never what is on the screen. It also records the country a visit comes from, as our hosting provider reports it, and never receives your IP address or your city. It receives no name and no email address; once you sign in, it knows you by a one-way code made from your account number.

Telegram — notifications to our own team: a new sign-up's email address, country and language, and which advertisement or site brought them; each connection event — a network connected, an ad account chosen, a permission about to expire, a connection ended — with the ad account's name or number, except for a Google product, whose notice leaves it out; the messages you send through the support chat, with your email address and your business's name; and errors, with keys removed.

Cloudflare — the Turnstile check on the sign-up, sign-in and password-reset forms, and on changing your email address or password in Settings, which tells people from automated abuse. It reads signals from your browser to do that.

DataForSEO — search data for the SEO tools. It receives the website addresses and keywords you research, not your name or contact details.

YouTube — only if you play a tutorial video inside King. The video loads from YouTube's privacy-enhanced domain, and YouTube receives that visit.

Google Tag Manager, Google Analytics and the advertising tags of Google Ads, Meta, TikTok and Snapchat — on this site's public pages only: the home page, pricing, about, the blog, changelog, help and roadmap, the legal pages, and the sign-up, sign-in and password-reminder pages. They never load on the pages inside your account, and they do load on a public page you open while signed in. They record visits and which advertising brought them. See Cookies, below.

Meta, TikTok, Snapchat and Google Ads, as advertisers ourselves — when you pay us, we report the purchase and its value so each network can tell which of our advertising works. Meta and Snapchat receive your email address, phone number and country, each turned into a one-way code (hashed) before it leaves us. TikTok receives your email address and phone number, hashed the same way. All three also receive any advertising click identifier from your first visit, and the address of the public page on this site where that visit began, or of our home page when it began on any other page. Google Ads receives a purchase only when a Google advertisement brought you: the click identifier and the amount. We also report three other steps. When you create an account, a network whose advertisement brought you is told so with that click identifier and no detail about you; Meta, which requires a page address, is also given the address of our sign-up page, the same for everyone; Snapchat is not told at all. The first time you connect an ad account to King, and when King first shows your figures, each network is told with the same details it is given for a purchase, without any amount, and with nothing about the account you connected or its figures. Google Analytics is sent these three steps and your purchases from our server, with the identifier its own tag set in your browser on our public pages and, for a purchase, the amount; it is not given your email address or phone number. A test payment is never reported. And none of these steps, and no purchase, of a business owned by one of King's own staff — an administrator of this platform, or an address we have listed as staff — is reported to any of them, Google Analytics included.

The services you connect — Google Ads, Google Analytics, Merchant Center, Search Console, Google Drive where it is offered, Meta, TikTok, Snapchat and Shopify. Only the accounts you connect, only through their own official interfaces, using access you granted and can withdraw. What King sends them is what reading requires, and the changes you approve or set an automation to make.

What King sends TikTok when you upload a file: when you press the TikTok upload card, the one library file you chose goes to your TikTok advertiser's creative library, and nothing else. TikTok keeps it there. King's record of that press keeps only the file's id in your library and TikTok's id for the new file, never its name.

What King sends TikTok when you create or rename a pixel: the pixel's name, and for a rename the pixel's id, and nothing about your customers. King sends none of the pixel's matching, cookie or data-sharing settings, and TikTok's code for the pixel comes back to you to install on your website.

We do not sell your data, we do not share it with other advertisers, and no other customer's account can reach yours. That last separation is enforced by the database itself, not by our code remembering to be careful.

This section is about the data King receives from Google's APIs when you connect a Google product. Each product asks for its own permission on Google's own consent screen, and each is read only for the business you connected it to.

Google Ads (the adwords permission): we read the ad accounts your login can reach and, for the one you choose, its campaigns with their budgets, status and daily figures — spend, impressions, clicks, conversions and conversion value. For every live campaign, on each refresh, we read its ad groups and asset groups, the text of its ads and asset groups, and its location targeting. For a campaign King is building or changing, we also read its ads, keywords and targeting settings, and for Performance Max its asset groups, assets, audience signals and product filters. For an ad group you copy, we read its placements, audiences, age ranges and genders, and recreate them in the copy, inside its paused ad group, each with the status it has in the original, so one you paused stays paused; any other targeting is named on the card and not copied. And we read the account's conversion actions, assets, experiments and their status, customer lists and custom audiences, billing setup and account budgets. When you ask King how things stand now, it can also read the account live: figures for each ad group, each ad, and each campaign by device, over the last 30 days; the search terms that led to your ads, by campaign and by ad group, with whether each is already a keyword; the keywords in each ad group with their quality scores; the account's change history, which says what changed, when, from what to what and what it was made through, and never who made it; and Google's recommendations, which King reads; it applies or dismisses one only when you approve that change. As Google reports them now, King also reads each campaign's settings, its budget's name and period, its bidding targets, its network settings, its geo targeting type and its labels; each campaign's targeting criteria, including locations, audiences, ad schedule, keywords, devices and languages; the asset groups of each Performance Max campaign, with their assets and their text, and each asset's policy findings; responsive display ads and responsive video ads, with their text; Demand Gen ads, with their headlines, descriptions, images, logos, business name and call to action text; each ad's ad strength, approval status and policy findings; the optimization score of the account and of each campaign; the account's status; its spending limit, amount served and billing status, but never payment card details; the account's conversion actions, with their status, type, how conversions are counted, whether each is primary for its goal, and its look-back windows, and which conversion each Performance Max campaign's goal uses; which recommendation types Google applies automatically to the account, and whether each is enabled or paused; each experiment's name, type, status, promotion status and dates, and each experiment's arms and their traffic split; each Shopping campaign's product groups, with their bids in the account's currency; and each campaign's figures over the last 30 days by ad network, hour of the day, day of the week, age range and gender, day by day, and in total with cost per conversion and search impression share, with the figures by country across the account. The same permission lets King create campaigns, pause and resume them, change their daily budgets, and change an existing campaign's countries, its ad text and its target ROAS or target CPA. The same approval covers applying or dismissing one of Google's recommendations, switching a recommendation type's automatic application on or off, swapping an image of a Performance Max asset group for one from your library, proposing the account's first budget, creating or changing a conversion action, and creating, starting, ending or promoting an experiment on one of your campaigns. King does that only when you approve the specific change. For a Shopping campaign you create, we read the Merchant Center account linked to your Google Ads account, and send its number with the campaign; King copies nothing else from that account for the create. And the conversion tracking setup of the account: the status of conversion tracking, its tracking id, whether the customer data terms are accepted, the account where conversions are created and managed, and each conversion action's status. King never reads a conversion action's tag code. When you ask King how things stand now, it can also read your invoices: for the approved billing setup, the invoices issued in the previous month and this one, each with its number, type, issue and due dates, the service period it covers, its currency and its totals, and each account budget's name and amounts on it. King reads invoice totals and dates, and never keeps or shows payment details: the payment account and profile numbers, the link to the PDF, the account's own name and purchase order numbers are dropped as the answer is built. On Google, automations only propose, even one you set to act on its own: it tells you the change, and nothing is sent to Google unless you make that change yourself.

When you create a Performance Max, Display or Demand Gen campaign with images from your library, the image files are sent to Google Ads twice. First, when King checks the card: Google checks them and stores nothing. Second, when you press the card: they are sent again and stored in your ad account as image assets. King sends no image before the card has been checked. When you swap an image of a Performance Max asset group for one from your library, the new file is sent the same two times; the old image then stops showing in that asset group, and the image itself stays in your ad account. When you switch Google's automatic application of a recommendation type on or off, the switch is sent only when you press its card. Switching it on lets Google apply recommendations of that type to your account on its own, which can change bids, keywords, ads, where ads show or budgets; King does not undo what Google has already applied.

When you create a custom audience, King sends Google only the keywords, web addresses and app names you type for it, and Google builds the audience from them. King never sends a list of customers or any person's details for it. A web address goes to Google without anything after a question mark or a #, because that part can hold a person's details. The audience is created when you press its card; King checks it with Google first, and it is attached to no campaign until you make that separate change. When you attach a custom audience King made to a campaign or an ad group, King first reads that audience's name and whether Google has it enabled, then sends Google only its id. The attachment is a change you press on its own card.

Google Analytics (analytics.readonly): we read the list of properties you can see and, for the property you choose, its summary figures — sessions, users and new users, engagement, key events, events by name, purchases, revenue and refunds, and the steps of the purchase and checkout journeys. They are broken down by day, traffic source, channel, the channel that first brought each user, landing page, country, device, age bracket and gender, by the products viewed, added to cart and bought, and by the audiences defined in the property. These are totals Google has already added up; no individual visitor is in them. When you ask how the property is set up, we also read its settings: your Google Analytics accounts and properties, the data streams with their measurement ids, key events, custom dimensions and metrics, linked Google Ads accounts, your BigQuery links (the Google Cloud project each one exports to, its dataset location, which exports are switched on, and which streams it exports and which events it leaves out of the export), how long Google keeps event and user data, and each audience's name, description and membership length. This permission cannot change anything.

Merchant Center (content): we read your products, the status of each one and the issues Google reports with them, your account's programs and homepage, and how often each product was shown and clicked. When you ask the assistant, it also reads these from Google at that moment, with the dates you choose, together with your account's settings (business information without any person's name, phone or contact, shipping, automatic improvements, terms of service, promotions, the programs the account takes part in with each one's state and what it still needs, its online return policies (each one's label, the countries it covers, its refund window and the return methods it lists), the accounts and services linked to it (each link's kind, the other side's id where Google gives one, and for a service whether both sides have approved it; never the name of a linked account), and how many users the account has, never who they are), a product's stock and price by store and region, and each store's pickup and local delivery options, Google's own explanation of how to fix an issue (King applies nothing), and Google's published market reports on best-selling products and brands and on how visible competing shops are, which describe other businesses and hold no personal details. Google offers no read-only version of this permission. King only reads with it, and contains no code that changes your products or your feed.

Search Console (webmasters.readonly): we read the searches that led people to your site — queries, pages, clicks, impressions and positions, by day, country, device and search appearance — your sitemaps, and whether Google has indexed the pages that already show in your search results, up to twenty of them, checked on each refresh. When you ask the assistant, it also reads from Google at that moment, for your connected site only: your permission level, the searches for the dates and filters you choose, your sitemaps and the sitemaps inside a sitemap index, and Google's check of one page of your site that you name. It reads nothing about the people who searched. This permission cannot change anything.

Google Drive (drive.file), where it is offered and you connect it: King sees only the files you choose in Google's own file picker, and copies each one into your library here. It cannot see, change or delete anything else in your Drive. The same connection reads your Google email address, to name the connection.

How King uses it: to show you your own figures, to answer your questions about your own account, to write your reports and alerts, and to make the changes described above. It is never used for advertising, never sold, and never used to answer another customer.

Who receives it: Anthropic processes it when King answers you and when it describes an image in your library, Resend delivers it inside the reports and alerts we email you, and Supabase and Vercel store and serve it. Our own team's connection notices on Telegram say which Google product was connected, chosen or disconnected, and for which business, but not the name or number of your Google account, and our team's console does not show your Google campaigns or spend. A Drive file you import becomes an ordinary file in your library: if you then choose it as a reference for a new image, it is sent to the image model you picked.

We do not use Google user data to develop, improve or train AI or machine-learning models, and we do not transfer it to anyone for that purpose.

How long it is kept: as long as the connection exists, because comparing this season with the last is the point. Pressing Disconnect on that Google product in King, deleting your account, or moving to a plan without Google each deletes the figures and the list of campaigns and products we copied, and the keys, and asks Google to revoke our access — unless another Google product is still connected in that business, or one you connected in another business, because Google ends every product of a login at once and that one would stop working too. On a plan without Google, a Drive connection does not keep the access open. Until the last one goes, your Google Account may still list King by AdsHackers, and you can remove it yourself at myaccount.google.com/permissions.

Three things outlive a Disconnect. A file you imported from Drive is an ordinary file in your library and stays until you delete it there; after an account deletion its stored copy stays too, as How long we keep it explains. Your conversations with King can quote your Google figures and campaign names, and they stay until you delete your account; so do the notes King saved about your business, unless you delete one yourself first. And the connection notices already in our team's Telegram stay there.

If you remove King's access in your Google Account instead (myaccount.google.com/permissions), our reads stop, because the access no longer works. The figures already copied stay in your account until you press Disconnect in King or delete your account, and either one deletes them.

How it is protected: see How we protect it, below — encrypted in transit, kept apart by row-level security, and the keys readable only by our servers.

King by AdsHackers' use of information received from Google APIs will adhere to Google API Services User Data Policy, including the Limited Use requirements. The policy is published at https://developers.google.com/terms/api-services-user-data-policy

Google's public list of places (public list): when you name a place to target, King asks Google for that place's identifier. The request goes through your own connected Google Ads account, whose account number is part of the request, and carries the place's name and nothing else about you.

When you connect Meta, the ads_read permission lets us read the ad accounts your login can reach and, for the one you choose, its campaigns, ad sets, ads, audiences, creatives and pixels, with their daily figures — spend, impressions, reach, clicks, conversions and conversion value — and the account's status and spending state: whether it is active, its spending limit, amount spent, balance and payment method. Two more things are read only when your Meta login has granted the permission each one needs: the Instant Forms (lead forms) on your Pages, which need pages_manage_ads, and the product catalogs of the business that owns the ad account, which King can reach only with business_management. King requests these permissions for these features; access depends on what Meta approves and you grant, and King records a missing permission as unread rather than an empty list. We also read the Facebook Pages and Instagram accounts the ad account can advertise from, so a new ad can be published from one of them. The pages_show_list and pages_read_engagement permissions let us list the Facebook Pages you manage and read their basic details, so a new ad can be published from one of them.

When you ask King how things stand now, it can also read the ad account live with ads_read: figures for each ad set and each ad, over a window of up to the last 30 days or a custom date range you choose, with daily totals, broken down by age, gender, country, region, platform or placement; why Meta is holding or has rejected an ad, in Meta's own review and delivery notices; the buttons and links of each creative; and an ad set's estimated audience, as Meta estimates it.

Why: to show you your figures, to answer your questions, and — through the ads_management permission — to publish campaigns, add new ads to an ad set that already exists, copy a campaign, and pause, resume or re-budget campaigns. A copy is created paused, and can carry the changes you ask for: new countries, a new daily budget for the campaign or for each ad set, or a minimum ROAS. Each of these happens when you approve that change; pausing and re-budgeting also happen when an automation you set to act on its own makes the change.

Meta's live reads also cover account totals, the owning business, the monthly invoices of your business (their numbers, dates, amounts as Meta sends them, currency, status and type, for invoices issued from the first day of the month six months ago to today; King does not store the invoices in its database, and for a long list it keeps the rest in memory on its server for up to ten minutes while it answers you; what the assistant says about them stays in your conversation like any other reply), custom and saved audiences, product catalogs including shared catalogs, product sets, products, product feeds and upload diagnostics, catalog diagnostics (the problems Meta reports for one product catalog, with how many items each affects, as Meta sends them), advertising rules, advertising studies, activity history without personal actor details, ad previews, Facebook Pages, Instagram accounts and media, the public Ad Library, uploaded images and videos, and pixels. Available fields are checked against the documented read contract. Catalog operations use business_management and catalog_management; Instagram media through Facebook Login uses instagram_basic and the Page permissions. King's assistant can also read and change your Meta ad account through Meta's own official ads MCP server, using ads_mcp_management with the same connection. It changes nothing on its own: every change is shown to you on a card first and is made only after you press it. Those changes are saved as drafts in your Ads Manager; King never publishes them or turns them on. Missing permissions and incomplete pages are reported explicitly.

For Meta, King also reads: large reports for your campaigns, ad sets and ads; your account's recommendations and opportunity score; how your payment method is shown, exactly as Meta displays it; your custom conversions and your pixel's event counts; your pixel's data quality as Meta reports it, for web events only: Meta's event match quality score and which kinds of customer detail it matched, how much of your pixel's events the Conversions API covered over the last seven days, how your deduplication keys work, and how current the data is; and search results for interests, behaviours and locations when building targeting.

If you upload a list of your customers' email addresses or phone numbers to add them to a Meta audience, King turns each one into a one-way code on our server, sends only those codes to Meta, and does not keep the file, the addresses or the numbers.

When you approve a Meta object confirmation, King can create, edit or copy the supported campaign, ad set, ad, creative, lead form, audience, catalog, product, product set, feed, rule, study or custom conversion. An immutable form or creative needs a replacement instead of an unsupported content edit. New advertising objects and copies are paused. Each confirmed request is recorded once; an uncertain outcome is not automatically retried.

Submitted lead answers are different from form definitions: with leads_retrieval and the required Page permissions, King reads them only to display to you inside your account. Names, phone numbers, email addresses and submitted answers are not sent to the AI model and are not stored in King's conversation history, database, logs or alerts. The display is read live again when you request it; only its form and time-range parameters are kept.

Retention and deletion: we keep it while the connection exists. Pressing Disconnect on Meta in King, or deleting your account, deletes the figures we copied and the key, and asks Meta to remove our permissions. Removing King in your Facebook settings, under Business integrations, ends our access, and King then deletes the figures it copied and the key as well: the next time King reads the account — daily, for a business your plan covers — Meta answers that King was removed, King checks with Meta once more, and the copy is deleted. This needs a business your plan covers and a connection that was still working; otherwise press Disconnect in King — see Disconnecting.

To have everything deleted without signing in, write to hello@adshackers.com. The steps are on our data-deletion page, king.adshackers.com/data-deletion

When you connect Snapchat, we read the ad accounts your login can reach and, for the one you choose, its campaigns, ad squads, ads, creatives, audiences, its media library, pixels, apps, product catalogs and the public profiles they are published from, with their daily figures — spend, impressions and conversions — and whether the account can spend: its delivery status, its payment methods with their status, remaining credit and the last four digits of a card, and whether a payment has failed. The snapchat-marketing-api permission also lets King publish campaigns and change them — pause and resume campaigns, ad squads and ads, rename them, set when they start and end, change an ad squad's daily budget and bid, and change an existing campaign's countries, its age range, its languages, its lifetime spend cap and its ad text (the headline and brand name), and an ad squad's gender and regions — which it does only when you approve the change or when an automation you set to act on its own makes it. The snapchat-profile-api permission lets it read the public profile an ad is published from.

When you ask King how things stand now, it can also read the ad account live: figures for each ad squad and each ad within one campaign, over a window of up to the last 30 days, over a date range you choose of up to 31 days, or hour by hour; figures by country, region, gender, age, operating system or device make, which Snapchat estimates; an ad squad's estimated audience; an ad squad's bid estimate, the lowest and highest bid Snapchat estimates for it; a campaign's change history, an ad squad's change history, an ad's change history and a creative's change history, which say what changed, when, and through which app; the funding sources the account is paid from, with their type, status and budget, but never the name on a card, a PayPal email, the last four card digits or the expiry date; the ad account's media library, newest first, with each file's name, type, status and the date it was added, but never its download link; and the account's invoices, with their amounts, billing period, due date and whether Snapchat has collected them, but never the invoice document or any detail of the customer. King also reads the billing centres of your organisation: each one's name and the dates it was created and changed, but never its contact or address details. The ad account's lead generation forms, with each form's name, id and the types and wording of its questions, but never its legal text, and never a lead or anyone's answer. The interests Snapchat offers for targeting in one country, which King searches by the words you give; those words stay with King and are never sent to Snapchat. The places Snapchat lists for targeting in one country, its regions and metros, and its postal codes only when you ask for a postcode, which King searches by the words you give; those words stay with King and are never sent to Snapchat. Snapchat's change history names the person behind each change by email address and id; King removes both before anything else reads it, and keeps neither. For the Snap Pixel on the account, King reads its name and status, the websites it sent events from in the last seven days with each site's event count, and its events by type over up to the last 14 days. A pixel that Snapchat shares with the ad account from its organisation is read the same way: to find out that it is this account's, King reads the list of accounts the pixel is visible to, and keeps none of that list. For these reads King sends Snapchat only the ad account's id and the pixel's id, one website's name and the dates it asks about, and no visitor's or customer's detail. It reads only the counts Snapchat keeps for the pixel. For the product catalogs your organisation holds, King reads each catalog's id, name and vertical, the names of its product sets, and the first page of its products: each product's title, availability, price, sale price, condition and item group. It never reads a product's description, brand, link, image or custom labels, and it reads a catalog only when the organisation's own list names it. For each of those catalogs King also reads each catalog's product feed: its name, status, currency, type and the times Snapchat fetches it, but never where the feed comes from or its login. It reads the latest uploads of that feed, three at most: each upload's status and dates, the counts of the items it changed, and Snapchat's count of each issue, but never the address or login the upload came from.

Audiences you ask King to create on Snapchat: an audience of website events from a pixel in your ad account, an audience of people who engaged with your ads, or a lookalike built from a customer list that already exists in your account. King sends only the audience's own settings: its name, the pixel, engagement or list it is built from, and how long Snapchat keeps its members. It sends no personal data, and King uploads no customer list.

What we share with Snap: the campaigns, ads, creatives, collection tiles and interaction zones you approve publishing, and the changes you approve to them — and, separately, our own purchase reporting described under Who else sees it.

Retention and deletion: we keep it while the connection exists, and the figures and records we copied from it no longer than 36 months, as Snap's terms require: figures for days more than 36 months ago, and any campaign, ad or other record Snapchat has not described to us for 36 months, are deleted automatically. Pressing Disconnect on Snapchat in King, or deleting your account, deletes the figures we copied and the key. King does not end its own access at Snapchat, so remove King yourself at accounts.snapchat.com, under Manage Apps; until you do, the permission stays granted at Snapchat with no key on our side to use it. Removing King there first ends our access, and King then deletes the figures it copied and the key: the next time King reads the account — daily, for a business your plan covers — Snapchat refuses King's key, King checks with Snapchat once more, and the copy is deleted. This needs a business your plan covers and a connection that was still working; otherwise press Disconnect in King — see Disconnecting.

Snap's Privacy Policy applies to the data Snapchat holds about you, and is incorporated into this policy by reference: https://values.snap.com/privacy/privacy-policy

Data travels encrypted between your browser, our servers and each network (HTTPS).

The database itself keeps each business's data apart: row-level security means a signed-in person can read only the businesses they belong to.

The keys that let us reach your ad accounts are readable only by our servers. The database refuses them to any signed-in browser, yours included.

Supabase, which holds our database and our file storage, encrypts everything stored there at rest with AES-256.

Your advertising history and conversations stay for as long as your account exists, because King's usefulness depends on remembering what happened last season. Two things shorten that. The figures and records we copy from Snapchat are kept for at most 36 months, as Snap's terms require. And when you remove King at Meta, TikTok or Snapchat, King deletes what it copied from that network once it learns the access is gone — see Disconnecting.

Delete your account from Settings and we immediately delete every business you own and everything in it, including the connections to your ad accounts, and end our access at every network where King can do that itself. The exception today is the image and video files in your library: their entries go, but the files themselves stay in our private file storage, where no screen shows them. Delete them from the library first if you want them gone at once.

Ask us by email instead and we do the same within 30 days. Records we are required to keep for accounting are also kept, and they contain no advertising data.

Press Disconnect on any account in Connected accounts at any time. That deletes the figures we copied from it and the keys. King also ends its own access at Google, Meta and TikTok. At Snapchat and Shopify it does not yet, so the screen tells you where to remove us yourself.

Or remove King in the network's own settings. The access we held then stops working, so our reads stop. At Meta, TikTok and Snapchat, King also deletes the figures it copied from that network, and the key, once it learns the access is gone: the next time King reads the account — daily, for a business your plan covers — the network refuses, King checks with it once more, and the copy is deleted. King learns of it only by reading the account, and it reads only a connection that is still working, of a business a plan covers. While the business has no plan in force or is locked, or once the connection has stopped working for another reason, King does not read it and does not learn of the removal: press Disconnect in King to have the copy deleted. At every other network the figures stay until you press Disconnect in King or delete your account, and either one deletes them at once. Nothing else is touched: your conversations, your library and your other networks stay.

Our own: one cookie remembers your language, for a year, and one remembers which advertisement or site brought you, when one did, for 90 days. Once you sign in, Supabase Auth keeps you signed in with its own cookies, and a few more remember choices you make on screens — such as notices you have closed — or carry a connection or a password reset through its steps.

Other companies': the public pages of this site load Google Tag Manager, which loads Google Analytics and the advertising tags of Google Ads, Meta, TikTok and Snapchat; the pages inside your account do not. PostHog loads on every page, inside your account too. Each of them sets its own cookies or similar identifiers in your browser, to count visits and to measure which advertising works. They load as soon as a page opens: the site does not ask first.

Your browser's settings can block or delete any of them.

Ask us for a copy of everything we hold about you, ask us to correct it, or ask us to delete it. Write to hello@adshackers.com and we will answer within 30 days.