Security

The controls in place today. This page lists only what the product does now.

CloseoutReady is sold and operated by AERA. Effective 10 November 2026.

Tax status: Exempt dealer (osek patur) · Business number: 315971192 · Contact: aeraops@gmail.com

Access to your projects

  • Every project, upload, preview, download and build request is checked on the server against your company and your role before it runs. Files are stored under your company and project.
  • Browsers never query the database directly; uploads go to storage through short-lived signed links.
  • On the Team plan, roles limit what each person can do: owners pay and manage members, integrations and deletion; editors work on projects; viewers only read.
  • View links and subcontractor upload links use long random tokens, open only the manual or project they were made for, and can be revoked. View links show a watermarked preview.

Sign-in

  • Passwords are stored as salted scrypt hashes, never in plain text.
  • The sign-in cookie is HTTP-only and secure, and expires after 30 days. Sign-in and password reset links expire.
  • Sign-in, sign-up, uploads, builds and other requests are rate limited; addresses are kept only as salted hashes for this.
  • Requests that change data are checked against the app's own origin to block cross-site request forgery.

Data in transit and at rest

  • All traffic uses HTTPS, with HSTS, a content security policy and anti-framing headers.
  • The app runs on Vercel; the database and files are on Supabase, which encrypts stored data at rest.
  • Payments are taken by PayPal; we never see card numbers. Orders are created on our server and checked on capture, and PayPal refund and dispute notices are verified with PayPal before they are acted on.

Files and logs

  • Uploads are checked for accepted file types and size limits, and duplicates are caught by a content hash within the project.
  • Office files and long text are read with size and time limits, so a booby-trapped file (such as a zip bomb hidden in a Word file) cannot exhaust the server.
  • Product events and error reports drop email addresses, phone numbers, file names, document text, links and payment references before they are stored.
  • Outside services receive only what the sub-processor page lists.

Not in place yet

So you can judge for yourself: there is no two-factor sign-in, no malware scanning of uploads, no independent audit (such as SOC 2) and no external penetration test yet, and a full backup restore drill has not been run. Automatic deletion of unpaid projects is built but not switched on yet (see the privacy page).

Reporting a problem

If you think you have found a security issue, email aeraops@gmail.com with the details. Please do not access other customers' data or disrupt the service while testing. We reply as soon as we can, and tell affected account owners without undue delay if an incident touches their data.