Privacy Policy

Last updated: 2025-12-17

What we process

• Uploaded file contents (only to generate the ProjectMap response).
• Request metadata (e.g., timestamp, response time, status code) for reliability and abuse prevention.

What we do not store

• We do not store your file contents after the request completes.
• We do not log request bodies (file contents) in application logs.
• We do not use your code to train models.

Temporary processing

For JS/TS, extraction runs in-memory. For Python, the system may create a temporary file during extraction and deletes it immediately after returning the response.

Cookies / analytics

Today, FileFig does not require cookies to run the Engine. If analytics are added later, they will be metadata-only (counts, latency) and never raw code. If cookies are introduced, this page will be updated.

Third-party infrastructure

FileFig may run on third-party hosting providers (for example, a web host and an API host). These providers may process standard operational logs needed to run the service.

Contact

Questions? Email luke@lroth.com.

This policy will evolve as paid plans, accounts, and billing are introduced.