Privacy Policy

Last updated 2026-05-05

HuggingArch is an open-source architecture analyzer and inference planner for HuggingFace transformer models. This page describes what data the service collects, why, and how to remove it.

What we collect

When you use the site without signing in:

• The model id you analyze, the endpoint you hit (/analyze, /inference/estimate), and how long the request took. No user identifier is attached. Used for site-wide popularity and latency analytics.
• Your IP address and User-Agent header, only as transient input to the rate limiter. Not stored.

When you sign in (email/password, GitHub, or Google):

• Profile: username, full name, bio, avatar URL — all editable from the profile page. Synced from your OAuth provider on first sign-in.
• Login history: IP address and User-Agent on each session creation. Used for active-user analytics; visible only to administrators of this deployment.
• Per-call activity: the same analyze events as above, but tagged with your account id. Used for per-user usage and admin analytics.

Where it lives

All user data lives in a Supabase Postgres database controlled by the operator of this deployment. Authentication is handled by Supabase Auth. We do not sell, share, or transfer your data to third parties.

Third-party providers

• Supabase — auth + database hosting. supabase.com/privacy
• Fly.io — application hosting. fly.io/legal/privacy-policy
• HuggingFace — public model metadata fetched on every analyze request (no PII sent). huggingface.co/privacy
• GitHub / Google — only when you choose to sign in via OAuth. Each provider has its own privacy policy.

How to delete your data

Email the operator of this deployment to request deletion of your profile, login history, and account. Past anonymous usage events are retained but cannot be linked back to you once your user id is removed (analyze logs cascade to user_id = NULL).

Cookies

The site uses one cookie set by Supabase Auth to keep you signed in across page loads. No analytics or advertising cookies are used.

Changes to this policy

Material changes will be reflected by an update to the date at the top of this page. The current version is always available at https://www.huggingarch.com/privacy.

Source code

HuggingArch is open source under the Apache 2.0 license. The exact data flow described above can be audited at github.com/shenh10/HuggingArch.