Trust
How a Drawvia draw is accounted for.
These notes describe how Drawvia protects access, separates workspaces, keeps draw records, and supports verification today.
Secure access
- Sign-in uses a server-side session cookie so access stays tied to the authenticated account.
- Sign-in, registration, uploads, draws, certificates, exports, and public verification lookups are rate limited.
- Production readiness is checked before the service is treated as ready.
Organization separation
- Draws stay inside the organization that created them.
- Workspace members act inside that organization scope; another organization cannot open those draws through the product UI.
Audit records
- A completed draw keeps the recorded result. Opening it again does not draw a second time.
- The uploaded file is stored with a SHA-256 fingerprint.
- Audit reports and certificates are available on the plans that include them.
Draw verification
- Selections use a cryptographic random source on the server.
- Equal Chance gives every eligible entry the same weight. Weighted Chance selects without replacement, so a winner cannot be selected twice in the same draw. Weights are not expanded into extra ticket rows.
- A verification fingerprint is the SHA-256 of the recorded verification facts.
- Public verification is available on the plans that include it.
- Verification confirms that this record corresponds to the completed draw recorded by the service. It does not independently verify the source population or inputs supplied before the draw.