Privacy policy for Bilby and navaal.ai

Navaal is operated by Waqas Ahmad, ABN 47 309 621 802, Sydney NSW, Australia.

Last updated 15 November 2026. This policy is in English only.

Who I am

Navaal is operated by Waqas Ahmad, ABN 47 309 621 802, Sydney NSW, Australia.

I run Navaal on my own, so “I” on this page means me. The one address for anything about your information is support@navaal.ai.

What this policy covers

It covers the navaal.ai website, its free tools, the free store scan, and Bilby, which checks an online store every night. The Navaal SEO app for Shopify has its own privacy policy at app.navaal.ai/privacy.

This page lists what I keep, so you can see it before you hand anything over. Where my code does less than I would like, such as deleting a record on a timer, the page says what it does today.

When you visit navaal.ai

A small script of mine counts visits. For each page it records the page address and the campaign tags (utm_source and the like) in the address you arrived by. When you arrive from another website it also records which website that was and, in the record of your actions, the page on it. Nothing else of the address you came from is kept, no query string and no fragment, and a move from one page of navaal.ai to another records no previous address. It also records your country, taken from the headers Cloudflare adds, your kind of device (phone, tablet or desktop), and actions such as starting a scan or pressing a button.

I keep no IP address with these records. To count each day’s visitors once, the page-view record holds a code made from your IP address and browser together with the day’s date; the code changes every day and the address itself is not stored. If you are signed in, the records of your actions are linked to your account and carry your email address. Once you give an email address in a tab, for a report, a form or a sign-in, that tab’s visit records can be tied to it too, and my admin view puts every visit that carried the same address together as one person, with the pages of each visit.

Browsing does not set a cookie. Your browser keeps, until you close the tab, a random visit id and your campaign tags (session storage keys nv_sid and nv_utm) and a note that a short animation has played (nv-walk-played). It keeps, until you clear it, your choice of day or night and your theme (local storage keys navaal-time and nv-theme). If you type your email address to get a sign-in link, your browser also keeps that address (local storage key nv_link_email) until it sees you signed in, and the blog page on whether Shopify is down keeps which boxes of its checklist you ticked (local storage key nv:sd-check:v1) until you clear it. If the address of a page that my platform serves, such as /bilby, ends in ?via= or ?ref= with a short code, your browser keeps that code (local storage key nv_via) until you clear it, and it is used for 60 days; the visit records then carry it so a visit can be credited to whoever gave out the link, and it goes with a checkout you start, to my server and to Stripe. The pages of the static site, such as the blog and the tools, do not set it. Signing in sets a cookie that keeps you signed in; it lasts 30 days and is renewed on each day you visit. Signing in with Google, or with Microsoft if I turn it on, also sets a short-lived cookie while you sign in.

navaal.ai has no advertising pixels, tag managers or outside analytics. One page asks an outside company for something from your browser: the page about the Shopify app has a video from YouTube, and nothing is loaded from YouTube until you press Play. Pressing it loads the player from YouTube’s privacy-enhanced address, and YouTube then sees your visit. The two scan tools no longer ask Google for a store’s icon; they draw its first letter instead.

The visit records are deleted when they are 400 days old.

When you use a free tool

The speed test and the security-certificate check record your IP address, the address you entered and whether it worked, so I can limit how often one visitor runs them each day. The speed test sends the address you enter to Google’s PageSpeed service. The product description writer records your IP address and how much it used for the same reason, and sends what you type (the product name, type, audience, features, keywords and brand) to Anthropic, an AI company, which writes the text.

I have not set a time after which these usage records are deleted.

The tracking check and the AI store check work differently. Your browser sends the address you type to a small service of mine that runs on Cloudflare. It reads up to four public files of that store (its home page, robots.txt, llms.txt and sitemap), following redirects a few steps, and asks Cloudflare’s public DNS service where each name points. It saves no record of the scan. To limit how often one visitor, and one store, can be scanned, Cloudflare’s rate limiter is given your IP address (an IPv6 address by its first 64 bits) and the host name of each store it reads, as counter keys that last 60 seconds; if the limiter cannot answer, the service counts your address in its own memory for the same minute.

