Start free

Legal

Privacy policy

We store your account details, the brands and questions you ask us to track, and the answers and citations the engines return. We send your tracked questions to Perplexity and your payments to Stripe. Card payments are not switched on yet. Until they are, nothing on the site or in the app can charge a card, and a plan is paid by an invoice we send you ourselves. We do not sell anything to anyone.

Last updated 20 October 2026 · Plain-language draft, not yet reviewed by a lawyer

Read this first. This is a plain-language draft written from the database schema and the code as they actually are on 20 September 2026. It is not legal advice and it has not been reviewed by a lawyer. The owner should have it reviewed before anyone relies on it. Passages marked [OWNER TO CONFIRM: …] are facts we could not source from the system itself, and they must be filled in rather than guessed. The passages about signing in with Google were added on 5 October 2026 from code that is built but not switched on yet. The cookie list and the storage table were checked against the code again on 8 October 2026. That storage encryption is switched on for the database is the owner's confirmation, given on 8 October 2026; it was not read from the system itself.

Who we are

Bungad AEO is an Answer Engine Optimization subscription. The marketing site is bungad.com and the application is app.bungad.com.

  • Registered entity: [OWNER TO CONFIRM: registered entity name and, if any, its registration number]
  • Registered address: [OWNER TO CONFIRM: registered business address]
  • Contact for anything on this page: marvin@bungad.com
  • Data protection contact: [OWNER TO CONFIRM: whether a separate data protection contact or officer is required and who it is]

What we store, field by field

This list is taken from the application database, not from a template. If a field is not here, we do not have it.

WhatExactly which fields, and why we have them
Your account Email address, name, a bcrypt hash of your password, your role in the organisation, the date the account was created, the date the email address was confirmed if it ever is, whether you have ever chosen a password yourself, and, after a password change, the time before which older sign-ins stop working. This is what lets you sign in and what a monthly report would be addressed to.
Your organisation Organisation name, a URL slug and the plan it is on. This is what groups accounts, brands and billing together.
Billing A Stripe customer id, a Stripe subscription id, the subscription status, the date the current period ends, and whether the subscription is set to lapse at that date. Card numbers never reach us.
Brands you track Brand name, domain, an optional description, the names and domains of any competitors you add, and any facts about the brand you type in for us to check answers against, such as a price. This is whose name we look for in an answer.
Questions you track The text of each question, the buying intent you tag it with, and whether it is active. These are the questions we send to the engine.
What the engine answered The full answer text, which engine produced it, whether your brand was named, where it appeared among the brands named, a sentiment label, how long the call took, and any error. A score means nothing without the answers behind it.
What the engine cited Each cited URL, its domain, its title, its rank in the list, and whether it is your own domain. Citation share is computed from these rows.
Runs and reports When a check started and finished, whether it was manual or scheduled, the score and metrics computed from it, the actions we recommend, and for a monthly report its summary, its metrics and the addresses it was sent to.
Email plumbing A SHA-256 hash of any email confirmation link we issue — never the link itself — so the link can only be used once, plus a list of addresses a provider has refused, so they are not mailed again.
Rate-limit counters Short-lived counts of how often something was done, such as checks started or searches made, so one account or one address cannot run up the bill. They are kept under our internal id for your organisation, your user, a brand or a brand's site, or under a one-way hash of an IP address (for an IPv6 address on the free check, of its network prefix, the first half of the address), never the address itself; the ceilings for the whole service count everyone together under no id. Deleting your account removes the ones kept under your ids in the same step. A request already under way at that moment can leave one behind; it holds an internal id and a number, stops counting within two hours, or at the end of the calendar month for the two monthly counts, and is removed the next time the service clears expired counts, which happens as it is used and not on a schedule. The free check's daily counts are the exception: a daily job deletes them once they are two days old. Sign-in, sign-up and password-reset attempts are also counted under one-way hashes of the email address typed and of the IP address, whether or not an account exists for that email. These hold no id, so deleting your account cannot find them; they stop counting within an hour and are removed the next time the service clears expired counts.
Stripe events The id and type of each webhook event Stripe delivers, and when we finished handling it, so a redelivered event is not processed twice.
Google sign-in (Planned, not switched on yet) Only if you choose to sign in with Google: your Google account id, the email address that Google account had when you linked it, and when you linked it. Plus a 90-day history of Google sign-ins that records a pseudonym of your IP address, never the address. Details below.

