EFFECTIVE AUGUST 16, 2026

Privacy Policy

This policy explains what information Zeekend uses, why we use it, and the choices available to brands, agent publishers, and users.

Information we collect

When an agent publisher’s app asks for a placement, the Zeekend SDK sends us the end user’s most recent message, optionally the app’s reply to it, the publisher’s key, a session identifier the SDK generates, and coarse locale. That is the whole of it.

We do not ask for, and the SDK does not attach, a name, email address, telephone number, account identifier, device identifier, advertising identifier (IDFA or GAID), or cookie. There is no cookie, no device graph, and no profile of a user built across apps. Matching is contextual: it runs on what is being discussed, not on who is asking.

To be precise about one thing: the message is sent as written. We shorten it; we do not scan it for personal details and remove them. If a user types their own name or email into a conversation, that text reaches us inside the message.

Every request also carries an IP address, as all web requests do. We use it to limit request rates and prevent abuse. We do not use it for targeting and do not store it against a user.

Separately, we collect account information, campaign settings, brand offers and placement rules from brands and publishers; the contact, company, website, scale and optional message you submit when requesting early access; messages you send us; and basic product usage and security logs.

How we use information

  • To decide whether a paid placement is eligible for a conversational moment.
  • To match an eligible brand offer with relevant context supplied by an agent publisher.
  • To deliver clearly disclosed placements and measure their performance.
  • To provide support, prevent fraud, keep Zeekend secure, and improve the product.
  • To review early-access requests and contact interested advertisers and AI platforms.

When information is shared

Advertisers never see the content of a user’s message. They receive performance and aggregated reporting only — which of their products ran, how well it matched, and whether it was seen or clicked. No advertiser sees another advertiser’s bid.

Deciding how well a product fits a conversation is done by a language model, so the message and the app’s reply are processed by Anthropic as our sub-processor. Conversation content leaves our own infrastructure for that step, and we would rather say so plainly than leave it inside the phrase “service providers.”

Beyond that, we share only what is needed with service providers that help operate Zeekend, with the brand and publisher involved in delivering an approved placement, when required by law, or as part of a business transaction. We do not sell information, and we do not share it with data brokers, ad networks, or identity resolution services.

Data choices and retention

Partners can disconnect an integration or ask us to access, correct, export, or delete information. We keep information only for as long as it is needed to provide the service, meet legal duties, resolve disputes, and protect Zeekend.

An end user’s request about data shared through a publisher’s app is best sent to that publisher, who holds the relationship with them; we will assist them with it.

Children and unknown-age users

Because we use no device or advertising identifier and do no personalisation or profiling, every Zeekend placement is non-personalised by design. That is the property rules for younger users are concerned with, and it does not depend on knowing anyone’s age — there is nothing to switch off, because the targeting was never there.

Zeekend is not currently listed as a self-certified ad SDK under Google Play’s Families policy. If an app is directed to children, is enrolled in Designed for Families, or its operator knows a user is under 13, they should tell us before going live and we will confirm our position in writing.

Conversation content is still processed by a language model, as described above. A publisher’s own privacy notice and Google Play Data Safety declaration need to cover that.

Security

We use reasonable technical and organizational safeguards designed to protect information. No system can guarantee perfect security, but we limit access and review our safeguards as the product changes.

Contact us

Questions or privacy requests can be sent to hello@zeekend.com.