When a store is scanned

A free scan opens a store’s home page, a collection and a product page, presses Add to cart, opens the cart and the first checkout page, and stops there, on a desktop and a phone. It never pays and never signs in. Bilby also scans public stores that nobody asked me to scan, for research into how often stores break; those use a lighter walk on a desktop only.

A scan keeps the store’s address, the pages it opened with their titles and load times, screenshots, the findings and a score. If you ran the scan I also keep your IP address, so I can limit how many a visitor starts in a day, and the country, region and city your visit came from, how you reached the site, and your email address if you asked for the report by email or gave it on a form.

I may publish combined, anonymous numbers from these scans. No store is named without its owner’s written yes. To keep Bilby away from a store, add a robots.txt rule that disallows the whole site for BilbyBot, or email me and I will add the store’s address to a do-not-scan list. The free scan and my research queue check that list before they start. The nightly walks of a store its owner monitors, and the rival walks described next, do not check it. Being on the list stops new free scans and research scans from starting; it does not delete anything already stored.

If you have Bilby Pro, Bilby also walks the rival stores you name, with the same light walk. Nobody at those stores asked for that, and the walk is kept as a scan of the rival’s address.

I have not set a time after which a free scan’s IP address, email address, location or store record is deleted, and the report PDFs of a scan are kept when its pictures are cleared out.

Bilby photographs pages that every visitor sees. Anything a store shows publicly, such as a review with a name, can therefore appear in a screenshot, and the screenshots are sent to Anthropic to be judged. Before a picture is taken Bilby blurs text that looks like an email address or a contact number, so those appear blurred in screenshots and video; this is a filter and can miss things. The up to 3,000 characters of page text sent to Anthropic with each screenshot are not blurred.

When you make an account

I keep your email address, your name if you give one, and how you sign in: a password, an emailed link, a passkey, Google or, if I turn it on, Microsoft. Each sign-in session records the IP address and browser it came from. Your account also holds an approximate location taken from the headers Cloudflare adds: country, region, city, time zone and a rough map position, with the browser’s description. Passwords must be at least ten characters. When you choose one, the first five characters of its SHA-1 fingerprint are sent to the Have I Been Pwned service to check whether it appears in a known breach; the password itself is not sent.

I keep an account until you delete it; I have not set any other time. When you use a tool while signed in, I save what you entered and the result, so you can find it again. I can open a 30-minute, read-only view of your account, and each time I do it is written to my audit record.

When Bilby watches your store

To watch a store I keep its address, your email address as its owner, the proof that the store is yours (an emailed code or a record in the store’s DNS) and the region it is walked from. I also keep the settings you choose for it: extra alert addresses, which severities to email, quiet hours, the day of the weekly summary, rival stores, search keywords, a monthly revenue estimate and a discount code. To suggest an address for the emailed code I may read the store’s public contact pages.

Each night Bilby opens the store in a real browser as a shopper would and keeps pages, screenshots, a video and a technical log of what the browser loaded and any errors. It keeps the findings, the scores and a record of every email it sent you, with the recipient and the subject.

A video or screenshot of a visit is deleted when the visit is 30 days old, or 90 days old if the store is verified and not paused; the screenshots of a visit whose picture I have approved for Bilby’s public wall are kept. A daily clean-up does this and works through a limited number each day, so a busy day can leave some of them a little longer. The text of each email Bilby sent is replaced after 90 days by a note that it was archived; the recipient, subject and time stay. Findings, scores and each visit’s technical log (which moves to storage when the pictures go) are not deleted on a timer.

Once a week Bilby sends the findings it recorded for your store, with the facts of the week, to Anthropic to write the weekly summary. If you have Bilby Pro, it also asks Anthropic’s Claude, with web search, buyer-style questions that do not carry your store’s name, once a month, and each week it searches DuckDuckGo for the keywords you chose. To warn you before your domain’s registration runs out, Bilby looks the domain up on rdap.org.

When you pay

