Security
Nothing changes on a client's account without approval for that one change.
Torin reads your accounts but changes them only one way: after your approval for a specific change, with a record of how things were and an honest answer on whether it can be undone. Below is that path step by step, and every condition that has to be met.
Accounts open on 1 December 2026. Join the list and we will email you once.
Found a vulnerability? Write to security@hiretorin.com.
Torin does
- Reads accounts and records how things were before every proposal.
- Makes a change after your approval for that one change.
- After 3, 7, 14 and 30 days, checks whether the change did what it promised.
- Records every decision in the history, ready to undo.
Torin doesn't
- Changes nothing on an account without your “yes”.
- Doesn't send emails: you send them, with a click.
- Doesn't publish anything on your behalf by itself.
- Doesn't train AI on your data.
Account changes
Nothing changes without your yes.
No change reaches a client's account without your approval for that one change and without the client's consent. Five steps from reading to undo, and each one leaves a trace.
- 01
First it records how things are
Before any proposal exists, Torin reads the account and saves the current settings. Without that record the change is never created.
- 02
Approval for this one change
The approval names one change and expires after 24 hours. If the client is below level 2 of autonomy, the change won't run, even with your approval.
- 03
The change, then a check
Right before sending, the account is read once more; if it looks different from when you approved, the change won't run. After saving, a second read confirms the result.
- 04
Check after 3, 7, 14 and 30 days
The check looks at whether the change did what it promised and whether anyone has undone it. The conclusion goes into memory as an entry for you to confirm.
- 05
Undo, where it exists
Undo restores the saved settings the same way the change was made. If Torin created something, undo removes exactly what he created. Before you approve, the card says whether it is a reversible setting, a compensating action, a manual fix or something irreversible. Undo does not return money spent in the meantime, and a deleted post may already have been seen.
Counted from the product on 2 November 202679 types of change, the state before saved for eachwhat Torin does
Conditions
Six conditions before every change.
| Condition | If it isn't met |
|---|---|
| The approval covers this one change and is less than 24 hours old | The change won't run; it has to be approved again. |
| The client allows changes after approval (they set this in their portal) | The change stays approved but won't run, and Torin tells you so plainly. |
| How things were is recorded before the proposal | The proposal is never created, so there is nothing to approve. |
| At the moment of the change, the account looks the same as when you approved | The change won't run: you approved something different from what is there now. |
| A second check of the account after the change | A fresh read confirms the result; if there is no confirmation, that is recorded in the history. |
| Every change goes the same single way | Across all the code, one place sends changes to accounts, and a test makes sure a second one never appears. |
Where this lives in the code (for developers)
- The approval covers this one change and is less than 24 hours oldwykonanie/zmiany.py, wykonanie/wykonaj.py
- The client allows changes after approval (they set this in their portal)portal/decyzje.py, wykonanie/wykonaj.py
- How things were is recorded before the proposalwykonanie/klasy.py
- At the moment of the change, the account looks the same as when you approvedwykonanie/wykonaj.py
- A second check of the account after the changewykonanie/wykonaj.py
- Every change goes the same single waywykonanie/klasy.py, test_wykonanie.py
Counted from the product on 2 November 20266 conditions before every change
Stopped
This is what a change that won't run looks like.
The account changed between your approval and the moment of the change. Next to this is exactly the message you would see.
Nothing reaches the account
Torin sends nothing, and the change keeps a note of why it stopped.
A new proposal on the new state
It has to be prepared again and approved again.
Change stopped: the account changed after approval
- Approval for this one changepassed
- How things were is recordedpassed
- The client allows changes after approvalpassed
- Account the same as at approvalstopped it
What you will seeThe account has changed since it was approved, so I'm not making the change. Prepare the proposal again on the current state.
Autonomy
A level per type of work, not for everything at once.
The weekly report can go out on its own, budgets always need approval. There is no “does it alone” level for account changes, and there never will be. Torin will never do these on his own:
- Spending: budgets, bids, spending limits and anything that opens up traffic or costs the client money.
- Publishing on the client's behalf: posts, replies to reviews, blog articles, emails to their customers.
- Access: granting, removing or changing permissions to accounts and integrations.
- Promises to the client: deadlines, results, prices and the scope of work.
What the client allows
The client picks one of three levels in their portal. Until they choose “We act after approval”, no change will run, even with the agency's approval.
- We readWe check the account and show what we found. We change nothing.
- We prepareWe also prepare ready-made fixes that a person applies.
- We act after approvalWe also make a specific change, but only after you click it.
Counted from the product on 2 November 20264 actions always with a person, 3 levels to choose from
Data
Data and access.
Where the data lives
Your agency's data and your clients' data are stored on the service's server. Where the server provider is based: not checked yet; we will add it to the Subprocessors page once it is confirmed. Access keys to ad accounts are stored encrypted; they are never kept in the database in plain form.
What we do with AI
The content of your conversations and data from your accounts go to the AI provider when you ask something, and for recurring AI work switched on in your account (scheduled tasks and automations, inbox summaries, review analysis, tidying up conversation memory), limited to what that work needs. We don't train any AI on them and we don't share them with anyone except the provider handling that work. The list of providers is on the Subprocessors page.
What we don't do
- Publishing on someone's behalf: each item separately approved. A social media post or a review reply goes out only after an approval of that one item and the client's consent in the portal, never in bulk; undo removes only our post. A person sends emails with a click.
- We change nothing on a client's account without approval that names one specific change and is checked again at the moment the change is made.
- We don't use paid sources without your approval.
- We don't guess. Whatever couldn't be checked is called “not checked”, along with the reason.
Who has access
Your data can be seen by your team, in the roles you give them. Agencies are kept separate from each other. On our side, only the people who run the service have access, and every login leaves a trace.
Report a vulnerability
Send reports to security@hiretorin.com. We reply within three working days and we won't pursue anyone who reports in good faith and leaves other people's data alone.
The same address is in /.well-known/security.txt.
Try it on one client's account.
No card and no password. The trial plan is €4.58 net of Torin's work.
