SECURITY · CURRENT CONTROLS ·LAST REVIEWED 11 OCT 2026
Work proof should settle an argument. It should not create a new risk.
IPI holds the work records your team relies on: what was asked, what was submitted, what was decided, and why. Access is limited, proof stays private, and important actions leave a record.
- IdentifyConfirm who is asking.
- CheckConfirm what they may access.
- LimitKeep the request within its purpose.
- DeliverReturn only authorized information.
- RecordKeep a record of important actions.
Access should depend on what someone is allowed to do, not simply whether they have a login.
At a glance
-
Company access
People see the records their role permits.
-
Proof files
Private access, with recorded submissions preserved.
-
Browser
Protections help keep harmful code out of the page.
-
Payments
Stripe handles card entry and checkout.
-
Super intelligence
Work information is limited to the task.
-
Releases
Automated security checks before release.
Our approach
A team member should be able to submit proof without publishing it to the world. A reviewer should be able to see the evidence they need without gaining access to everything. And a later update should not quietly change what was originally submitted.
These are the boundaries IPI is built to protect.
01ACCESS
A login is not a master key.
IPI checks company membership, role, and permission to access the work before returning protected records.
An employee or contractor using a Human Agent account is limited to their own work. Authorized owners and reviewers can access the company records needed for their responsibilities. Another company's login does not grant access to your company's records.
Hiding a button is not security. Unauthorized access must still be refused.
02SESSIONS
Access should end when a session does.
Inactive sessions end automatically. Signing out clears the signed-in state in that browser.
This helps reduce the risk of a device remaining signed in after someone stops using it.
03BROWSER
A message should not become code.
IPI uses secure connections and browser protections that restrict what can run on its pages. Content added to a page is checked before it is displayed to help prevent harmful code from running.
A sentence from a user should stay a sentence. It should not become code.
04PROOF FILES
Submitting proof does not make it public.
Proof files are stored privately and opened through IPI's access controls. Access follows the work and the permissions of the person requesting it.
Once proof forms part of the recorded work, later evidence is added as a new version rather than quietly replacing the original. That keeps the submission history available when authorized people review what happened.
05SUPER INTELLIGENCE
Super intelligence gets what the task needs.
IPI uses super intelligence to help review work, keep context, and make routine work judgments.
When an outside service is used, it receives the work information needed for that task, not unrestricted access to your company account. Proof is not made public to provide that access.
06PAYMENTS
Stripe handles card details. Your company controls payouts.
Stripe handles card entry and checkout. IPI keeps the billing and payment-status records needed to run the account, not full card numbers. Payment confirmation must come from Stripe before it changes paid access.
Paying for IPI is separate from decisions about paying your team. Your company's authorized people retain authority over approvals, revision requests, payouts, and employment or contractor decisions.
07RECORDS
Important actions leave a record.
IPI records objectives, submitted proof, reviews, decisions, and relevant account activity so authorized people can understand what happened and why.
Important actions have safeguards against duplicate processing. Repeating a request should not create a second decision or consequence.
An email or text failing to arrive does not change a saved work decision.
08RELEASES
Security checks are part of a release.
Automated checks test important protections before changes are released, including access to company records, proof files, signed-in sessions, and payment confirmation.
Changes that fail these security checks are blocked from release.
NEXT STEP
See how the work fits together.
Follow one work cycle through IPI, from the objective to the proof and recorded decision.Common questions
Are proof files public?
No. Proof files are stored privately, and IPI checks permission before opening them.
Can one team member see another person's proof?
A Human Agent account is limited to that person's own work. Authorized owners or reviewers can access the records needed for their responsibilities.
Can another company see our records?
IPI checks company membership and work permissions. A request without the required access is refused.
Does IPI store full card numbers?
No. Stripe handles card entry and checkout. IPI retains the billing and payment-status information needed to operate the account.
SECURITY REPORTING
Report a security concern.
Use Contact us to report a suspected security issue privately. Include the affected page or feature, what happened, and the steps needed to reproduce it. Remove passwords, customer information, and other secrets from your examples.
Test only accounts and data you own or have permission to test. Stop once the issue is demonstrated. Do not access someone else's information, disrupt the service, use social engineering, or publish the issue before IPI has had a reasonable opportunity to investigate.
For questions about information use, retention, or deletion, read the Privacy Policy or contact us.