Privacy
Privacy Policy.
This Privacy Policy explains what information StatEze collects, how it is used, who it is shared with, and what choices you have. It applies to stateze.com (the marketing site, including the public landing page, the pricing page, and the waitlist form) and app.stateze.com (the StatEze application, available to invited beta participants).
1. Who we are
StatEze is operated by Ali Alsayegh (sole proprietor), based in Canada. References to “we”, “us”, and “StatEze” in this policy mean Ali Alsayegh acting in that capacity. For privacy-related questions, contact: info@stateze.com.
2. Information we collect
2.1 Waitlist form (stateze.com)
When you submit the waitlist form on the /pricing page, we collect the fields you enter (email address, the tier you are interested in, and an optional short note about your use case). The submission is stored so we can contact you when capacity opens or when the tier you selected becomes available.
2.2 Account and authentication data (app.stateze.com)
If you are invited to the beta and sign in, our authentication provider (Supabase) handles your email address and a session identifier. Sign-in supports three paths: (a) a third-party identity provider you choose (Google or Microsoft); (b) email and password; or (c) an emailed sign-in link (“magic link”). When you sign in via an identity provider, StatEze does not see or store your provider password — the provider returns your email address and basic profile metadata to Supabase. When you sign in with email and password, Supabase stores a securely hashed password (we do not see or store the password in plaintext). Sign-in links are single-use tokens delivered to your email.
2.3 Application usage data
While you use the application, we process: datasets you upload, the analyses you run, and the results returned. All statistical computation runs on our servers using established, deterministic statistical libraries (scipy and statsmodels). The full content of an uploaded dataset — the raw, participant-level data rows — is processed server-side to produce results and is never forwarded to any third-party AI or machine-learning service.
The one exception is an optional manuscript-prose polishing layer. When this feature is enabled, only variable names and summary statistics (for example, group means, p-values, and effect sizes already shown in your results) may be sent to Anthropic to refine the wording of the manuscript prose. Raw participant-level data rows are never sent. Data sent for this purpose is not used to train any model. The underlying statistical results are computed deterministically (scipy and statsmodels) and do not depend on this layer; with it disabled, prose is generated from templates and no data leaves our servers for AI processing.
2.4 Error and diagnostic data
We use Sentry to capture errors so we can fix them. Captured automatically:
- Backend (Python): unhandled exceptions and stack traces; the request URL, HTTP method, and response status code (request bodies are not sent); a release tag (the deployed git commit SHA); environment label (“prod”).
- Frontend (browser): unhandled JavaScript errors and stack traces; your authenticated user identity (Supabase user ID and email) attached to error events so we can follow up if needed; release tag; browser, operating system, and locale metadata; IP address.
- Session replay (errors only): If the frontend hits an error, a short session replay is uploaded. All text content is masked, all images and video are blocked, and form input values are not recorded. Captured: DOM structure, click positions, scroll events, route changes, console errors, and request URLs (not request bodies).
Not sent to Sentry under any circumstance: form input text, file contents, dataset rows, analytical results, API request or response bodies, browser localStorage.
2.5 Network and security data
Cloudflare sits in front of stateze.com and handles TLS termination, DDoS protection, and bot mitigation. In doing so, Cloudflare processes your IP address, request metadata, and browser fingerprint signals on our behalf.
2.6 REDCap import (optional)
If you choose to import data from your institutional REDCap server, you supply your REDCap server URL and an API token. The token is held in server memory only for the duration of the import and is never persisted to disk, written to logs, or shared. The records you select are pulled over HTTPS into your StatEze project, where they become a sheet subject to the same retention and deletion rules as any uploaded CSV.
3. How we use your information
- To evaluate beta-access applications and contact you about your application.
- To operate, maintain, secure, and improve the StatEze application.
- To produce statistical results in response to actions you take.
- To diagnose and fix errors, and to detect abuse.
- To comply with legal obligations.
We do not sell your personal information, and we do not use your data to train any general-purpose machine-learning model.
4. Lawful basis
Where applicable law requires a lawful basis (for example PIPEDA in Canada, or analogous frameworks elsewhere), we rely on: your consent (form submission, account creation, optional features); the necessity of processing to perform the service you requested; and our legitimate interests in operating, securing, and improving the service. You may withdraw consent at any time by contacting us; doing so may end your access to the beta.
5. Sub-processors
We rely on the following third-party services to operate StatEze. Each is bound by its own privacy policy and, where applicable, a Data Processing Addendum.
| Sub-processor | Purpose | Data touched |
|---|---|---|
| Modal | Application hosting + persistent storage | Uploaded datasets, analysis artifacts, chart images, server logs, request paths, IP addresses |
| Supabase | Authentication, database, edge functions | User identity, waitlist submissions |
| Google LLC | OAuth identity verification (“Continue with Google”) | Email address and basic profile metadata you consent to share at sign-in |
| Microsoft Corporation | OAuth identity verification (“Continue with Microsoft”) | Email address and basic profile metadata you consent to share at sign-in |
| Cloudflare (CDN) | Asset delivery | IP addresses, request metadata, browser fingerprints |
| Sentry | Error tracking + replay-on-error | See section 2.4 |
| Anthropic | Optional manuscript-prose polishing | Variable names and summary statistics only — never raw participant-level data rows (see section 2.3) |
6. International transfers and data residency
StatEze infrastructure is hosted across multiple regions:
- Modal runs the application backend on shared US-region compute (currently the Modal US-East region) with attached persistent storage (an encrypted
modal.Volume). Datasets and artifacts are stored on that volume until a signout triggers deletion (see section 7). - Supabase projects can be located in
ca-central-1(Montréal) or other regions; the active region is reflected in your account dashboard. - Cloudflare serves traffic from a global anycast network.
- Sentry stores events in the United States or European Union depending on the organization region.
If you are located outside the country in which a sub-processor stores data, your information will be transferred across borders. We rely on contractual safeguards published by each sub-processor (Standard Contractual Clauses, Cloudflare/Supabase/Sentry DPAs, etc.) for such transfers.
7. Retention and in-account storage
- Beta-access applications are retained while the closed-beta program is active so we can review and respond. A formal retention schedule will be published before public launch.
- Uploaded datasets, analysis artifacts, and chart images are stored on Modal’s persistent volume (currently provisioned in the Modal US-East region; see section 5) and remain in your account while it is active. You can delete an individual project, sheet, or analysis from within the application at any time, which removes it instantly. You may also request full account deletion per section 8.4. While you are signed in, datasets persist across visits so you can resume analyses — you do not need to re-upload on every visit.
- Storage medium and isolation. Dataset files live on an encrypted
modal.Volume. Per-user isolation is enforced at the application layer through a row-level ownership check on every API request that touches a project, sheet, or artifact; this is an authorization check, not a filesystem partition. One user’s data is never returned to another user, and files on the volume are accessed only through the authenticated application layer. - Demo project. The built-in Acute Inflammations CSV (a publicly available 99-row UCI teaching dataset) is auto-seeded to every account as a ready-to-explore example and preserved across sign-out so the demo is always available on your next sign-in. Each account has its own independent copy of the demo — no demo data is shared across users.
- Backups. We do not currently maintain automated off-platform backups of uploaded datasets. Durability is whatever Modal’s volume infrastructure provides by default. You can delete any dataset, sheet, project, or analysis from the application at any time, and the deletion takes effect immediately on the volume. If you need long-term retention, export the data yourself.
- Account identifiers (your email address and Supabase user record) are retained until you request account deletion by email. See section 8.4 for how to make that request. Retention beyond a deletion request is limited to what applicable law requires.
- Sentry events and replays follow Sentry’s default retention (currently 90 days for events; replays similarly time-bounded).
- Server logs follow each provider’s default rolling-window retention.
8. Your rights
Depending on where you live, you have rights with respect to your personal information.
8.1 Canada (PIPEDA and provincial equivalents)
You have the right to access the personal information we hold about you, request correction of inaccuracies, withdraw consent (subject to legal or contractual restrictions), and lodge a complaint with the Office of the Privacy Commissioner of Canada or your provincial regulator.
8.2 United States
If you are a resident of California, Colorado, Connecticut, Virginia, Utah, Texas, Oregon, or another U.S. state with a comprehensive privacy law, you may have rights to know, access, correct, delete, and obtain a portable copy of your personal information; to opt out of “sale” or “sharing” (we do not sell or share for cross-context behavioural advertising); to limit the use of sensitive personal information; and to be free from retaliation for exercising any of these rights.
StatEze does not knowingly process personal information of California residents under 16. We do not engage in profiling that produces legal or similarly significant effects.
8.3 Elsewhere
If you are located in the EEA, the United Kingdom, or another jurisdiction with applicable privacy law, you may have analogous rights under that law.
8.4 How to exercise your rights
Email info@stateze.com with a description of your request. We will respond within the timelines required by applicable law (generally 30 days, extendable where the law permits). We may need to verify your identity before acting on a request.
9. Security
Access to production systems is restricted to the operator. Authentication uses HTTPS in transit, password hashing at rest (Supabase), and credential rotation. The application backend gates every request under /api/ with a Supabase-issued JWT bearer token, verified server-side on every call. No system is perfectly secure; if you become aware of a vulnerability, please contact info@stateze.com.
10. Cookies and similar technologies
The marketing site does not use analytics or advertising cookies. Cloudflare may set short-lived cookies for bot mitigation. The application uses session storage to maintain your sign-in state.
11. Children
StatEze is not directed at, and is not intended for use by, anyone under 16. We do not knowingly collect personal information from children.
12. Changes to this policy
We may update this policy as the service evolves. Material changes will be reflected in the “Last updated” date below; substantive changes affecting your rights will be communicated by email to active beta participants.
13. Contact
Privacy questions, rights requests, complaints: info@stateze.com.
Last updated: 2026-05-20.