Two things are worth stating in the negative, because they are the ones people assume. We never see or store a card number, expiry date or security code — those go straight to Stripe from your browser. And we do not build a profile of you, do not run behavioural advertising, and do not sell, rent or share your data with anyone for their own purposes.

The free visibility check

The check at app.bungad.com/check needs no account and asks for no personal details. You type a domain; we ask the engine what the site is, then ask three buyer questions in that category and count what comes back.

  • What is stored: the domain checked, the category the engine derived, the questions we asked, the counts and score we computed, the domains the engine cited instead, and what we found when we fetched that site's home page, robots.txt and llms.txt to see whether AI crawlers can read it.
  • What is deliberately not stored: the engine's answer text. The check keeps the measurement and discards the prose, so nothing an answer could be steered into saying becomes content we host.
  • Your IP address is not written to the database. The daily limits are counted against a keyed one-way HMAC of it, or for an IPv6 address of its network prefix, which cannot be turned back into an address. Devices on one IPv6 network therefore share one daily count. The raw address exists only transiently in server memory, and in our hosting provider's own request logs, which we do not control.
  • Results are cached and shared. A domain checked in the last seven days is served from the stored run rather than asked again, so anyone who checks the same domain inside that window sees the same stored result. The page always shows when it was measured.
  • It is capped. There are daily ceilings per address, per site and across the whole service, because every fresh check costs us money at the engine.

Anyone can check any domain, including yours. The check is public and unauthenticated, so a result may exist for a domain you own without you having asked for it. It contains only what a public AI answer already says about that category. If you want a stored result removed, email marvin@bungad.com.

Signing in with Google

Status: Planned. Not switched on yet. The code is written and tested, but there is no Google button you can use today, so nothing below has happened to anyone. We describe it now so that this page is already right on the day it is switched on.

When you choose to sign in with Google, we send you to Google, Google confirms who you are, and we keep the least that lets us recognise you next time.

  • What we keep from Google: your Google account id (Google calls it sub, and never reassigns it to anyone else), the email address that Google account had when you linked it, and the time you linked it. If you create a new account this way, the account also takes its email address and display name from Google, and the address counts as confirmed, because Google only lets us in with an address it has confirmed.
  • What we do not keep: your Google password, which never reaches us, your profile photo, or any Google access token. We ask Google only to confirm who you are (the openid email profile scopes) and use nothing from Google after the sign-in itself.
  • A sign-in history, kept 90 days, then deleted: a daily job removes each row 90 days after it is written, and the rows about your account go at once if you delete the account.
  • What a history row holds: one row per Google sign-up, sign-in, link, unlink or refused attempt, recording what happened, when, which account (none, for a refusal that matched no account) and a pseudonym of your IP address.
  • The IP pseudonym: a keyed HMAC under a key used for nothing else, so it cannot be turned back into an address or matched against our other hashes. The address itself is not stored.
  • Rate limits: starting a Google sign-in, and coming back from Google, are limited per IP address. The counters are keyed by an HMAC of the address under its own key, never by the address itself. Password attempts while linking or unlinking are limited per account.
  • Three short-lived cookies while you use it, listed under Cookies.
  • Unlinking removes the stored Google account id, email address and link time; the history rows stay until their 90 days are up. It needs a password you chose yourself, so nobody can unlink their only way in, and it signs out every other session.
  • Google itself knows that you signed in to Bungad, as it does for any site you use Google to sign in to. Google's own privacy policy governs that.

Who else sees your data

Four companies process data on our behalf, and one more receives your IP address simply because a page loads a font from it. There are no others.

