Privacy policy

Last updated: October 14, 2026

This page explains what data Bina collects about you and your site’s visitors, what it’s used for and how long it’s kept.

1. In short

  • The Bina script sets no cookies and doesn’t store your visitors’ IP addresses.
  • We use data to provide and improve Bina. We don’t sell it or use it for advertising.
  • When you delete your account, your monitoring data and personal details are deleted 30 days later.

2. Data about your site’s visitors

The site owner decides to add the Bina script to their site. Bina processes visitor data on the owner’s behalf and only to provide the service.

For each visit, the Bina script sends:

  • The page address and the domain of the site the visitor came from
  • The type of device (phone, tablet or computer) and the browser name
  • A temporary id that changes every time a page loads and is never stored in a cookie or in browser storage. It can’t be used to follow a visitor from one page to the next.

On plans with speed and error monitoring, it also sends:

  • Page speed measurements (Web Vitals)
  • The text of the site’s JavaScript errors, the first few lines of where they happened, and the browser and operating system name

Error text is whatever your site’s code produces. If your site puts personal details (such as a user’s email) in an error message, that text is stored as is. Bina doesn’t remove such details automatically yet.

Visitors’ IP addresses are only used to block excessive requests, kept in hashed form for a few minutes, and never written to server logs. Visits from bots and automated browsers aren’t counted.

3. Data about your account

  • Account details: name, email, mobile number and password. The password is stored hashed and nobody can see it.
  • Sites and alerts: your site addresses, check results, incidents and the history of alerts sent.
  • Alert channels: your Telegram chat id, the mobile number for SMS, your email, and for browser notifications the browser’s subscription details and its name (such as “Chrome on Windows”).
  • Wallet: top-ups and SMS charges.
  • Support: your tickets and the images you attach.
  • Dashboard use: for each day we only record which hours you used the dashboard, which sections you opened and the kind of device. No IP address or click details are stored.

4. How we use data

We use this data to monitor your site, build the dashboard’s reports, send alerts and account messages (such as sign-in codes and password changes), and answer your tickets. We also use it to keep accounts secure, prevent abuse (such as getting the free trial again), fix problems, understand how the dashboard is used so we can improve it, and meet legal obligations. We don’t sell your data or use it for advertising. You can turn off announcement emails from the link at the bottom of any such email or from your account settings.

5. Services we work with

To provide parts of the service, the data needed is sent to these services. Each one only receives the data its task needs.

ServiceWhat it does and the data it receives
Content delivery network (CDN) and cloud storageServing the Bina website and storing ticket attachments. The CDN sees the IP address of requests.
Payment gateway (Zarinpal)The wallet top-up amount. The gateway takes your card details itself, and they never reach Bina.
SMS serviceThe mobile number and the message text
TelegramSending alerts to the chat you connected
Email serviceThe email address and the message text
Browser push serviceNotifications are delivered through your browser maker’s service.
AI serviceWriting explanations of site errors. Only details of the error itself are sent.

6. Cookies

  • The Bina website sets one cookie, only to keep you signed in. The theme and language you choose are saved in your browser’s storage.
  • Visits to this site’s public pages are counted with Bina’s own script, which sets no cookie and stores nothing that identifies you.
  • The Bina script sets no cookies on your site.
  • If “Don’t count visits from admins and authors” is on in the WordPress plugin, the plugin sets the bina_ignore cookie only in the browsers of signed-in users who can edit posts. The cookie only says that the visit shouldn’t be counted and is never sent to Bina’s servers.

7. How long data is kept

DataKept for
Visits, errors, speed measurements and check results90 days. Each plan shows part of this range.
Incidents and alert historyAs long as the account is active.
Dashboard use history400 days
A browser you disconnected from notifications90 days after disconnecting
An attached image whose ticket was never sent24 hours

8. Deleting your account

When you delete your account from Settings, sign-in, monitoring and alerts stop at once. 30 days later your sites and all their data, channels, team members and blog comments are deleted. Your name, mobile number, email and password are deleted too.

Wallet transactions and support tickets are kept without your name, for financial and support records. To prevent signing up again with the same email and number, an irreversible hashed form of them is kept.

9. Access by the Bina team

To answer tickets, the support team can view your dashboard read-only for up to 30 minutes. Nothing can be changed during that time, a notice shows at the top of the dashboard, and every view is logged.

10. Security

All connections are encrypted with HTTPS. Ticket attachments are private and only open through short-lived links. Still, no system is completely safe. If you find a security problem, tell us at support@binaguard.ir.

11. Telling your own visitors

If your site has a privacy policy, mention that it uses Bina. Also, don’t put your users’ personal details in error messages.

12. Changes and contact

You can see and correct your account details in Settings. To get a copy of your data, ask support.

If this policy changes, the date at the top of the page is updated and we email you about important changes. For any question about your data, open a ticket or email support@binaguard.ir.