Privacy policy
Effective 18 November 2026
This is a translation for convenience. The Thai version is the legally binding one; if the two differ, the Thai version prevails.
Bologu is a website security scanner. We collect as little data as possible, and most of it deletes itself within a few hours, except the service logs the law requires us to keep for at least 90 days. This page explains plainly what the system stores, why and for how long, in line with Thailand’s Personal Data Protection Act B.E. 2562 (2019) (PDPA).
1. Who is responsible for your data
The data controller is Bologu (bologu.com). For anything about personal data, contact [email protected]
2. What we store, and for how long
We have no accounts and don’t ask for your name, email or phone number. This is everything the system stores:
- The URL you ask us to scan, and the result. Results come from what that site already shows everyone (its pages, JavaScript files and headers). Kept 24 hours. Deep scan, Supabase audit and GitHub code scan reports are kept 6 hours. Paid website scan reports are kept 30 days, while Deep scan, Supabase and GitHub reports are still deleted within 6 hours of the scan even when paid (you can download the files to keep). After that they are deleted automatically.
- IP address. Used to limit how many scans can be started per minute (kept at most 1 minute), and recorded with domain ownership verification for the Deep scan (verification requests kept 24 hours, verified domains kept 7 days).
- Strictly necessary cookies only: a cookie that marks this browser as the owner of a private report (6 hours) and a cookie for a GitHub or Supabase connection (at most 1 hour). All are random values JavaScript can’t read. We use no advertising or tracking cookies.
- Messages sent with the “Wrong warning? Tell us” button. We store the check’s rule ID, the severity, the type of scan and the text you type. No URL, code or IP. Only the latest 500 are kept, to improve our checks.
- Usage statistics. Daily totals, such as the number of scans per mode, the grades given and the most common issues. No URLs or IPs, and nothing that identifies anyone. Kept 90 days.
- Security event log. Only for suspicious requests, such as scans aimed at internal networks, attempts to reach the admin area, requests for someone else’s report or use above our limits. We record the time, IP address, User-Agent, the path requested and the scan target, to prevent attacks and misuse (legitimate interest). Kept at most 30 days. Normal use is not recorded here (but is recorded in the service log below).
- Service log (computer traffic data). Every time your browser calls our system, for example to start a scan, open a report, download a file or pay, we record the date and time (UTC), IP address, User-Agent, the part of the system called and the result, together with details of that use: the URL or repo scanned, the type of scan, the Stripe payment reference, the connected GitHub username, the Supabase project/organization ID audited, and a hash of the cookie (used to link requests from the same browser; it can’t be used as the cookie). We don’t record report contents, code, tokens or anything you type. We keep this because section 26 of Thailand’s Computer Crime Act requires service providers to keep it for at least 90 days (legal obligation). It is kept about 100 days and then deleted automatically, unless an authority lawfully orders us to keep it longer. Only the system administrator can access it, and it is given only to authorities with legal power to request it, on formal request.
- Block list. In case of misuse, the administrator may record that domain or IP to suspend its use until the block is lifted.
3. When you connect GitHub
- You choose which repos the Bologu app may access. The app can only read code; it can’t change files or push.
- The token GitHub gives us is kept at most 1 hour and then deleted automatically, or immediately when you disconnect.
- Code is read in memory during the scan; it is not written to disk and not kept after the scan. The report contains only file names, line numbers and short excerpts from the lines with problems, with anything that looks like a key or password hidden.
- Package names and versions from package.json and lockfiles (not code) are sent to the npm registry and Google’s OSV.dev vulnerability database to find packages that don’t exist or have known vulnerabilities.
- You can revoke access any time in GitHub → Settings → Applications → Installed GitHub Apps → Bologu → Uninstall.
4. When you connect Supabase
- We ask for read-only access, to see your project list, Security Advisor and Performance Advisor results, Auth settings, backup status and the conditions of your RLS policies (read from pg_policies with Supabase’s read-only user).
- We never read the data in your tables and never change any settings.
- The token is kept at most 1 hour. We don’t keep a refresh token, so we can’t extend the connection on our own.
- You can revoke access any time in Supabase Dashboard → Organization settings → OAuth Apps → Authorized apps.
5. What we use data for
- To scan the site or code you asked us to and show you the result (providing the service you requested).
- To prevent misuse, such as mass requests or Deep scans of sites the user doesn’t own (legitimate interest).
- To keep the service log required by law and provide it to authorities on lawful request (legal obligation).
We don’t sell data, don’t show ads and don’t use your code or results to train AI.
6. Service providers and transfers abroad
The system runs on these services, which may see or log IP addresses under their own policies:
- Cloudflare: serves the website and stores the service log files (Cloudflare R2)
- Railway: servers and temporary database, located in Singapore
- Google Fonts: the website’s fonts
- GitHub and Supabase: only when you choose to connect your account
- npm registry and OSV.dev: receive only package names and versions during a GitHub code scan
- Stripe: payments (if you pay). We never see or store your card details, only the payment reference.
Our servers are outside Thailand, so the data described above is processed abroad. We choose providers with data security standards and send only what is needed to provide the service.
7. Security
- Every connection uses HTTPS, and GitHub and Supabase tokens are never sent back to the browser.
- Deep scan, Supabase and code scan reports open only in the browser that started the scan; anyone else with the link sees it as not found.
- Regular (passive) website scan reports can be opened by anyone with the link for 24 hours. Don’t share the link if you don’t want others to see it.
8. Your rights
Under the PDPA you have the right to access, obtain a copy of, correct, delete, restrict the use of, object to the processing of, and port your personal data. Send requests to [email protected]. We reply within 30 days. Most of our data deletes itself within 24 hours, so if a request arrives after that, there may be nothing left to act on. The service log can’t be deleted or changed before 90 days because the law requires us to keep it, but you may ask to see or get a copy of the parts about you.
If you believe we have handled data wrongly, you can complain to Thailand’s Office of the Personal Data Protection Committee (PDPC).
9. Sites that get scanned
If you own a site that someone scanned through Bologu without permission, tell us at [email protected]. A regular scan reads only what any browser can see, and a Deep scan works only on domains whose ownership has been verified. See also the terms of use.
10. Changes to this policy
If we change how we store or use data, we will update this page and the effective date above before the change takes effect.
