Skip to content

How your data and access are protected

Portus runs on Amazon Web Services and takes HTTPS and nothing else. It encrypts what it stores, and keeps each organisation’s data apart in every table.

Request leave · Sara Al-Otaibi · 09:14Approve Sara Al-Otaibi's leave, record it and email her a confirmation with a calendar entry.
4working days
Leave type
Annual leave
Dates
19 to 22 October 2026
Days left after
17 of 21
What goes out
ToSara Al-Otaibisara.alotaibi@najdtrading.exampleSubjectLeave approved: Annual leave, 19 to 22 October

Dear Sara, Your annual leave from 19 to 22 October has been approved. You have 17 days left this year.

  • leave.ics
Ask for changesApprove leave and email Sara
Approving with a passkey: the device asks for Face ID, the check completes, and the approval is given

Reachable only over the web

Portus runs on Amazon Web Services, in an AWS account of its own. The database and the file store sit behind the app and have no address on the internet.

How Portus runs: browsers reach the server on AWS over HTTPS only, SSH is closed, administration goes through AWS Systems Manager, the database and file store sit inside the server, and backups, the AI model and email are the only ways your data leaves it
  • Ports 80 and 443 only

    Port 80 only sends browsers on to HTTPS. Every other port is closed, SSH among them.

  • No server keys to lose

    There is no SSH key and no server password. We reach the server through AWS Systems Manager, which needs a signed-in AWS account every time.

  • HTTPS, remembered

    A browser that has reached Portus once keeps to HTTPS for a year, even if someone types the address without it.

  • No other site can frame it

    No other website can show Portus inside a frame, so no one can be led to press Approve on a page they can’t see.

  • Logs without secrets

    Request logs leave out headers, cookies and the tokens in shared links, so a log never holds what it takes to act as someone.

Encrypted on disk, in transit and in backups

  • The disk

    The server’s disk is encrypted, and so are its daily snapshots.

  • Settings and secrets

    The database, file store and email passwords sit in AWS Parameter Store, under a key only this server and our administrators may use.

  • Connection keys

    Keys your organisation saves to connect other systems are encrypted with a separate key that is never stored in the database.

  • In transit

    HTTPS between browsers and Portus, and TLS from Portus to AWS, Amazon SES and Anthropic.

  • Backups

    Encrypted with AWS KMS and accepted only over TLS. The server can add a backup but never read or delete one.

  • Passwords

    Kept only as hashes. Each person sets their own from a one-time emailed link, so no one else ever knows it.

Who can sign in, and what each person can do

Roles decide what each person can do

A role is a set of permissions you choose: who starts runs, who approves, who makes a workflow live, who manages people.

An approval goes only to the role the workflow names. The HR manager decides leave; finance decides claims above the threshold.

Roles and what each may do: HR manager, finance manager, line manager and employee

Face ID or a fingerprint, to sign in and to approve

People can sign in with a passkey instead of a password, and confirm an approval the same way, so a decision is tied to that person’s own device.

Sessions live in secure, HTTP-only cookies that no script on the page can read.

Approving with a passkey: the device asks for Face ID, the check completes, and the approval is given

Every change has a name and a time

Who changed a workflow, who made a version live, who gave someone a role, and when.

You can also require a second person: whoever changed a version can’t make it live, and asks someone else to check it.

The audit history: who changed which workflow, who made it live and who joined, with when

Each organisation’s data is kept apart

Every row carries the organisation it belongs to. A row that points at another row carries the organisation too, so the database itself refuses a link between two organisations.

One person can belong to several organisations and switch between them. They only ever see the one they are in.

Two approvals being saved: one pointing at a run of its own organisation is saved, one pointing at another organisation’s run is refused by the database
Rows of two organisations pulling apart: every row carries its organisation, so none can point across

What the AI can and can’t do on its own

The AI reads, scores and drafts. Anything that leaves the company waits for a person.

An approval card for Sara’s leave whose dates changed after the HR manager looked, so it asks her again before anything is sent
A step that emails Sara fails after the email went out and runs again: the ledger finds the email already sent and does not send it a second time
  • Nothing leaves without a person

    Emails, calendar invites, exports and tickets in other systems wait for an approval that shows exactly what goes out and to whom.

  • Approval is bound to the content

    If the message changes after someone looked, they’re asked again. An approval can’t carry over to different words.

  • Sent once

    Every send goes through a ledger. A step that runs again after a failure skips what already went out.

  • The model sees what a step sends

    A step that scores a CV sends that CV and the job. The model has no way into the rest of your data.

Security updates go in before dawn on Friday

Every Friday at 01:00 UTC, 04:00 in Riyadh, when almost no one in Saudi Arabia is at work, the server installs the week’s security updates and restarts if one needs it.

A week with Friday marked, and two clocks at the hour the security updates go in: 01:00 UTC and 04:00 in Riyadh

Report a security problem

Write to info@portusai.co with what you found and how to see it again. Please give us the chance to fix it before you tell anyone else.

Portus objects floating around the invitation: step cards, a check, an envelope, an hourglass, a riyal coin and a calendar page.

Go through it with your IT team

Book a demo and bring them along. Their questions get answered on the call, with the product open.