Stripe takes your card and billing address and asks for a tax number if you have one; I never see your card number. I keep your Stripe customer and subscription numbers and your plan and its dates. Stripe is given your email address and name.

When you write to me

Email sent to a navaal.ai address is forwarded to my mailbox, which is a Gmail mailbox, and a copy of the sender, recipients, subject and text is stored in Navaal’s database so that a reply can be matched to what I sent. The contact form and the quote forms on the service pages keep your name, your email address, what you wrote, a contact number if you gave one, project, calculator estimate and choices you gave, and the page the form was on. They keep no IP address with the message, take no store address and start no scan, though a code made from your IP address (not the address itself) is counted for the day so I can limit how many enquiries one visitor sends. The enquiry also goes into the visit records with your email address. A help request sent from inside your account keeps your account, email address, name, store and what you wrote. The newsletter box keeps your email address and the form it came from. If you ask for a store’s status alerts, I keep your email address, a hash of your IP address and whether you confirmed. I may keep notes about you as a customer.

When I write to you from my dashboard, a link in my message can be one I made to record that you pressed it. I keep Resend’s reports on each email (sent, delivered, bounced or marked as spam). I have not set a time after which these records, or the forms and stored email, are deleted.

Emails from me

Emails come from “Bilby” at support@navaal.ai, and a reply reaches me. Bilby sends email because you asked for something or have an account: sign-in links, verification codes, the report you asked for, check-up and weekly emails you signed up for, alerts about your store, receipts and notices about your plan and payments, and, if I have the setting switched on, an acknowledgement of a form you sent.

No machine sends email to a store that never asked: the automated sender was removed and a switch in the code keeps it off. One exception, written by me by hand: when Bilby’s research finds a real fault on a store that never asked, I may send that store one plain email with the proof and no sales pitch, to a business address the store itself publishes, in Australia or the United States only, saying who I am and how to stop hearing from me. It is never a second email.

Until 13 November 2026 an automated sender did email some stores that had not asked. Its records are still kept and I still read them: the stores it picked and their status, the address and kind of each email it sent with when it was delivered, bounced or answered, the label I gave a reply, and the reason it recorded for writing to that business. The sender is gone and no code adds a new record about a store to them. I have not set a time after which they are deleted, and deleting an account does not touch them.

Who else receives it

These are the outside services my code sends personal information to. Apart from the email servers that deliver a message to its recipient, two more are named below the table.

ServiceWhat it does for NavaalWhat it receives
CloudflareServes navaal.ai, passes some paths to my servers, receives email sent to navaal.ai addresses and forwards it, and runs the scan service and its rate limiter for the two scan tools.Your browser’s requests; the email sent to navaal.ai addresses; in the two scan tools, the address you scan, and your IP address and the stores’ host names as counter keys for 60 seconds.
Fly.ioRuns my servers, my databases and the browsers Bilby walks stores with.Everything in my databases.
TigrisStores files.Screenshots, videos, technical logs, report files and the files of data exports.
StripeTakes payment and holds billing records.Card and billing details, your email address and name, a tax number if you give one, and the affiliate code if you arrived with one.
ResendSends my emails and reports on each one.Your email address and the content of each email.
AnthropicAn AI company. Judges screenshots, writes the weekly summary, writes product descriptions, answers Bilby Pro’s questions.For each page Bilby visits: a screenshot, its address and title, up to 3,000 characters of visible text and up to five failed requests and five browser errors. The week’s findings for a store. What you type into the description writer. Questions that carry no store name.
GoogleGoogle sign-in, the speed test, the mailbox email to navaal.ai is forwarded to, and YouTube.Your Google sign-in if you choose it; the address you speed-test; the email you send me; your browser’s request for the video, only if you press Play.
Have I Been PwnedChecks a new password against known breaches.The first five characters of the password’s SHA-1 fingerprint.
DuckDuckGo, rdap.org, IndexNowSearch look-up for Bilby Pro keywords; domain registration look-up; telling search engines a navaal.ai page changed.A keyword you chose; your store’s domain name; the address of a public page.

