Your scans. Your choices.

Privacy policy.

Core scanning, optional Pro subscriptions and private agent beta · Updated 31 October 2026

Meshmorrow is operated by Matthew Holdsworth. Contact support@meshmorrow.com for privacy questions or access, correction and deletion requests. This notice distinguishes the core iPhone/iPad workflow, optional private agent-finishing beta, older accounts and separate beta web studio.

Core scans and projects stay on your device

Object and detailed-area photos are reconstructed locally. Earlier quick room/outdoor captures can retain local geometry and selected camera views. Their saved LiDAR source and recovery files can include photos, depth, camera poses, tracking maps, measured planes and surface labels. RoomPlan creates a separate local measured-layout document and, when available, preserves its measured source and original USDZ. Floor-plan dimension overrides are annotations alongside the measured values.

Capture, photo checks, source-based reprocessing, repairs, collections, model export and PNG presentation rendering run on your device. The core workflow does not send these room photos, depth, geometry, floor plans or private source evidence to Meshmorrow’s server or AI providers. Core scanning requires no account. Optional account-based agent finishing is described separately below; connecting does not automatically upload scans.

Camera permission enables capture. The system photo picker supplies only images you select for local photo work. The app does not request full photo-library, microphone, contacts, location, advertising-identifier or tracking access. The core app and these static pages contain no advertising or third-party analytics SDK.

Local files, backups and sharing

Projects, original models, retained capture photos, recovery drafts, measured layouts and exported files can remain in separate on-device folders. Deleting a saved library asset does not necessarily remove separate capture sources, floor plans, earlier downloads or exports. Use Device storage for the source categories it lists, and Files for other retained documents. Removing source files can remove recovery or reprocessing options. Back up work you want to keep before deleting it.

Device backups, Files, the system share sheet and a destination app or service can copy these documents according to your choices and settings. Exported files may include original geometry, textures, names, collection metadata or measured room details depending on the format. Private room-source bundles are kept local by the core app; inspect any files you choose to share. Meshmorrow cannot remove copies held by recipients or other backup services.

Optional agent finishing — private beta

Asset checks, capture observations, finishing feedback and workflow timing records are stored locally. They are not automatically uploaded, shared for learning or used to train a model. Local history and separate saved assets can remain after you remove a handoff; remove the corresponding records and files when no longer needed. Optional completion notices are requested only when you choose to enable them and follow a job update observed while the app is active; no continuous background monitoring is promised.

Optional connected agent finishing is available in the app to invited testers. You connect your Meshmorrow account to the agent you select through a separate, revocable authorization. You approve a short-lived connection code in the app. Connecting alone does not upload scans or start monitoring. When you explicitly send a prepared scan, the Meshmorrow API receives that model, its embedded textures, name, finishing instructions, source identifiers and checksums. Original capture photographs and depth-source bundles are not included by this workflow.

The connection can access only jobs you assign to it. Your agent can download that job on its computer, run Blender and upload a candidate for your review. Source and result files are removed from active server storage seven days after the job was created, or when you delete that cloud job or account; job metadata and checksums remain until you delete the job or account. Retained database backups follow the backup policy below. Revocation blocks future connector and transfer access. It cannot recall copies already downloaded to an agent computer, conversation, Space, or another recipient. Those services have their own retention and privacy terms.

Private beta account creation requires an invitation; signing in uses a username and password or Sign in with Apple where configured. Account records can include a username, account identifier, salted password hash, session-token hashes and creation/expiry dates. Apple sign-in can store Apple’s user identifier and an encrypted refresh token for revocation. Private native account sessions stay in device Keychain. Separate connector tokens and short-lived transfer grants are stored as hashes on our service. The server stores job status, timestamps and a bounded failure message for recovery; scan contents are not used for model training by Meshmorrow. Blender work takes place on the computer used by your agent, not on the shared Meshmorrow server. Provider API keys are not part of the connection. You review the returned model before saving it separately, and your local original is preserved.

If you explicitly ask a supported agent platform to monitor later jobs for one selected scan, our service stores that selected asset identifier and encrypted callback credentials for the subscription. Signed callbacks contain job, asset and connection identifiers, queue status and a timestamp, not model bytes or names. Subscriptions expire within 24 hours; revocation or account deletion removes their active subscription and pending-event records. Linking alone does not subscribe, upload or browse your library. An event already delivered or a file already downloaded remains subject to the receiving platform’s retention.

Existing online accounts

No account is required for core scanning. The app can read a previously stored username, account identifier and authentication session from this device’s Keychain to show an existing account under More → Existing data & provider keys. Opening that screen does not fetch an online library or upload a scan. If you choose Delete online account, an authenticated request goes to the configured Meshmorrow server to identify and delete that account.

The legacy service can still hold usernames, account identifiers, salted password hashes, session-token hashes, creation/expiry dates and previously uploaded project packages. Earlier Sign in with Apple accounts can also hold Apple’s user identifier and an encrypted refresh token used for authorization revocation. If applicable, deletion first contacts Apple to revoke that authorization; an unsuccessful revocation can require retrying deletion.

