What we store
- Your jobs. The specs you submit, the files you upload, compiled outputs, reports, preview images and preview MP4s are stored in Cloudflare R2. They are served from our API at api.spatialcompiler.dev.
- Your account. Your email, display name, organization membership, sessions and API key records are stored in Cloudflare D1 and related Cloudflare services used by the console at console.appliedmanifold.com.
- Payments. Stripe handles payments. We do not store full payment card numbers. We may store Stripe identifiers, payment status, subscription status, refunds, and the last four digits and brand of a saved card.
- Site analytics. Cloudflare Web Analytics counts page views on this website and sets no cookies.
- The ask box. If you type a question into the site's ask box, the question is sent to OpenAI to write an answer from our published pages. OpenAI is not used for your compile jobs.
How long we keep it
Job files, including preview videos, are kept for 90 days after they are created. After that we delete them. There is no per-account storage cap.
To keep files after those 90 days, turn on Keep job files longer in billing. That costs $0.10 per GB each month, billed on the files older than 90 days. If you turn it off, each file already stored is kept for 90 days from the day you turned it off, and new files follow the usual 90 days from when they are created.
Preview links
A preview link is a signed, unlisted URL. It works for 30 days from the end of the UTC day it was created. During that time, anyone with the link can view the preview and read the spec.
When a link expires, it stops working. Expiry does not delete the file. Ask for the job again to get a fresh link while the file is still kept (90 days after it was created, or longer with Keep job files longer).
Who can see it
- Members of your organization can see the organization's jobs, keys and billing in the console.
- Anyone with a valid preview link can watch that preview and read that spec, without signing in.
- Staff admin routes on the console (
console.appliedmanifold.com/admin) are behind Cloudflare Access.
API keys
You see the full key once, when you create it. We store a SHA-256 hash of the key, plus its mode (test or live), prefix, last four characters and scopes. We do not store the secret in plain text.
Keys are scoped, with compile and read by default. You can revoke a key at any time, and a revoked key stops working. See API keys for how to create and use them.
Sign-in and access
You sign in with a link sent to your email, or with GitHub or Google when those options are offered. We do not store passwords. We do not store GitHub or Google access tokens.
Staff admin access to the console is behind Cloudflare Access.
Encryption
Traffic to our services uses HTTPS. Job files and account data live on Cloudflare R2, D1 and KV, which Cloudflare encrypts at rest.
Subprocessors
These companies process data for us to run the service.
| Who | What for |
|---|---|
| Cloudflare, Inc. | Hosting, storage, email (Cloudflare Email Service), analytics, and staff admin access. |
| RunPod, Inc. | Compute for compilation jobs. Your inputs are sent there to produce outputs, and the outputs are stored in our Cloudflare storage. |
| Stripe, Inc. | Payments. |
| GitHub and Google | Sign-in, only if you choose those options. |
| OpenAI, LLC | The website's ask box only. |
Policies
Our Privacy Policy and Terms of Service are drafts and are not in force. Service checks are on the status page.