Notiseer

Updated

What Notiseer holds, and how it is kept.

Where Notiseer’s compliance work stands, the controls in place today, and who receives what. Notiseer holds no certificate yet, and nothing here claims one.

  • UK GDPR
    1. Planned
    2. In progress
    3. In place

    Notiseer is a processor of the mail its customers connect. The deletion a processor owes is built, person by person and organisation by organisation, and the privacy policy is published. The data processing agreement and a route in the product for asking for deletion are still to come.

  • ISO/IEC 27001:2022
    1. Planned
    2. In progress
    3. In place

    Each security control built into the app is recorded with where it lives in the code, the test that proves it where there is one, and the Annex A control it supports, ahead of an ISO 27001 screening. The mapping is indicative, and it is not a certificate.

  • Microsoft publisher verification
    1. Planned
    2. In progress
    3. In place

    Verifying Notiseer’s app registration with Microsoft, so the consent page a customer’s administrator sees names a verified publisher, before the first pilot firm approves it.

Who else receives it.

Every company that processes the mail Notiseer reads, and what for.

  • Amazon Web ServicesRunning Notiseer: its database, its file storage and its servers, and sending its emails through Amazon SES.

    Receives

    Everything Notiseer holds: the mail it reads, the files people add, and its risk analysis, encrypted at rest.

  • OpenAIA project’s search index.

    Receives

    The subject and full text of each email copied into a project, and the searches run against it.

  • AnthropicThe risk review, describing files, and answering what people ask the assistant.

    Receives

    The whole threads of project mail; the name and opening text of each file on project mail or added by a person; and what people ask, with the mail and documents read to answer.

The controls in place today.

