Skip to content
Blisscco

Privacy Policy

Last updated: 3 November 2026

Blisscco is an online ad network for AI chatbot platforms that is in early access. Ads are served only to publishers our team has approved, and the dashboard on this site shows your own account data.

This policy describes how the current product handles data: account information, requests from publishers to the Ad API, ad events, and contextual matching. It describes what the service does today. It is not a statement that Blisscco meets the requirements of any particular privacy law or certification.

  • Email address and password when you create an account with email. Passwords are handled by our authentication provider and stored only in hashed form. We cannot read them.
  • Account type and status: whether you joined as an advertiser or an AI publisher, and whether the account is active.
  • Google sign-in: if you choose “Continue with Google”, Google shares your email address with us, and may also share your name and profile picture. We use your email address to create and recognise your account. We do not currently use or display your name or picture.
  • Advertiser details: the campaigns you create (name, description, category, budgets and dates) and your ads (headline, ad text, button text and destination URL).
  • Publisher details: the platform name, website and category you save, your API key records (a name, a short prefix, the last four characters, and created, last used and expiry times), and any earnings and payout request records shown in your dashboard.
  • Technical data that any website receives, such as IP address and browser type, which our hosting provider may keep in standard server logs.

Publishers call the Ad API from their own servers. A request carries the publisher’s API key in a header and a topic: one category slug such as gaming, chosen by the publisher’s own code. It may also carry up to two fallback topics, up to 20 ids of ads the publisher already showed, and a random retry key.

The API accepts no other field. A request that includes a prompt, a message or a user identifier is rejected with an error. Blisscco does not receive, store or log chatbot prompts, conversations or user identifiers through the Ad API.

The API reads a request only to check it against the fields above. The Ad API code does not write the request body to our database and does not log it. Our hosting provider may still keep standard server logs of the request itself (see Technical data above).

What Blisscco keeps from a request that returns an ad:

  • A serve record: which publisher received which ad from which campaign, for which topic, and when.
  • A retry record that links the publisher and the retry key to the ad that was chosen, so a repeated request does not count twice. These records are set up to be removed after about 48 hours.
  • Only a one-way hash of an API key is stored. The full key is shown once when it is created and cannot be shown again.

To limit abuse, the ad endpoints use a best-effort rate limit. For this, the requesting IP address is held in server memory for about a minute. This limit does not write it to our database.

Blisscco records three kinds of ad events, each linked to one serve record: a serve (the ad was handed to the publisher), an impression (the publisher reports that the ad was shown) and a click. An event record holds the publisher, campaign and ad it belongs to, the event type, where it was reported from, and timestamps. It has no field for a prompt, IP address, user agent, user id or referrer.

Impressions are reported by the publisher’s server using a signed token that expires, one hour after the serve by default. A click goes through a Blisscco click link: the person’s browser contacts Blisscco, which checks the link and redirects to the advertiser’s destination. As with any website, our hosting provider may keep standard server logs of that visit (see Technical data above). Once the person reaches the advertiser’s site, the advertiser’s own privacy practices apply.

Impression and click counts depend on the publisher reporting them honestly. We use event data for counts and reporting in dashboards, and to keep the service working and secure.

Matching works on the topic alone. Blisscco compares the topic with the category of eligible, approved campaigns and returns at most one ad, or no ad. It does not read conversations, build a profile of a person, use a person’s history, or send anything to an external AI service.

Sensitive topics, for example health, religion or politics, are not matched and return no ad. Publishers are asked not to request ads in sensitive conversations in the first place.

Publishers run their own chatbot products. What a publisher shows to its users, and what it tells them about sponsored placements, is the publisher’s responsibility.

The website does not collect or store chatbot conversations, and it does not sell your personal data. The website itself does not currently use advertising or analytics trackers.

We use your information to create your account, log you in, send account emails such as email verification, run campaigns and the Ad API, show you your own counts and earnings, keep the service secure, and prevent misuse. We do not use it for any other purpose without telling you first.

We use only essential cookies that keep you logged in and complete the sign-in process (including the temporary steps of signing in with Google). We do not use advertising cookies. Logging out ends the session on that device.

  • Supabase, for authentication and our database.
  • Vercel, for hosting this website.
  • Google, if you choose to sign in with Google.

We keep your account information while your account exists. You can ask us to delete your account and the data linked to it at any time using the contact below.

Serve and event records are set up to be removed by a cleanup routine once they are about 90 days old. Spend and earnings totals are kept separately from these logs.

These periods, and the 48-hour period for retry records above, are what the cleanup is set up to do. The cleanup relies on a scheduled database job that is switched on separately, so they are targets and not a guarantee.

Connections to this site use HTTPS. API keys are stored only as hashes, and tracking tokens are signed and expire. We take reasonable steps to protect your data, but no online service can promise perfect security.

Blisscco is a business service and is not directed at children.

When our services change, we will update this page and the date above. If a change is significant, we will make it clear on the site.

For questions about this policy or to request deletion of your data, email support.blisscco@gmail.com.

← Back to the Blisscco home page