WhoWhat reaches themWhy
Perplexity The text of the questions we run for you, under our API key. Not your name, your email or your account It is the engine that answers. Their own terms govern what they do with a request, and we do not control that
Stripe Your payment details, which you give to Stripe directly, plus your email address, your organisation's name, the plan you chose and our id for your organisation Stripe takes the payment and is the authority on your subscription. Card payments are not switched on yet. Until they are, nothing on the site or in the app can charge a card, and a plan is paid by an invoice we send you ourselves.
Amazon Web Services Everything in the storage table further up this page. The database runs on AWS RDS PostgreSQL in the ap-southeast-1 region, which is Singapore It is where the data lives
Vercel Every request to this site and to the app, including your IP address and browser details, in their platform request logs They host and serve both sites
Google Fonts Your IP address and browser details, when a page loads its typefaces The site loads two typefaces from Google's font CDN. Nothing else on this site calls a third party

There is no email provider configured yet. No message has ever been sent from this system. The monthly report is written and tested but dormant, and the confirmation and password-reset emails cannot deliver, because no provider key exists. When one is added, that provider becomes a fifth company processing data on our behalf, and it will hold a copy of every message sent to you, including its subject and its contents. This page will say so before that happens. The provider our code is written for is Resend. Once it is switched on, Resend will receive your email address and each email we send you, including alert emails if an account owner switches them on.

Slack, if you connect it. On Growth and above you can save a Slack webhook for a brand. We keep that webhook address, and post to it when you send a test and after scheduled checks. A post carries at most the brand's name, the names of competitors, scores and counts, and a link to the app that needs signing in. Never the text of an answer or a question, and never an email address. The message then sits in your Slack workspace, under your own agreement with Slack. Remove the webhook in Brand settings and nothing more is posted.

Google sign-in is not switched on yet either. When it is, and you choose it, Google learns that you signed in to Bungad. Signing in with Google says what we keep.

Cookies

The app sets three cookies while you use it, and a fourth for at most one minute after you delete your account. None of them tracks you. This marketing site sets one, the theme cookie below, and only when you choose a theme.

  • bungad_session — set when you sign up or sign in, and replaced when you change your name or password. A signed token carrying your user id, organisation id, email address and name, when it was issued, and a one-way tag of the password or Google account you signed in with (never the password itself), so the session stops working if that changes. It is HttpOnly, is SameSite=Lax so a browser does not send it with requests other sites make in the background, is marked Secure in production, and expires after fourteen days. Signing out deletes it.
  • bungad_plan_intent — set only when you create an account after clicking one of the plan buttons on this site. It holds the name of that plan and nothing about you, so the billing page can open on the plan you chose. It never grants a plan. It is HttpOnly and SameSite=Lax, is marked Secure in production, and expires after thirty days.
  • bungad-theme — set only when you choose a theme, in the app or at the foot of this site. It holds one word, light, dark or system, so the next page opens in the theme you chose; without it pages are light. It is shared by bungad.com and app.bungad.com, is SameSite=Lax, is marked Secure in production, and lasts a year. It is not HttpOnly, because the page itself writes it, and it says nothing about you. A copy of the same word is kept in that browser's local storage, used only if the cookie is missing. An older app-only cookie, bungad_theme (with an underscore), held the same word; it is being retired, is still read if the new one is missing, and is deleted the next time you choose a theme in the app.
  • __Host-bungad-deleted — set only when you delete your account, after the deletion has gone through. It holds the single character 1 and nothing about you or the account. The sign-in page you land on reads it as the instruction to clear the list of dismissed suggestions from that browser's local storage, and then removes it. If that page never loads, it expires by itself after one minute. It is HttpOnly, Secure and SameSite=Strict: a browser does not send it with any request that starts on another site, and no other host can set it.

When Google sign-in is switched on (it is not yet; see Signing in with Google), it adds three more, and only while you use it. All three are HttpOnly, Secure and SameSite=Lax:

  • __Host-bungad-google-oidc — set when you press the Google button. It holds a signed record of that one attempt: random one-time values that tie Google's reply to the attempt you started, what the attempt is for, the page to return to and, when you are already signed in, a one-way marker of your current session. Not your name or email address. It lasts at most ten minutes and is cleared when Google sends you back.
  • __Host-bungad-google-reauth — set only when you confirm who you are with Google again from your account page. It holds your user id, an expiry time and a tag tied to your current session, and proves for five minutes that you just did so. Deleting your account clears it.
  • __Host-bungad-google-unlinked — set only after you unlink Google from your account and the unlink worked. It holds your user id and an expiry time, signed, so the account page can tell you that Google is unlinked. It lasts two minutes.