Each is in the app now, not on a plan. Open one for the detail and any exception. Production, where a pilot’s mail will be held, is not yet open.

  • Infrastructure

    • Hosted in London

      Notiseer’s database, file storage and servers run on Amazon Web Services in the London region, eu-west-2. Backup copies of the database and of stored files are kept in the Ireland region, eu-west-1.

    • A private network

      The servers and scheduled jobs run in private subnets with no public address. The database is not publicly reachable, and production’s takes connections only from production’s servers.

    • Production kept apart

      Production has a database of its own, separate from the one development and previews share.

    • No database password

      The servers reach the database with short-lived IAM tokens minted as they connect, never a stored password, and only over TLS.

    • Backups

      Database backups are kept for 7 days, in London and in Ireland.

  • Encryption

    • At rest

      The database and file storage are encrypted at rest, the file storage under a key of Notiseer’s own that rotates.

    • In transit

      TLS 1.3 or 1.2 between the browser and Notiseer, which turns plain HTTP to HTTPS, and TLS between Notiseer and Microsoft, its database, its file storage and each subprocessor. The one hop without it is inside Notiseer’s private network on AWS, from its load balancer to its servers.

    • Microsoft tokens

      The tokens that let Notiseer read mail are encrypted by Notiseer itself, with AES-256-GCM, before they are stored.

    • Private file storage

      The file storage blocks all public access and refuses any request not made over TLS.

  • Isolation and roles

    • Organisations kept apart

      All customers share one database, and Postgres row-level security keeps each person’s mailbox and each organisation’s projects apart. The exceptions are the assistant’s working state, not yet under those rules, and a few lookup tables that hold no mail.

    • Files placed by the server

      Where a stored file sits is decided on the server, from the organisation it resolved, never from anything the browser sends.

    • Roles

      Each organisation has one owner, and everyone else is an admin or a member. One policy decides every permission and denies by default, and a member sees only the projects someone has put them on.

    • Invites that work once

      The owner and admins invite people with a link that works once, for seven days, and only for a signed-in account holding the address it was sent to.

  • Microsoft 365

    • Two permissions

      Two delegated Microsoft Graph permissions, User.Read and Mail.Read, beside the openid, profile and offline_access that Microsoft’s sign-in library adds. It never asks for send, write or shared-mailbox access.

    • A narrow read, checkable

      The Inbox and Sent Items, plus any folder a person chooses for a project. No calendar and no contacts, and Drafts, Deleted Items, Junk Email, Outbox and Conversation History cannot be chosen. A chosen folder later moved under one of those, as deleting it in Outlook does, is read until the project’s folders next change. Notiseer enforces this, not Microsoft, so each request that reads messages names its folder in your own tenant’s audit logs; fetching a message’s attachments, listing folders for the picker and the change notification address the mailbox as a whole.

    • Never sends

      Notiseer never sends, writes or deletes anything in a mailbox. A notice it helps draft opens in the person’s own mail client, for them to send or not.

    • Your administrator decides

      An administrator can limit who connects with Assignment required in Microsoft Entra, and revoke the grant there. Reading stops when the current token expires, within about 90 minutes at Microsoft’s default token lifetime. Someone who approved Notiseer for themselves holds a grant of their own that this does not revoke; setting Enabled for users to sign-in to No under Notiseer’s Properties (or Foresight’s, the name Microsoft may still list it under) stops every token.

  • Sign-in and sessions

    • Only the people named

      Any Microsoft account, work or personal, can reach the sign-in. Production then refuses every account its list does not name, whether by address, by domain or by Microsoft Entra directory, and while the list names no one it refuses everyone.

    • Sessions the page cannot read

      A session is an HttpOnly cookie that the page’s scripts cannot read, kept on the server only as a SHA-256 hash. It ends after 24 hours unused or 14 days at most, and a person can sign out on every device at once. Signing out, even everywhere, does not stop Notiseer reading new mail in the background; only revoking the Microsoft grant does.

    • Requests from its own pages

      The session cookie is SameSite, and a browser request that would change something is refused unless it comes from one of the app’s own pages.

    • Sign-in with PKCE

      Microsoft sign-in runs on the authorisation-code flow with PKCE, and a started sign-in can be redeemed once, within ten minutes, by the browser that started it.

  • Retention and logs

    • Kept until deleted

      Mail Notiseer reads is kept, whether or not it belongs to a project, until the person deletes it in Outlook, moves it out of the folders Notiseer reads, or Notiseer deletes it. A project keeps its own copy of the mail matched to it, which stays when a message is deleted in Outlook and after the person whose mailbox it came from leaves. There is no time limit, and ending access deletes nothing.

    • Deleting a project

      Removes its copy of the mail, its files and its risk analysis; the mail itself stays with the people whose mailboxes fed it, and Notiseer keeps its audit copies of the emails each risk cited and the description a model wrote of each file. Database backups keep the records for 7 days more, and the file storage a deleted file’s previous version for up to 30.

    • Logs without mail

      The server’s logs, kept for 30 days, hold no text from mail and nothing written from it. The load balancer’s, kept for 90 days, hold request addresses, which carry record ids but no mail.

    • Signed-in devices

      Each sign-in keeps the browser and IP address it came from, so a person can see every device signed in to their account and sign any one out. Only that person sees them, and they are deleted when the session ends, at most 14 days after it began.

    • Emails without your mail

      The two emails Notiseer sends a person about their projects never carry text from their mail, or anything it wrote from it, and nor do its invitations. Both are sent through Amazon SES in London, and each can be turned off.

    • Evidence sealed

      Each flag seals the evidence it rests on with a SHA-256 hash, so a later change to that evidence shows.

  • Development

    • Reviewed changes

      Changes reach the app’s main branch by pull request, through a required CI gate and approving reviews.

    • Secrets scanned

      Every pull request is scanned for committed secrets, and a hit blocks the merge.

    • Dependencies watched

      Dependabot watches the backend’s, the frontend’s and CI’s dependencies for known vulnerabilities.

    • Images scanned

      Each container image is scanned for known vulnerabilities as it is pushed, and a production image’s tag cannot be overwritten.

    • No stored cloud keys

      Continuous integration reaches AWS through OIDC, with no stored keys.

    • A strict browser policy

      Every page of the app carries a Content-Security-Policy made per request around a fresh nonce, and HSTS for a year.