MessyPoly

Effective August 29, 2026

Privacy Policy

This Privacy Policy explains what MessyPoly collects, why it is collected, and how it is handled when you use the service.

1. Information We Collect

2. Information We Do Not Store

MessyPoly does not store full card numbers, CVC codes, or raw payment credentials. Payment collection is handled by Stripe. Passwords are stored only as password hashes, not plaintext passwords.

If you use the optional MessyPoly print bridge to send a print to your own machine, the printer credentials you enter there and the G-code you send are held by that application on your own computer. They are not transmitted to, or stored by, MessyPoly.

3. How We Use Information

4. Service Providers

MessyPoly uses third-party providers to operate the product: Vercel for the web layer, Koyeb for backend and worker services, MongoDB for application data, Cloudflare R2 for file storage, Stripe for payments, Resend for transactional email, fal.ai for image-to-3D model generation, and Google Analytics for website usage analytics. These providers process data as needed to provide their services.

Image-to-3D generation is the one feature that sends your content to an AI provider. When you ask MessyPoly to generate a model from a photo, it issues a short-lived, time-limited link to that photo and passes the link to fal.ai, which retrieves the image and returns a generated 3D model. Only the photograph for that generation is shared. Your other uploads, your finished models, and your account details are not sent to fal.ai. This feature is optional: models you upload yourself are never sent to an AI provider.

5. File Retention

Uploaded source files and generated artifacts are retained only as needed to operate the service, support account history and download windows, debug failures, and maintain analytics. Files referenced by Pro, Studio, or administrator account history are protected from automatic deletion. Free-account files may expire under the published retention windows. To avoid repeated uploads of the same model, MessyPoly may briefly use a content-addressed staging cache; accepted jobs are copied into job-owned storage before processing. Deleting a version, asset, job, or account may permanently remove its associated files.

6. Security

MessyPoly uses HTTPS, HTTP-only session cookies, server-side service tokens, password hashing, Stripe-hosted payment surfaces, signed webhooks, and access controls for account-owned jobs. No internet service can guarantee perfect security.

7. Your Choices

You may request account help, billing help, correction, export, or deletion by emailing support@messypoly.com. Some records may be retained when needed for security, legal, billing, or abuse-prevention reasons.

8. Changes

We may update this Privacy Policy as MessyPoly changes. The effective date will show when the latest version applies.

Privacy questions: support@messypoly.com