Skip to main content
Identity verification is required before you can withdraw. Everything else on the platform works without it. Go to Personal → Verification.

​
Accepted documents

​
Photo requirements

All four must hold, or the submission is rejected on review:
  • Document must be valid and not expired
  • All four corners must be visible
  • Text must be clearly legible
  • No glare, shadows or obstructions

​
File limits

8 MB is deliberately modest. These are photographs of a document, not archival scans — a phone camera shot at default settings lands well inside it. If yours does not, your camera is set to something unusual.

​
The liveness step

After the document images, you are asked for a liveness capture — a selfie, taken in the moment, to check that the person submitting the document is the person in it.

​
Submission flow

​
Statuses

A rejection is not final. Read the note, fix the specific problem, and submit again. The overwhelming majority of rejections are glare on a laminated card or a cropped corner.

​
Where your documents are stored

Documents go to private object storage — an S3-compatible bucket (AWS S3, Cloudflare R2, Backblaze B2 or MinIO), never a public directory and never the application database.
Self-hosting note. If no bucket is configured, the deployment falls back to a local directory that is explicitly development-only. Never run a production deployment in that mode: identity documents would sit on the application server’s filesystem. See Environment variables.
You can check which mode a deployment is in from the Verification screen — it reports whether storage is a bucket or the local development fallback.

​
Privacy

  • Documents are used for verification and are not shared with other users.
  • You can export everything the platform holds on you from My Profile → Export account data.
  • Account deletion is available from My Profile, and cascades to submissions and documents.

​
Next