Privacy Policy

1. What we collect

ModelForgeLab is designed to collect as little data as possible. Registration flows are simulated client-side: no email address, password, or personal identifier is written to any database or log. Adapter and dataset files uploaded through the UI are received into memory and discarded — nothing is persisted to disk.

Standard HTTP server logs (request path, response code, timestamp) may be written by the reverse proxy in front of this service. These logs do not contain account credentials or uploaded content and are rotated within 24 hours.

2. What we do not collect

We do not store email addresses, passwords, IP address histories, or user-identifiable session data. We do not use tracking pixels, third-party analytics scripts, or advertising networks. We do not sell or share any data with third parties.

3. How we use your data

Because no personal data is retained, there is nothing to use beyond serving the current request. The multi-step authentication cookie (mfl_flow) contains only an attempt counter signed with a server key — it carries no PII and expires when you close your browser.

4. Data retention

No user data is retained beyond the lifetime of a single HTTP request. There is nothing to delete. If you have questions, write to support@modelforgelab.cloud.

5. Security

All traffic is encrypted via TLS. The session cookie is signed with HMAC-SHA1 and is not readable or forgeable by the client. No credentials are stored anywhere on this service.

6. Cookies

We set one cookie: mfl_flow, used only to track the step count in a multi-step form. It contains no personal information and is not shared with any third party.

7. Contact

For privacy inquiries write to support@modelforgelab.cloud.