Security
This page lists the security controls we run today, so you can check them instead of taking our word for it. Where a control has a limit, we say so.
Automated code scanning, every day
Six scanners run every day across our code, history, dependencies and container image. A scan that finds a problem fails and notifies us.
-
Static analysis
Semgrep
Scans the application for cross-site scripting, injection, command injection, unsafe cryptography and hard-coded secrets using the community
p/python,p/security-audit,p/xss,p/command-injectionandp/secretsrule packs. Any high-severity finding fails the run. -
Static analysis
Bandit
Python-specific security checks for the application code, such as
shell=True,eval/execand weak crypto. Runs at medium severity and confidence and above, and fails the run on a finding. -
Secrets
Gitleaks
Scans the full git history, not just the latest commit, for API keys, tokens and credentials committed by mistake. A leaked secret fails the run.
-
Dependencies, container and config
Trivy
Scans our Python and npm lockfiles, the built container image (operating-system packages and everything installed in it) and the Dockerfile and deploy configuration for misconfigurations. A high or critical issue that has a fix available fails the run.
-
Dependencies
OSV-Scanner
Checks the npm packages behind our JavaScript SDK and MCP server against the OSV vulnerability database, daily. Any advisory we have not reviewed fails the run.
-
Dependencies
pip-audit
Checks every pinned runtime Python package against public vulnerability advisories, daily, so a package that turns vulnerable after we shipped is flagged within a day. Any advisory we have not reviewed fails the run.
Dependabot also opens monthly update proposals for our Python, npm, container and CI dependencies, and each one is tested before it is merged.
A few advisories in third-party packages are reviewed and tracked rather than fixed, because the package that depends on them pins an older version. We list each one in the workflow with the reason, and we remove it when the pin lifts.
Credentials and access
-
API keys are stored hashed
We keep only a SHA-256 hash of each key. The full key is shown once at creation, so we cannot read it back. Lost keys are replaced, not recovered.
-
Self-service key rotation
You can rotate a key from the dashboard at any time. The old secret stops working immediately and your plan and usage history carry over.
-
Passwords use bcrypt
Account passwords are stored as salted bcrypt hashes. You can also sign in with Google or GitHub.
-
Hardened session cookie
The dashboard session cookie is signed,
HttpOnly,SameSite=Lax, andSecurein production. -
Rate limits and abuse controls
Every key has a daily request limit. Free keys also share a per-IP cap, and account signups are limited per IP and per subnet.
-
Payments stay with the gateway
We do not store card details. Payments are processed by our payment gateways.
Transport and browser protections
-
HTTPS enforced
Production responses send
Strict-Transport-Securityfor one year, including subdomains. -
Security headers
Every response sends
X-Content-Type-Options: nosniff,X-Frame-Options: DENYand astrict-origin-when-cross-originreferrer policy.
Infrastructure and data handling
-
Private service network
The API reaches its database and cache over a private network, not the public internet.
-
Off-host backups
The database is backed up twice a day to separate object storage outside the primary host, so a problem with that host cannot take the backups with it.
-
Limited request logging
Per-key usage and request-IP records are deleted after about 13 months. They hold daily counts and IP addresses, not request bodies.
-
Delete your account
You can delete your account from the dashboard. See our Privacy Policy for what is retained.
Report a vulnerability
If you find a security issue, email
[email protected]
with the subject “Security report”. Please give us reasonable time to
fix it before disclosing it publicly, and do not access other customers’
data. Our machine-readable contact is at
/.well-known/security.txt.
What we do not claim
BharatStock has not been through a third-party SOC 2 or ISO 27001 audit. The controls above are our own, and each one is something you can check. Automated scanning reduces risk; it does not guarantee that the software is free of vulnerabilities. For the freshness and accuracy of our data, see the Data Trust & Status page.