Security at ScopePay

ScopePay sits between an agreement and a payment, so it is built to keep both trustworthy. Here is exactly how.

Payments stay in PayPal

Invoices are created, sent and paid in PayPal. ScopePay never receives funds and never sees card or bank details. Payment updates arrive by PayPal webhook, and ScopePay verifies each one with PayPal before trusting it.

Accounts

  • Passwords are hashed with scrypt and a unique salt, never stored as text.
  • Sessions use random tokens in secure, HttpOnly cookies; only a hash of each token is stored.
  • Repeated failed sign-ins are throttled by address and by email.

Client review links

Each project has an unguessable review link (192 bits of randomness). It is placed after the # in the URL, so it is not sent to servers or leaked through referrer headers. A link only shows that one project.

Your data

  • Agreements, evidence files and project records are stored in a managed Postgres database.
  • Each account sees only its own projects; every request is checked against the signed-in account.
  • Deleting your account removes your projects, files and sessions.

AI, with people in charge

  • Documents and client messages are treated as data, never as instructions to the AI.
  • Every extracted term and verdict cites its source, and quotes that do not match the agreement are flagged.
  • The AI never accepts work or sends money. You confirm terms; your client accepts.

Web protections

  • All traffic is served over HTTPS.
  • State-changing requests from other websites are rejected.
  • Uploaded files are checked by type and size and served with strict content headers.

Found a problem? Please open a private security advisory on our GitHub repository.