Security Policy
Version v1.0 · effective 20 September 2026 · binding on every account
What we do to protect the platform, and what you must do in return. It sits alongside the Terms, the Usage Policy and the Privacy notice. Accepting it is a condition of holding an account.
1. How the platform protects you
- Passwords are never stored in readable form. They are hashed with scrypt (16384/8/1) by the authentication service — slow by design, so a stolen database cannot be ground through.
- Two steps at every sign-in. Password, then a six-digit one-time code sent to your e-mail and phone. Codes are stored hashed, expire in ten minutes, are limited to five attempts and are consumed on use.
- Registration is verified on both a Gmail address and an Indian mobile number, so throwaway inboxes cannot hold accounts.
- Transport is encrypted end to end (HTTPS/TLS with automatically renewed certificates). Plain HTTP is redirected, never served.
- Separation between organisations is enforced in code: another tenant's camera or incident answers "not found", and the administrator's panel is invisible to operators.
- Automation is throttled — a signed single-use anti-robot challenge, plus limits of five sign-ups an hour and ten sign-in attempts every fifteen minutes per address.
- Video stays on your premises. Processing runs on your own GPU node; the server receives incidents, findings, status and preview images, not your footage.
- Sessions are signed tokens with a fixed lifetime, and a suspended account stops working immediately.
- Everything sensitive is audited — sign-ins, failures, blocked attempts, identity-sensitive reads and administrator actions, with timestamp and network address.
- Privacy by default — bystander faces are blurred before frames leave the processing machine, and identity escalation needs an approval.
2. What you must do
- Use a unique, strong password for this platform — at least eight characters, never reused from another service.
- Never share your password, your one-time codes or your session with anyone, including colleagues and anyone claiming to be support. We will never ask for your password or a code.
- Keep the e-mail account and phone number on your Eagles Eye account secure; they are the recovery path for it.
- Sign out on shared machines, and keep the browser and operating system you use up to date.
- Secure the machine running the GPU node: an up-to-date OS, a firewall, no unnecessary exposed ports, and a non-shared account. The node needs only outbound HTTPS — never forward a port to it from the internet.
- Secure the cameras themselves: change default passwords, keep firmware current, and keep camera streams on a private network segment.
- Give each person their own account. Do not create shared "control room" logins.
- Tell us immediately if a device, account, phone or e-mail is lost or compromised, so the account can be suspended.
3. Reporting a vulnerability
- Report suspected vulnerabilities to support@visioncoders.online with enough detail to reproduce them. We will acknowledge and respond.
- Please give us reasonable time to fix an issue before disclosing it publicly.
- You may not test against other organisations' data or accounts, degrade the service, run automated scanners against it, or access more data than a proof needs. Testing beyond your own account is a breach of the Usage Policy.
- We do not operate a paid bug bounty. We will credit you if you wish.
4. If something goes wrong
- On a suspected breach we will investigate, contain it, suspend affected accounts, and notify the organisations involved without undue delay.
- Where the law requires notification of an authority or of affected people, we will comply.
- We will tell you what we know plainly, including when the answer is that we do not yet know.
5. Honest limits
- This is an educational research platform, not a certified or independently audited security product. It has not been penetration-tested by a third party.
- No system is perfectly secure. The measures above reduce risk; they do not eliminate it.
- SMS and e-mail delivery depend on third-party providers and may be delayed or intercepted at the carrier level — a risk inherent to one-time codes everywhere.
- Data is stored on a single hosted server. Do not put anything on this platform that you could not tolerate losing or disclosing.
In short: we hash passwords properly, verify two channels, encrypt traffic, separate tenants and audit access — and we expect you to use a unique password, keep your codes to yourself, secure the machine your cameras run through, and tell us the moment something looks wrong.