Signing up with Google after clicking a plan button also sets bungad_plan_intent, described above, at the moment you press the Google button.

That is the entire list. This marketing site carries no analytics, no tag manager, no advertising pixel and no third-party script of any kind. The scripts on this site are our own and sit in the page itself: they set the year in the footer, open the menu on a narrow screen, show a swipe hint above a table that is too wide to fit, switch the plan tabs on the pricing page and play the example answer on the home page, and they apply and remember the theme you choose. Apart from that theme choice, none of them stores anything in your browser, and none sends anything anywhere. We do not ask for cookie consent: the sign-in cookies are strictly necessary for the app to work, the plan and theme cookies only remember a choice you made yourself, and the deletion marker only finishes a deletion you asked for. [OWNER TO CONFIRM: whether the applicable law still requires a cookie notice on that basis, in particular for bungad_plan_intent and bungad-theme]

Besides the theme copy described above, the app keeps one thing in your browser's local storage, which is not a cookie. When you dismiss a suggested brand in the app, the names you dismissed are saved in that browser under a key that starts with bungad:discover-dismissed: and ends with our id for the brand you were looking at. The list stays in that browser and is not sent to our servers. Clearing your browser's site data removes it. Deleting your account clears that list in the browser you delete from. Any other browser keeps its copy until you clear its site data.

Email

There is no mailing list and no newsletter. The only mail this system is built to send is a link to confirm your email address, a link to reset your password, and the monthly report for a brand you track. It has never sent any of them, because no email provider is configured. When sending starts, the way to stop receiving reports will be to reply to marvin@bungad.com and ask — there is no one-click unsubscribe endpoint yet, and we would rather say so than imply machinery that does not exist.

Where the data is and how it is protected

  • The database is AWS RDS PostgreSQL in ap-southeast-1 (Singapore), with storage encryption switched on, and is reached over TLS with a pinned Amazon certificate authority.
  • Passwords are stored as bcrypt hashes at cost factor 12. We cannot read your password and cannot tell you what it is.
  • Email confirmation links are stored as SHA-256 hashes, so a database dump contains nothing that can confirm an address.
  • Where an IP address is written to the database — the rate-limit counters today, and the Google sign-in history once that is switched on — it is stored only as a keyed HMAC, each use under a key of its own, never in the clear.
  • To slow down password guessing, the app counts attempts to sign in, sign up, reset a password and confirm an email address by IP address, and attempts to sign in, ask for a reset link or ask for a new confirmation link by the email address typed as well. Those counts are held in server memory and are not written to the database. Each one stops counting after five minutes to an hour, and is gone when that server instance shuts down.
  • Database backups are whatever AWS RDS is configured to take for this database, and we will not describe them more precisely than we can check. [OWNER TO CONFIRM: whether automated backups are enabled, the retention window, and where they are held]
  • Hosting is Vercel; secrets are held in Vercel's encrypted environment store and never in the source repository.

We are a very small operation and we will not pretend otherwise: there is no security certification, no formal security review process and no signed data processing agreement on offer today. If your procurement needs those, we are not yet the right supplier, and that is a fair reason to buy elsewhere.

How long we keep it

Two things are deleted on a schedule, by one job that runs once a day. The free check's daily counters are deleted once they are two days old: the job keeps today's and yesterday's and removes the rest, oldest first, in batches of 50,000 rows until none are left or its time for the night is up; anything left goes the next night. Google sign-in history will be deleted 90 days after each row is written, once Google sign-in is switched on. Alerts (what changed at each check, and whether it was sent by Slack or email) are kept 13 months, then deleted by the same daily job; they can be worked out again from the checks, which are kept. Nothing else is deleted on a schedule today. Account data, brands, questions, runs, answers and citations are kept for as long as the account exists, because the product is a trend over months and a deleted run is a hole in it. Free-check results are kept after their seven-day cache window expires. [OWNER TO CONFIRM: the retention period to commit to for account data]

Deleting your data

