Privacy Policy
What we collect, why, where it goes and how long we keep it.
01Controller
The controller of personal data processed through the Service is BIDUA Industries Pvt Ltd (registered office: Suite 209, C-104, Sector 65, Noida, Uttar Pradesh 201301, India, CIN U72100UP2024PTC213229, GSTIN 09AANCB0882D1ZM). Contact: [email protected].
02The principle
Sentinel is local-first: detection runs on your device, and protection keeps working without our cloud. Data leaves the device only in the classes below and, for consumer devices, only after you turn on cloud reporting. Anything not explicitly classified is treated as the most sensitive class.
03What never leaves your device
- File contents and full file paths
- Browsing history
- Keystrokes, clipboard and screen contents (except during a remote screen session you approve on the phone)
- The full URL you paste into a link check (only the verdict and hostname, with consent)
- Text you paste into a message or scam check
- Your password-vault contents in readable form: the vault is encrypted in your browser and we store only ciphertext
04What we process
- Account data: name, email, organisation, role, password hash, login times and sessions.
- Device and server data (with consent on consumer devices): device name, OS and version, CPU, memory, disk, network and uptime figures.
- Security data: detection category, severity, rule, confidence, ATT&CK technique, link verdict and hostname.
- Server-agent data on servers you enrol: processes, services, containers, logs and authentication events, which may contain usernames and IP addresses.
- Android data on phones you link: posture signals, installed-app risk findings, a fingerprint of the installed-app list (the list itself when it changes) and, only when you enable sharing or a locate request is waiting, the phone's location.
- Audit records of administrative actions, commands and account changes.
- Payment records: plan, amount in rupees, any coupon used, and the payment gateway reference; never your card number or UPI PIN, which the gateway handles and we do not receive.
- Server vulnerability data (when you run vulnerability management): the package names and versions installed on a server, the network ports its services listen on, and the findings.
- Web attack data (when the server agent reads a web server log): the source address and the attack pattern in a request address, for sources that keep attacking; request bodies are never read.
- Site lists: the sites you block or allow for link checks on your phones.
- Optional family and new phone tools: family chat, chosen location sharing, shared daily usage totals, new-app counts and risk summaries. Sharing can be revoked. Other apps’ private messages are not collected.
- Optional reputation reports: numbers you submit for review and package/signer observations you consent to share. Pending number reports are not automatically trusted. Signer counts are scoped and small groups are suppressed.
05Why (legal bases)
- To provide the Service you asked for (performance of the contract).
- To keep the Service secure and to prevent abuse and fraud (our legitimate interest).
- Consent, which you can withdraw: cloud reporting on consumer devices, phone location, and e-mail breach monitoring.
- To keep the tax and accounting records the law requires (legal obligation).
06Consent you control
Cloud reporting is off by default on consumer devices and can be turned off at any time. Turning it off also stops events already waiting in the queue from being sent, and the server refuses telemetry from a device with reporting off.
Local scans do not upload scanned files. Downloading threat-list updates contacts the service. Optional reports and provider checks have their own consent and connection requirements.
08Retention
How long we keep things:
- Host metrics: 7 days.
- Anomaly records: 30 days.
- Desktop detections, alerts and incidents: 90 days on the device; raw desktop events 30 days.
- Quarantined files: until you act.
- Undelivered Android commands: 7 days.
- Backups: 14 days, at least three kept.
- Security events and the audit trail: kept for 12 months. Automatic deletion is not switched on yet, so until it is they stay until you ask us to delete them or close your account.
- Vulnerability findings and playbook run history: kept until you delete the server or the playbook, or close your account.
09Where data is stored
The Service is hosted on a server we operate at a hosting provider. Region selection (data residency) is not available yet; write to us if where your data is stored matters to you.
10Security of processing
Connections to the Service use TLS. Device secrets are stored as hashes; alert-channel and database-monitor credentials are encrypted at rest; agent updates are signed. Known gaps are listed in the trust center, including that database contents other than those named are not encrypted by the application.
11Your rights
From your account page you can export your data as JSON and request deletion of your account. A deletion request can be withdrawn for 7 days; after that an operator removes the account.
For a copy in another form, a correction, or anything else, write to [email protected] with the subject "Privacy request".
12Children
Accounts are for adults. An adult can pair a child’s phone without creating a child account. Family sharing depends on permissions and consent on the paired phone; an adult does not gain access to another person’s private chats.
13Changes
We will post changes here and notify account holders of material changes.