Security & Data Handling

Read this first if you plan to upload client or staff documents. BisMaps is built for business notes, briefs and reports. It is not built for, and must not be used for, special-category personal data — health records, biometric data, or anything about children. If your documents contain personal data about identifiable people, you are the controller of it and we process it on your instructions.

1. What happens to a document you upload

1. It is uploaded over TLS to our application server and written to private storage. It is never served from a public URL, and the file name is not used as a path.
2. It is read once. Text is extracted to build the plan. When that finishes, the uploaded file is deleted from storage. The database row that pointed at it is cleared at the same time, so nothing is left referring to a file that no longer exists.
3. The extracted text is kept, because the plan quotes it: every point in a synthesised plan carries the sentence it came from, and a quote that cannot be checked is not evidence. The text stays in your workspace, attached to that plan, and is deleted with it.
4. The text for one request is sent to our AI provider to produce that answer, and is not used by us for anything else.

2. Where the AI fits

• Requests go to the Deepseek chat-completions API over HTTPS, using credentials held in our server environment. No AI request is made from your browser directly — your browser never holds an API key.
• Deepseek's API terms exclude API inputs and outputs from model training by default. We selected it partly for that reason. If you need that in writing for a procurement review, ask us and we will point you at the current terms rather than paraphrase them.
• Credits are counted per AI action, and the full price list is in your billing page — there is no silent metering.
• What we do not do: we do not use your content to train any model of ours (we have none), we do not sell it, and we do not read it to build customer profiles.

3. Encryption

• All traffic to and from BisMaps is served over HTTPS (TLS 1.2 or newer). HTTP is redirected.
• Data at rest — the database, backups and file storage — is encrypted by our hosting provider.
• Passwords are stored only as one-way hashes, never in a recoverable form.
• Session cookies are set with the __Host- prefix, Secure and HttpOnly in production.
• Not yet in place, and we would rather say so: we do not offer customer-managed keys or a bring-your-own-key mode, and there is no SOC 2 or ISO 27001 report. If those are requirements for you, BisMaps is not the right tool yet.

4. Sub-processors

These are the only third parties that can see personal data, and what each one sees:

We will add to this list before a new provider starts handling data, not after. The Privacy Policy describes the same providers in the language of GDPR Article 13.

5. Access, export and deletion

• Export at any time — JSON and Markdown on every plan; PNG, PDF and CSV on paid plans. Every sourced plan can be exported as a spreadsheet with its quotes beside each point.
• Delete a plan and its extracted source text goes with it. Delete your account and your profile and personal workspace data go with it; backups age out within 30 days.
• Ask for a copy or a deletion by email and we will confirm in writing when it is done.

6. Reporting a problem

If you think you have found a security issue, email support@bismaps.com with what you found and how to reproduce it. We will acknowledge it, tell you what we are doing about it, and credit you if you want to be named. Please do not test against another customer's workspace.