Back to home

STLRepair Privacy Policy

How STLRepair handles local model processing, consented cloud uploads, account and payment information, retention and deletion requests.

Local File Processing

Free STL checking and basic repair run in your browser. Your local STL contents and mesh coordinates are not uploaded for those operations. A failed or cancelled local repair does not replace your source file.

When you choose to leave the workspace for sign-in or checkout, the browser can temporarily save selected files in local IndexedDB to restore your work after the redirect. The restore window is 30 minutes. Restored files still need your permission before cloud upload. Local storage is on your device; clearing the site's browser data also removes local saved work. The restore window is not a promise that browser storage is physically erased while the website is closed.

Cloud Upload Consent

Advanced repair requires an account and explicit permission to upload the selected STL files. The file is sent to the service for private storage and processing only after that choice. A local diagnostic result does not itself authorize an upload.

Cloud processing uses infrastructure needed to store, check and repair the model. Model files are not sent to unrelated analytics services. Use the local workflow or do not submit a file if you are not permitted to send it for cloud processing.

Types of Collected Data

Account features use information such as your name, email address, sign-in method and session records. Repair jobs use account ownership, file names and sizes, internal file identifiers or hashes, processing status, diagnostic reports, engine versions and access-expiry times. These records support validation, delivery, troubleshooting and abuse prevention.

Payments create order, transaction and subscription records. Support requests store the messages and attachments you choose to provide. Website operation can involve IP addresses, request information and security logs. Do not place confidential information in a file name or a support message unnecessarily.

Private R2 File Storage and Processing

Advanced input files, previews and results use private Cloudflare R2 storage. Server-side processing runs through Modal. Access is checked against the owning account; download access is temporary and subject to the job's delivery state. The service does not expose an unpaid complete result as a public viewer file.

The web application and database keep the metadata needed to associate an account, job and order. Your model is processed to provide the requested repair. Uploading a file is not a public publication or a transfer of ownership of its design.

Retention and Deletion

  • Unpaid advanced jobs normally expire 24 hours after they are created. Failed or incomplete uploads are also temporary. The expiry shown with a job is the applicable download deadline.
  • A successful paid result is normally available for 7 days after purchase, or after an eligible successful Pro repair. Source files can expire earlier than the paid result.
  • Starting checkout or reconciling an unsettled payment can extend retention so that a payment is not separated from its result. Expired objects are scheduled for cleanup; expiry does not promise immediate physical deletion at an exact minute.

Files are not a permanent backup. Download a result you need before its displayed expiry. Order, billing and task records are separate from model files and can be retained for accounting, security, payment disputes and applicable legal requirements.

You can request earlier deletion of a cloud model through Contact. Identify the relevant job if possible. Account ownership may need to be verified before acting on a request. A request to delete a model file is different from a request to remove billing records, which may need to be retained for applicable obligations or disputes.

Payment Processing

Checkout identifies the payment provider before you pay. Stripe is currently enabled to process payments. Payment credentials are handled by that provider; STLRepair uses payment references, status, amount and account details to verify purchases and provide access. Do not include card numbers or banking credentials in support requests.

The payment provider's own privacy information applies to its processing. Review the provider identified in checkout before completing a payment.

Cookies, Local Storage and Analytics

The website uses necessary session and preference storage for sign-in, security, theme preferences and restoring local work after a redirect. Browser-local mesh files are not sent to analytics services.

Currently configured website analytics: Google Analytics. These services can receive page and device/usage information when their scripts are enabled. Cookie and tracking requirements depend on the deployment and applicable law.

Your browser can control or clear cookies and local site storage. Blocking necessary storage can affect sign-in and restoration of local files. Account order history is separate from local browser storage.

Security

The application uses account access checks, private file storage, temporary delivery links and processing limits to protect the workflow. No online service can guarantee absolute security. Keep downloaded files and account credentials secure, and report suspected unauthorized access through Contact.

User Rights and Requests

Depending on the laws that apply to you and the service operator, you may have rights concerning access, correction, deletion, restriction, portability or objections to processing. Make a request through the support channel and identify what information it concerns. Identity verification and lawful retention requirements can affect how a request is handled.

Contact and Policy Updates

For repair, payment, privacy or other questions, open a support ticket in your account. Sign in to submit a request and read the reply. Keep your job ID or order reference if you have one.

Review the current policy when deciding whether to use local or cloud processing. Material changes to data handling will be reflected in this policy.