rdap.org passes the look-up on to the registry that runs the domain’s ending, so that registry also receives the domain name. Sign-in with Microsoft is in my code and works only if I set its keys; if I turn it on, Microsoft receives your sign-in.

Anthropic, Stripe, Resend, Google and Have I Been Pwned may handle what they receive outside Australia. Tigris file storage is set to an automatic region, so I cannot name the country where files are held.

My main servers are in Sydney. Bilby’s browsers run on Fly.io in Sydney, Virginia, Los Angeles, Toronto, London and Frankfurt, so what a visit records can be handled in any of those places.

Your choices and your data

Email support@navaal.ai to ask what I hold about you or your store, to have it corrected, or to have it deleted. I answer these myself. If you live in the European Union or the United Kingdom, your own law gives you rights too, and you use them the same way. I use the Australian Privacy Act and its Australian Privacy Principles as my guide.

With an account, your Account page does two things for you.

  • Export: it makes a file of your profile, sign-in methods, your 100 latest sign-in sessions, passkeys, plan, credits, tool runs, saved invoices, the records of your actions and a short list of audit entries about your account. For your stores it holds their address, region and verification, their check-up subscriptions, their scans and findings, and the subject and time of the emails Bilby sent you. I email you a link to the file, and the link works for seven days. The file itself stays in storage after the link stops working. It leaves out your approximate-location record, free-scan and store records made under your email address, contact messages, stored email and threads, notes about you, your stores’ settings (alert addresses, rivals, keywords, discount code) and the full audit record; email me at the address above for any of those.
  • Delete: there is a seven-day wait, in which an emailed link lets you change your mind; that email is sent only while my email service is switched on. After the wait I try to cancel any running plan with Stripe. If Stripe returns an error the deletion still goes ahead, and the error is only written to my server log, so if your plan is still running afterwards, email me. Your email address and name are replaced with a placeholder and your Stripe customer is renamed to match. Your sign-in sessions, sign-in methods, passkeys, tool runs and saved invoices are deleted. For your stores, the owner address is replaced, the store is no longer marked as verified, your check-up subscriptions are switched off, the recipients on the emails Bilby sent are replaced and their text emptied, and your share links are revoked.

Deleting an account does not delete everything. It leaves, in plain words:

  • The audit record. It lists what happened on accounts and stores (for example adding or removing a store, buying credits, exporting or deleting data, and what I do in support) with the email address of whoever acted, their IP address and browser, and the values before and after. It cannot be deleted: the database refuses to change or remove its rows, and a copy of each day is written to file storage.
  • Files already made. An export file is not removed from file storage when its link expires, and deleting the account removes only the link.
  • Your stores’ history. It does not delete a store’s scans, findings, pictures or logs, which go on to the times above.
  • Money and place. It leaves your billing records and your approximate-location record.
  • Free scans and store records. A free scan keeps its IP address and any email address given, and the store record keeps the email address and your account number.
  • What you sent me and I sent you: contact and quote forms and help requests, newsletter and status-alert sign-ups, stored email and email threads, the records Resend reports on each email, the links I made to record a press, the list of addresses I must not email, and my notes about you.
  • Visit records, until their 400 days are up; your email address in them is replaced.

If you want any of these removed, write to me; I cannot remove the audit record.

The shoppers on your store

Bilby visits your store from outside. It does not sign in, order or pay, and cannot see your orders or your customer list. It does not look for your shoppers’ details, but anything your store shows every visitor can appear in a screenshot.

Security

Pages on navaal.ai are sent over an encrypted connection. No online service is perfectly safe, and I do not claim this one is.

Children

Navaal is a tool for people who run online stores. It is not meant for children and does not ask your age.

Changes to this policy

When what I collect or who receives it changes, this page changes, and so does the date at the top.

How to reach me, and how to complain

Write to support@navaal.ai. If you are unhappy with how I handled your information, tell me first so I can put it right. You can also complain to the Office of the Australian Information Commissioner at oaic.gov.au. If you live in the European Union you may also complain to your own data protection authority, and in the United Kingdom that is the Information Commissioner’s Office at ico.org.uk.