Security
Reporting a vulnerability.
If you have found a security problem in 3D Print Dash, please tell us before you tell anyone else. We will not take legal action against anyone who reports a genuine issue in good faith and gives us a reasonable chance to fix it.
How to reach us
Email louwrensventures@gmail.com
with the subject line SECURITY. Include what you found, how to reproduce it, and
what you think the impact is. A machine-readable copy of this lives at
/.well-known/security.txt.
What to expect
We aim to acknowledge a report within 3 business days and to tell you what we intend to do about it within 10. We are a very small team, so we would rather promise a slow honest reply than a fast one we cannot keep. There is no paid bounty programme today; if your report leads to a fix we will credit you here unless you would rather we did not.
Please do not
Run automated scanners against production, attempt denial of service, access or modify data that is not yours, or social-engineer our operators or customers. If a proof of concept needs real customer data to demonstrate, stop and describe it to us instead.
How we handle your data
- In transit and at rest
- Everything is served over HTTPS. Customer data lives in a managed Postgres database (Supabase), which is encrypted at rest, with row-level security so an account can only reach its own records.
- Payments
- Card details never reach our servers. Payment fields are hosted by Stripe and the card number goes straight to them; we store only a token and the last four digits.
- Your models
- Uploaded and generated model files are private to your account. An operator receives a file only for a job they have accepted.
- Who else touches it
- Listed in full on the subprocessors page.
This page describes our practice, not a certification. We do not hold SOC 2 or ISO 27001 today and we will not imply otherwise.