The short version: your business plan content is yours. We protect it with encrypted transport, hashed credentials, hardened access, and a small set of named vendors that each do one job. Everything below states what we actually do today, with no certifications claimed that we do not hold.
1. What we store
We keep the minimum needed to run the service:
- Account data — name, email address, and a password stored only as a bcrypt hash. We never store or transmit your plain-text password.
- Plan content — the business information, inputs, and generated plans you create. This is the material you own.
- Uploaded documents — files you submit for analysis, parsed so their text can inform your plan.
- Billing records — subscription and order identifiers plus payment status. We do not receive or store card numbers. Card entry happens on the payment processor’s own hosted pages.
- Usage and security logs — IP address, browser and device type, page events, and authentication events.
2. How it is protected
In transit
All traffic is served over HTTPS with TLS. Plain HTTP is redirected. Traffic to the application passes through an nginx reverse proxy before reaching the application server.
Credentials and sessions
Passwords are hashed with bcrypt. Sessions use signed JSON Web Tokens with an expiry, transmitted in an HttpOnly cookie, with a bearer-token fallback for the authenticated dashboard. Administrative endpoints require an administrator-level token in addition to a session, and reject requests that lack one.
Application hardening
User-supplied content is sanitised before rendering (DOMPurify) to reduce script-injection risk. Database access uses parameterised queries through a MySQL client library. File uploads are parsed by dedicated document parsers rather than executed.
Access control
Production access is limited to the operator account on the application server. We do not issue shared credentials, and administrative access to the application is gated on a specific administrator identity rather than any logged-in user.
Payments
Payments are processed by Polar (primary) and Cashfree (secondary, for Indian customers). Both operate hosted checkout: your card details are entered on their infrastructure and are never transmitted to or stored by us. We receive only confirmation of payment and the identifiers needed to provision your plan.
3. Artificial intelligence processing
Plan and idea generation is performed by external model providers — currently Groq for primary inference, with OpenAI models as fallbacks. Requests are sent to those providers’ APIs for the sole purpose of returning a result to you.
These are paid API endpoints, not consumer chat products. Per the providers’ published API terms, data submitted through their APIs is not used to train their models. We do not use your plan content to train models of our own.
4. Data location and transfers
Account and plan data are stored in a MySQL database on the application server that hosts tools.bizplanaipro.com. The content of the website is served by WordPress on the same infrastructure.
Because our subprocessors are located in the United States and India, using the service involves a transfer of the data listed in Section 1 to those jurisdictions. Our Subprocessors page lists every provider, what it receives, and where it operates.
5. Retention and deletion
Plan content is retained while your account is active. Deleting a plan removes it from your workspace. Deleting your account removes your account record and associated plan content, subject to records we must keep for tax, accounting, and fraud-prevention purposes.
Account and plan content are retained while your account is active. Deleting a plan removes it from your workspace; deleting your account removes the account record and its plan content. Billing records are kept for as long as tax law requires, and web-server access logs are retained on a rolling basis for security and troubleshooting. We do not keep plan content for any other purpose.
6. Backups
We do not currently operate an automated database backup schedule. Plan content lives in your workspace and can be exported at any time from within the application, so if you need a durable copy of a plan, export it. This page will be updated before any automated backup regime is introduced, and will then state its frequency, storage location and retention.
7. Incident response
If we become aware of a breach affecting personal data, we will notify affected customers without undue delay, describing what happened, what data was involved, and what we have done about it. Where the GDPR applies, our processor obligations require notification to the controller without undue delay after becoming aware.
Report a suspected vulnerability or incident to security@bizplanaipro.com. We welcome good-faith reports and will not pursue action against researchers who avoid privacy violations, data destruction, and service disruption.
8. What we do not claim
We hold no SOC 2, ISO 27001, or similar third-party security certification, and we do not describe ourselves as certified. If that changes, this page will say so and name the certifying body and the scope of the certification.
9. Your responsibilities
- Keep your credentials confidential and use a unique password.
- Do not upload data you are not entitled to process — including other people’s personal data without a lawful basis.
- Tell us promptly if you believe your account has been compromised.
10. Related documents
- Privacy Policy — what we collect and why, and how to exercise your rights
- Data Processing Agreement — the contractual terms when we process personal data on your behalf
- Subprocessors — every vendor that touches your data
Questions about this page: security@bizplanaipro.com