Successful account deletion removes active account, session, package, sharing, agent connection, agent job and block records associated with that account. Report account/package identifiers are disconnected, but report text, reasons, content hashes, review status and timestamps can remain. It does not delete local files, provider records, recipient downloads or retained backups. If no valid prior session is available, contact support to request help with account deletion; do not send a password or session token.

Server metadata and retention

The Meshmorrow API and this website are hosted on an isolated Meshmorrow service on a Hostinger VPS. Requests expose ordinary connection information such as an IP address. The API uses source IP addresses and counters in memory to limit abuse; entries are expired during later requests or cleared on process restart. Ordinary HTTPS API access logging is disabled. Operational error codes and server security/error logs can still be retained; the public website can log IP addresses and request information.

The inspected server configuration rotates Nginx logs daily, retaining up to 14 rotated files in addition to an active file; empty files may not rotate. API container logs are size-limited to three files of up to 10 MB each. These settings do not promise deletion after a fixed number of days. The backup task keeps the seven most recent successful daily database backups, so deleted account/package data may remain in retained copies until replaced by successful backups. No fixed worldwide storage-region or off-host deletion guarantee is made here.

Support and older provider keys

Emailing support provides your email address, message and any attachments you choose to send. Send only the information needed for the request. We may need to verify an account-related request and retain information needed to handle support or abuse reports. Contact us to ask about this information; no automatic support-email retention period is claimed.

Provider keys from earlier native builds can be removed through Existing data & provider keys. They are stored in device Keychain; the core scanner does not submit new provider jobs. Removing a key does not delete existing provider inputs, jobs, outputs or accounts. Manage those records with the provider.

Separate beta web studio and earlier optional services

The beta web studio is hosted on Vercel. Imported models and editing work are processed in the browser, with local browser recovery storage where available. Recovery data can persist after closing a page and can also be cleared or evicted by the browser. Download a workspace backup to keep a portable copy. The web studio is separate from the current core iOS workflow; availability can vary.

If you choose the web studio’s private online-library features, authentication and selected project uploads go to the Meshmorrow API. Uploads can include original meshes, textures and other project data. They are separate copies, not automatic synchronization. Web sign-in credentials remain in page memory until sign-out or page closure; browser recovery files are a separate storage mechanism. Earlier sharing codes permit authenticated recipients to download a copy for seven days unless revoked sooner. Revocation does not erase downloaded copies. Reports and blocks retain the data described above.

Older web or native provider features send data only when explicitly submitted: Meshy or Tripo can receive a prompt, selected image or model and task/authentication information; Meshy retexturing can receive a selected rest-pose model, current colour texture and description or reference image. OpenRouter and its chosen model provider receive the submitted request and mesh summary statistics through the optional assistant, rather than the full scan geometry or photo source bundle. ElevenLabs or the independent SunoAPI.org integration can receive an audio/video prompt, voice selection or chosen reference image. Generated media requests and downloads also expose ordinary connection information to the provider and its delivery hosts.

Web keys are held in browser memory and are excluded from workspace downloads. SunoAPI.org can send completion metadata to the Vercel acknowledgement endpoint; that application handler does not log or store the callback body. Hosting infrastructure may retain request metadata. Task IDs, result links and earlier native job history support recovery; removing a key or closing a page does not cancel a provider job or delete its records. Provider processing, storage and charges follow the provider’s own terms and can occur internationally.

Review the relevant provider notice before using an older optional integration: Meshy, Tripo, OpenRouter, ElevenLabs, or the terms/privacy information in your SunoAPI.org account. Hosting providers can process IP addresses and request information for delivery and security.

Subscriptions and purchase verification

The free allowance of two total exports per device per UTC calendar month, shared across 3D models, PNG images and floor-plan documents, is recorded locally in device Keychain and resets by UTC month. It requires no account and creates no server quota collection. Each successfully prepared new file updates this local record. Re-sharing an existing prepared file and failed or cancelled preparation do not use the allowance. Project backups remain unlimited. Pro and existing Creator lifetime owners have unlimited exports, with existing editing and format rights unchanged. No model, image or floor-plan content is uploaded to enforce this allowance.

Optional Meshmorrow Pro subscriptions and older Creator lifetime entitlements are checked on your device through Apple StoreKit. Apple processes purchases, renewal, trial eligibility, restoration and billing; Meshmorrow does not receive payment-card details. No scan or photograph is sent to our server to verify access. Our backend does not store subscription transaction records. Subscription status can change access to new Pro operations; it does not delete local projects or their existing edits.

Use Restore purchases and Manage subscription in the Pro screen. Deleting the app does not cancel an Apple subscription. See subscription help for billing and cancellation, and Apple’s standard Terms of Use.

Your choices

Revoke camera access in iOS Settings. Review local files before using a share sheet, backup or external service.

These static pages set no advertising or analytics cookies. If you believe a child has provided personal information, or need help with local, account or support data, contact us. Material changes to this notice will be reflected with an updated date.