What protects your documents?
The security page lists the safeguards Bidligence runs today. These are the main ones.
- Every connection uses TLS, and browsers are told to use HTTPS only.
- Hosting and database providers encrypt data and files at rest.
- Every request is checked against your workspace and your role.
- You can turn on two-factor sign-in with an authenticator app.
- Passwords are stored only as hashes, which are scrambled codes.
- Sign-in, sign-up and password reset allow only a limited number of tries.
- Card details go straight to Paddle, so Bidligence never sees a card number.
Who else can see your content?
Your team sees what its roles allow. A supplier sees only the RFQ package sent to that supplier.
Outside providers process your data to run the service. They cover hosting and database, the model provider that reads and drafts, e-mail, mail forwarding and billing. Autodesk converts drawing files when that feature is on. The Privacy Policy names each one and says they work only on Bidligence's instructions.
The Privacy Policy says staff do not open your bid content. The exceptions are a support request and a security incident. Each such access needs a recorded reason and is logged. It is also e-mailed to your workspace admins.