Privacy Policy — turboIFC Quantifier

Your IFC stays local

turboIFC Quantifier reads the file you select inside your browser. The application does not upload your IFC file, filename, BIM identifiers, model contents, quantities, materials, project identity or export snapshot to turboIFC or its payment backend. Browser workers are local processing, not an upload. Model and workspace state are not stored by the application between page sessions.

Minimum commerce information

When you request checkout or verify a payment, the application sends an opaque random export-session identifier. The commerce service keeps the provider transaction ID, payment/revocation status, USD amount and currency, timestamps and event identifiers needed for idempotency. It does not keep model information. A signed export permission is issued to the browser from this state.

Providers and operational data

Paddle processes checkout and payment information as Merchant of Record, under its Privacy Policy. Payment information entered in Paddle checkout is not BIM content. Cloudflare serves application assets and the commerce service. Infrastructure providers may process IP addresses and other network information needed to deliver and secure requests.

Production monitoring is limited to fixed operational route categories, response status and aggregate commerce records. Application logs must not contain request bodies, filenames, model hashes or BIM contents. turboIFC does not intentionally store raw IP addresses at application-log level. This does not prevent infrastructure providers from processing network information as described above.

The application has no third-party behavioral analytics, marketing tracking, account requirement or model-storage service. The enclosing website and a separately opened consultancy website may have their own policies.

Retention and requests

Minimal commerce records are retained for as long as needed to administer payments, refunds and disputes, prevent duplicate processing or incorrect reactivation of export permissions, and meet applicable legal and accounting obligations. Retention is based on these purposes rather than a fixed quarterly review or 90-day deletion schedule.

Application operational logs are normally retained for up to 30 days.

Paddle controls its own retention under its policy. Closing the browser clears the local session but does not delete a payment record already held by the commerce service or Paddle.

Contact

Ingeniería + Sustentabilidad SpA is the commercial supplier and authorized commercial licensee. For product privacy questions, contact contact@turboifc.com. Contact Paddle directly for requests concerning information it processes as Merchant of Record. Avoid including confidential model data.

Juan Beaumont retains ownership of the turboIFC brand and proprietary software.