Sign in and go to Account. Delete this account removes your organisation and everything in our database that is tied to it, at once and with no undo: users, brands, competitors, brand facts and extra sites, questions, checks, answers, sources, recommendations and reports, and the usage counters kept under your ids. Your address is also removed from the suppression list. It asks for your password and for you to type DELETE, because a stolen session cookie carries neither. If the account has a subscription at Stripe, deleting the account cancels it there first, immediately, and you are not charged for it again. Nothing is refunded, including any time you have already paid for, and the page says so before anything is cancelled. Your customer record at Stripe is then deleted, which removes your card details there, and only after that is your data deleted here. If Stripe cannot be reached or does not confirm, nothing is deleted here, the page tells you what was and was not done at Stripe, and you can try again. You can still email marvin@bungad.com instead, from the email address on the account; how we check a request made by email is under Your rights, below. Once Google sign-in is switched on, deleting your account also removes a linked Google account id and your Google sign-in history. An account created with Google has no password of its own, so Delete this account will ask it to confirm with Google again and then delete within five minutes; email from the address on the account always works. Stripe keeps the deleted customer record so that its history can still be looked up. That record is Stripe's, and deleting your account here does not remove it.

Your rights

Which rights you have depends on where you live and which law applies to us, and that is exactly the kind of fact this draft must not invent. [OWNER TO CONFIRM: which privacy laws Bungad AEO is subject to — the owner is based in the Philippines, so the Data Privacy Act of 2012 is likely, and customers elsewhere may bring the GDPR or similar with them]

Independently of that, and as a matter of how we intend to behave: ask us for a copy of what we hold about you and we will send it; tell us something is wrong and we will correct it; ask us to delete your account and we will. We answer only to the email address on the account, and we act once you confirm from that address. A person does this by hand; it is not automated, and we never send a copy of an account's data to any other address.

Children

This is a business product. It is not directed at children and we do not knowingly collect data about anyone under [OWNER TO CONFIRM: the minimum age under the applicable law].

Changes to this policy

The date at the top is the date this page last changed. If a change materially affects what we collect or who we send it to, we will email account holders rather than quietly update the page — once there is an email provider able to send that message.

Common questions

What personal data does Bungad AEO store?

Your account email address, your name, a bcrypt hash of your password, your organisation name, the brands you track with their domains, the questions you ask us to track, and the answers and citations the engines return for those questions. We never store payment card details: Stripe holds those, and we keep only a Stripe customer id and the status of your subscription.

Which AI engines do you send my tracked questions to?

Perplexity, and only Perplexity. It is the one engine we hold an API key for. Adapters for OpenAI, Anthropic and Gemini exist in the code but are not keyed, so nothing is sent to them.

Does the free visibility check store anything about me?

It stores the domain that was checked, the category the engine derived for it, the questions we asked and the counts we measured. It does not store your IP address: the daily limits are keyed by a one-way HMAC of it, or of its network prefix for an IPv6 address, instead. A stored result is reused for seven days, so anyone who checks the same domain inside that window is shown the stored run rather than a fresh one.

Do you use tracking or advertising cookies?

No. This marketing site carries no analytics, advertising or tracking scripts at all. The app sets bungad_session, which holds a signed session token and lasts fourteen days; if you sign up from a plan button, bungad_plan_intent, which remembers that plan for thirty days; if you choose a theme on this site or in the app, bungad-theme, which remembers light, dark or system for a year; and, if you delete your account, __Host-bungad-deleted, which holds the single character 1, tells the next page to clear the list of dismissed suggestions saved in that browser, and lasts at most one minute. Google sign-in is not switched on yet; when it is, it adds three short-lived cookies while you use it. Web fonts are loaded from Google Fonts, so Google receives your IP address and browser details when a page loads.

How do I delete my account and my data?

Sign in and go to Account, where Delete this account removes your organisation and everything in our database that is tied to it. It asks for your password and for you to type DELETE. If the account has a subscription at Stripe, deleting cancels it there first, immediately and with no refund, and deletes your customer record at Stripe; the page says this before anything is cancelled, and if Stripe does not confirm, nothing is deleted. Apart from the free check's daily counters and Google sign-in history, which a daily job clears, nothing deletes data on a schedule, so until you ask, we keep it. You can also email marvin@bungad.com and we will do it for you, once you confirm from the email address on the account.