Security and vulnerability disclosure

If you have found a security problem in CalculatorLib, we want to hear about it, and this page tells you exactly how to tell us, what we will do about it and how quickly. It is the policy referenced by our security.txt file.

How to report

Email [email protected]. Please write in English or Vietnamese. One report per issue.

[email protected]

What helps us most, in this order: the URL or endpoint, the steps to reproduce it, what you saw happen, and the date and time you tested. A short proof of concept beats a long description. If the issue exposes somebody else's data, tell us what you saw but please do not download, keep or share it.

What we promise

We acknowledge every report within 5 working days, and that reply comes from a person, not an autoresponder. We will tell you whether we consider it a vulnerability, and once it is fixed we will tell you that too. If a report needs longer than a month to resolve we will say why rather than going quiet.

Service status

Live availability of the website, calculations, the API and the MCP endpoint, checked every 60 seconds from an independent host, is published on our status page, together with any incident and every planned maintenance window. You can follow it by RSS.

Open status.calculatorlib.com · Status feed (RSS)

Safe harbour

If you research in good faith, follow this page and give us a reasonable chance to fix the problem before telling anyone else, we will not take legal action against you and will not ask anybody else to. We will treat your report as an authorised test. If a third party brings a claim about research that followed these rules, we will say publicly that it was authorised.

What is in scope

calculatorlib.com and its subdomains, the public API under /api, the MCP endpoint, the embeddable calculator widget, and the account and billing flows.

What is out of scope

Reports about the third-party services listed on our subprocessors page — send those to the provider. Denial of service, load testing and traffic floods. Social engineering of our staff or our users, and anything physical. Automated scanner output with no demonstrated impact, including missing headers, missing SPF or DMARC records on domains that send no mail, and version-number fingerprinting. Reports that require a user to be already compromised, or to paste code into their own browser console.

We do not pay for reports

There is no bug bounty and we are not going to pretend otherwise so that you find out after the work. We will credit you by name if you want that, and we answer every report from a person.

How we test our own code

New code is scanned for leaked secrets every hour, and the full history of the repository is rescanned weekly. The JavaScript packages we ship are checked for known vulnerabilities every week. These scans run on our own operations infrastructure and alert the people who run the service; fixes go out through reviewed releases. Independent external testing is arranged for enterprise engagements; ask us and we will tell you where that stands.

Who can see your data

Only the people who operate the service can open its administration area; nobody else at a vendor or partner has an account there. Administrative sessions expire after 30 days, and administrative actions are written to an audit log that is kept for 730 days. Two-factor authentication is available for administrator accounts. The services that process data on our behalf, and what each of them receives, are listed on our subprocessors page.

How long we keep things

Records that expire on their own, and the ones that do not. Each period below is read straight from the expiry rule the database is configured with, so this table cannot quietly go out of date.

Record Kept for
Security and admin audit trail 730 days
Your signed-in devices 35 days
Staff signed-in devices 30 days
Sign-in IP history 90 days
Payment provider events 180 days
API and MCP usage counts 400 days
Browser extension usage counts 400 days
Browser extension uninstall survey answers 400 days
Browser extension telemetry counts (opt-in, per day) 400 days
Browser extension calculator demand counts (which tools, per day; no query, no identity) 400 days
Browser extension refused-request ledger (pseudonymous network bucket or account id) 90 days
Browser extension synced history (calculators you opened, values only with your consent) 400 days
Per-calculator usage counts 400 days
Embedded widget usage counts 400 days
Skill downloads 180 days
Webhook delivery attempts 30 days
Assistant and MCP request logs 30 days
Searches that found nothing 90 days
Pending erasure follow-ups 30 days
Changed page addresses queued for search engines 30 days
Game data erasure requests (Tính Nhanh) 90 days
Sign-in links sent by email 2 hours
Your account and saved work Until you delete it
Support conversations Kept as a record; your name and address are removed when you delete your account
Invoices and payment records Kept as long as tax law requires

Deleting your account removes the records tied to you before their period is up — see the privacy policy for what that covers and what survives as an anonymous row.

security.txt

Our machine-readable contact file lives at /.well-known/security.txt and is the canonical version of the contact details above.

View security.txt

Privacy policy · Subprocessors