What Portus keeps, who processes it, and for how long
Everything is kept on Amazon Web Services, encrypted. Anthropic’s models read only what a step sends them, and you choose how long run details are kept.
The records Portus holds
People
Names, work email addresses, roles and teams of the people you invite, and the public half of their passkeys. Passwords only as hashes.
Workflows and policies
Each workflow and every version of it, and the leave and expense policies, public holidays and weekend you set.
Runs and their files
What each run started with, what each step produced, and the files it read or made: CVs, receipts, letters.
Approvals
What the approver was shown, who decided, what they decided and when.
The audit history
Changes to workflows, roles, people and settings, each with a name and a time.
Connection keys
Keys for the systems you connect, encrypted with a key kept outside the database.
Kept on AWS, encrypted
Amazon Web Services
Your data, its backups and the disk snapshots are kept on Amazon Web Services, in an AWS account that holds Portus and nothing else, encrypted at rest and in transit.
Apart from the systems you connect yourselves, three things leave it: the text a step sends to Anthropic’s model, the emails your people approve on their way to the people they’re for, and reports of errors in the app, which carry no one’s data.
The companies that process it for us
| Company | What for | What it receives | Where |
|---|---|---|---|
| Amazon Web Services | The server, the database, the files and the backups | Everything Portus stores | Portus’s own AWS account |
| Amazon SES | Sending email, as part of AWS | The emails approved to go out, with their recipients and attachments, and sign-in and invitation emails | Portus’s own AWS account |
| Anthropic | The Claude models that read, score and draft | Only what a step sends: a CV and the job to score it, a receipt to read it | Anthropic’s API |
| Sentry | Reporting errors in the app to our team | What went wrong and where in the code. No request contents, cookies or IP addresses | Sentry’s service |
Amazon Web Services
- What for
- The server, the database, the files and the backups
- What it receives
- Everything Portus stores
- Where
- Portus’s own AWS account
Amazon SES
- What for
- Sending email, as part of AWS
- What it receives
- The emails approved to go out, with their recipients and attachments, and sign-in and invitation emails
- Where
- Portus’s own AWS account
Anthropic
- What for
- The Claude models that read, score and draft
- What it receives
- Only what a step sends: a CV and the job to score it, a receipt to read it
- Where
- Anthropic’s API
Sentry
- What for
- Reporting errors in the app to our team
- What it receives
- What went wrong and where in the code. No request contents, cookies or IP addresses
- Where
- Sentry’s service
Under Anthropic’s commercial terms, what Portus sends through its API isn’t used to train its models.
This website sets no cookies, runs no analytics and loads nothing from other companies.
How long each kind is kept
Your organisation sets how long run details are kept, in Settings under Safeguards. The rest follows the table below.
- Run details
- As long as your organisation chooses. After that, what a run started with, what each step produced and its files are cleared; who approved what is kept. A run someone marks to keep stays as it is.
- Backups
- 14 days, then each one expires on its own.
- Disk snapshots
- The last seven daily snapshots.
- Everything else
- For as long as your organisation uses Portus.
When you leave, we delete your data
- 1
You ask
Write to info@portusai.co and name the organisation to delete.
- 2
We delete it
Its rows in every table, the files it stored, and the accounts of people who belong to no other organisation.
- 3
The copies run out
Backups holding it expire within 14 days, and disk snapshots within seven.
Ask us what happens to your data
Book a demo and bring the questions your data protection officer will ask. We answer them with the product open.
Or write toinfo@portusai.co