Security and privacy
At a glance
| Does SAVER store situation descriptions, AI responses, plans or exercises? | No. The content stays in the user's browser. SAVER has no database of customer content. |
|---|---|
| Where is the server? | In the EU: Railway, Amsterdam region (the Netherlands). |
| Who processes the text? | OpenAI Ireland Ltd., as a processor for SAVER, under a data processing agreement. |
| Is the content used to train AI models? | No. |
| How long does OpenAI keep the text? | SAVER has turned off storage of responses. OpenAI may retain requests for up to 30 days to detect abuse, and then deletes them. |
| Encryption? | All traffic uses HTTPS. Browsers are required to always use HTTPS (HSTS). |
| User accounts and passwords? | None. Access is granted with a signed cookie. The subscription is managed through Stripe, with a sign-in link sent by email. |
| Data processing agreement? | Yes, on request to post@saver.no. |
1. What happens to what you write
- The situation description and the boards are sent from the browser via our server to OpenAI, which generates the suggestions. The response returns the same way. The server forwards the content without storing it and does not write it to the logs. The logs contain only technical information, such as response time and token usage.
- An uploaded emergency response plan is read in the server's memory, and the text is sent back to the browser. The file is not stored. The text accompanies each analysis to OpenAI so that the suggestions can draw on the plan.
- Message drafts are generated by OpenAI from what is on the boards, and are shown only in the browser. When a draft is copied, it is recorded in the incident log in the browser.
- Exercises are handled the same way: the scenario, injects and evaluation are generated by OpenAI and exist only in the browser.
- In the browser, the latest session, the incident log and any exercise in progress are stored locally on the device, so that work is not lost by accident. "Start over" deletes them. On shared computers, always finish with "Start over".
- Speech to text uses the browser's own speech recognition. The audio is processed by the browser vendor (Google in Chrome and Edge, Apple in Safari), not by SAVER. SAVER receives only the transcribed text. The feature is optional.
Recommendation: describe roles, not names ("an employee", "the night watchman"). Do not enter national identity numbers or health information about individuals. The tool does not need them to give good suggestions.
2. What SAVER actually stores
| What | Where | Why |
|---|---|---|
| Email, name and payment details (for purchases in euro also business name, address and VAT number) | Stripe | Subscription and invoicing. SAVER never sees the card number. |
| Proof of access | Cookie in the browser (signed, HttpOnly, Secure) | Access without a password |
| Improvement suggestions and any email address | Server memory and operational log | To follow up the suggestion. Only when the user chooses to send one. |
| Anonymous visit count | Server memory, reset on restart | Number of visits, country and region. SAVER does not store IP addresses. |
| Technical logs with IP addresses | Railway (hosting provider) | Operations and troubleshooting. Deleted automatically after Railway's retention period. |
3. Sub-processors
| Provider | Purpose | Data | Location / transfer mechanism |
|---|---|---|---|
| OpenAI Ireland Ltd. | AI analysis and exercises | Text sent for analysis | Ireland. May be transferred to OpenAI's group company in the United States under the EU Standard Contractual Clauses. |
| Railway Corporation | Server hosting | Content passes through without being stored. Technical logs. | Server in the EU (Amsterdam). The company is American. |
| Stripe | Payment and subscription | Customer and payment details | Stripe Payments Europe Ltd. (Ireland). PCI DSS Level 1. |
| Microsoft Clarity | Usage statistics | Clicks and movement. The content of the fields is not recorded. | Only with consent in the browser. |
Map data and public alerts (Natural Earth, GDACS, USGS) are fetched by our server. The user's browser does not contact these sources, and no user data is sent to them.
4. Technical safeguards
- No database of customer content. What is not stored cannot leak from us.
- HTTPS everywhere, with HSTS.
- Strict Content Security Policy: the page can only load code from saver.no and, with consent, Microsoft Clarity. Fonts and the map library are hosted on our own server, not by third parties.
- Signed cookies that JavaScript cannot read
(
HttpOnly), that are only sent over HTTPS (Secure) and that are not sent from other websites (SameSite). - No passwords to steal: no user accounts at SAVER. The subscription is managed at Stripe, with a sign-in link sent by email.
- Rate limiting on all APIs, against abuse and automated attacks.
- Secret keys are held as environment variables at the hosting provider, never in the source code.
5. Availability and fallback
SAVER is decision support and must not be the organisation's only emergency management tool. The service depends on the internet, OpenAI and the hosting provider. Always have a fallback that works offline: paper, a whiteboard and your own notification list. The incident report can be printed as a PDF during the incident and should be stored in the organisation's own systems.
6. Incidents and vulnerabilities
- Personal data breaches affecting the customer's data are notified to the customer without undue delay.
- Found a security vulnerability? Write to post@saver.no. The contact details are also in security.txt.
7. Data protection officers, DPAs and questions
If your organisation needs a data processing agreement, answers to a vendor security questionnaire or further documentation for a risk assessment, contact post@saver.no. The full terms are in the terms of sale, section 8.
Contact
SAVER AS · Norway · Organisation number 924 505 206 · post@saver.no