Trust
This page says what is true about how Nash'a handles your data today. Where something is not done, it says so plainly. It does not claim any certification or any compliance with a standard.
How to read this page
Every statement below starts with a status word. The word is always written out, so you never have to rely on colour.
- done
- In place today.
- in progress
- Partly in place, or in place only under some settings, or being worked on.
- gap
- Not in place. We say so rather than leave it out.
- plan
- An intention only. It is not something we have achieved.
Hosting and transport
- in progress The application service runs on our cloud provider's managed container service in a Doha region. This covers the application service only, not other services.
- in progress When the secure-cookie setting is on, the service sends a Strict-Transport-Security header and marks the session cookie secure. The setting is off by default in the code and is set on in the deployment instructions.
- gap Encryption at rest is not confirmed. Nothing in our code configures it, and we have not verified what our hosting provider applies by default.
Sign-in and access
- in progress Sign-in is required to use the assistant when authentication is enabled, which is the default in the code. If it is turned off, the whole application is open.
- done Account passwords are stored as hashes, not as plain text.
- in progress A sign-in session lasts 12 hours by default. The lifetime can be changed by a deployment setting.
- done Sign-in attempts are limited: every attempt from one address counts toward a per-minute limit, whatever the request contains, and a separate limit applies per username. Over the limit, the service answers "too many attempts". The counters are kept in the memory of a single instance, and users who reach us through the same load balancer may share one address.
- in progress A per-caller rate limit applies to signed-in API requests when it is enabled. It does not cover the public Trust pages.
- in progress We do not yet keep an audit log of operator access to customer data. Adding one is in progress.
Retention, deletion and your rights
- gap Support tickets can contain free-text personal data. They are kept with no deletion path, and they are lost when the service is redeployed without a storage volume.
- gap There is no in-app route to export, correct or delete your data. To make a request, contact us at the address shown on this page.
Use of your data
- in progress We do not currently use customer prompts, uploads or feedback to train a model. Feedback only changes the order in which sources are ranked. The owner has not yet confirmed that no ticket, feedback or log file was added to a training run by hand.
- done When a question goes to web search, its text is sent to a search provider, and the provider in use depends on how the deployment is configured. The realtime route does not remove personal data from the question before it is sent.
- in progress On the realtime route, text derived from a question can reach public data services for weather, prices, news, sport and routes. These services are listed below by category only, as public data services.
- gap How we describe the model that answers questions has not been settled, and this page makes no statement about it.
Standards we are working towards
- plan We intend to work towards meeting the requirements of the GDPR and the Saudi PDPL. We make no claim of having met them today.
- plan We intend to prepare for a SOC 2 audit. No audit has been done.
Sub-processors
These are the sub-processors we have identified as of [date to be set when the owner verifies], listed by category only. The named list is provided to customers with the signed Data Processing Agreement, and customers are told before a new one is added.
| Category | Purpose | Data | Region |
|---|---|---|---|
| Cloud hosting | Hosting of the application service | All data the service handles, including accounts, questions, uploads and support tickets | The application service runs in a Doha region; other services not confirmed |
| Web search | Web search, used only when a question goes to web search and a search key is configured on the deployment | The text of the question sent to web search | Not confirmed |
| Public data services | Weather, prices, news, sport and route information, used only on the realtime route | Text derived from the question | Not confirmed |
| Font delivery | Delivery of web fonts to the application's pages | Visitor IP address and user agent | Not confirmed |
| Integrations the customer switches on | Email, SMS, webhook and Slack notifications, off by default and sent to destinations the customer configures | The notification content the customer chooses to send | Set by the customer's choice of destination |
Data processing agreement
A draft data processing agreement is available as a download: draft DPA. It is a draft, to be reviewed by a lawyer before signing, and it is not an offer.
Contact
To ask a question or make a request about your data, contact us at: [contact address to be set by the owner before publishing]