Privacy Policy

• Files you analyze in the browser are processed and then deleted immediately — they are not retained.
• Files you submit to a longer optimize job are stored only to run the job and return your result, behind time-limited signed links, and are automatically deleted within 7 days.
• We store your account email and, if you subscribe, your Stripe customer reference — never your card number.
• Usage telemetry records what was optimized; the client IP address is hashed before storage, never kept raw.

When you use the in-browser analyzer, your file is written to a temporary working directory on the server, analyzed, and the working directory is deleted immediately when the request finishes — whether it succeeds or fails. We do not retain files processed through the synchronous analyzer.

When you submit a file to a longer-running optimize or bundling job, the uploaded file and the optimized result are stored by our file store (our cloud blob storage in production) so the job can run and you can download the result. Those files are served only through cryptographically signed, time-limited links (each link expires about an hour after it is issued), so a file is not publicly browsable. We treat these stored job artifacts as transient working data and do not use them for any purpose other than delivering your result.

Stored job artifacts are automatically deleted within 7 days. A scheduled cleanup job runs daily and permanently removes the uploaded file, the optimized result, and the job’s record once it is older than the retention window; nothing is kept beyond that point. You can also request earlier deletion of your stored job artifacts at any time by emailing support@spatialpack.dev.

Uploads are capped at 25 MB; larger assets are intended to be processed locally with the SpatialPack CLI, in which case your files never leave your machine.

If you create an account, we use Google sign-in or an emailed magic link (via Resend). We store your email address and the account/session records needed to keep you signed in, along with your plan tier. We use this to authenticate you, enforce quotas, and contact you about your account.

Payments are processed by Stripe. We do not collect, see, or store your full card number or other sensitive payment details — Stripe handles those directly. We store a Stripe customer reference (customer id) and subscription status so we can apply your plan and let you manage billing. Stripe’s handling of your payment data is governed by Stripe’s own privacy policy.

When the Service performs a billable operation (such as serving an optimized download, or a CLI / MCP optimize), we record a usage event so we can enforce quotas and understand aggregate usage. Each event includes the account, the job, the preset and output size, the source (web, CLI, or MCP), the operation name, and a timestamp.

We also record a hash of the originating IP address. The IP address is not stored in raw form: it is combined with a daily rotating salt and run through a one-way SHA-256 hash before storage, so the stored value cannot be trivially reversed back to your IP and changes each day. We use this only for abuse prevention and rough deduplication, not to identify or track individuals.

We use strictly necessary cookies to keep you signed in and to enforce anonymous free-tier limits (a download-count cookie). We do not use third-party advertising cookies.

We rely on the following providers to operate the Service:

• Stripe — payment processing and subscription billing.
• Google and Resend — authentication (OAuth sign-in and magic-link email).
• Our hosting and cloud blob storage providers — running the application and temporarily storing job artifacts.
• Our database provider — storing accounts, plan state, and usage events.

The operator should confirm and name each provider here before launch.

Synchronous analyzer uploads are deleted immediately after processing. Stored job artifacts (uploaded files, optimized results, and the job record) are automatically deleted within 7 days by a daily scheduled cleanup job — see Section 2. Account records persist while your account is active; usage events persist for quota accounting and aggregate analytics. We retain data only as long as needed for the purposes described here or as required by law.

We use industry-standard measures to protect data in transit and at rest, restrict file access to signed, expiring links, hash IP addresses before storage, and never store raw card data. No method of transmission or storage is perfectly secure, but we work to protect your information.

Depending on where you live, you may have rights to access, correct, export, or delete your personal data, and to object to or restrict certain processing. To exercise these rights — including deleting your account or any stored job artifacts — email support@spatialpack.dev. We will respond as required by applicable law.

The Service is not directed to children under 16, and we do not knowingly collect personal data from them. If you believe a child has provided us personal data, contact us and we will delete it.

We and our service providers may process and store data in countries other than where you live. Where required, we use appropriate safeguards for such transfers.

We may update this Privacy Policy from time to time. When we do, we will revise the “last updated” date and, for material changes, provide additional notice where appropriate.

For privacy questions or requests, email support@spatialpack.dev. This policy is provided by Michael Montalbano.