Security & Data Handling
Your schedule is the product of your judgment. It stays yours.
Schedule Intel runs two different architectures, and we explain both honestly — including exactly what each one transmits, processes, and retains.
The free tools: your file never leaves your computer
The Single-File Health Check and the Two-File Lite Comparison run entirely in your browser. The comparison engine is JavaScript delivered to your machine; your XER file is read and analyzed locally, in your browser's memory.
No network request contains the XER file, the filename, or any schedule contents. When you run a comparison, the application sends one anonymous usage counter whose entire application-defined body is:
{ "tool": "two-file" }As with any web page, requests also carry ordinary HTTP and infrastructure metadata — IP address, browser user-agent, and similar — handled by our hosting provider under its privacy terms. None of it includes your schedule.
1 · The offline test
Load the tool, then disconnect from the internet. Run a full comparison. It works — your schedule never needed to go anywhere.
2 · The network test
Open DevTools → Network and run a comparison. Inspect every request yourself: none contains your file or its contents.
Your IT team is welcome to audit the page — all code that touches your file runs on your machine, where they can see it.
The Pro app: transient processing, no intentional persistence
The Pro engine performs deeper analysis than a browser can, so it runs server-side. Here is the data path for an uploaded XER file, described precisely:
- Your file travels encrypted in transit (TLS) to the app.
- During parsing it is held in backend memory, and a temporary file exists for the duration of the parse. Cleanup of that file is programmatic and runs even when parsing fails. (We verify this behavior with automated tests; like any software, we do not claim guaranteed instant deletion in the event of a process crash — the hosting platform recycles containers and their temporary storage.)
- Comparison results are held in memory for your session while you work. A small bounded cache of recently parsed schedules makes re-runs fast; it is RAM-only, scoped to your session, and cleared when your session ends or you sign out — schedule data is never shared across sessions or users. (Verified by automated isolation tests, including concurrent sessions.)
- Excel and PDF reports are generated in memory when you click the button and streamed to your download — not written to durable storage.
Our policy and our architecture:schedule content is processed transiently and is never intentionally persisted to our application database or object storage. There is no "delete my schedule" button because there is no schedule store behind the app.
What we DO store durably (and it isn't your schedule)
| Data | Where | Why | Retention |
|---|---|---|---|
| Email + name (Google sign-in) | Supabase (account DB) | Your Pro account | Until you ask us to delete it |
| Trial usage counter | Supabase | Enforce the trial | Same |
| Subscription status | Stripe | Billing | Per Stripe's terms |
| Anonymous tool-run tally | Analytics | Aggregate usage counts | No identity attached |
| Your XER files / schedule content | No application database or object storage | — | Transient processing only |
Third-party services, stated honestly
- Streamlit Community Cloud, a service provided by Snowflake Inc., hosts the Pro app. When you upload a schedule to Pro, that upload is received and processed on that infrastructure on our behalf, subject to Snowflake Inc.'s security and privacy terms. This is inherent to any hosted analysis tool.
- Vercel hosts the website and its anonymous analytics. For the free browser tools, your schedule is not sent to Vercel or to us — the analysis happens on your machine.
- Google provides sign-in (we never see your password). Stripe processes payments (we never see your card number). Supabase stores account records. None of these three receive schedule data.
For enterprise
- Source audit under NDA. The entire Pro data path is a small amount of code. Serious security reviews are welcome.
- Private deployment may be available for qualified enterprise customers whose policies require schedule data to remain inside their own network. Contact us to discuss.
Questions: hello@scheduleintel.com
Last verified against shipped code: August 2026.